Merge pull request #179764 from pritamso/Broken-link-fix-duongau

Court72 · web-flow · commit 5de83b1bba44 · 2021-11-18T10:29:59.000-07:00
Broken link fix
diff --git a/articles/frontdoor/standard-premium/concept-origin.md b/articles/frontdoor/standard-premium/concept-origin.md
@@ -81,7 +81,7 @@ Azure Front Door Standard/Premium sends periodic HTTP/HTTPS probe requests to ea
     >[!NOTE]
     >For faster failovers, set the interval to a lower value. The lower the value, the higher the health probe volume your backends receive. For example, if the interval is set to 30 seconds with say, 100 Front Door POPs globally, each backend will receive about 200 probe requests per minute.
 
-For more information, see [Health probes](concept-health-probes.md).
+For more information, see [Health probes](/azure/frontdoor/front-door-health-probes).
 
 ### Load-balancing settings
 
@@ -105,7 +105,7 @@ There are four traffic routing methods available in Azure Front Door Standard/Pr
 * **[Priority](#priority):** You can assign priorities to your backends when you want to configure a primary backend to service all traffic. The secondary backend can be a backup in case the primary backend becomes unavailable.
 * **[Weighted](#weighted):** You can assign weights to your backends when you want to distribute traffic across a set of backends. Whether you want to evenly distribute or according to the weight coefficients.
 
-All Azure Front Door Standard/Premium configurations include monitoring of backend health and automated instant global failover. For more information, see [Backend Monitoring](concept-health-probes.md). Your Front Door can work based off of a single routing method. But depending on your application needs, you can also combine multiple routing methods to build an optimal routing topology.
+All Azure Front Door Standard/Premium configurations include monitoring of backend health and automated instant global failover. For more information, see [Backend Monitoring](/azure/frontdoor/front-door-health-probes). Your Front Door can work based off of a single routing method. But depending on your application needs, you can also combine multiple routing methods to build an optimal routing topology.
 
 ### <a name = "latency"></a>Lowest latencies based traffic-routing
 
diff --git a/articles/frontdoor/standard-premium/index.yml b/articles/frontdoor/standard-premium/index.yml
@@ -64,7 +64,7 @@ landingContent:
           - text: Origin
             url: concept-origin.md
           - text: Health probes
-            url: concept-health-probes.md
+            url: /azure/frontdoor/front-door-health-probes
       - linkListType: how-to-guide
         links:
           - text: Configure an Origin Group
@@ -96,7 +96,7 @@ landingContent:
           - text: WAF on Azure Front Door Standard/Premium
             url: ../../web-application-firewall/afds/afds-overview.md
           - text: DDoS protection
-            url: concept-ddos.md
+            url: /azure/frontdoor/front-door-ddos
       - linkListType: how-to-guide
         links:
           - text: Enable Private Link
diff --git a/articles/frontdoor/standard-premium/overview.md b/articles/frontdoor/standard-premium/overview.md
@@ -48,7 +48,7 @@ Key features included with Azure Front Door Standard/Premium (Preview):
 
 - Accelerated application performance by using **[split TCP-based](../front-door-routing-architecture.md#splittcp)** anycast protocol.
 
-- Intelligent **[health probe](concept-health-probes.md)** monitoring and load balancing among **[origins](concept-origin.md)**.
+- Intelligent **[health probe](/azure/frontdoor/front-door-health-probes)** monitoring and load balancing among **[origins](concept-origin.md)**.
 
 - Define your own **[custom domain](how-to-add-custom-domain.md)** with flexible domain validation.
 
diff --git a/articles/virtual-network-manager/create-virtual-network-manager-powershell.md b/articles/virtual-network-manager/create-virtual-network-manager-powershell.md
@@ -44,7 +44,7 @@ Install-Module -Name Az.Network -AllowPrerelease
 
 ## Create Virtual Network Manager
 
-1. Define the scope and access type this Azure Virtual Network Manager instance will have. You can choose to create the scope with subscriptions group or management group or a combination of both. Create the scope by using [New-AzNetworkManagerScope](/powershell/module/az.network/new-aznetworkmanagerscope).
+1. Define the scope and access type this Azure Virtual Network Manager instance will have. You can choose to create the scope with subscriptions group or management group or a combination of both. Create the scope by using New-AzNetworkManagerScope.
 
     ```azurepowershell-interactive
     [System.Collections.Generic.List[string]]$subGroup = @()  
@@ -59,7 +59,7 @@ Install-Module -Name Az.Network -AllowPrerelease
     $scope = New-AzNetworkManagerScope -Subscription $subGroup  -ManagementGroup $mgGroup
     ```
 
-1. Create the Virtual Network Manager with [New-AzNetworkManager](/powershell/module/az.network/new-aznetworkmanager). This example creates an Azure Virtual Network Manager named **myAVNM** in the West US location.
+1. Create the Virtual Network Manager with New-AzNetworkManager. This example creates an Azure Virtual Network Manager named **myAVNM** in the West US location.
 
     ```azurepowershell-interactive
     $avnm = @{
@@ -150,7 +150,7 @@ $virtualnetworkC | Set-AzVirtualNetwork
 
 ### Static membership
 
-1. Create a static virtual network member with [New-AzNetworkManagerGroupMembersItem](/powershell/module/az.network/new-aznetworkmanagergroupmembersitem).
+1. Create a static virtual network member with New-AzNetworkManagerGroupMembersItem.
 
     ```azurepowershell-interactive
     $member = New-AzNetworkManagerGroupMembersItem –ResourceId "/subscriptions/abcdef12-3456-7890-abcd-ef1234567890/resourceGroups/myAVNMResourceGroup/providers/Microsoft.Network/virtualNetworks/VNetA"
@@ -178,7 +178,7 @@ $virtualnetworkC | Set-AzVirtualNetwork
     }' 
     ```
 
-1. Create the network group using the conditional statement defined in the last step using [New-AzNetworkManagerGroup](/powershell/module/az.network/new-aznetworkmanagergroup).
+1. Create the network group using the conditional statement defined in the last step using New-AzNetworkManagerGroup.
 
     ```azurepowershell-interactive
     $ng = @{
@@ -194,7 +194,7 @@ $virtualnetworkC | Set-AzVirtualNetwork
 
 ## Create a configuration
 
-1. Create a connectivity group item to add a network group to with [New-AzNetworkManagerConnectivityGroupItem](/powershell/module/az.network/new-aznetworkmanagerconnectivitygroupitem).
+1. Create a connectivity group item to add a network group to with New-AzNetworkManagerConnectivityGroupItem.
 
     ```azurepowershell-interactive
     $gi = @{
@@ -210,7 +210,7 @@ $virtualnetworkC | Set-AzVirtualNetwork
     $configGroup.Add($groupItem)
     ```
 
-1. Create the connectivity configuration with [New-AzNetworkManagerConnectivityConfiguration](/powershell/module/az.network/new-aznetworkmanagerconnectivityconfiguration).
+1. Create the connectivity configuration with New-AzNetworkManagerConnectivityConfiguration.
 
     ```azurepowershell-interactive
     $config = @{
@@ -225,7 +225,7 @@ $virtualnetworkC | Set-AzVirtualNetwork
 
 ## Commit deployment
 
-Commit the configuration to the target regions with [Deploy-AzNetworkManagerCommit](/powershell/module/az.network/deploy-aznetworkmanagercommit).
+Commit the configuration to the target regions with Deploy-AzNetworkManagerCommit.
 
 ```azurepowershell-interactive
 [System.Collections.Generic.List[string]]$configIds = @()  
@@ -251,7 +251,7 @@ If you no longer need the Azure Virtual Network Manager, you'll need to make sur
 * All configurations have been deleted.
 * All network groups have been deleted.
 
-1. Remove the connectivity deployment by deploying an empty configuration with [Deploy-AzNetworkManagerCommit](/powershell/module/az.network/deploy-aznetworkmanagercommit).
+1. Remove the connectivity deployment by deploying an empty configuration with Deploy-AzNetworkManagerCommit.
 
     ```azurepowershell-interactive
     [System.Collections.Generic.List[string]]$configIds = @()
@@ -267,7 +267,7 @@ If you no longer need the Azure Virtual Network Manager, you'll need to make sur
     Deploy-AzNetworkManagerCommit @removedeployment
     ```
 
-1. Remove the connectivity configuration with [Remove-AzNetworkManagerConnectivityConfiguration](/powershell/module/az.network/remove-aznetworkmanagerconnectivityconfiguration)
+1. Remove the connectivity configuration with Remove-AzNetworkManagerConnectivityConfiguration
 
     ```azurepowershell-interactive
     $removeconfig = @{
@@ -278,7 +278,7 @@ If you no longer need the Azure Virtual Network Manager, you'll need to make sur
     Remove-AzNetworkManagerConnectivityConfiguration @removeconfig   
     ```
 
-1. Remove the network group with [Remove-AzNetworkManagerGroup](/powershell/module/az.network/remove-aznetworkmanagergroup).
+1. Remove the network group with Remove-AzNetworkManagerGroup.
 
     ```azurepowershell-interactive
     $removegroup = @{
@@ -289,7 +289,7 @@ If you no longer need the Azure Virtual Network Manager, you'll need to make sur
     Remove-AzNetworkManagerGroup @removegroup
     ```
 
-1. Delete the network manager instance with [Remove-AzNetworkManager](/powershell/module/az.network/remove-aznetworkmanager).
+1. Delete the network manager instance with Remove-AzNetworkManager.
 
     ```azurepowershell-interactive
     $removenetworkmanager = @{
diff --git a/articles/virtual-network-manager/how-to-block-network-traffic-powershell.md b/articles/virtual-network-manager/how-to-block-network-traffic-powershell.md
@@ -27,7 +27,7 @@ Before you start configuring security rules, confirm the following steps:
 
 ## Create a SecurityAdmin configuration
 
-1. Create a new SecurityAdmin configuration with [New-AzNetworkManagerSecurityAdminConfiguration](/powershell/module/az.network/new-aznetworkmanagersecurityadminconfiguration).
+1. Create a new SecurityAdmin configuration with New-AzNetworkManagerSecurityAdminConfiguration.
 
     ```azurepowershell-interactive
     $config = @{
@@ -38,7 +38,7 @@ Before you start configuring security rules, confirm the following steps:
     $securityconfig = New-AzNetworkManagerSecurityAdminConfiguration @config 
     ```
 
-1. Store network group to a variable with [Get-AzNetworkManagerGroup](/powershell/module/az.network/get-aznetworkmanagergroup).
+1. Store network group to a variable with Get-AzNetworkManagerGroup.
 
     ```azurepowershell-interactive
     $ng = @{
@@ -49,7 +49,7 @@ Before you start configuring security rules, confirm the following steps:
     $networkgroup = Get-AzNetworkManagerGroup @ng   
     ```
 
-1. Create a connectivity group item to add a network group to with [New-AzNetworkManagerSecurityGroupItem](/powershell/module/az.network/new-aznetworkmanagersecuritygroupitem).
+1. Create a connectivity group item to add a network group to with New-AzNetworkManagerSecurityGroupItem.
 
     ```azurepowershell-interactive
     $gi = @{
@@ -65,7 +65,7 @@ Before you start configuring security rules, confirm the following steps:
     $configGroup.Add($groupItem) 
     ```
 
-1. Create a security admin rules collection with [New-AzNetworkManagerSecurityAdminRuleCollection](/powershell/module/az.network/new-aznetworkmanagersecurityadminrulecollection).
+1. Create a security admin rules collection with New-AzNetworkManagerSecurityAdminRuleCollection.
 
     ```azurepowershell-interactive
     $collection = @{
@@ -78,7 +78,7 @@ Before you start configuring security rules, confirm the following steps:
     $rulecollection = New-AzNetworkManagerSecurityAdminRuleCollection @collection
     ```
 
-1. Define the variables for the source and destination address prefixes and ports with [New-AzNetworkManagerAddressPrefixItem](/powershell/module/az.network/new-aznetworkmanageraddressprefixitem).
+1. Define the variables for the source and destination address prefixes and ports with New-AzNetworkManagerAddressPrefixItem.
 
     ```azurepowershell-interactive
     $sourceip = @{
@@ -101,7 +101,7 @@ Before you start configuring security rules, confirm the following steps:
     $destinationPortList.Add("443”)
     ```
 
-1. Create a security rule with [New-AzNetworkManagerSecurityAdminRule](/powershell/module/az.network/new-aznetworkmanagersecurityadminrule).
+1. Create a security rule with New-AzNetworkManagerSecurityAdminRule.
 
     ```azurepowershell-interactive
     $rule = @{
@@ -124,7 +124,7 @@ Before you start configuring security rules, confirm the following steps:
 
 ## Commit deployment
 
-Commit the security configuration to target regions with [Deploy-AzNetworkManagerCommit](/powershell/module/az.network/deploy-aznetworkmanagercommit).
+Commit the security configuration to target regions with Deploy-AzNetworkManagerCommit.
 
 ```azurepowershell-interactive
 [System.Collections.Generic.List[string]]$configIds = @()  
@@ -151,7 +151,7 @@ If you no longer need the security configuration, you'll need to make sure the f
 
 ### Remove security configuration deployment
 
-Remove the security deployment by deploying a configuration with [Deploy-AzNetworkManagerCommit](/powershell/module/az.network/deploy-aznetworkmanagercommit).
+Remove the security deployment by deploying a configuration with Deploy-AzNetworkManagerCommit.
 
 ```azurepowershell-interactive
 [System.Collections.Generic.List[string]]$configIds = @()
@@ -169,7 +169,7 @@ Deploy-AzNetworkManagerCommit @removedeployment
 
 ### Remove security rules
 
-Remove security rules with [Remove-AzNetworkManagerSecurityAdminRule](/powershell/module/az.network/remove-aznetworkmanagersecurityadminrule).
+Remove security rules with Remove-AzNetworkManagerSecurityAdminRule.
 
 ```azurepowershell-interactive
 $removerule = @{
@@ -195,7 +195,7 @@ Remove-AzNetworkManagerSecurityAdminRuleCollection @removecollection
 
 ### Delete configuration
 
-Delete the security configuration with [Remove-AzNetworkManagerSecurityAdminConfiguration](/powershell/module/az.network/remove-aznetworkmanagersecurityadminconfiguration).
+Delete the security configuration with Remove-AzNetworkManagerSecurityAdminConfiguration.
 
 ```azurepowershell-interactive
 $removeconfig = @{
diff --git a/articles/virtual-network-manager/how-to-create-hub-and-spoke-powershell.md b/articles/virtual-network-manager/how-to-create-hub-and-spoke-powershell.md
@@ -30,7 +30,7 @@ This section will help you create a network group containing the virtual network
 
 ### Static membership
 
-1. Create a static virtual network member with [New-AzNetworkManagerGroupMembersItem](/powershell/module/az.network/new-aznetworkmanagergroupmembersitem).
+1. Create a static virtual network member with New-AzNetworkManagerGroupMembersItem.
 
     ```azurepowershell-interactive
     $member = New-AzNetworkManagerGroupMembersItem –ResourceId "/subscriptions/abcdef12-3456-7890-abcd-ef1234567890/resourceGroups/myAVNMResourceGroup/providers/Microsoft.Network/virtualNetworks/VNetA"
@@ -58,7 +58,7 @@ This section will help you create a network group containing the virtual network
     }' 
     ```
 
-1. Create the network group using either the static membership group (GroupMember) or the dynamic membership group (ConditionalMembership) defined previously using [New-AzNetworkManagerGroup](/powershell/module/az.network/new-aznetworkmanagergroup).
+1. Create the network group using either the static membership group (GroupMember) or the dynamic membership group (ConditionalMembership) defined previously using New-AzNetworkManagerGroup.
 
     ```azurepowershell-interactive
     $ng = @{
@@ -76,7 +76,7 @@ This section will help you create a network group containing the virtual network
 
 This section will guide you through how to create a hub-and-spoke configuration with the network group you created in the previous section.
 
-1. Create a spokes connectivity group item to add a network group with [New-AzNetworkManagerConnectivityGroupItem](/powershell/module/az.network/new-aznetworkmanagerconnectivitygroupitem). You can enable direct connectivity with the `-GroupConnectivity` flag, global mesh with `-IsGlobal` flag, or `-UseHubGateway` flag to use the gateway in the hub virtual network:
+1. Create a spokes connectivity group item to add a network group with New-AzNetworkManagerConnectivityGroupItem. You can enable direct connectivity with the `-GroupConnectivity` flag, global mesh with `-IsGlobal` flag, or `-UseHubGateway` flag to use the gateway in the hub virtual network:
 
     ```azurepowershell-interactive
     $spokes = @{
@@ -92,7 +92,7 @@ This section will guide you through how to create a hub-and-spoke configuration
     $configGroup.Add($spokesGroup) 
     ```
 
-1. Create a hub connectivity group item and define the virtual network you'll use as the hub with [New-AzNetworkManagerHub](/powershell/module/az.network/new-aznetworkmanagerhub).
+1. Create a hub connectivity group item and define the virtual network you'll use as the hub with New-AzNetworkManagerHub.
 
     ```azurepowershell-interactive
     [System.Collections.Generic.List[Microsoft.Azure.Commands.Network.Models.NetworkManager.PSNetworkManagerHub]]$hubList = @()
@@ -106,7 +106,7 @@ This section will guide you through how to create a hub-and-spoke configuration
     $hubList.Add($hubvnet)
     ```
 
-1. Create the connectivity configuration with [New-AzNetworkManagerConnectivityConfiguration](/powershell/module/az.network/new-aznetworkmanagerconnectivityconfiguration).
+1. Create the connectivity configuration with New-AzNetworkManagerConnectivityConfiguration.
 
     ```azurepowershell-interactive
     $config = @{
@@ -122,7 +122,7 @@ This section will guide you through how to create a hub-and-spoke configuration
 
 ## Deploy the hub-and-spoke configuration
 
-Commit the configuration to the target regions with [Deploy-AzNetworkManagerCommit](/powershell/module/az.network/deploy-aznetworkmanagercommit).
+Commit the configuration to the target regions with Deploy-AzNetworkManagerCommit.
 
 ```azurepowershell-interactive
 [System.Collections.Generic.List[string]]$configIds = @()  
diff --git a/articles/virtual-network-manager/how-to-create-mesh-network-powershell.md b/articles/virtual-network-manager/how-to-create-mesh-network-powershell.md
@@ -26,7 +26,7 @@ In this article, you'll learn how to create a mesh network topology with Azure V
 
 This section will help you create a network group containing the virtual networks you'll be using for the hub-and-spoke network topology.
 
-1. Create a static virtual network member with [New-AzNetworkManagerGroupMembersItem](/powershell/module/az.network/new-aznetworkmanagergroupmembersitem).
+1. Create a static virtual network member with New-AzNetworkManagerGroupMembersItem.
 
     ```azurepowershell-interactive
     $member = New-AzNetworkManagerGroupMembersItem –ResourceId "/subscriptions/abcdef12-3456-7890-abcd-ef1234567890/resourceGroups/myAVNMResourceGroup/providers/Microsoft.Network/virtualNetworks/VNetA"
@@ -54,7 +54,7 @@ This section will help you create a network group containing the virtual network
     }' 
     ```
 
-1. Create the network group using either the static membership group (GroupMember) or the dynamic membership group (ConditionalMembership) define previously using [New-AzNetworkManagerGroup](/powershell/module/az.network/new-aznetworkmanagergroup).
+1. Create the network group using either the static membership group (GroupMember) or the dynamic membership group (ConditionalMembership) define previously using New-AzNetworkManagerGroup.
 
     ```azurepowershell-interactive
     $ng = @{
@@ -72,7 +72,7 @@ This section will help you create a network group containing the virtual network
 
 This section will guide you through how to create a mesh configuration with the network group you created in the previous section.
 
-1. Create a connectivity group item to add a network group to with [New-AzNetworkManagerConnectivityGroupItem](/powershell/module/az.network/new-aznetworkmanagerconnectivitygroupitem).
+1. Create a connectivity group item to add a network group to with New-AzNetworkManagerConnectivityGroupItem.
 
     ```azurepowershell-interactive
     $gi = @{
@@ -88,7 +88,7 @@ This section will guide you through how to create a mesh configuration with the
     $configGroup.Add($groupItem)
     ```
 
-1. Create the connectivity configuration with [New-AzNetworkManagerConnectivityConfiguration](/powershell/module/az.network/new-aznetworkmanagerconnectivityconfiguration).
+1. Create the connectivity configuration with New-AzNetworkManagerConnectivityConfiguration.
 
     ```azurepowershell-interactive
     $config = @{
@@ -103,7 +103,7 @@ This section will guide you through how to create a mesh configuration with the
 
 ## Deploy the mesh configuration
 
-Commit the configuration to the target regions with [Deploy-AzNetworkManagerCommit](/powershell/module/az.network/deploy-aznetworkmanagercommit).
+Commit the configuration to the target regions with Deploy-AzNetworkManagerCommit.
 
 ```azurepowershell-interactive
 [System.Collections.Generic.List[string]]$configIds = @()  
