Hi Pritish Mohan
In Microsoft Azure terminology, a Geo refers to a geographical region grouping defined by Microsoft for data residency and compliance purposes. Examples of Geos include:
- United States
- European Union
- Asia Pacific
- United Kingdom
- Brazil
Each Geo contains one or more Azure regions (e.g., West US, East US, North Europe, West Europe). When you create an Azure resource, you select a region, and that region belongs to a specific Geo.
Is it the location of the AI Foundry resource?
Yes, in the context of Azure OpenAI deployments, the customer-specified Geo is determined by the Azure region where your resource (e.g., AI Foundry or Azure OpenAI resource) is provisioned. For example:
- If you create your Azure OpenAI resource in Sweden Central, your Geo is European Union.
- If you create it in East US, your Geo is United States.
Why does this matter?
- Data at Rest: Microsoft guarantees that your data at rest stays within the Geo of your resource.
- Data Redundancy: Microsoft may replicate data between regions within the same Geo for durability (e.g., East US ↔ West US).
Processing: For Standard deployments:
- Global Standard: Processing may occur outside your Geo.
- Data Zone Standard / Azure Geography Standard: Processing stays within your Geo or data zone
Reference:
https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/deployment-types
https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/openai/data-privacy?tabs=azure-portal
https://learn.microsoft.com/en-us/azure/ai-foundry/openai/encrypt-data-at-rest
Thank you.