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/networking/check-usage-against-limits.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ In this article, you learn how to see the number of each network resource type t
42
42
43
43
You can run the commands that follow in the [Azure Cloud Shell](https://shell.azure.com/powershell), or by running PowerShell from your computer. The Azure Cloud Shell is a free interactive shell. It has common Azure tools preinstalled and configured to use with your account. If you run PowerShell from your computer, you need the Azure PowerShell module, version 1.0.0 or later. Run `Get-Module -ListAvailable Az` on your computer, to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-az-ps). If you're running PowerShell locally, you also need to run `Login-AzAccount` to log in to Azure.
44
44
45
-
View your usage against limits with [Get-AzNetworkUsage](https://docs.microsoft.com/powershell/module/az.network/get-aznetworkusage). The following example gets the usage for resources where at least one resource is deployed in the East US location:
45
+
View your usage against limits with [Get-AzNetworkUsage](/powershell/module/az.network/get-aznetworkusage). The following example gets the usage for resources where at least one resource is deployed in the East US location:
Copy file name to clipboardExpand all lines: articles/networking/connectivty-interoperability-data-plane.md
+13-15
Original file line number
Diff line number
Diff line change
@@ -562,19 +562,17 @@ See the [ExpressRoute FAQ][ExR-FAQ] to:
562
562
[5]: ./media/backend-interoperability/Loc1-HubVM-S2S.jpg"Network Performance Monitor view of connectivity from the Location 1 VM to the hub VNet via a site-to-site VPN"
Copy file name to clipboardExpand all lines: articles/networking/disaster-recovery-dns-traffic-manager.md
+3-12
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Most enterprise customers are choosing a multi-region architecture for resilienc
41
41
42
42
*Figure: Active/Passive with warm standby disaster recovery configuration*
43
43
44
-
To learn more about failover and high availability, see [Disaster Recovery for Azure Applications](https://docs.microsoft.com/azure/architecture/resiliency/disaster-recovery-azure-applications).
44
+
To learn more about failover and high availability, see [Disaster Recovery for Azure Applications](/azure/architecture/resiliency/disaster-recovery-azure-applications).
45
45
46
46
47
47
## Planning your disaster recovery architecture
@@ -50,7 +50,7 @@ There are two technical aspects towards setting up your disaster recovery archit
50
50
- Using a deployment mechanism to replicate instances, data, and configurations between primary and standby environments. This type of disaster recovery can be done natively via Azure Site-Recovery via Microsoft Azure partner appliances/services like Veritas or NetApp.
51
51
- Developing a solution to divert network/web traffic from the primary site to the standby site. This type of disaster recovery can be achieved via Azure DNS, Azure Traffic Manager(DNS), or third-party global load balancers.
52
52
53
-
This article is limited to approaches via Network and Web traffic redirection. For instructions to set up Azure Site Recovery, see [Azure Site Recovery Documentation](https://docs.microsoft.com/azure/site-recovery/).
53
+
This article is limited to approaches via Network and Web traffic redirection. For instructions to set up Azure Site Recovery, see [Azure Site Recovery Documentation](../site-recovery/index.yml).
54
54
DNS is one of the most efficient mechanisms to divert network traffic because DNS is often global and external to the data center and is insulated from any regional or availability zone (AZ) level failures. One can use a DNS-based failover mechanism and in Azure, two DNS services can accomplish the same in some fashion - Azure DNS (authoritative DNS) and Azure Traffic Manager (DNS-based smart traffic routing).
55
55
56
56
It is important to understand few concepts in DNS that are extensively used to discuss the solutions provided in this article:
@@ -170,13 +170,4 @@ During a disaster, the primary endpoint gets probed and the status changes to **
170
170
171
171
## Next steps
172
172
- Learn more about [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md).
173
-
- Learn more about [Azure DNS](../dns/dns-overview.md).
174
-
175
-
176
-
177
-
178
-
179
-
180
-
181
-
182
-
173
+
- Learn more about [Azure DNS](../dns/dns-overview.md).
0 commit comments