Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
731 questions
Azure Site Recovery - Couldn't configure the appliance
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 8%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUK%3C/text%3E%3C/svg%3E)
Ugur Kurbanov
0
Reputation points
I have configured ASR in the past and was able to migrate some of my servers from vSphere 7.0 to Azure a month ago, and it worked perfectly without any issues.
Now I don't need that subscription and I have created a new subscription to configure ASR but this time it keeps giving me an error
Details
Either the proxy details provided are incorrect or the proxy server/firewall is blocking your request to access required URLs. Ensure that the following URLs are allowed through your proxy server/firewall https://....................privatelink.siterecovery.windowsazure.com.
I had tried to reconfigure ASR and Appliance again by removing them and following the same steps I followed before when it worked, and yet I keep receiving this message.
{count} votes
-
SadiqhAhmed-MSFT 47,271 Reputation points Microsoft Employee2023-06-06T16:03:51.9033333+00:00 Hello @Ugur Kurbanov Thank you for contacting us on Microsoft Q&A platform. Happy to assist!
I see that you are trying to configure ASR appliance in a new subscription that seems to be erroring out.
First thing, could you please check if you are deploying ASR modernized appliance or a classic one.
Guidance for Modernized appliance - https://learn.microsoft.com/en-us/azure/site-recovery/deploy-vmware-azure-replication-appliance-modernized
Guide for classic ASR appliance - https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-configuration-server-requirements
As per error message, you should ensure to allow the required URLs mentioned in the documentation.
Hope this helps. Let me know if you need any assistance!
If the response helped, do "Accept Answer" and up-vote it
-
SadiqhAhmed-MSFT 47,271 Reputation points Microsoft Employee
2023-06-08T08:23:26.3433333+00:00 @Ugur Kurbanov Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
-
Ugur Kurbanov 0 Reputation points
2023-06-08T12:18:18+00:00 Hi SadiqhAhmed
Thank you for the quick response I am using the modernized ASR appliance; all the URLs are open, and I don't see anything to be blocked from my firewall end. As I mentioned, just a month ago I was able to replicate my infrastructure without any issues, but now it gives me an error.
Last time I used a private endpoint as a point of contact, and I did the same this time; maybe I made some mistakes configuring a private endpoint. -
Ugur Kurbanov 0 Reputation points
2023-06-08T12:18:58.08+00:00 Forgot to mention that the URL was allowed on the firewall and yet it returned with the same error message.
-
SadiqhAhmed-MSFT 47,271 Reputation points Microsoft Employee
2023-06-08T17:06:39.71+00:00 @Ugur Kurbanov Would it be possible for you to contact Azure technical support team to investigate this issue further?
-
SadiqhAhmed-MSFT 47,271 Reputation points Microsoft Employee
2023-06-12T06:26:45.6066667+00:00 @Ugur Kurbanov Let us know if there are any challenges contacting Azure technical support team.
-
Ugur Kurbanov 0 Reputation points
2023-06-12T11:31:15.0466667+00:00 Thank you SadiqhAhmed, I resolved the issue by having to compromise and use public access instead of the private endpoint.
-
SadiqhAhmed-MSFT 47,271 Reputation points Microsoft Employee
2023-06-12T15:50:17.5133333+00:00 Thanks for the update.
Sign in to comment
Sign in to answer