Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 15e8ef6

Browse files
committedJan 11, 2021
Links: Azure Networking
1 parent ec028c7 commit 15e8ef6

21 files changed

+139
-157
lines changed
 

‎articles/networking/TOC.yml

+15-15
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,13 @@
1111
- name: Asymmetric routing with multiple network paths
1212
href: ../expressroute/expressroute-asymmetric-routing.md?toc=%2fazure%2fnetworking%2ftoc.json
1313
- name: Secure network designs
14-
href: ../best-practices-network-security.md?toc=%2fazure%2fnetworking%2ftoc.json
14+
href: /azure/cloud-adoption-framework/reference/networking-vdc?toc=%2fazure%2fnetworking%2ftoc.json
1515
- name: Hub-spoke topology
16-
href: https://docs.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/hub-spoke
16+
href: /azure/architecture/reference-architectures/hybrid-networking/hub-spoke
1717
- name: Network security best practices
1818
href: ../security/fundamentals/network-best-practices.md?toc=%2fazure%2fnetworking%2ftoc.json
1919
- name: Highly available network virtual appliances
20-
href: https://docs.microsoft.com/azure/architecture/reference-architectures/dmz/nva-ha
20+
href: /azure/architecture/reference-architectures/dmz/nva-ha
2121
- name: Combine load balancing methods
2222
href: ../traffic-manager/traffic-manager-load-balancing-azure.md?toc=%2fazure%2fnetworking%2ftoc.json
2323
- name: Disaster recovery using Azure DNS and Traffic Manager
@@ -79,27 +79,27 @@
7979
- name: Internet connectivity
8080
items:
8181
- name: Network load balance public servers
82-
href: ../load-balancer/load-balancer-get-started-internet-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
82+
href: ../load-balancer/quickstart-load-balancer-standard-public-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
8383
- name: Application load balance public servers
8484
href: ../application-gateway/quick-create-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
8585
- name: Protect web applications
86-
href: ../application-gateway/application-gateway-web-application-firewall-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
86+
href: ../web-application-firewall/ag/application-gateway-web-application-firewall-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
8787
- name: Distribute traffic across locations
8888
href: ../traffic-manager/traffic-manager-configure-geographic-routing-method.md?toc=%2fazure%2fnetworking%2ftoc.json
8989
- name: Internal connectivity
9090
items:
9191
- name: Network load balance private servers
92-
href: ../load-balancer/load-balancer-get-started-ilb-arm-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
92+
href: ../load-balancer/quickstart-load-balancer-standard-internal-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
9393
- name: Application load balance private servers
9494
href: ../application-gateway/application-gateway-ilb-arm.md?toc=%2fazure%2fnetworking%2ftoc.json
9595
- name: Connect virtual networks (same location)
96-
href: ../virtual-network/virtual-networks-create-vnetpeering-arm-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
96+
href: ../virtual-network/tutorial-connect-virtual-networks-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
9797
- name: Connect virtual networks (different locations)
9898
href: ../vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
9999
- name: Cross-premises connectivity
100100
items:
101101
- name: Create a S2S VPN connection (IPsec/IKE)
102-
href: ../vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
102+
href: ../vpn-gateway/tutorial-site-to-site-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
103103
- name: Create a P2S VPN connection (SSTP with certificates)
104104
href: ../vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
105105
- name: Create a dedicated private connection (ExpressRoute)
@@ -115,7 +115,7 @@
115115
- name: Check resource usage against Azure limits
116116
href: check-usage-against-limits.md
117117
- name: View network topology
118-
href: ../network-watcher/network-watcher-topology-powershell.md?toc=%2fazure%2fnetworking%2ftoc.json
118+
href: ../network-watcher/view-network-topology.md?toc=%2fazure%2fnetworking%2ftoc.json
119119
- name: Sample scripts
120120
items:
121121
- name: Azure CLI
@@ -131,22 +131,22 @@
131131
- name: Reference
132132
items:
133133
- name: Azure CLI
134-
href: https://docs.microsoft.com/cli/azure/network
134+
href: /cli/azure/network
135135
- name: Azure PowerShell
136-
href: https://docs.microsoft.com/powershell/module/az.network/
136+
href: /powershell/module/az.network/
137137
- name: .Net
138-
href: https://docs.microsoft.com/dotnet/api/microsoft.azure.management.network?view=azuremgmtnetwork-9.1.0-preview
138+
href: /dotnet/api/microsoft.azure.management.network?view=azuremgmtnetwork-9.1.0-preview
139139
- name: Node.js
140140
href: https://azure.microsoft.com/develop/nodejs/#azure-sdk
141141
- name: REST
142-
href: https://msdn.microsoft.com/library/mt163658.aspx
142+
href: /rest/api/virtual-network/
143143
- name: Azure Policy built-ins
144144
displayName: samples, policies, definitions
145145
href: ./policy-reference.md
146146
- name: Resources
147147
items:
148148
- name: Author templates
149-
href: /azure/azure-resource-manager/resource-group-authoring-templates?toc=%2fazure%2fnetworking%2ftoc.json
149+
href: ../azure-resource-manager/templates/template-syntax.md?toc=%2fazure%2fnetworking%2ftoc.json
150150
- name: Providers
151151
href: networking-partners-msp.md
152152
- name: Azure Roadmap
@@ -164,4 +164,4 @@
164164
- name: Stack Overflow
165165
href: https://stackoverflow.com/questions/tagged/azure-virtual-network
166166
- name: Videos
167-
href: https://azure.microsoft.com/resources/videos/index/?services=virtual-network
167+
href: https://azure.microsoft.com/resources/videos/index/?services=virtual-network

‎articles/networking/azure-for-network-engineers.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,6 @@ Learn about [virtual network routing][vnet-routing].
8383
Learn about the [network security groups][network-security].
8484

8585
<!--Link References-->
86-
[VNet]: https://docs.microsoft.com/azure/virtual-network/tutorial-connect-virtual-networks-portal
87-
[vnet-routing]: https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview
88-
[network-security]: https://docs.microsoft.com/azure/virtual-network/security-overview
89-
86+
[VNet]: ../virtual-network/tutorial-connect-virtual-networks-portal.md
87+
[vnet-routing]: ../virtual-network/virtual-networks-udr-overview.md
88+
[network-security]: ../virtual-network/network-security-groups-overview.md

‎articles/networking/check-usage-against-limits.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ In this article, you learn how to see the number of each network resource type t
4242

4343
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.
4444

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:
4646

4747
```azurepowershell-interactive
4848
Get-AzNetworkUsage `
@@ -87,4 +87,4 @@ Network Interfaces 1 24000
8787
Network Watchers 1 1
8888
Load Balancers 0 100
8989
Application Gateways 0 50
90-
```
90+
```

‎articles/networking/connectivty-interoperability-configuration.md

+12-14
Original file line numberDiff line numberDiff line change
@@ -214,18 +214,16 @@ See the [ExpressRoute FAQ][ExR-FAQ] to:
214214
[8]: ./media/backend-interoperability/ExR2-Remote-Connection.png "Connection configuration of ExpressRoute 2 to a remote VNet ExR gateway"
215215

216216
<!--Link References-->
217-
[Setup]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-preface
218-
[ExpressRoute]: https://docs.microsoft.com/azure/expressroute/expressroute-introduction
219-
[VPN]: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways
220-
[VNet]: https://docs.microsoft.com/azure/virtual-network/tutorial-connect-virtual-networks-portal
221-
[Configuration]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-configuration
217+
[Setup]: ./connectivty-interoperability-preface.md
218+
[ExpressRoute]: ../expressroute/expressroute-introduction.md
219+
[VPN]: ../vpn-gateway/vpn-gateway-about-vpngateways.md
220+
[VNet]: ../virtual-network/tutorial-connect-virtual-networks-portal.md
221+
[Configuration]:
222222
[Control-Analysis]:https://docs.microsoft.com/azure/networking/connectivty-interoperability-control-plane
223-
[Data-Analysis]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-data-plane
224-
[ExR-FAQ]: https://docs.microsoft.com/azure/expressroute/expressroute-faqs
225-
[S2S-Over-ExR]: https://docs.microsoft.com/azure/expressroute/site-to-site-vpn-over-microsoft-peering
226-
[ExR-S2S-CoEx]: https://docs.microsoft.com/azure/expressroute/expressroute-howto-coexist-resource-manager
227-
[Hub-n-Spoke]: https://docs.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/hub-spoke
228-
[Deploy-NVA]: https://docs.microsoft.com/azure/architecture/reference-architectures/dmz/nva-ha
229-
[VNet-Config]: https://docs.microsoft.com/azure/virtual-network/virtual-network-manage-peering
230-
231-
223+
[Data-Analysis]: ./connectivty-interoperability-data-plane.md
224+
[ExR-FAQ]: ../expressroute/expressroute-faqs.md
225+
[S2S-Over-ExR]: ../expressroute/site-to-site-vpn-over-microsoft-peering.md
226+
[ExR-S2S-CoEx]: ../expressroute/expressroute-howto-coexist-resource-manager.md
227+
[Hub-n-Spoke]: /azure/architecture/reference-architectures/hybrid-networking/hub-spoke
228+
[Deploy-NVA]: /azure/architecture/reference-architectures/dmz/nva-ha
229+
[VNet-Config]: ../virtual-network/virtual-network-manage-peering.md

‎articles/networking/connectivty-interoperability-control-plane.md

+13-15
Original file line numberDiff line numberDiff line change
@@ -98,19 +98,17 @@ See the [ExpressRoute FAQ][ExR-FAQ] to:
9898
[5]: ./media/backend-interoperability/ExR1-RouteTable.png "ExpressRoute 1 route table"
9999

100100
<!--Link References-->
101-
[Setup]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-preface
102-
[Configuration]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-configuration
103-
[ExpressRoute]: https://docs.microsoft.com/azure/expressroute/expressroute-introduction
104-
[VPN]: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways
105-
[VNet]: https://docs.microsoft.com/azure/virtual-network/tutorial-connect-virtual-networks-portal
106-
[Configuration]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-configuration
101+
[Setup]: ./connectivty-interoperability-preface.md
102+
[Configuration]: ./connectivty-interoperability-configuration.md
103+
[ExpressRoute]: ../expressroute/expressroute-introduction.md
104+
[VPN]: ../vpn-gateway/vpn-gateway-about-vpngateways.md
105+
[VNet]: ../virtual-network/tutorial-connect-virtual-networks-portal.md
106+
[Configuration]: ./connectivty-interoperability-configuration.md
107107
[Control-Analysis]:https://docs.microsoft.com/azure/networking/connectivty-interoperability-control-plane
108-
[Data-Analysis]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-data-plane
109-
[ExR-FAQ]: https://docs.microsoft.com/azure/expressroute/expressroute-faqs
110-
[S2S-Over-ExR]: https://docs.microsoft.com/azure/expressroute/site-to-site-vpn-over-microsoft-peering
111-
[ExR-S2S-CoEx]: https://docs.microsoft.com/azure/expressroute/expressroute-howto-coexist-resource-manager
112-
[Hub-n-Spoke]: https://docs.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/hub-spoke
113-
[Deploy-NVA]: https://docs.microsoft.com/azure/architecture/reference-architectures/dmz/nva-ha
114-
[VNet-Config]: https://docs.microsoft.com/azure/virtual-network/virtual-network-manage-peering
115-
116-
108+
[Data-Analysis]: ./connectivty-interoperability-data-plane.md
109+
[ExR-FAQ]: ../expressroute/expressroute-faqs.md
110+
[S2S-Over-ExR]: ../expressroute/site-to-site-vpn-over-microsoft-peering.md
111+
[ExR-S2S-CoEx]: ../expressroute/expressroute-howto-coexist-resource-manager.md
112+
[Hub-n-Spoke]: /azure/architecture/reference-architectures/hybrid-networking/hub-spoke
113+
[Deploy-NVA]: /azure/architecture/reference-architectures/dmz/nva-ha
114+
[VNet-Config]: ../virtual-network/virtual-network-manage-peering.md

‎articles/networking/connectivty-interoperability-data-plane.md

+13-15
Original file line numberDiff line numberDiff line change
@@ -562,19 +562,17 @@ See the [ExpressRoute FAQ][ExR-FAQ] to:
562562
[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"
563563

564564
<!--Link References-->
565-
[Setup]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-preface
566-
[Configuration]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-configuration
567-
[ExpressRoute]: https://docs.microsoft.com/azure/expressroute/expressroute-introduction
568-
[VPN]: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways
569-
[VNet]: https://docs.microsoft.com/azure/virtual-network/tutorial-connect-virtual-networks-portal
570-
[Configuration]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-configuration
565+
[Setup]: ./connectivty-interoperability-preface.md
566+
[Configuration]: ./connectivty-interoperability-configuration.md
567+
[ExpressRoute]: ../expressroute/expressroute-introduction.md
568+
[VPN]: ../vpn-gateway/vpn-gateway-about-vpngateways.md
569+
[VNet]: ../virtual-network/tutorial-connect-virtual-networks-portal.md
570+
[Configuration]: ./connectivty-interoperability-configuration.md
571571
[Control-Analysis]:https://docs.microsoft.com/azure/networking/connectivty-interoperability-control-plane
572-
[Data-Analysis]: https://docs.microsoft.com/azure/networking/connectivty-interoperability-data-plane
573-
[ExR-FAQ]: https://docs.microsoft.com/azure/expressroute/expressroute-faqs
574-
[S2S-Over-ExR]: https://docs.microsoft.com/azure/expressroute/site-to-site-vpn-over-microsoft-peering
575-
[ExR-S2S-CoEx]: https://docs.microsoft.com/azure/expressroute/expressroute-howto-coexist-resource-manager
576-
[Hub-n-Spoke]: https://docs.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/hub-spoke
577-
[Deploy-NVA]: https://docs.microsoft.com/azure/architecture/reference-architectures/dmz/nva-ha
578-
[VNet-Config]: https://docs.microsoft.com/azure/virtual-network/virtual-network-manage-peering
579-
580-
572+
[Data-Analysis]:
573+
[ExR-FAQ]: ../expressroute/expressroute-faqs.md
574+
[S2S-Over-ExR]: ../expressroute/site-to-site-vpn-over-microsoft-peering.md
575+
[ExR-S2S-CoEx]: ../expressroute/expressroute-howto-coexist-resource-manager.md
576+
[Hub-n-Spoke]: /azure/architecture/reference-architectures/hybrid-networking/hub-spoke
577+
[Deploy-NVA]: /azure/architecture/reference-architectures/dmz/nva-ha
578+
[VNet-Config]: ../virtual-network/virtual-network-manage-peering.md

‎articles/networking/connectivty-interoperability-preface.md

+8-10
Original file line numberDiff line numberDiff line change
@@ -82,16 +82,14 @@ See the [ExpressRoute FAQ][ExR-FAQ] to:
8282
[1]: ./media/backend-interoperability/TestSetup.png "Diagram of the test topology"
8383

8484
<!--Link References-->
85-
[ExpressRoute]: https://docs.microsoft.com/azure/expressroute/expressroute-introduction
86-
[VPN]: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways
87-
[VNet]: https://docs.microsoft.com/azure/virtual-network/tutorial-connect-virtual-networks-portal
85+
[ExpressRoute]: ../expressroute/expressroute-introduction.md
86+
[VPN]: ../vpn-gateway/vpn-gateway-about-vpngateways.md
87+
[VNet]: ../virtual-network/tutorial-connect-virtual-networks-portal.md
8888
[Configuration]: connectivty-interoperability-configuration.md
8989
[Control-Analysis]: connectivty-interoperability-control-plane.md
9090
[Data-Analysis]: connectivty-interoperability-data-plane.md
91-
[ExR-FAQ]: https://docs.microsoft.com/azure/expressroute/expressroute-faqs
92-
[S2S-Over-ExR]: https://docs.microsoft.com/azure/expressroute/site-to-site-vpn-over-microsoft-peering
93-
[ExR-S2S-CoEx]: https://docs.microsoft.com/azure/expressroute/expressroute-howto-coexist-resource-manager
94-
[Hub-n-Spoke]: https://docs.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/hub-spoke
95-
[Deploy-NVA]: https://docs.microsoft.com/azure/architecture/reference-architectures/dmz/nva-ha
96-
97-
91+
[ExR-FAQ]: ../expressroute/expressroute-faqs.md
92+
[S2S-Over-ExR]: ../expressroute/site-to-site-vpn-over-microsoft-peering.md
93+
[ExR-S2S-CoEx]: ../expressroute/expressroute-howto-coexist-resource-manager.md
94+
[Hub-n-Spoke]: /azure/architecture/reference-architectures/hybrid-networking/hub-spoke
95+
[Deploy-NVA]: /azure/architecture/reference-architectures/dmz/nva-ha

‎articles/networking/disaster-recovery-dns-traffic-manager.md

+3-12
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Most enterprise customers are choosing a multi-region architecture for resilienc
4141

4242
*Figure: Active/Passive with warm standby disaster recovery configuration*
4343

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).
4545

4646

4747
## Planning your disaster recovery architecture
@@ -50,7 +50,7 @@ There are two technical aspects towards setting up your disaster recovery archit
5050
- 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.
5151
- 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.
5252

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).
5454
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).
5555

5656
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 **
170170

171171
## Next steps
172172
- 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

Comments
 (0)
Please sign in to comment.