Skip to content

Sovereign Cloud Support: Specific Updates#1729

Draft
jairmyree wants to merge 1 commit intomainfrom
jairmyree/sov-cloud-no-multicloud
Draft

Sovereign Cloud Support: Specific Updates#1729
jairmyree wants to merge 1 commit intomainfrom
jairmyree/sov-cloud-no-multicloud

Conversation

@jairmyree
Copy link
Member

This pull request introduces support for sovereign Azure clouds (China and US Government) across several services by making cloud-specific endpoint and scope selection dynamic. The changes add an explicit cloud type to the core authentication configuration and propagate this awareness through dependent services, ensuring correct endpoints and tokens are used for each cloud environment.

Key changes include:

Core authentication enhancements:

  • Added the AzureCloud enum and a new CloudType property to AzureCloudConfiguration, updating its logic to parse and expose the current cloud environment. This is also reflected in the IAzureCloudConfiguration interface. [1] [2] [3] [4]

Cloud-aware endpoint and scope selection:

  • Updated AppLensService, ProfilerDataService, AppServiceService, and ConfidentialLedgerService to use the detected cloud type from the tenant service, dynamically selecting the correct endpoints and token scopes for public, China, and US Government clouds. This includes methods for resolving management, diagnostics, and CosmosDB endpoints. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]

Service-specific improvements:

  • In AppServiceService, CosmosDB connection string generation is now cloud-aware, ensuring correct domain suffixes for each environment.
  • In ConfidentialLedgerService, the ledger URI is now built with the appropriate domain for the current cloud.

These changes collectively enable multi-cloud support, allowing the codebase to function correctly in Azure Public, China, and US Government environments.

@jairmyree jairmyree force-pushed the jairmyree/sov-cloud-no-multicloud branch from 9a497ee to e41d678 Compare February 13, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.

1 participant