# Regional Standard Azure OpenAI Deployments Without a Data Residency Requirement Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/regional-standard-azure-openai-deployments-without-a-data-residency-requirement Azure OpenAI models in Microsoft Foundry (formerly Azure AI services) can be deployed as Global, Data Zone or regional (Standard) pay-per-token... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Azure OpenAI models in Microsoft Foundry (formerly Azure AI services) can be deployed as Global, Data Zone or regional (Standard) pay-per-token deployments. PointFive Research Cloud cost research at PointFive Azure service [Azure Cognitive Services](https://www.pointfive.co/efficiency-hub/cloud-services/azure-cognitive-services) Category [AI](https://www.pointfive.co/efficiency-hub/service-category/ai) Reference CER-0510 Type Suboptimal Pricing Model ## Explanation Why the waste happens and who it affects. The types differ in where prompts and responses are processed: Global may use any Azure region, Data Zone stays within the US, EU or APAC data zone, and Standard stays within the chosen Azure geography. Data at rest stays in the resource's geography for all of them. Microsoft's guidance is to start with Global Standard, which it describes as having the lowest price, the broadest region coverage and the earliest access to new models, and to move to another type only for a specific reason such as data residency. Deployments created from older templates, or by teams that assume regional processing is required, often use regional Standard or Data Zone Standard without a documented residency requirement. On the Azure OpenAI pricing page (East US, USD, checked September 2026) the Data Zone and Regional per-token rates for the GPT-4.1 family are 10% higher than Global (GPT-4.1 input $2.20 vs $2 per 1M tokens), Data Zone rates for GPT-5 and GPT-5.4 carry a similar premium, and regional rows show no Batch or Priority processing option. Where no residency obligation exists, the premium buys nothing. ## Billing model The pricing dimensions that drive this cost. Standard deployment types are billed per million input, cached input and output tokens, at a rate that depends on the deployment type. Global Standard SKU GlobalStandard, pay-per-token, may process in any Azure region, lowest listed per-token price Data Zone Standard SKU DataZoneStandard, processing kept within the US, EU or APAC data zone, priced above Global Standard (regional) SKU Standard, processing kept within the Azure geography, priced above Global and with fewer models and lower quota Data at rest Stays in the designated Azure geography for every deployment type ## How to detect 4 checks to find it in your estate. - List deployments and their sku.name for every Azure OpenAI or Foundry resource (for example with az cognitiveservices account deployment list) and flag Standard and DataZoneStandard deployments - For each flagged deployment, confirm with the owner whether a documented data residency, sovereignty or contractual requirement exists; deployments without one are candidates - Compare the per-token rates for the same model and deployment type on the Azure OpenAI pricing page for the resource's region, and multiply the difference by the deployment's monthly token volume from Azure Monitor metrics or Cost analysis - Check whether regional deployments are blocking use of Batch or Priority processing, which the pricing page lists only for Global and Data Zone types ## How to fix 5 ways to remove the waste. - Create a Global Standard deployment of the same model and version, move traffic to it by updating the deployment name used by clients, then delete the old regional deployment - Where only zone-level residency is required, use Data Zone Standard rather than a regional deployment so the workload can also use Data Zone Batch and Priority processing - Keep regional Standard only for workloads with a documented geography requirement, and record the reason on the deployment or resource tags - Use the Azure Policy definition documented for Foundry deployment types to restrict which sku.name values can be created in subscriptions that have no residency requirement - Before switching, check quota for the target deployment type and model and review the high availability guidance, since Global and Data Zone deployments are tied to a primary region ## Documentation Vendor references for pricing and configuration. - [Understanding deployment types in Microsoft Foundry Models learn.microsoft.com](https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/deployment-types) - [Azure OpenAI pricing azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/cognitive-services/openai-service/) - [Plan and Manage Costs - Microsoft Foundry learn.microsoft.com](https://learn.microsoft.com/en-us/azure/foundry/concepts/manage-costs) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Cognitive Services CER-0248 ### [Non-Production Azure OpenAI Deployments Using PTUs Instead of PAYG](https://www.pointfive.co/efficiency-hub/inefficiencies/non-production-azure-openai-deployments-using-ptus-instead-of-payg-9fe81) Development, testing, QA, and sandbox environments rarely have the steady, predictable traffic patterns needed to justify PTU deployments. These workloads often run intermittently, with lower throughput and shorter usage windows. When PTUs... AI - Azure Cognitive Services CER-0246 ### [Missing Reserved PTUs for Steady-State Azure OpenAI Workloads](https://www.pointfive.co/efficiency-hub/inefficiencies/missing-reserved-ptus-for-steady-state-azure-openai-workloads-f78d4) Many production Azure OpenAI workloads - such as chatbots, inference services, and retrieval-augmented generation (RAG) pipelines-use PTUs consistently throughout the day. When usage stabilizes after initial experimentation, continuing to... AI - Azure Cognitive Services CER-0511 ### [Missing Commitment Tier for High-Volume Foundry Tools (Azure AI Services)](https://www.pointfive.co/efficiency-hub/inefficiencies/missing-commitment-tier-for-high-volume-foundry-tools-azure-ai-services) Foundry Tools (formerly Azure AI services and Cognitive Services) such as Speech, Translator, Azure Language, Vision OCR and Document Intelligence bill per unit of usage on the default Standard pricing: per audio hour, per million... AI --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.