Relocate Azure Private Link Service to another region

This article shows you how to relocate Azure Private Link Service when moving your workload to another region.

There are various reasons why you may want to move your existing Azure resources from one region to another. You may want to:

• Take advantage of a new Azure region.
• Deploy features or services available in specific regions only.
• Meet internal policy and governance requirements.
• Align with company mergers and acquisitions
• Meet capacity planning requirements.

To learn how to to reconfigure private endpoints for a particular service, see the appropriate service relocation guide.

Downtime

To understand the possible downtimes involved, see Cloud Adoption Framework for Azure: Select a relocation method.

Prepare

Identify all resources that are used by Private Link Service, such as Standard load balancer, virtual machines, virtual network, etc.

Redeploy

1. Redeploy all resources that are used by Private Link Service.

2. Ensure that a standard load balancer with all dependent resources is relocated to the target region.

3. Create a Private Link Service that references the relocated load balancer. To create the Private Link, you can use Azure Portal, PowerShell, or Azure CLI.

   In the load balancer selection process: - Choose the frontend IP configuration where you want to receive the traffic. - Choose a subnet for NAT IP addresses for the Private Link Service. - Choose Private Link Service settings that are the same as the source Private Link Service.

4. Redeploy the private endpoint into the relocated virtual network.

5. Configure your DNS settings by following guidance in Private DNS zone values.

Next steps

To learn more about moving resources between regions and disaster recovery in Azure, refer to:

• Move resources to a new resource group or subscription
• Move Azure VMs to another region