Skip to content
Home » Deploying Dynamics Production to an Azure Geography

Deploying Dynamics Production to an Azure Geography


An Azure geography is a discrete market, typically containing at least one or more regions, that preserves data residency and compliance boundaries. Geographies allow customers with specific data-residency and compliance needs to keep their data and applications close. Geographies are fault-tolerant to withstand complete region failure through their connection to the dedicated high-capacity networking infrastructure of Azure.

Azure Geographies can be split up into 4 main geographies.

  • Americas
  • Asia Pacific
  • Europe
  • Middle East and Africa

Within each of these main geographies are the countries within the main Azure geography that Dynamics can be deployed to.

Geographical Availability

Production environment – One production instance is provided per tenant. The production multi-box instance includes disaster recovery and high availability. It will be provisioned when the implementation approaches the Operate phase, after the required activities in the Microsoft Dynamics Lifecycle Services (LCS) methodology and a successful go-live assessment are completed. Additionally, some file storage and database storage are included in the offer:

  • File storage: Every customer receives a certain amount of file/Azure blob cloud storage for files and binary data. Additional file/blob storage can be purchased.
  • Database storage: Every subscription includes a certain amount of Azure SQL Database storage per customer at no additional charge. Additional storage capacity is provided at no charge as an organization increases the number of user and device service licenses. 

Deployment Best Practices

Any additional Sandbox/UAT (Tier 2+) environments and any additional Demo/Development/Build instances should be deployed to the same Azure Geography and Region.

Useful Links

Additional information relating to Azure Geography can be found here:

Global Infrastructure | Microsoft Azure