#9127 Add Dataverse Cloud endpoints override for sovereign clouds
A new interface and enum enable partners to override Dataverse endpoints for sovereign cloud environments without forking BaseApp. The setup table stores the cloud selection and endpoints are routed through the interface at all call sites.
- 10files
- 7AL files
- 7objects
Pull request · merged into main (BC30) on 2026-07-09 by onbuyuka · 10 files (+326 -22), 7 AL · feature · tier official · reviewed (checked by Opus)
What changed
- New extensible enum and interface allow partners to provide sovereign cloud endpoints like GCC High, US-DoD, and China
- Setup table gains a field to store the selected Dataverse cloud, defaulting to Commercial with no UI changes
- All hardcoded OAuth and Discovery URLs now route through the interface implementation
- Existing commercial tenants are unaffected; no upgrade code needed
- Partners can extend the enum and implement their own endpoint codeunit
- Behaviour changes for users or extensions.
AL objects touched
- Table 7200 “CDS Connection Setup”, Base Application: modified
- Page 7201 “CDS Connection Setup Wizard”, Base Application: modified
- Codeunit 7203 “CDS Environment”, Base Application: modified
- Codeunit 7201 “CDS Integration Impl.”, Base Application: modified
- Codeunit 7208 “Commercial Dataverse Endpoints”, Base Application: added
- Enum 7207 “Dataverse Cloud”, Base Application: added
- Interface “Dataverse Cloud Endpoints”, Base Application: added
Context
- Work items: AB#635858
- Systems: integration
- From the description: “Add a structured, partner-extensible hook and route every sovereign-sensitive URL through it.”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).