Share via

Where does my data processed in Standard Type deployment in Azure OpenAI models?

Pritish Mohan 40 Reputation points
2025-10-06T07:13:04.3733333+00:00

Hi,

This query is regarding deployment types in Azure AI models.
Regarding Standard Deployment type-

Documentation here mentions that Standard deployments provide a pay-per-call billing model on the chosen model. This model can be a fast way to get started, because you pay only for what you consume. Models available in each region and throughput might be limited.

*Standard deployments are optimized for low-to-medium volume workloads with high burstiness. Customers with high consistent volume might experience greater latency variability.
*
Further when we deploy models Standard Definition comes as follows -

User's image

Question _ Where does my data processed in Standard Type deployment ? For Example- If my resource location is India, will data processing will also take place within India ? It is amply clear that data at rest is within geographic region. Clarity is need for data in transit, input, output and processed.

Regards**

Foundry Tools
Foundry Tools

Formerly known as Azure AI Services or Azure Cognitive Services is a unified collection of prebuilt AI capabilities within the Microsoft Foundry platform

0 comments No comments

Answer accepted by question author

Adharsh Santhanam 8,225 Reputation points Microsoft Employee Volunteer Moderator
2025-10-06T10:21:39.58+00:00

Hello Pritish Mohan, according to Azure’s data residency policies, Microsoft may replicate data to other regions for resiliency (such as for backup and disaster recovery purposes), but Microsoft will NOT store or process customers data outside the selected region for normal operations. So, in your case, it'll remain within India. See https://azure.microsoft.com/en-us/explore/global-infrastructure/data-residency/#overview

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Was this answer helpful?

1 person found this answer helpful.

Answer accepted by question author

Manas Mohanty 16,840 Reputation points Microsoft External Staff Moderator
2025-10-06T16:45:08.32+00:00

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.

Was this answer helpful?

0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.