Global Standard vs Data Zone Standard vs Global Batch vs Global Provisioned vs Data Zone Provisioned
Verdict: No residency need and lowest price: Global Standard. Prompts and responses must stay in a zone such as the EU: Data Zone Standard. Large asynchronous jobs: Global Batch. Predictable, low-variance throughput bought as PTUs: Global Provisioned or Data Zone Provisioned.
| Criterion | Global Standard | Data Zone Standard | Global Batch | Global Provisioned | Data Zone Provisioned |
|---|---|---|---|---|---|
| Billing | Pay-per-token, no reserved capacity | Pay-per-token, no reserved capacity | Discounted asynchronous processing | Fixed number of purchased provisioned throughput units | Fixed number of purchased PTUs |
| Data residency | May route processing to any Azure region | Processes prompts and responses only inside the specified data zone, e.g. the EU | May route globally | Reserves capacity across any Azure region | Reserves capacity while keeping traffic inside the specified data zone |
| Region coverage and price | Broadest region coverage, lowest price; launches first for new models | Narrower than Global Standard; no price advantage | Any Azure region; 50% less cost than Global Standard, 24-hour target turnaround | N/A - reserved-capacity pricing | N/A - reserved-capacity pricing |
| Choose when | No residency requirement, general low-latency workload | A regulatory requirement keeps processing inside one zone | Large volume with no immediate deadline | Heavy, consistent traffic needs predictable throughput with no residency requirement | Heavy, consistent traffic needs predictable throughput inside one data zone |
Rules
- Data Zone Standard deployments process prompts and responses only within a Microsoft-specified data zone such as the EU, while still billing pay-per-token, fitting variable, low-volume traffic without reserving capacity.
- Global Standard launches first for new models, offers the lowest price and the broadest region coverage, making it the default when no residency or throughput commitment is required.
- Data Zone Standard keeps prompt and response processing inside a specified zone such as the EU, satisfying a residency requirement while still billing per token.
- Global Provisioned and Data Zone Provisioned both require purchasing a fixed number of provisioned throughput units that guarantee reserved processing capacity; Global Provisioned spans any Azure region while Data Zone Provisioned keeps traffic inside the specified data zone.
Traps
- Global Batch is for large asynchronous jobs, not a live interactive workload - it is not a fit merely because it is cheap or global.
- Developer deployments carry no data residency guarantee at all and no SLA; they are a temporary evaluation environment, not a production or compliance choice.
- Global Standard is pay-per-token with no reserved throughput commitment, so it does not use PTUs even though it is the default deployment type.