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/backup/microsoft-azure-backup-server-protection-v3-ur1.md
+2-18Lines changed: 2 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,32 +64,16 @@ The following sections details the protection support matrix for MABS:
64
64
65
65
## Azure ExpressRoute support
66
66
67
-
You can back up your data over Azure ExpressRoute with public peering (available for old circuits) and Microsoft peering. Backup over private peering isn't supported.
67
+
You can back up your data over Azure ExpressRoute with Microsoft peering. Backup over private peering isn't supported.
68
68
69
-
With public peering: Ensure access to the following domains/addresses:
70
-
71
-
* URLs
72
-
*`www.msftncsi.com`
73
-
*`*.Microsoft.com`
74
-
*`*.WindowsAzure.com`
75
-
*`*.microsoftonline.com`
76
-
*`*.windows.net`
77
-
*`www.msftconnecttest.com`
78
-
* IP addresses
79
-
* 20.190.128.0/18
80
-
* 40.126.0.0/18
81
-
82
-
With Microsoft peering, select the following services/regions and relevant community values:
69
+
Select the following services/regions and relevant community values:
83
70
84
71
* Microsoft Entra ID (12076:5060)
85
72
* Microsoft Azure Region (according to the location of your Recovery Services vault)
86
73
* Azure Storage (according to the location of your Recovery Services vault)
87
74
88
75
For more information, see the [ExpressRoute routing requirements](../expressroute/expressroute-routing.md).
89
76
90
-
>[!NOTE]
91
-
>Public Peering is deprecated for new circuits.
92
-
93
77
## Operating systems and applications at end of support
94
78
95
79
Support for the following operating systems and applications in MABS are deprecated. We recommended you to upgrade them to continue protecting your data.
0 commit comments