When configuring ASR using private endpoints for the source and target vnets I am seeing 9 IP addresses being used in each subnet where replicated resources are located by the RSV private endpoint, is this correct?

Paul Downes 20 Reputation points
2024-09-24T11:46:23.7466667+00:00

I have configured ASR to replicated VMs in a source region to a target region and want to use private endpoints for the RSV. After enabling replication I see the following FQDNs and each one uses an IP in the source and target subnets, adding up to 9 total required. Is this correct? This seems excessive and may mean I need to redesign my network to allow further replicated items.

asr-prod01-tel1.target

asr-pod01-prodt2.target

asr-pod01-srs1.target

asr-pod01-rcm1.target

asr-pod01-id1.target

asr-pod01-gws1.source

asr-pod01-rcm1.source

asr-pod01-prot2.source

asr-pod01-gws1.target

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
712 questions
0 comments No comments
{count} votes

Accepted answer
  1. SadiqhAhmed-MSFT 45,516 Reputation points Microsoft Employee
    2024-09-24T21:42:30.69+00:00

    @Paul Downes Greetings!

    Yes, it is normal to see multiple FQDNs and IP addresses associated with the Azure Site Recovery (ASR) service when using private endpoints. Each FQDN corresponds to a specific component of the ASR service, and each IP address corresponds to a specific subnet in the source and target regions.

    The number of required IP addresses will depend on the specific configuration of your ASR deployment and the number of subnets that you have in your source and target regions. In your case, it appears that you have a total of 9 IP addresses that are required for the ASR service.

    If you are concerned about the number of IP addresses that are required, you may want to consider using a hub-and-spoke network topology to consolidate your subnets and reduce the number of IP addresses that are required for the ASR service. This can help to simplify your network configuration and reduce the overall complexity of your ASR deployment.

    Alternatively, you can also consider using Azure ExpressRoute to establish a private, dedicated connection between your on-premises network and Azure. This can provide a more secure and reliable connection for your ASR deployment and help to reduce the number of IP addresses that are required.

    Hope this helps. Please write back to us if you have any further questions.


    If the response helped, do "Accept Answer" and up-vote it


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.