Tenant Structure#
Caascad Azure structure is composed of multiple tenants that serve different purposes:
- A staging tenant (ocbdevcaascad.onmicrosoft.com) hosting staging cloud zones
- A subscription named
caascad_staging - One resource group per cloud zone that will hold the resources
- A subscription named
- A staging tenant for customers (ocbcustomercaascad.onmicrosoft.com) that will be used to deploy staging client zones
- A subscription named
caascad_staging_customer - One resource group per client zone that will hold the resources
- A subscription named
- A production tenant (ocbprodcaascad.onmicrosoft.com) hosting production cloud zones
- A subscription named
caascad_prod - One resource group per cloud zone that will hold the resources
- A subscription named
- Finally, we will have client tenants for production client zones. The Azure structure will differ depending on the client's existing infrastructure.
- By default we will consider that a dedicated subscription for Caascad will be created and the zone will be deployed on a resourcegroup inside this subscription
- It is also possible that, at the client's demand, the zone will be deployed on an existing subscription/resourcegroup
