You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/site-recovery/azure-to-azure-about-networking.md
+4-60Lines changed: 4 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: sujayt
6
6
manager: rochakm
7
7
ms.service: site-recovery
8
8
ms.topic: article
9
-
ms.date: 1/8/2020
9
+
ms.date: 1/23/2020
10
10
ms.author: sutalasi
11
11
12
12
---
@@ -45,77 +45,21 @@ If you are using a URL-based firewall proxy to control outbound connectivity, al
45
45
--- | ---
46
46
*.blob.core.windows.net | Required so that data can be written to the cache storage account in the source region from the VM. If you know all the cache storage accounts for your VMs, you can allow access to the specific storage account URLs (Ex: cache1.blob.core.windows.net and cache2.blob.core.windows.net) instead of *.blob.core.windows.net
47
47
login.microsoftonline.com | Required for authorization and authentication to the Site Recovery service URLs.
48
-
*.hypervrecoverymanager.windowsazure.com | Required so that the Site Recovery service communication can occur from the VM. You can use the corresponding 'Site Recovery IP' if your firewall proxy supports IPs.
49
-
*.servicebus.windows.net | Required so that the Site Recovery monitoring and diagnostics data can be written from the VM. You can use the corresponding 'Site Recovery Monitoring IP' if your firewall proxy supports IPs.
48
+
*.hypervrecoverymanager.windowsazure.com | Required so that the Site Recovery service communication can occur from the VM.
49
+
*.servicebus.windows.net | Required so that the Site Recovery monitoring and diagnostics data can be written from the VM.
50
50
51
51
## Outbound connectivity for IP address ranges
52
52
53
-
If you are using an IP-based firewall proxy, or NSG to control outbound connectivity, these IP ranges need to be allowed.
53
+
If you are using an NSG to control outbound connectivity, these service tags need to be allowed.
54
54
55
55
- All IP address ranges that correspond to the storage accounts in source region
56
56
- Create a [Storage service tag](../virtual-network/security-overview.md#service-tags) based NSG rule for the source region.
57
57
- Allow these addresses so that data can be written to the cache storage account, from the VM.
58
58
- Create a [Azure Active Directory (AAD) service tag](../virtual-network/security-overview.md#service-tags) based NSG rule for allowing access to all IP addresses corresponding to AAD
59
-
- If new addresses are added to the Azure Active Directory (AAD) in the future, you need to create new NSG rules.
60
59
- Create an EventsHub service tag based NSG rule for the target region, allowing access to Site Recovery monitoring.
61
60
- Create an AzureSiteRecovery service tag based NSG rule for allowing access to Site Recovery service in any region.
62
61
- We recommend that you create the required NSG rules on a test NSG, and verify that there are no problems before you create the rules on a production NSG.
63
62
64
-
65
-
If you prefer using Site Recovery IP address ranges (not recommended), please refer the below table:
Copy file name to clipboardExpand all lines: articles/site-recovery/azure-to-azure-architecture.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: rayne-wiselman
6
6
manager: carmonm
7
7
ms.service: site-recovery
8
8
ms.topic: conceptual
9
-
ms.date: 1/08/2020
9
+
ms.date: 1/23/2020
10
10
ms.author: raynew
11
11
---
12
12
@@ -142,7 +142,7 @@ Please note that details of network connectivity requirements can be found in [
142
142
**Rule** | **Details** | **Service tag**
143
143
--- | --- | ---
144
144
Allow HTTPS outbound: port 443 | Allow ranges that correspond to storage accounts in the source region | Storage.\<region-name>
145
-
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Azure Active Directory (Azure AD).<br/><br/> If Azure AD addresses are added in future you need to create new Network Security Group (NSG) rules. | AzureActiveDirectory
145
+
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Azure Active Directory (Azure AD) | AzureActiveDirectory
146
146
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Events Hub in the target region. | EventsHub.\<region-name>
147
147
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Azure Site Recovery | AzureSiteRecovery
148
148
@@ -151,7 +151,7 @@ Allow HTTPS outbound: port 443 | Allow ranges that correspond to Azure Site Reco
151
151
**Rule** | **Details** | **Service tag**
152
152
--- | --- | ---
153
153
Allow HTTPS outbound: port 443 | Allow ranges that correspond to storage accounts in the target region | Storage.\<region-name>
154
-
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Azure AD.<br/><br/> If Azure AD addresses are added in future you need to create new NSG rules. | AzureActiveDirectory
154
+
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Azure AD | AzureActiveDirectory
155
155
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Events Hub in the source region. | EventsHub.\<region-name>
156
156
Allow HTTPS outbound: port 443 | Allow ranges that correspond to Azure Site Recovery | AzureSiteRecovery
Copy file name to clipboardExpand all lines: articles/site-recovery/azure-to-azure-tutorial-enable-replication.md
+1-12Lines changed: 1 addition & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: rayne-wiselman
5
5
manager: carmonm
6
6
ms.service: site-recovery
7
7
ms.topic: tutorial
8
-
ms.date: 1/8/2020
8
+
ms.date: 1/24/2020
9
9
ms.author: raynew
10
10
ms.custom: mvc
11
11
---
@@ -77,17 +77,6 @@ If you're using a URL-based firewall proxy to control outbound connectivity, all
77
77
78
78
If you're using NSG, create service tag based NSG rules for access to Azure Storage, Azure Active Directory, Site Recovery service and Site Recovery monitoring. [Learn more](azure-to-azure-about-networking.md#outbound-connectivity-for-ip-address-ranges).
79
79
80
-
If you want to control outbound connectivity using IP addresses instead of NSG rules, allow these addresses for IP-based firewalls, proxy, or NSG rules.
81
-
82
-
>[!NOTE]
83
-
>It is recommended to always configure NSG rules with service tags for outbound access.
84
-
85
-
-[Microsoft Azure Datacenter IP Ranges](https://www.microsoft.com/download/details.aspx?id=41653)
86
-
-[Windows Azure Datacenter IP Ranges in Germany](https://www.microsoft.com/download/details.aspx?id=54770)
87
-
-[Windows Azure Datacenter IP Ranges in China](https://www.microsoft.com/download/details.aspx?id=42064)
88
-
-[Office 365 URLs and IP address ranges](https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_identity)
89
-
-[Site Recovery service endpoint IP addresses](https://aka.ms/site-recovery-public-ips)
90
-
91
80
## Verify Azure VM certificates
92
81
93
82
Check that the VMs you want to replicate have the latest root certificates. If they don't the VM can't registered to Site Recovery, due to security constraints.
Copy file name to clipboardExpand all lines: articles/site-recovery/site-recovery-faq.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: General questions about the Azure Site Recovery service
3
3
description: This article discusses popular general questions about Azure Site Recovery.
4
4
ms.topic: conceptual
5
-
ms.date: 1/10/2020
5
+
ms.date: 1/24/2020
6
6
ms.author: raynew
7
7
8
8
---
@@ -142,7 +142,7 @@ Azure Site Recovery replicates data to an Azure storage account or managed disks
142
142
143
143
### Why can't I replicate over VPN?
144
144
145
-
When you replicate to Azure, replication traffic reaches the public endpoints of an Azure Storage. Thus you can only replicate over the public internet with ExpressRoute (Microsoft peering or an existing public peering), and VPN doesn't work.
145
+
When you replicate to Azure, replication traffic reaches the public endpoints of an Azure Storage. Thus you can only replicate over the public internet or via ExpressRoute (Microsoft peering or an existing public peering).
146
146
147
147
### Can I use Riverbed SteelHeads for replication?
0 commit comments