2025_01 - Fix monthly broken links - ankitaduttaMSFT

Albertyang0 · Albertyang0 · commit f448933320eb · 2025-01-20T08:54:56.000-08:00
diff --git a/articles/site-recovery/hyper-v-prepare-on-premises-tutorial.md b/articles/site-recovery/hyper-v-prepare-on-premises-tutorial.md
@@ -65,7 +65,7 @@ For this tutorial, the simplest configuration is for the Hyper-V hosts and the V
 
 1. Make sure that Hyper-V hosts and the Virtual Machine Manager server, if relevant, can access the required URLs listed in the following table.
 1. If you're controlling access by IP address, make sure that:
-    - IP address-based firewall rules can connect to [Azure Datacenter IP ranges](https://www.microsoft.com/download/confirmation.aspx?id=41653) and the HTTPS port (443).
+    - IP address-based firewall rules can connect to [Azure Datacenter IP ranges](https://www.microsoft.com/download/details.aspx?id=41653) and the HTTPS port (443).
     - Allow IP address ranges for the Azure region of your subscription.
 
 ### Required URLs
diff --git a/articles/site-recovery/physical-azure-disaster-recovery.md b/articles/site-recovery/physical-azure-disaster-recovery.md
@@ -133,7 +133,7 @@ Make sure the machine can access these URLs based on your environment:
 
 IP address-based firewall rules should allow communication to all of the Azure URLs that are listed above over HTTPS (443) port. To simplify and limit the IP Ranges, it's recommended that URL filtering is done.
 
-- **Commercial IPs** - Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/confirmation.aspx?id=41653), and the HTTPS (443) port. Allow IP address ranges for the Azure region of your subscription to support the Microsoft Entra ID, Backup, Replication, and Storage URLs.  
+- **Commercial IPs** - Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/details.aspx?id=41653), and the HTTPS (443) port. Allow IP address ranges for the Azure region of your subscription to support the Microsoft Entra ID, Backup, Replication, and Storage URLs.  
 - **Government IPs** - Allow the [Azure Government Datacenter IP Ranges](https://www.microsoft.com/en-us/download/details.aspx?id=57063), and the HTTPS (443) port for all USGov Regions (Virginia, Texas, Arizona, and Iowa) to support Microsoft Entra ID, Backup, Replication, and Storage URLs.  
 
 #### Run setup
diff --git a/articles/site-recovery/region-move-cross-geos.md b/articles/site-recovery/region-move-cross-geos.md
@@ -140,7 +140,7 @@ Make sure the machine can access these URLs based on your environment:
 
 IP address-based firewall rules should allow communication to all of the Azure URLs that are listed above over HTTPS (443) port. To simplify and limit the IP Ranges, it is recommended that URL filtering is done.
 
-- **Commercial IPs** - Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/confirmation.aspx?id=41653), and the HTTPS (443) port. Allow IP address ranges for the Azure region of your subscription to support the Microsoft Entra ID, Backup, Replication, and Storage URLs.  
+- **Commercial IPs** - Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/details.aspx?id=41653), and the HTTPS (443) port. Allow IP address ranges for the Azure region of your subscription to support the Microsoft Entra ID, Backup, Replication, and Storage URLs.  
 - **Government IPs** - Allow the [Azure Government Datacenter IP Ranges](https://www.microsoft.com/en-us/download/details.aspx?id=57063), and the HTTPS (443) port for all USGov Regions (Virginia, Texas, Arizona, and Iowa) to support Microsoft Entra ID, Backup, Replication, and Storage URLs.  
 
 #### Run setup
diff --git a/articles/site-recovery/vmware-azure-deploy-configuration-server.md b/articles/site-recovery/vmware-azure-deploy-configuration-server.md
@@ -111,7 +111,7 @@ Make sure the machine can access these URLs based on your environment:
 
 IP address-based firewall rules should allow communication to all of the Azure URLs that are listed above over HTTPS (443) port. To simplify and limit the IP Ranges, it is recommended that URL filtering be done.
 
-- **Commercial IPs** - Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/confirmation.aspx?id=41653), and the HTTPS (443) port. Allow IP address ranges for the Azure region of your subscription to support the Microsoft Entra ID, Backup, Replication, and Storage URLs.  
+- **Commercial IPs** - Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/details.aspx?id=41653), and the HTTPS (443) port. Allow IP address ranges for the Azure region of your subscription to support the Microsoft Entra ID, Backup, Replication, and Storage URLs.  
 - **Government IPs** - Allow the [Azure Government Datacenter IP Ranges](https://www.microsoft.com/en-us/download/details.aspx?id=57063), and the HTTPS (443) port for all USGov Regions (Virginia, Texas, Arizona, and Iowa) to support Microsoft Entra ID, Backup, Replication, and Storage URLs.  
 
 ### Configure settings
diff --git a/includes/site-recovery-config-server-reqs-physical.md b/includes/site-recovery-config-server-reqs-physical.md
@@ -33,7 +33,7 @@ IP address type | Static
 **ACCESS SETTINGS** | 
 MYSQL | MySQL should be installed on the configuration server. You can install manually, or Site Recovery can install it during deployment. For Site Recovery to install, check that the machine can reach http://cdn.mysql.com/archives/mysql-5.5/mysql-5.5.37-win32.msi.
 URLs | The configuration server needs access to these URLs (directly or via proxy):<br/><br/> Microsoft Entra ID: `login.microsoftonline.com`; `login.microsoftonline.us`; `*.accesscontrol.windows.net`<br/><br/> Replication data transfer: `*.backup.windowsazure.com`; `*.backup.windowsazure.us`<br/><br/> Replication management: `*.hypervrecoverymanager.windowsazure.com`; `*.hypervrecoverymanager.windowsazure.us`; `https://management.azure.com`; `*.services.visualstudio.com`<br/><br/> Storage access: `*.blob.core.windows.net`; `*.blob.core.usgovcloudapi.net`<br/><br/> Time synchronization: `time.nist.gov`; `time.windows.com`<br/><br/> Telemetry (optional): `dc.services.visualstudio.com`
-Firewall | IP address-based firewall rules should allow communication to Azure URLs. To simplify and limit the IP ranges, we recommend using URL filtering.<br/><br/>**For commercial IPs:**<br/><br/>- Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/confirmation.aspx?id=41653), and the HTTPS (443) port.<br/><br/> - Allow IP address ranges for the West US (used for Access Control and Identity Management).<br/><br/> - Allow IP address ranges for the Azure region of your subscription, to support the URLs needed for Microsoft Entra ID, backup, replication, and storage.<br/><br/> **For government IPs:**<br/><br/> - Allow the Azure Government Datacenter IP Ranges, and the HTTPS (443) port.<br/><br/> - Allow IP address ranges for all US Gov Regions (Virginia, Texas, Arizona, and Iowa), to support the URLs needed for Microsoft Entra ID, backup, replication, and storage.
+Firewall | IP address-based firewall rules should allow communication to Azure URLs. To simplify and limit the IP ranges, we recommend using URL filtering.<br/><br/>**For commercial IPs:**<br/><br/>- Allow the [Azure Datacenter IP Ranges](https://www.microsoft.com/download/details.aspx?id=41653), and the HTTPS (443) port.<br/><br/> - Allow IP address ranges for the West US (used for Access Control and Identity Management).<br/><br/> - Allow IP address ranges for the Azure region of your subscription, to support the URLs needed for Microsoft Entra ID, backup, replication, and storage.<br/><br/> **For government IPs:**<br/><br/> - Allow the Azure Government Datacenter IP Ranges, and the HTTPS (443) port.<br/><br/> - Allow IP address ranges for all US Gov Regions (Virginia, Texas, Arizona, and Iowa), to support the URLs needed for Microsoft Entra ID, backup, replication, and storage.
 Ports | Allow 443 (Control channel orchestration)<br/><br/> Allow 9443 (Data transport) 
 
 
