LinkFix: azure-docs-pr (2022-03) - 3

Author: Christopher McClister

articles/storage/blobs/storage-quickstart-blobs-nodejs.md

@@ -212,7 +212,7 @@ Step through the code in your debugger and check your [Azure portal](https://por
 
 ## Use the storage emulator
 
-This quickstart created a container and blob on the Azure cloud. You can also use the Azure Blob storage npm package to create these resources locally on the [Azure Storage emulator](/azure/storage/common/storage-use-emulator) for development and testing. 
+This quickstart created a container and blob on the Azure cloud. You can also use the Azure Blob storage npm package to create these resources locally on the [Azure Storage emulator](../common/storage-use-emulator.md) for development and testing. 
 
 ## Clean up 
 
@@ -230,4 +230,4 @@ For tutorials, samples, quickstarts, and other documentation, visit:
 
 - To learn how to deploy a web app that uses Azure Blob storage, see [Tutorial: Upload image data in the cloud with Azure Storage](./storage-upload-process-images.md?preserve-view=true&tabs=javascript)
 - To see Blob storage sample apps, continue to [Azure Blob storage package library v12 JavaScript samples](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/storage-blob/samples).
-- To learn more, see the [Azure Blob storage client library for JavaScript](https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/storage/storage-blob).
+- To learn more, see the [Azure Blob storage client library for JavaScript](https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/storage/storage-blob).

articles/storage/common/storage-introduction.md

@@ -154,7 +154,7 @@ You can access resources in a storage account by any language that can make HTTP
 - [Azure Storage REST API](/rest/api/storageservices/)
 - [Azure Storage client library for .NET](/dotnet/api/overview/azure/storage)
 - [Azure Storage client library for Java/Android](/java/api/overview/azure/storage)
-- [Azure Storage client library for Node.js](/azure/storage/blobs/reference#javascript-client-libraries)
+- [Azure Storage client library for Node.js](../blobs/reference.md#javascript-client-libraries)
 - [Azure Storage client library for Python](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/storage/azure-storage-blob)
 - [Azure Storage client library for PHP](https://github.com/Azure/azure-storage-php)
 - [Azure Storage client library for Ruby](https://github.com/Azure/azure-storage-ruby)
@@ -181,4 +181,4 @@ You can access resources in a storage account by any language that can make HTTP
 
 ## Next steps
 
-To get up and running with Azure Storage, see [Create a storage account](storage-account-create.md).
+To get up and running with Azure Storage, see [Create a storage account](storage-account-create.md).

articles/storage/index.yml

@@ -32,7 +32,7 @@ highlightedContent:
       url: ./common/storage-account-create.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
     - title: Build new Azure Storage skills with Microsoft Learn
       itemType: learn
-      url: https://aka.ms/azurestoragelearn
+      url: /users/henryyan-8971/collections/d2zmi3jdje144m
     - title: Migrate data to Azure Storage
       itemType: concept
       url: ./common/storage-migration-overview.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
@@ -172,4 +172,4 @@ additionalContent:
           - url: ../backup/backup-afs.md
             text: Back up Azure file shares
           - url: ../backup/index.yml
-            text: See more >
+            text: See more >

articles/stream-analytics/move-cluster.md

@@ -43,7 +43,7 @@ New-AzResourceGroupDeployment `
   -ResourceGroupName <name of your resource group> `
   -TemplateFile <path-to-template>
 ```
-For more information on how to deploy a template using Azure PowerShell, see [Deploy a template](https://docs.microsoft.com/azure/azure-resource-manager/management/manage-resources-powershell#deploy-a-template).
+For more information on how to deploy a template using Azure PowerShell, see [Deploy a template](../azure-resource-manager/management/manage-resources-powershell.md#deploy-a-template).
 
 ## Next steps
 

articles/synapse-analytics/overview-faq.yml

@@ -148,7 +148,7 @@ sections:
       - question: |
           Now that Azure Synapse is GA, how do I move my dedicated SQL pools that were previously standalone into Azure Synapse? 
         answer: |
-          There is no “move” or “migration” necessary. You can choose to enable new workspace features on your existing pools. If you do, there are no breaking changes, instead you’ll be able to use new features such as Synapse Studio, Spark, and serverless SQL pools. Not all features of the dedicated SQL pool in Azure Synapse workspaces apply to dedicated SQL pool (formerly SQL DW), and vice versa. To enable workspace features for an existing dedicated SQL pool (formerly SQL DW) refer to [How to enable a workspace for your dedicated SQL pool (formerly SQL DW)](/azure/synapse-analytics/sql-data-warehouse/workspace-connected-create).
+          There is no “move” or “migration” necessary. You can choose to enable new workspace features on your existing pools. If you do, there are no breaking changes, instead you’ll be able to use new features such as Synapse Studio, Spark, and serverless SQL pools. Not all features of the dedicated SQL pool in Azure Synapse workspaces apply to dedicated SQL pool (formerly SQL DW), and vice versa. To enable workspace features for an existing dedicated SQL pool (formerly SQL DW) refer to [How to enable a workspace for your dedicated SQL pool (formerly SQL DW)](./sql-data-warehouse/workspace-connected-create.md).
           
       - question: |
           What is the default deployment of dedicated SQL pools now? 
@@ -169,4 +169,4 @@ additionalContent: |
   ## Next steps
      * [Get started with Azure Synapse Analytics](get-started.md)
      * [Create a workspace](quickstart-create-workspace.md)
-     * [Use serverless SQL pool](quickstart-sql-on-demand.md)
+     * [Use serverless SQL pool](quickstart-sql-on-demand.md)

articles/synapse-analytics/whats-new-archive.md

@@ -33,7 +33,7 @@ Improvements to the Synapse Machine Learning library v0.9.5 (previously called M
 
 ### Data Integration
 
-* Data quality validation rules using Assert transformation - You can now easily add data quality, data validation, and schema validation to your Synapse ETL jobs by leveraging Assert transformation in Synapse data flows. To learn more, see the [Assert transformation in mapping data flow article](/azure/data-factory/data-flow-assert) or [the blog post](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/azure-synapse-analytics-january-update-2022/ba-p/3071681#TOCREF_8).
+* Data quality validation rules using Assert transformation - You can now easily add data quality, data validation, and schema validation to your Synapse ETL jobs by leveraging Assert transformation in Synapse data flows. To learn more, see the [Assert transformation in mapping data flow article](../data-factory/data-flow-assert.md) or [the blog post](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/azure-synapse-analytics-january-update-2022/ba-p/3071681#TOCREF_8).
 
 * Native data flow connector for Dynamics - Synapse data flows can now read and write data directly to Dynamics through the new data flow Dynamics connector. Learn more on how to [Create data sets in data flows to read, transform, aggregate, join, etc. using this article](../data-factory/connector-dynamics-crm-office-365.md) or the [blog post](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/azure-synapse-analytics-january-update-2022/ba-p/3071681#TOCREF_9). You can then write the data back into Dynamics using the built-in Synapse Spark compute.
 
@@ -181,4 +181,4 @@ The following updates are new to Azure Synapse Analytics this month.
 
 ## Next steps
 
-[Get started with Azure Synapse Analytics](get-started.md)
+[Get started with Azure Synapse Analytics](get-started.md)

articles/virtual-machines/dedicated-host-migration-guide.md

@@ -146,4 +146,4 @@ Once all VMs have been migrated from your old Dedicated Host to the target Dedic
 
 ## Help and support
 
-If you have questions, ask community experts in [Microsoft Q&A](https://aka.ms/azure-dedicated-host-qa).
+If you have questions, ask community experts in [Microsoft Q&A](/answers/topics/azure-dedicated-host.html).

articles/virtual-machines/migration-classic-resource-manager-deep-dive.md

@@ -160,7 +160,7 @@ You can find the classic deployment model and Resource Manager representations o
 | Multiple network interfaces on a VM |Network interfaces |If a VM has multiple network interfaces associated with it, each network interface becomes a top-level resource as part of the migration, along with all the properties. |
 | Load-balanced endpoint set |Load balancer |In the classic deployment model, the platform assigned an implicit load balancer for every cloud service. During migration, a new load-balancer resource is created, and the load-balancing endpoint set becomes load-balancer rules. |
 | Inbound NAT rules |Inbound NAT rules |Input endpoints defined on the VM are converted to inbound network address translation rules under the load balancer during the migration. |
-| VIP address |Public IP address with DNS name |The virtual IP address becomes a public IP address, and is associated with the load balancer. A virtual IP can only be migrated if there is an input endpoint assigned to it. To retain the IP, you can [convert it to Reserved IP](https://docs.microsoft.com/previous-versions/azure/virtual-network/virtual-networks-reserved-public-ip#reserve-the-ip-address-of-an-existing-cloud-service) before migration. There will be downtime of about 60 seconds during this change.|
+| VIP address |Public IP address with DNS name |The virtual IP address becomes a public IP address, and is associated with the load balancer. A virtual IP can only be migrated if there is an input endpoint assigned to it. To retain the IP, you can [convert it to Reserved IP](/previous-versions/azure/virtual-network/virtual-networks-reserved-public-ip#reserve-the-ip-address-of-an-existing-cloud-service) before migration. There will be downtime of about 60 seconds during this change.|
 | Virtual network |Virtual network |The virtual network is migrated, with all its properties, to the Resource Manager deployment model. A new resource group is created with the name `-migrated`. |
 | Reserved IPs |Public IP address with static allocation method |Reserved IPs associated with the load balancer are migrated, along with the migration of the cloud service or the virtual machine. Unassociated reserved IPs can be migrated using [Move-AzureReservedIP](/powershell/module/servicemanagement/azure.service/move-azurereservedip).  |
 | Public IP address per VM |Public IP address with dynamic allocation method |The public IP address associated with the VM is converted as a public IP address resource, with the allocation method set to dynamic. |
@@ -188,4 +188,4 @@ As part of migrating your resources from the classic deployment model to the Res
 * [Migrate ExpressRoute circuits and associated virtual networks from the classic to the Resource Manager deployment model](../expressroute/expressroute-migration-classic-resource-manager.md)
 * [Community tools for assisting with migration of IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-community-tools.md)
 * [Review most common migration errors](migration-classic-resource-manager-errors.md)
-* [Review the most frequently asked questions about migrating IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-faq.yml)
+* [Review the most frequently asked questions about migrating IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-faq.yml)

articles/virtual-machines/monitor-vm-reference.md

@@ -26,7 +26,7 @@ For more information, see a list of [platform metrics that are supported in Azur
 
 ## Metric dimensions
 
-For more information about metric dimensions, see [Multi-dimensional metrics](/azure/azure-monitor/essentials/data-platform-metrics#multi-dimensional-metrics).
+For more information about metric dimensions, see [Multi-dimensional metrics](../azure-monitor/essentials/data-platform-metrics.md#multi-dimensional-metrics).
 
 Azure virtual machines and virtual machine scale sets have the following dimensions that are associated with their metrics.
 

articles/virtual-machines/workloads/oracle/oracle-database-backup-strategies.md

@@ -113,13 +113,13 @@ Because Azure Files is designed to be a multi-user file share service, there are
 
 ## Azure NetApp Files
 
-The [Azure NetApp Files](/azure/azure-netapp-files/azure-netapp-files-introduction) service is a complete storage solution for Oracle Databases in Azure VMs. Built on an enterprise-class, high-performance, metered file storage, it  supports any workload type and is highly available by default. Together with the Oracle Direct NFS (dNFS) driver, Azure NetApp Files provides a highly optimized storage layer for the Oracle Database.
+The [Azure NetApp Files](../../../azure-netapp-files/azure-netapp-files-introduction.md) service is a complete storage solution for Oracle Databases in Azure VMs. Built on an enterprise-class, high-performance, metered file storage, it  supports any workload type and is highly available by default. Together with the Oracle Direct NFS (dNFS) driver, Azure NetApp Files provides a highly optimized storage layer for the Oracle Database.
 
-Azure NetApp Files provides efficient storage-based snapshots on the underlying storage system that uses a Redirect on Write (RoW) mechanism. While snapshots are extremely fast to take and restore, they only serve as a first-line-of-defence, which can account for the vast majority of the required restore operations of any given organization, which is often recovery from human error. However, snapshots are not a complete backup. To cover all backup and restore requirements, [external snapshot replicas](/azure/azure-netapp-files/cross-region-replication-introduction) and/or other [backup vaults](/azure/azure-netapp-files/backup-introduction) must be created in a (remote) geography to protect from regional outage. Read more about [how Azure NetApp Files snapshots work](/azure/azure-netapp-files/snapshots-introduction).
+Azure NetApp Files provides efficient storage-based snapshots on the underlying storage system that uses a Redirect on Write (RoW) mechanism. While snapshots are extremely fast to take and restore, they only serve as a first-line-of-defence, which can account for the vast majority of the required restore operations of any given organization, which is often recovery from human error. However, snapshots are not a complete backup. To cover all backup and restore requirements, [external snapshot replicas](../../../azure-netapp-files/cross-region-replication-introduction.md) and/or other [backup vaults](../../../azure-netapp-files/backup-introduction.md) must be created in a (remote) geography to protect from regional outage. Read more about [how Azure NetApp Files snapshots work](../../../azure-netapp-files/snapshots-introduction.md).
 
-In order to ensure the creation of database consistent snapshots the backup process must be orchestrated between the database and the storage. Azure Application Consistent Snapshot tool (AzAcSnap) is a command-line tool that enables data protection for third-party databases by handling all the orchestration required to put them into an application consistent state before taking a storage snapshot, after which it returns them to an operational state. Oracle databases are supported with AzAcSnap since [version 5.1](/azure/azure-netapp-files/azacsnap-release-notes#azacsnap-v51-preview-build-2022012585030).
+In order to ensure the creation of database consistent snapshots the backup process must be orchestrated between the database and the storage. Azure Application Consistent Snapshot tool (AzAcSnap) is a command-line tool that enables data protection for third-party databases by handling all the orchestration required to put them into an application consistent state before taking a storage snapshot, after which it returns them to an operational state. Oracle databases are supported with AzAcSnap since [version 5.1](../../../azure-netapp-files/azacsnap-release-notes.md#azacsnap-v51-preview-build-2022012585030).
 
-To learn more about using Azure NetApp Files for Oracle Databases on Azure, read more [here](/azure/azure-netapp-files/azure-netapp-files-solution-architectures#oracle).
+To learn more about using Azure NetApp Files for Oracle Databases on Azure, read more [here](../../../azure-netapp-files/azure-netapp-files-solution-architectures.md#oracle).
 
 ## Azure Backup service
 
@@ -142,4 +142,4 @@ Azure Backup is now providing an [enhanced pre-script and post-script framework]
 
 - [Create Oracle Database quickstart](oracle-database-quick-create.md)
 - [Back up Oracle Database to Azure Files](oracle-database-backup-azure-storage.md)
-- [Back up Oracle Database using Azure Backup service](oracle-database-backup-azure-backup.md)
+- [Back up Oracle Database using Azure Backup service](oracle-database-backup-azure-backup.md)

articles/virtual-machines/workloads/sap/sap-rise-integration.md

@@ -32,13 +32,13 @@ A vnet peering is the most performant way to connect securely and privately two
 
 For SAP RISE/ECS deployments, virtual peering is the preferred way to establish connectivity with customer’s existing Azure environment. Both the SAP vnet and customer vnet(s) are protected with network security groups (NSG), enabling communication on SAP and database ports through the vnet peering. Communication between the peered vnets is secured through these NSGs, limiting communication to customer’s  SAP environment. For details and a list of open ports, contact your SAP representative.
 
-SAP managed workload is preferably deployed in the same [Azure region](https://azure.microsoft.com/global-infrastructure/geographies/) as customer’s central infrastructure and applications accessing it. Virtual network peering can be set up within the same region as your SAP managed environment, but also through [global virtual network peering](/azure/virtual-network/virtual-network-peering-overview) between any two Azure regions. With SAP RISE/ECS available in many Azure regions, the region ideally should be matched with workload running in customer vnets due to latency and vnet peering cost considerations. However, some of the scenarios (for example, central S/4HANA deployment for a multi-national, globally presented company) also require to peer networks globally.
+SAP managed workload is preferably deployed in the same [Azure region](https://azure.microsoft.com/global-infrastructure/geographies/) as customer’s central infrastructure and applications accessing it. Virtual network peering can be set up within the same region as your SAP managed environment, but also through [global virtual network peering](../../../virtual-network/virtual-network-peering-overview.md) between any two Azure regions. With SAP RISE/ECS available in many Azure regions, the region ideally should be matched with workload running in customer vnets due to latency and vnet peering cost considerations. However, some of the scenarios (for example, central S/4HANA deployment for a multi-national, globally presented company) also require to peer networks globally.
 
 :::image type="complex" source="./media/sap-rise-integration/sap-rise-peering.png" alt-text="Customer peering with SAP RISE/ECS":::
    This diagram shows a typical SAP customer's hub and spoke virtual networks. Cross-tenant virtual network peering connects SAP RISE vnet to customer's hub vnet.
 :::image-end:::
 
-Since SAP RISE/ECS runs in SAP’s Azure tenant and subscriptions, the virtual network peering needs to be set up between [different tenants](/azure/virtual-network/create-peering-different-subscriptions). This can be accomplished by setting up the peering with the SAP provided network’s Azure resource ID and have SAP approve the peering. Add a user from the opposite AAD tenant as a guest user, accept the guest user invitation and follow process documented at [Create a VNet peering - different subscriptions](/azure/virtual-network/create-peering-different-subscriptions#cli). Contact your SAP representative for the exact steps required. Engage the respective team(s) within your organization that deal with network, user administration and architecture to enable this process to be completed swiftly.
+Since SAP RISE/ECS runs in SAP’s Azure tenant and subscriptions, the virtual network peering needs to be set up between [different tenants](../../../virtual-network/create-peering-different-subscriptions.md). This can be accomplished by setting up the peering with the SAP provided network’s Azure resource ID and have SAP approve the peering. Add a user from the opposite AAD tenant as a guest user, accept the guest user invitation and follow process documented at [Create a VNet peering - different subscriptions](../../../virtual-network/create-peering-different-subscriptions.md#cli). Contact your SAP representative for the exact steps required. Engage the respective team(s) within your organization that deal with network, user administration and architecture to enable this process to be completed swiftly.
 
 ## VPN Vnet-to-Vnet
 
@@ -64,7 +64,7 @@ With this architecture, central policies and security rules governing network co
 
 If there's no currently existing Azure to on-premise connectivity, contact your SAP representative for details which connections models are possible to be established. Any on-premise to SAP RISE/ECS connection is then for reaching the SAP managed vnet only. The on-premise to SAP RISE/ECS connection isn't used to access customer's own Azure vnets.
 
-**Important to note**: A virtual network can have [only have one gateway](/azure/virtual-network/virtual-network-peering-overview#gateways-and-on-premises-connectivity), local or remote. With vnet peering established between SAP RISE/ECS using remote gateway transit like in above architecture, no gateways can be added in the SAP RISE/ECS vnet. A combination of vnet peering with remote gateway transit together with another VPN gateway in the SAP RISE/ECS vnet isn't possible.
+**Important to note**: A virtual network can have [only have one gateway](../../../virtual-network/virtual-network-peering-overview.md#gateways-and-on-premises-connectivity), local or remote. With vnet peering established between SAP RISE/ECS using remote gateway transit like in above architecture, no gateways can be added in the SAP RISE/ECS vnet. A combination of vnet peering with remote gateway transit together with another VPN gateway in the SAP RISE/ECS vnet isn't possible.
 
 ## Virtual WAN with SAP RISE/ECS managed workloads
 
@@ -129,5 +129,5 @@ See a series of blog posts on the architecture of the SAP BTP Private Link Servi
 Check out the documentation:
 
 - [SAP workloads on Azure: planning and deployment checklist](./sap-deployment-checklist.md)
-- [Virtual network peering](/azure/virtual-network/virtual-network-peering-overview)
+- [Virtual network peering](../../../virtual-network/virtual-network-peering-overview.md)
 - [Public endpoint connectivity for Virtual Machines using Azure Standard Load Balancer in SAP high-availability scenarios](./high-availability-guide-standard-load-balancer-outbound-connections.md)

articles/virtual-network/create-vm-accelerated-networking-cli.md

@@ -178,7 +178,7 @@ Accelerated Networking is now enabled for your VM.
 ## Handle dynamic binding and revocation of virtual function 
 Applications must run over the synthetic NIC that is exposed in VM. If the application runs directly over the VF NIC, it doesn't receive **all** packets that are destined to the VM, since some packets show up over the synthetic interface. If you run an application over the synthetic NIC, it guarantees that the application receives **all** packets that are destined to it. It also makes sure that the application keeps running, even if the VF is revoked during host servicing. Applications binding to the synthetic NIC is a **mandatory** requirement for all applications taking advantage of **Accelerated Networking**.
 
-For more details on application binding requirements, see [How Accelerated Networking works in Linux and FreeBSD VMs](/azure/virtual-network/accelerated-networking-how-it-works#application-usage).
+For more details on application binding requirements, see [How Accelerated Networking works in Linux and FreeBSD VMs](./accelerated-networking-how-it-works.md#application-usage).
 
 ## Enable Accelerated Networking on existing VMs
 If you've created a VM without Accelerated Networking, it's possible to enable this feature on an existing VM. The VM must support Accelerated Networking by meeting the following prerequisites that are also outlined:
@@ -264,5 +264,4 @@ A VM with Accelerated Networking enabled can't be resized to a VM instance that
 ## Next steps
 * Learn [how Accelerated Networking works](./accelerated-networking-how-it-works.md)
 * Learn how to [create a VM with Accelerated Networking in PowerShell](../virtual-network/create-vm-accelerated-networking-powershell.md)
-* Improve latency with an [Azure proximity placement group](../virtual-machines/co-location.md)
-
+* Improve latency with an [Azure proximity placement group](../virtual-machines/co-location.md)

articles/virtual-network/nat-gateway/troubleshoot-nat.md

@@ -70,7 +70,7 @@ NAT gateway is not compatible with basic resources, such as Basic Load Balancer
 
 ### NAT gateway cannot be attached to a gateway subnet
 
-NAT gateway cannot be deployed in a gateway subnet. VPN gateway uses gateway subnets for VPN connections between site-to-site Azure virtual networks and local networks or between two Azure virtual networks. See [VPN gateway overview](/azure/vpn-gateway/vpn-gateway-about-vpngateways) to learn more about how gateway subnets are used.
+NAT gateway cannot be deployed in a gateway subnet. VPN gateway uses gateway subnets for VPN connections between site-to-site Azure virtual networks and local networks or between two Azure virtual networks. See [VPN gateway overview](../../vpn-gateway/vpn-gateway-about-vpngateways.md) to learn more about how gateway subnets are used.
 
 ### IPv6 coexistence
 
@@ -102,7 +102,7 @@ NAT gateway has a configurable TCP idle timeout timer that defaults to 4 minutes
 
 | Scenario | Evidence | Mitigation |
 |---|---|---|
-| You would like to ensure that TCP connections stay active for long periods of time without idle timing out so you increase the TCP idle timeout timer setting. After a while you start to notice that connection failures occur more often. You suspect that you may be exhausting your inventory of SNAT ports since connections are holding on to them longer. | You check the following [NAT gateway metrics](nat-metrics.md) in Azure Monitor to determine if SNAT port exhaustion is happening: **Total SNAT Connection**: "Sum" aggregation shows high connection volume. "Failed" connection state shows transient or persistent failures over time. **Dropped Packets**: "Sum" aggregation shows packets dropping consistent with high connection volume. | You have a few possible mitigation steps that you can take to resolve SNAT port exhaustion: - **Reduce the TCP idle timeout** to a lower value to free up SNAT port inventory earlier. The TCP idle timeout timer cannot be set lower than 4 minutes. - Consider **[asynchronous polling patterns](/azure/architecture/patterns/async-request-reply)** to free up connection resources for other operations. - **Use TCP keepalives or application layer keepalives** to avoid intermediate systems timing out. For examples, see [.NET examples](/dotnet/api/system.net.servicepoint.settcpkeepalive). - For connections going to Azure PaaS services, use **[Private Link](/azure/private-link/private-link-overview)**. Private Link eliminates the need to use public IPs of your NAT gateway which frees up more SNAT ports for outbound connections to the internet.|
+| You would like to ensure that TCP connections stay active for long periods of time without idle timing out so you increase the TCP idle timeout timer setting. After a while you start to notice that connection failures occur more often. You suspect that you may be exhausting your inventory of SNAT ports since connections are holding on to them longer. | You check the following [NAT gateway metrics](nat-metrics.md) in Azure Monitor to determine if SNAT port exhaustion is happening: **Total SNAT Connection**: "Sum" aggregation shows high connection volume. "Failed" connection state shows transient or persistent failures over time. **Dropped Packets**: "Sum" aggregation shows packets dropping consistent with high connection volume. | You have a few possible mitigation steps that you can take to resolve SNAT port exhaustion: - **Reduce the TCP idle timeout** to a lower value to free up SNAT port inventory earlier. The TCP idle timeout timer cannot be set lower than 4 minutes. - Consider **[asynchronous polling patterns](/azure/architecture/patterns/async-request-reply)** to free up connection resources for other operations. - **Use TCP keepalives or application layer keepalives** to avoid intermediate systems timing out. For examples, see [.NET examples](/dotnet/api/system.net.servicepoint.settcpkeepalive). - For connections going to Azure PaaS services, use **[Private Link](../../private-link/private-link-overview.md)**. Private Link eliminates the need to use public IPs of your NAT gateway which frees up more SNAT ports for outbound connections to the internet.|
 
 ## Connection failures due to idle timeouts
 
@@ -176,21 +176,21 @@ Once the custom UDR is removed from the routing table, the NAT gateway public IP
 
 ### Private IPs are used to connect to Azure services by Private Link
 
-[Private Link](/azure/private-link/private-link-overview) connects your Azure virtual networks privately to Azure PaaS services such as Storage, SQL, or Cosmos DB over the Azure backbone network instead of over the internet. Private Link uses the private IP addresses of virtual machine instances in your virtual network to connect to these Azure platform services instead of the public IP of NAT gateway. As a result, when looking at the source IP address used to connect to these Azure services, you will notice that the private IPs of your instances are used. See [Azure services listed here](/azure/private-link/availability) for all services supported by Private Link.   
+[Private Link](../../private-link/private-link-overview.md) connects your Azure virtual networks privately to Azure PaaS services such as Storage, SQL, or Cosmos DB over the Azure backbone network instead of over the internet. Private Link uses the private IP addresses of virtual machine instances in your virtual network to connect to these Azure platform services instead of the public IP of NAT gateway. As a result, when looking at the source IP address used to connect to these Azure services, you will notice that the private IPs of your instances are used. See [Azure services listed here](../../private-link/availability.md) for all services supported by Private Link.   
 
 When possible, Private Link should be used to connect directly from your virtual networks to Azure platform services in order to [reduce the demand on SNAT ports](#tcp-idle-timeout-timers-set-higher-than-the-default-value). Reducing the demand on SNAT ports can help reduce the risk of SNAT port exhaustion. 
 
 To create a Private Link, see the following Quickstart guides to get started: 
-- [Create a Private Endpoint](/azure/private-link/create-private-endpoint-portal)
-- [Create a Private Link](/azure/private-link/create-private-link-service-portal)
+- [Create a Private Endpoint](../../private-link/create-private-endpoint-portal.md)
+- [Create a Private Link](../../private-link/create-private-link-service-portal.md)
 
 To check which Private Endpoints you have set up with Private Link:
 1. From the Azure portal, search for Private Link in the search box.
-2. In the Private Link center, select Private Endpoints or Private Link services to see what configurations have been set up. See [Manage private endpoint connections](/azure/private-link/manage-private-endpoint#manage-private-endpoint-connections-on-azure-paas-resources) for more details.
+2. In the Private Link center, select Private Endpoints or Private Link services to see what configurations have been set up. See [Manage private endpoint connections](../../private-link/manage-private-endpoint.md#manage-private-endpoint-connections-on-azure-paas-resources) for more details.
 
 Service endpoints can also be used to connect your virtual network to Azure PaaS services. To check if you have service endpoints configured for your virtual network:
 1. From the Azure portal, navigate to your virtual network and select "Service endpoints" from Settings.
-2. All Service endpoints created will be listed along with which subnets they are configured. See [logging and troubleshooting Service endpoints](/azure/virtual-network/virtual-network-service-endpoints-overview#logging-and-troubleshooting) for more details.
+2. All Service endpoints created will be listed along with which subnets they are configured. See [logging and troubleshooting Service endpoints](../virtual-network-service-endpoints-overview.md#logging-and-troubleshooting) for more details.
 
 >[!NOTE]
 >Private Link is the recommended option over Service endpoints for private access to Azure hosted services.
@@ -244,4 +244,4 @@ To learn more about NAT gateway, see:
 
 * [Virtual Network NAT](nat-overview.md)
 * [NAT gateway resource](nat-gateway-resource.md)
-* [Metrics and alerts for NAT gateway resources](nat-metrics.md).
+* [Metrics and alerts for NAT gateway resources](nat-metrics.md).

articles/virtual-network/setup-dpdk.md

@@ -57,7 +57,7 @@ All Azure regions support DPDK.
 
 Accelerated networking must be enabled on a Linux virtual machine. The virtual machine should have at least two network interfaces, with one interface for management. Enabling Accelerated networking on management interface is not recommended. Learn how to [create a Linux virtual machine with accelerated networking enabled](create-vm-accelerated-networking-cli.md).
 
-On virtual machines that are using InfiniBand, ensure the appropriate `mlx4_ib` or `mlx5_ib` drivers are loaded, see [Enable InfiniBand](/azure/virtual-machines/workloads/hpc/enable-infiniband).
+On virtual machines that are using InfiniBand, ensure the appropriate `mlx4_ib` or `mlx5_ib` drivers are loaded, see [Enable InfiniBand](../virtual-machines/workloads/hpc/enable-infiniband.md).
 
 ## Install DPDK via system package (recommended)
 
@@ -282,4 +282,4 @@ When you're running the previous commands on a virtual machine, change *IP_SRC_A
 
 * [EAL options](https://dpdk.org/doc/guides/testpmd_app_ug/run_app.html#eal-command-line-options)
 * [Testpmd commands](https://dpdk.org/doc/guides/testpmd_app_ug/run_app.html#testpmd-command-line-options)
-* [Packet dump commands](https://doc.dpdk.org/guides/tools/pdump.html#pdump-tool)
+* [Packet dump commands](https://doc.dpdk.org/guides/tools/pdump.html#pdump-tool)

articles/virtual-network/virtual-networks-faq.md

@@ -499,4 +499,4 @@ For more information, see [FAQ about classic to Azure Resource Manager migration
 
 ### How can I report an issue? 
 
-You can post your questions about your migration issues to the [Microsoft Q&A](https://aka.ms/AAflal1) page. It's recommended that you post all your questions on this forum. If you have a support contract, you can also file a support request.
+You can post your questions about your migration issues to the [Microsoft Q&A](/answers/topics/azure-virtual-network.html) page. It's recommended that you post all your questions on this forum. If you have a support contract, you can also file a support request.

includes/azure-load-testing-role-assignment.md

@@ -10,7 +10,7 @@ ms.topic: "include"
 ms.date: 02/15/2022
 ---
 
-Before you can manage load tests in the Azure Load Testing resource, you need to have the right access permissions. [Azure role-based access control (Azure RBAC)](/azure/role-based-access-control/overview) is used to manage access to Azure resources, such as the ability to create new resources or use existing ones.
+Before you can manage load tests in the Azure Load Testing resource, you need to have the right access permissions. [Azure role-based access control (Azure RBAC)](../articles/role-based-access-control/overview.md) is used to manage access to Azure resources, such as the ability to create new resources or use existing ones.
 
 1. In the [Azure portal](https://portal.azure.com), go to your Azure Load Testing resource.
 
@@ -25,4 +25,4 @@ Before you can manage load tests in the Azure Load Testing resource, you need to
     :::image type="content" source="media/azure-load-testing-role-assignment/add-role-assignment.png" alt-text="Screenshot that shows the role assignment screen.":::
 
     > [!IMPORTANT]
-    > To assign Azure roles, you must have `Microsoft.Authorization/roleAssignments/write` permissions, such as [User Access Administrator](../articles/role-based-access-control/built-in-roles.md#user-access-administrator) or [Owner](../articles/role-based-access-control/built-in-roles.md#owner).
+    > To assign Azure roles, you must have `Microsoft.Authorization/roleAssignments/write` permissions, such as [User Access Administrator](../articles/role-based-access-control/built-in-roles.md#user-access-administrator) or [Owner](../articles/role-based-access-control/built-in-roles.md#owner).

includes/functions-bindings-blob-storage-usage-csharp.md

@@ -104,6 +104,6 @@ The following parameter types are extension version-specific and require you to
 
 ---
 
-Binding to `string`, or `Byte[]` is only recommended when the blob size is small. This is recommended because the entire blob contents are loaded into memory. For most blobs, use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](/azure/azure-functions/functions-bindings-storage-blob-trigger#concurrency-and-memory-usage).
+Binding to `string`, or `Byte[]` is only recommended when the blob size is small. This is recommended because the entire blob contents are loaded into memory. For most blobs, use a `Stream` or `CloudBlockBlob` type. For more information, see [Concurrency and memory usage](../articles/azure-functions/functions-bindings-storage-blob-trigger.md#concurrency-and-memory-usage).
 
-If you get an error message when trying to bind to one of the Storage SDK types, make sure that you have a reference to [the correct Storage SDK version](/azure/azure-functions/functions-bindings-storage-blob#tabpanel_2_functionsv1_in-process).
+If you get an error message when trying to bind to one of the Storage SDK types, make sure that you have a reference to [the correct Storage SDK version](../articles/azure-functions/functions-bindings-storage-blob.md#tabpanel_2_functionsv1_in-process).