Repository navigation
Add support for the Delos (Germany) & GovSG (Singapore ) sovereign clouds #34129
Description
Activity
Thank you for opening this issue, we will look into it.
Reacted by Ohad Schneider- changed the title
[-]Add support for Delos & GovSG[/-][+]Add support for the Delos (Germany) & GovSG (Singapore ) sovereign clouds[/+]on Sep 24, 2026 Hi Ohad Schneider (@ohadschn), thanks! The
az cloud setrequest, both cloud names, and SDK-readiness confirmation are clear. This is a feature request, not a reproduced bug.To assess implementation readiness, could you provide these missing details?
- Publicly shareable, authoritative configuration or metadata for each cloud: supported endpoints, suffixes, and resource/audience IDs, with unsupported entries identified.
- Supported availability/access prerequisites and a minimal acceptance example for each cloud: CLI version, validation commands, and expected results. A failure log is not required.
Template (repeat for each cloud):
Cloud: AzureDelosCloud / AzureGovSgCloud Authoritative configuration: <public reference or configuration> Availability/prerequisites: <non-sensitive details> CLI version: <version> Validation commands: <cloud selection and a supported operation> Expected results: <sanitized results>Please omit credentials and private tenant/subscription or infrastructure details. This issue will be picked up automatically once you reply with the details.
Hi Ohad Schneider (@ohadschn), thanks! The
az cloud setrequest, both cloud names, and SDK-readiness confirmation are clear. This is a feature request, not a reproduced bug.To assess implementation readiness, could you provide these missing details?
- Publicly shareable, authoritative configuration or metadata for each cloud: supported endpoints, suffixes, and resource/audience IDs, with unsupported entries identified.[ ] Supported availability/access prerequisites and a minimal acceptance example for each cloud: CLI version, validation commands, and expected results. A failure log is not required.
Template (repeat for each cloud):
Cloud: AzureDelosCloud / AzureGovSgCloud Authoritative configuration: <public reference or configuration> Availability/prerequisites: <non-sensitive details> CLI version: <version> Validation commands: <cloud selection and a supported operation> Expected results: <sanitized results>Please omit credentials and private tenant/subscription or infrastructure details. This issue will be picked up automatically once you reply with the details.
Yong Zhang (@yonzhan) Surely you don't need me to provide this info? Whatever process you used to get the details for the existing Bleu cloud, do the same for Delos and GovSG...
Hi Ohad Schneider (@ohadschn), understood: this is cloud onboarding, not a bug reproducer. The
az cloud setcommand, both requested cloud names, desired endpoint/suffix/audience coverage, and SDK readiness are clear. Your reply identifies Bleu as the precedent.I checked the current cloud definitions: Bleu has explicit configuration, but neither requested cloud is defined there. Its structure alone cannot establish their cloud-specific values.
The remaining input can come from maintainers/cloud owners; you do not need to compile the values yourself:
- For each cloud, provide an authoritative, publicly shareable configuration/metadata source covering endpoints, suffixes and resource/audience IDs, with unavailable services and access prerequisites identified.
A short reply is sufficient:
Cloud: Authoritative public configuration: Unavailable services / access prerequisites:No failure logs, CLI version, or repeat description are needed for this feature request. This will be picked up automatically once the remaining details are supplied.
Hi Ohad Schneider (@ohadschn), a brief follow-up on the remaining cloud-onboarding details. The scope, SDK readiness, and Bleu precedent are already clear.
Could maintainers or the cloud owners share an authoritative public configuration/metadata source for each of
AzureDelosCloudandAzureGovSgCloud, covering endpoints, suffixes, resource/audience IDs, unavailable services, and access prerequisites?You do not need to compile these values yourself; no failure logs or CLI version are needed. Please omit credentials and private infrastructure details. We'll pick this up automatically once the remaining information is supplied.
Preconditions
Related command
az cloud setResource Provider
N/A
Description of Feature or Work Requested
CloudNameEnum currently contains:
AzureCloud: public cloudAzureChinaCloud: Mooncake national cloudAzureUSGovernment: Fairfax national cloud)AzureGermanCloud: Blackforest national cloud (deprecated)AzureBleuCloud: France sovereign cloudazure-cli/src/azure-cli-core/azure/cli/core/cloud.py
Line 353 in 9a3432d
It is currently missing the other 2 sovereign clouds:
AzureDelosCloud: Germany sovereign cloudAzureGovSgCloud: Singapore sovereign cloudWhen you add it, please make sure to include all applicable endpoints/suffixes and resource IDs (see #34059)
Minimum API Version Required
N/A
Swagger PR link / SDK link
N/A
Request Example
No response
Target Date
N/A
PM Contact
ohads
Engineer Contact
ohads
Additional context
This will simplify various critical internal efforts