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.

CriterionGlobal StandardData Zone StandardGlobal BatchGlobal ProvisionedData Zone Provisioned
BillingPay-per-token, no reserved capacityPay-per-token, no reserved capacityDiscounted asynchronous processingFixed number of purchased provisioned throughput unitsFixed number of purchased PTUs
Data residencyMay route processing to any Azure regionProcesses prompts and responses only inside the specified data zone, e.g. the EUMay route globallyReserves capacity across any Azure regionReserves capacity while keeping traffic inside the specified data zone
Region coverage and priceBroadest region coverage, lowest price; launches first for new modelsNarrower than Global Standard; no price advantageAny Azure region; 50% less cost than Global Standard, 24-hour target turnaroundN/A - reserved-capacity pricingN/A - reserved-capacity pricing
Choose whenNo residency requirement, general low-latency workloadA regulatory requirement keeps processing inside one zoneLarge volume with no immediate deadlineHeavy, consistent traffic needs predictable throughput with no residency requirementHeavy, consistent traffic needs predictable throughput inside one data zone

Rules

Traps