Merge pull request #174071 from JasonWHowell/fix-links

PRMerger16 · web-flow · commit b182f525d4d3 · 2021-09-29T20:50:45.000-07:00
Fix absolute links - docs-link-absolute suggestions
diff --git a/articles/active-directory/saas-apps/media/fortigate-ssl-vpn-tutorial/fortigate-deployment-guide-converted.md b/articles/active-directory/saas-apps/media/fortigate-ssl-vpn-tutorial/fortigate-deployment-guide-converted.md
@@ -1,7 +1,6 @@
 ---
-title: FortiGate deployment guide | Microsoft Docs
+title: FortiGate deployment guide
 description: Set up and work with the Fortinet FortiGate next-generation firewall product.
-services: active-directory
 author: jeevansd
 manager: CelesteDG
 ms.reviewer: celested
diff --git a/articles/aks/concepts-sustainable-software-engineering.md b/articles/aks/concepts-sustainable-software-engineering.md
@@ -98,4 +98,4 @@ Learn more about the features of AKS mentioned in this article:
 [node-sizing]: use-multiple-node-pools.md#specify-a-vm-size-for-a-node-pool
 [sustainability-calculator]: https://azure.microsoft.com/blog/microsoft-sustainability-calculator-helps-enterprises-analyze-the-carbon-emissions-of-their-it-infrastructure/
 [system-pools]: use-system-pools.md
-[principles-sse]: https://docs.microsoft.com/learn/modules/sustainable-software-engineering-overview/
+[principles-sse]: /learn/modules/sustainable-software-engineering-overview/
diff --git a/articles/aks/windows-faq.md b/articles/aks/windows-faq.md
@@ -2,7 +2,6 @@
 title: Windows Server node pools FAQ
 titleSuffix: Azure Kubernetes Service
 description: See the frequently asked questions when you run Windows Server node pools and application workloads in Azure Kubernetes Service (AKS).
-services: container-service
 ms.topic: article
 ms.date: 10/12/2020
 
@@ -65,7 +64,8 @@ Yes. For the implications and options that are available, see [Maximum number of
 
 If you created your cluster before February 2020 and have never done any cluster upgrade operations, the cluster still uses an old Windows image. You may have seen an error that resembles:
 
-"The following list of images referenced from the deployment template is not found: Publisher: MicrosoftWindowsServer, Offer: WindowsServer, Sku: 2019-datacenter-core-smalldisk-2004, Version: latest. Please refer to https://docs.microsoft.com/azure/virtual-machines/windows/cli-ps-findimage for instructions on finding available images."
+"The following list of images referenced from the deployment template is not found: Publisher: MicrosoftWindowsServer, Offer: WindowsServer, Sku: 2019-datacenter-core-smalldisk-2004, Version: latest. Please refer to [Find and use Azure Marketplace VM images with Azure PowerShell
+](../virtual-machines/windows/cli-ps-findimage.md) for instructions on finding available images.
 
 To fix this error:
 
@@ -193,8 +193,8 @@ To see the current time zone of the running container or an available list of ti
 While this will be supported in the WS2022 OS version, the current way to achieve session affinity by Client IP is done by limiting your desired pod to run a single instance per node and configuring your Kubernetes service to direct traffic to the pod on the local node. To achieve this, the following configuration can be used:
 1. AKS cluster running a minimum version of 1.20.
 1. Constrain your pod to allow only one instance per Windows node. This can be achieved by using anti-affinity in your deployment configuration.
-1. In your Kubernetes service configuration, set “externalTrafficPolicy=Local”. This will ensure the Kubernetes service only directs traffic to pods within the local node.
-1. In your Kubernetes service configuration, set “sessionAffinity: ClientIP”. This will ensure the Azure Load Balancer gets configured with session affinity.
+1. In your Kubernetes service configuration, set "externalTrafficPolicy=Local". This will ensure the Kubernetes service only directs traffic to pods within the local node.
+1. In your Kubernetes service configuration, set "sessionAffinity: ClientIP". This will ensure the Azure Load Balancer gets configured with session affinity.
 
 ## What if I need a feature that's not supported?
 
diff --git a/articles/azure-maps/migrate-from-google-maps-web-app.md b/articles/azure-maps/migrate-from-google-maps-web-app.md
@@ -6,7 +6,6 @@ ms.author: v-stharr
 ms.date: 12/07/2020
 ms.topic: tutorial
 ms.service: azure-maps
-services: azure-maps
 manager: cpendle
 ms.custom: devx-track-js
 ---
@@ -1679,7 +1678,7 @@ The following appendix provides a cross reference of the commonly used classes i
 |---------------|-------------|
 | `google.maps.Map` | [atlas.Map](/javascript/api/azure-maps-control/atlas.map)  |
 | `google.maps.InfoWindow` | [atlas.Popup](/javascript/api/azure-maps-control/atlas.popup)  |
-| `google.maps.InfoWindowOptions` | [atlas.PopupOptions](https://docs.microsoft.com/) |
+| `google.maps.InfoWindowOptions` | [atlas.PopupOptions](/javascript/api/azure-maps-control/atlas.popupoptions) |
 | `google.maps.LatLng`  | [atlas.data.Position](/javascript/api/azure-maps-control/atlas.data.position)  |
 | `google.maps.LatLngBounds` | [atlas.data.BoundingBox](/javascript/api/azure-maps-control/atlas.data.boundingbox) |
 | `google.maps.MapOptions`  | [atlas.CameraOptions](/javascript/api/azure-maps-control/atlas.cameraoptions)<br/>[atlas.CameraBoundsOptions](/javascript/api/azure-maps-control/atlas.cameraboundsoptions)<br/>[atlas.ServiceOptions](/javascript/api/azure-maps-control/atlas.serviceoptions)<br/>[atlas.StyleOptions](/javascript/api/azure-maps-control/atlas.styleoptions)<br/>[atlas.UserInteractionOptions](/javascript/api/azure-maps-control/atlas.userinteractionoptions) |
diff --git a/articles/azure-monitor/app/snapshot-debugger-troubleshoot.md b/articles/azure-monitor/app/snapshot-debugger-troubleshoot.md
@@ -89,7 +89,7 @@ To check the setting, open your web.config file and find the system.web section.
    ```
 
 > [!NOTE]
-> Modifying the httpRuntime targetFramework value changes the runtime quirks applied to your application and can cause other, subtle behavior changes. Be sure to test your application thoroughly after making this change. For a full list of compatibility changes, please see https://docs.microsoft.com/dotnet/framework/migration-guide/application-compatibility#retargeting-changes
+> Modifying the httpRuntime targetFramework value changes the runtime quirks applied to your application and can cause other, subtle behavior changes. Be sure to test your application thoroughly after making this change. For a full list of compatibility changes, see [Retargeting changes](/dotnet/framework/migration-guide/application-compatibility#retargeting-changes).
 
 > [!NOTE]
 > If the targetFramework is 4.7 or above then Windows determines the available protocols. In Azure App Service, TLS 1.2 is available. However, if you are using your own virtual machine, you may need to enable TLS 1.2 in the OS.
diff --git a/articles/azure-monitor/essentials/metrics-supported.md b/articles/azure-monitor/essentials/metrics-supported.md
@@ -1575,7 +1575,7 @@ The Azure Monitor Agent replaces the Azure Diagnostics extension and Log Analyti
 |---|---|---|---|---|---|---|
 |AddRegion|Yes|Region Added|Count|Count|Region Added|Region|
 |AutoscaleMaxThroughput|No|Autoscale Max Throughput|Count|Maximum|Autoscale Max Throughput|DatabaseName, CollectionName|
-|AvailableStorage|No|(deprecated) Available Storage|Bytes|Total|"Available Storage"will be removed from Azure Monitor at the end of September 2023. Cosmos DB collection storage size is now unlimited. The only restriction is that the storage size for each logical partition key is 20GB. You can enable PartitionKeyStatistics in Diagnostic Log to know the storage consumption for top partition keys. For more info about Cosmos DB storage quota, please check this doc https://docs.microsoft.com/azure/cosmos-db/concepts-limits. After deprecation, the remaining alert rules still defined on the deprecated metric will be automatically disabled post the deprecation date.|CollectionName, DatabaseName, Region|
+|AvailableStorage|No|(deprecated) Available Storage|Bytes|Total|"Available Storage"will be removed from Azure Monitor at the end of September 2023. Cosmos DB collection storage size is now unlimited. The only restriction is that the storage size for each logical partition key is 20GB. You can enable PartitionKeyStatistics in Diagnostic Log to know the storage consumption for top partition keys. For more info about Cosmos DB storage quota, please check this doc [Azure Cosmos DB service quotas](../../cosmos-db/concepts-limits.md). After deprecation, the remaining alert rules still defined on the deprecated metric will be automatically disabled post the deprecation date.|CollectionName, DatabaseName, Region|
 |CassandraConnectionClosures|No|Cassandra Connection Closures|Count|Total|Number of Cassandra connections that were closed, reported at a 1 minute granularity|APIType, Region, ClosureReason|
 |CassandraConnectorAvgReplicationLatency|No|Cassandra Connector Average ReplicationLatency|MilliSeconds|Average|Cassandra Connector Average ReplicationLatency|No Dimensions|
 |CassandraConnectorReplicationHealthStatus|No|Cassandra Connector Replication Health Status|Count|Count|Cassandra Connector Replication Health Status|NotStarted, ReplicationInProgress, Error|
diff --git a/articles/cloud-services-extended-support/swap-cloud-service.md b/articles/cloud-services-extended-support/swap-cloud-service.md
@@ -7,12 +7,11 @@ author: surbhijain
 ms.author: surbhijain
 ms.reviewer: gachandw
 ms.date: 04/01/2021
-ms.custom: 
 ---
 
 # Swap or switch deployments in Azure Cloud Services (extended support)
 
-You can swap between two independent cloud service deployments in Azure Cloud Services (extended support). Unlike in Azure Cloud Services (classic), the Azure Resource Manager model in Azure Cloud Services (extended support) doesn't use deployment slots. In Azure Cloud Services (extended support), when you deploy a new release of a cloud service, you can make the cloud service “swappable” with an existing cloud service in Azure Cloud Services (extended support).
+You can swap between two independent cloud service deployments in Azure Cloud Services (extended support). Unlike in Azure Cloud Services (classic), the Azure Resource Manager model in Azure Cloud Services (extended support) doesn't use deployment slots. In Azure Cloud Services (extended support), when you deploy a new release of a cloud service, you can make the cloud service "swappable" with an existing cloud service in Azure Cloud Services (extended support).
 
 After you swap the deployments, you can stage and test your new release by using the new cloud service deployment. In effect, swapping promotes a new cloud service that's staged to production release.
 
@@ -27,7 +26,6 @@ Upon deployment of the second cloud service, both the cloud services have their
 
 Once set, the SwappableCloudService property is treated as readonly. It cannot be deleted or changed to another value. Deleting one of the cloud services (of the swappable pair) will result in the SwappableCloudService  property of the remaining cloud service being cleared.
 
-
 ## ARM template
 
 If you use an ARM template deployment method, to make the cloud services swappable, set the `SwappableCloudService` property in `networkProfile` in the `cloudServices` object to the ID of the paired cloud service:
@@ -60,7 +58,7 @@ To save compute costs, you can delete one of the cloud services (designated as a
 
 ## REST API
 
-To use the [REST API](https://review.docs.microsoft.com/rest/api/compute/load-balancers/swap-public-ip-addresses?branch=net202102) to swap to a new cloud services deployment in Azure Cloud Services (extended support), use the following command and JSON configuration:
+To use the [REST API](/rest/api/compute/load-balancers/swap-public-ip-addresses) to swap to a new cloud services deployment in Azure Cloud Services (extended support), use the following command and JSON configuration:
 
 ```http
 POST https://management.azure.com/subscriptions/subid/providers/Microsoft.Network/locations/westus/setLoadBalancerFrontendPublicIpAddresses?api-version=2021-02-01
diff --git a/articles/cognitive-services/Bing-Entities-Search/tutorial-bing-entities-search-single-page-app.md b/articles/cognitive-services/Bing-Entities-Search/tutorial-bing-entities-search-single-page-app.md
@@ -2,10 +2,7 @@
 title: "Tutorial: Bing Entity Search single-page web app"
 titleSuffix: Azure Cognitive Services
 description: This tutorial shows how to use the Bing Entity Search API in a single-page Web application.
-services: cognitive-services
 author: aahill
-manager: nitinme
-
 ms.service: cognitive-services
 ms.subservice: bing-entity-search
 ms.topic: tutorial
@@ -559,7 +556,7 @@ Leave the command window open while you use the tutorial app; closing the window
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Bing Entity Search API reference](//docs.microsoft.com/rest/api/cognitiveservices/bing-entities-api-v7-reference)
+> [Bing Entity Search API reference](/rest/api/cognitiveservices/bing-entities-api-v7-reference)
 
 > [!div class="nextstepaction"]
-> [Bing Maps API documentation](//msdn.microsoft.com/library/dd877180.aspx)
+> [Bing Maps API documentation](/bingmaps/)
diff --git a/articles/cognitive-services/Custom-Vision-Service/role-based-access-control.md b/articles/cognitive-services/Custom-Vision-Service/role-based-access-control.md
@@ -2,7 +2,6 @@
 title: "Azure role-based access control - Custom Vision"
 titleSuffix: Azure Cognitive Services
 description: This article will show you how to configure Azure role-based access control for your Custom Vision projects.
-services: cognitive-services
 author: PatrickFarley
 manager: nitinme
 ms.service: cognitive-services
@@ -29,7 +28,7 @@ Azure RBAC can be assigned to a Custom Vision resource. To grant access to an Az
 1. On the **Members** tab, select a user, group, service principal, or managed identity.
 1. On the **Review + assign** tab, select **Review + assign** to assign the role.
 
-Within a few minutes, the target will be assigned the selected role at the selected scope. For help with these steps, see [Assign Azure roles using the Azure portal](https://review.docs.microsoft.com/azure/role-based-access-control/role-assignments-portal).
+Within a few minutes, the target will be assigned the selected role at the selected scope. For help with these steps, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.md).
 
 ## Custom Vision role types
 
diff --git a/articles/cognitive-services/Custom-Vision-Service/storage-integration.md b/articles/cognitive-services/Custom-Vision-Service/storage-integration.md
@@ -34,7 +34,7 @@ Next, go to your storage resource in the Azure portal. Go to the **Access contro
 * If you plan to use the model backup feature, select the **Storage Blob Data Contributor** role, and add your Custom Vision training resource as a member. Select **Review + assign** to complete.
 * If you plan to use the notification queue feature, then select the **Storage Queue Data Contributor** role, and add your Custom Vision training resource as a member. Select **Review + assign** to complete.
 
-For help with role assignments, see [Assign Azure roles using the Azure portal](https://review.docs.microsoft.com/azure/role-based-access-control/role-assignments-portal).
+For help with role assignments, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.md).
 
 ### Get integration URLs
 
