Azure AI model availability in the jioindiacentral region (Asia) has regressed for all monitored OpenAI models. The following SKUs—ada.1, babbage.1, curie.1, davinci.1, and gpt-4o-audio-preview.2024-12-17—are now absent from the regional catalog after 55 days of uninterrupted presence, marking a recurring regression but with no prior disappearances. Coverage for these features in jioindiacentral is now 0/63 (0%), down from 1.6%, and there are no fallback regions currently available.
This is a clean sweep: deprecated coverage stands at 100%, and the entire Asia region group has lost access to these OpenAI models for now. Operationally, this means SREs, platform engineers, and architects must review model deployment targets and consider alternative model/version choices for latency, data residency, and failover.
For teams relying on Azure AI in jioindiacentral, this sudden loss impacts placement flexibility and may force workload migration or re-architecture. There is no regional fallback, so latency and residency requirements may be compromised until coverage is restored or alternative models become available.
For more context on model capabilities and deployment options, see the Azure documentation: https://learn.microsoft.com/azure/ai-foundry/openai/concepts/models.
AKS Extension Rollout Across Oceania and Beyond
Meanwhile, AKS cluster extensions have seen a major regional expansion. Multiple extension types—including corepatchmanager, thecorecompliance, thecorefull, thecorekubernetescompliance, thecorepatching, dcassociatesgroup.keycloak, and dcassociatesgroup.opensearch—are now available in australiacentral, australiacentral2, australiaeast, australiasoutheast, and other regions. This is the first observed presence in Oceania and, for some features, the first anywhere in monitored regions.
Coverage for these AKS extensions has jumped from 27% to 92.1% across monitored regions, opening up new managed cluster capabilities such as GitOps, policy, and observability. This rollout enables improved lifecycle management and operational flexibility for AKS workloads, especially for teams seeking compliance or enhanced automation.
For details on AKS cluster extensions and their capabilities, refer to: https://learn.microsoft.com/azure/aks/cluster-extensions.