Extension URLs use a standard CNAME pattern. Legacy DIY Extensions follow the CNAME naming pattern, and extensions that use a hosting service use the hosting service name convention. CNAMEs for hosting services are managed by the Ibiza team.
The CNAMEs that are created are unique for each environment, and use the formats that are specified in the following table. The table describes the URL format and the hosting service name convention for each environment, and includes links to the configuration files for each environment.
| Portal Environment | Purpose | Legacy URL | Configuration File | Hosting Service |
|---|---|---|---|---|
| DOGFOOD | Testing environment | df.<extension>.onecloud-ext.azure-test.net |
Extensions.dogfood.json | //hosting.onecloud.azure-test.net/{hostingServiceRoutePrefix} |
| RC, MPAC, Preview, PROD | Preview and Production environments | main.<extension>.ext.azure.com |
Extensions.prod.json | {hostingServiceRoutePrefix}.hosting.portal.azure.net/{hostingServiceRoutePrefix} |
| BLACKFOREST | Localization site | main.<extension>.ext.microsoftazure.de |
Extensions.bf.json | //{hostingServiceRoutePrefix}.hosting.azure-api.de/{hostingServiceRoutePrefix} |
| FAIRFAX | Localization site | main.<extension>.ext.azure.us |
Extensions.ff.json | {hostingServiceRoutePrefix}.hosting.azureportal.usgovcloudapi.net/{hostingServiceRoutePrefix |
| MOONCAKE | Localization site | main.<extension>.ext.azure.cn |
Extensions.mc.json | {hostingServiceRoutePrefix}.hosting.azureportal.chinacloudapi.cn/{hostingServiceRoutePrefix} |
NOTE The RC, MPAC, Preview, and PROD environments all share the same Extensions.prod.json file for configuration; therefore there can be only one entry for the extension across all these environments.
The relationship between the environments and the configuration files specified in portalfx-extensions-branches.md.
You can create DOGFOOD/PROD CNAMEs using the Azure DNS that is located at https://azure.microsoft.com/en-us/services/dns/. Its documentation is located at https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal. You can also use any DNS hosting system.
The PROD CNAME is used for RC, MPAC, Preview and PROD environments.
Create National Cloud CNAMEs using the process specified in each cloud. For more information, search for "DNS" on their wiki pages, as described in the following table.
| CLOUD | LOCATION |
|---|---|
| Fairfax | https://aka.ms/fairfax |
| Blackforest | https://aka.ms/blackforest |
| Mooncake | https://aka.ms/mooncake |
This section contains a glossary of terms and acronyms that are used in this document. For common computing terms, see https://techterms.com/. For common acronyms, see https://www.acronymfinder.com.
| Term | Meaning |
|---|---|
| BF | Black Forest |
| CNAME | Canonical Name record. A type of resource record in the Domain Name System (DNS) that specifies that a domain name is an alias for another domain (the 'canonical' domain). |
| DNS | Domain name server |
| FF | Fairfax |
| MPAC | ms.portal.azure.com, the Azure Portal instance for internal Microsoft customers. |
| national cloud | Network instances of Microsoft enterprise cloud services that are isolated physically and logically. They are confined within the geographic borders of specific countries and operated by local personnel. See sovereign cloud. |
| PROD | Production |
| RC | Release Candidate environment, used to deploy daily builds of the Azure Portal. There is no user traffic in this environment. |
| sovereign cloud | Instances of Azure restricted to a particular group of users. This group may consist of one geopolitical boundary, like a country. It may also consist of one legal boundary, for example, the public sector. |
| TFS | Team Foundation Server |
| URL | Uniform Resource Locator |