Prepare the App Service custom-domain binding before regional cutover

Source facts

App Service resources are regional and cannot be moved directly across regions; Microsoft describes creating a copy in the destination. Its portal procedure prepares the custom-domain binding on the target with asuid. before remapping the domain name.

For the public multitenant service, domain ownership must be verified for the binding. Once the binding exists, the source says public DNS does not have to point at that App Service endpoint merely to keep the binding in place. Microsoft Learn.

Applicability

Identify the source app, destination app and plan, custom name, certificate arrangement and cutover owner. Use this as a sequencing check within a complete regional relocation plan, not as the entire migration procedure.

DSE recommendation

DSE recommends treating binding preparation and traffic redirection as separately approved milestones. Verify the destination’s application settings and dependencies before asking the DNS owner to remap the name. Preserve the existing name-to-service mapping and an agreed reversal decision. Avoid using public traffic as the first test of whether the destination was configured correctly.

Verification

Before cutover, inspect the target’s custom-domain binding and complete the approved target application tests. After the authorized name change, check resolution and the intended application transaction from representative client paths. Record which app actually served the request, along with certificate and dependency results. Investigate discrepancies before declaring regional relocation complete.

Official references

Microsoft Learn: Relocate Azure App Services to another region. Source retrieved September 9, 2026.