Fixing docs-link-absolute links

Author: JasonWHowell

articles/industry/agriculture/query-telemetry-data-from-azure-farmbeats.md

@@ -113,7 +113,7 @@ Follow the steps to visualize data on TSI:
 1. Go to **Azure Portal** > **FarmBeats DataHub resource group** > select **Time Series Insights** environment (tsi-xxxx) > **Data Access Policies**. Add user with Reader or Contributor access.
 2. Go to the **Overview** page of **Time Series Insights** environment (tsi-xxxx) and select the **Time Series Insights Explorer URL**. You'll now be able to visualize the ingested telemetry.
 
-Apart from storing, querying and visualization of telemetry, TSI also enables integration to a Power BI dashboard. For more information, see [here]( https://docs.microsoft.com/azure/time-series-insights/how-to-connect-power-bi)
+Apart from storing, querying and visualization of telemetry, TSI also enables integration to a Power BI dashboard. For more information, see [here](../../time-series-insights/how-to-connect-power-bi.md)
 
 ## Next steps
 

articles/industry/agriculture/troubleshoot-azure-farmbeats.md

@@ -282,7 +282,7 @@ This issue can occur if any maintenance activities are being done on the Sentine
 
 ## Collect logs manually
 
-[Install and deploy Azure Storage Explorer]( https://docs.microsoft.com/azure/vs-azure-tools-storage-manage-with-storage-explorer?tabs=windows).
+[Install and deploy Azure Storage Explorer](../../vs-azure-tools-storage-manage-with-storage-explorer.md?tabs=windows).
 
 ### Collect Azure Data Factory job logs or App Service logs in Datahub
 

articles/marketplace/find-tenant-object-id.md

@@ -52,14 +52,15 @@ If you need to get screenshots of these items in Azure Cloud Shell to use for de
 1. Sign in to the [Office 365 Admin Portal](https://portal.office.com/adminportal/home) with an account in the desired tenant with the appropriate administrative rights.
 2. In the left-side menu, expand the **Admin Centers** section at the bottom and then select the Azure Active Directory option to launch the admin console in a new browser window.
 3. Select **Users**.
-4. Browse to or search for the desired user, then select the account name to view the user account’s profile information.
+4. Browse to or search for the desired user, then select the account name to view the user account's profile information.
 5. The Object ID is located in the Identity section on the right.
 
     :::image type="content" source="media/tenant-and-object-id/azure-ad-admin-center.png" alt-text="Azure Active Directory admin center.":::
 
 6. Find **role assignments** by selecting **Access control (IAM)** in the left menu, then **Role assignments**.
 
-    :::image type="content" source="https://docs.microsoft.com/azure/role-based-access-control/media/role-assignments-portal/role-assignments.png" alt-text="Role assignments for Azure resources.":::
+    :::image type="content" source="../role-based-access-control/media/role-assignments-portal/rg-role-assignments.png" alt-text="Role assignments for Azure resources.":::
+
 
 ## Find IDs for debugging
 

articles/security/develop/threat-modeling-tool-cryptography.md

@@ -1,25 +1,17 @@
 ---
 title: Cryptography - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
 description: Learn about cryptography mitigation for threats exposed in the Threat Modeling Tool. See mitigation information and view code examples.
-services: security
-documentationcenter: na
 author: jegeib
 manager: jegeib
 editor: jegeib
-
-ms.assetid: na
 ms.service: security
 ms.subservice: security-develop
-ms.workload: na
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: article
 ms.date: 02/07/2017
 ms.author: jegeib
-
 ---
 
-# Security Frame: Cryptography | Mitigations 
+# Security Frame: Cryptography | Mitigation
 
 | Product/Service | Article |
 | --------------- | ------- |
@@ -167,12 +159,12 @@ ms.author: jegeib
 
 | Title                   | Details      |
 | ----------------------- | ------------ |
-| **Component**               | IoT Device | 
+| **Component**               | IoT Device |
 | **SDL Phase**               | Build |  
 | **Applicable Technologies** | Generic |
 | **Attributes**              | Device OS - Windows IoT Core, Device Connectivity - Azure IoT device SDKs |
 | **References**              | [TPM on Windows IoT Core](/windows/iot-core/secure-your-device/TPM), [Set up TPM on Windows IoT Core](/windows/iot-core/secure-your-device/setuptpm), [Azure IoT Device SDK TPM](https://github.com/Azure/azure-iot-hub-vs-cs/wiki/Device-Provisioning-with-TPM) |
-| **Steps** | Symmetric or Certificate Private keys securely in a hardware protected storage like TPM or Smart Card chips. Windows 10 IoT Core supports the user of a TPM and there are several compatible TPMs that can be used: https://docs.microsoft.com/windows/iot-core/secure-your-device/tpm#discrete-tpm-dtpm. It is recommended to use a Firmware or Discrete TPM. A Software TPM should only be used for development and testing purposes. Once a TPM is available and the keys are provisioned in it, the code that generates the token should be written without hard coding any sensitive information in it. | 
+| **Steps** | Symmetric or Certificate Private keys securely in a hardware protected storage like TPM or Smart Card chips. Windows 10 IoT Core supports the user of a TPM and there are several compatible TPMs that can be used: [Discrete TPM (dTPM)](/windows/iot-core/secure-your-device/tpm#discrete-tpm-dtpm). It is recommended to use a Firmware or Discrete TPM. A Software TPM should only be used for development and testing purposes. Once a TPM is available and the keys are provisioned in it, the code that generates the token should be written without hard coding any sensitive information in it. |
 
 ### Example
 ```

articles/service-fabric/service-fabric-node-transition-apis.md

@@ -2,7 +2,6 @@
 title: Start and stop cluster nodes
 description: Learn how to use fault injection to test a Service Fabric application by starting and stopping cluster nodes.
 author: LMWF
-
 ms.topic: conceptual
 ms.date: 6/12/2017
 ms.author: lemai
@@ -21,17 +20,16 @@ As described earlier, a *stopped* Service Fabric node is a node intentionally ta
 
 In addition, some errors returned by these APIs are not as descriptive as they could be.  For example, invoking the Stop Node API on an already *stopped* node will return the error *InvalidAddress*.  This experience could be improved.
 
-Also, the duration a node is stopped for is “infinite” until the Start Node API is invoked.  We’ve found this can cause problems and may be error-prone.  For example, we’ve seen problems where a user invoked the Stop Node API on a node and then forgot about it.  Later, it was unclear if the node was *down* or *stopped*.
+Also, the duration a node is stopped for is "infinite" until the Start Node API is invoked.  We've found this can cause problems and may be error-prone.  For example, we've seen problems where a user invoked the Stop Node API on a node and then forgot about it.  Later, it was unclear if the node was *down* or *stopped*.
 
 
 ## Introducing the Node Transition APIs
 
-We’ve addressed these issues above in a new set of APIs.  The new Node Transition API (managed: [StartNodeTransitionAsync()][snt]) may be used to transition a Service Fabric node to a *stopped* state, or to transition it from a *stopped* state to a normal up state.  Please note that the “Start” in the name of the API does not refer to starting a node.  It refers to beginning an asynchronous operation that the system will execute to transition the node to either *stopped* or started state.
+We've addressed these issues above in a new set of APIs.  The new Node Transition API (managed: [StartNodeTransitionAsync()][snt]) may be used to transition a Service Fabric node to a *stopped* state, or to transition it from a *stopped* state to a normal up state.  Please note that the "Start" in the name of the API does not refer to starting a node.  It refers to beginning an asynchronous operation that the system will execute to transition the node to either *stopped* or started state.
 
 **Usage**
 
-If the Node Transition API does not throw an exception when invoked, then the system has accepted the asynchronous operation, and will execute it.  A successful call does not imply the operation is finished yet.  To get information about the current state of the operation, call the Node Transition Progress API (managed: [GetNodeTransitionProgressAsync()][gntp]) with the guid used when invoking Node Transition API for this operation.  The Node Transition Progress API returns an NodeTransitionProgress object.  This object’s State property specifies the current state of the operation.  If the state is “Running”, then the operation is executing.  If it is Completed, the operation finished without error.  If it is Faulted, there was a problem executing the operation.  The Result property’s Exception property will indicate what the issue was.  See https://docs.microsoft.com/dotnet/api/system.fabric.testcommandprogressstate for more information about the State property, and the “Sample Usage” section below for code examples.
-
+If the Node Transition API does not throw an exception when invoked, then the system has accepted the asynchronous operation, and will execute it.  A successful call does not imply the operation is finished yet.  To get information about the current state of the operation, call the Node Transition Progress API (managed: [GetNodeTransitionProgressAsync()][gntp]) with the guid used when invoking Node Transition API for this operation.  The Node Transition Progress API returns an NodeTransitionProgress object.  This object's State property specifies the current state of the operation.  If the state is "Running", then the operation is executing.  If it is Completed, the operation finished without error.  If it is Faulted, there was a problem executing the operation.  The Result property's Exception property will indicate what the issue was.  See [TestCommandProgressState Enum](/dotnet/api/system.fabric.testcommandprogressstate) for more information about the State property, and the "Sample Usage" section below for code examples.
 
 **Differentiating between a stopped node and a down node**
 If a node is *stopped* using the Node Transition API, the output of a node query (managed: [GetNodeListAsync()][nodequery], PowerShell: [Get-ServiceFabricNode][nodequeryps]) will show that this node has an *IsStopped* property value of true.  Note this is different from the value of the *NodeStatus* property, which will say *Down*.  If the *NodeStatus* property has a value of *Down*, but *IsStopped* is false, then the node was not stopped using the Node Transition API, and is *Down* due to some other reason.  If the *IsStopped* property is true, and the *NodeStatus* property is *Down*, then it was stopped using the Node Transition API.

articles/service-fabric/service-fabric-sfctl-chaos.md

@@ -2,7 +2,6 @@
 title: Azure Service Fabric CLI- sfctl chaos
 description: Learn about sfctl, the Azure Service Fabric command line interface. Includes a list of commands for managing chaos.
 author: jeffj6123
-
 ms.topic: reference
 ms.date: 1/16/2020
 ms.author: jejarry
@@ -72,7 +71,7 @@ Get the status of Chaos indicating whether or not Chaos is running, the Chaos pa
 ## sfctl chaos start
 Starts Chaos in the cluster.
 
-If Chaos is not already running in the cluster, it starts Chaos with the passed in Chaos parameters. If Chaos is already running when this call is made, the call fails with the error code FABRIC_E_CHAOS_ALREADY_RUNNING. Refer to the article [Induce controlled Chaos in Service Fabric clusters](https\://docs.microsoft.com/azure/service-fabric/service-fabric-controlled-chaos) for more details.
+If Chaos is not already running in the cluster, it starts Chaos with the passed in Chaos parameters. If Chaos is already running when this call is made, the call fails with the error code FABRIC_E_CHAOS_ALREADY_RUNNING. Refer to the article [Induce controlled Chaos in Service Fabric clusters](service-fabric-controlled-chaos.md) for more details.
 
 ### Arguments
 

articles/virtual-machines/workloads/sap/deployment-guide.md

@@ -2,12 +2,9 @@
 title: Azure Virtual Machines deployment for SAP NetWeaver | Microsoft Docs
 description: Learn how to deploy SAP software on Linux virtual machines in Azure.
 services: virtual-machines-linux,virtual-machines-windows
-documentationcenter: ''
 author: MSSedusch
 manager: juergent
-editor: ''
 tags: azure-resource-manager
-keywords: ''
 ms.assetid: 1c4f1951-3613-4a5a-a0af-36b85750c84e
 ms.service: virtual-machines-sap
 ms.topic: article
@@ -183,7 +180,7 @@ ms.author: sedusch
 [Logo_Linux]:media/virtual-machines-shared-sap-shared/Linux.png
 [Logo_Windows]:media/virtual-machines-shared-sap-shared/Windows.png
 
-[msdn-set-Azvmaemextension]:https://docs.microsoft.com/powershell/module/az.compute/set-azvmaemextension
+[msdn-set-Azvmaemextension]:/powershell/module/az.compute/set-azvmaemextension
 
 [planning-guide]:planning-guide.md (Azure Virtual Machines planning and implementation for SAP)
 [planning-guide-1.2]:planning-guide.md#e55d1e22-c2c8-460b-9897-64622a34fdff (Resources)

articles/virtual-machines/workloads/sap/hana-vm-troubleshoot-scale-out-ha-on-sles.md

@@ -2,17 +2,14 @@
 title: SAP HANA scale-out HSR-Pacemaker with SLES on Azure VMs troubleshooting| Microsoft Docs
 description: Guide to check and troubleshoot a complex SAP HANA scale-out high-availability configuration based on SAP HANA System Replication (HSR) and Pacemaker on SLES 12 SP3 running on Azure virtual machines
 services: virtual-machines-linux
-documentationcenter: ''
 author: hermanndms
 manager: juergent
-editor: 
 ms.service: virtual-machines-sap
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure
 ms.date: 09/24/2018
 ms.author: hermannd
-
 ---
 
 
@@ -22,7 +19,7 @@ ms.author: hermannd
 [sles-hana-scale-out-ha-paper]:https://www.suse.com/documentation/suse-best-practices/singlehtml/SLES4SAP-hana-scaleOut-PerfOpt-12/SLES4SAP-hana-scaleOut-PerfOpt-12.html
 [sap-hana-iaas-list]:https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/iaas.html
 [suse-pacemaker-support-log-files]:https://www.suse.com/support/kb/doc/?id=7022702
-[azure-linux-multiple-nics]:https://docs.microsoft.com/azure/virtual-machines/linux/multiple-nics
+[azure-linux-multiple-nics]:../../linux/multiple-nics.md
 [suse-cloud-netconfig]:https://www.suse.com/c/multi-nic-cloud-netconfig-ec2-azure/
 [sap-list-port-numbers]:https://help.sap.com/viewer/ports
 [sles-12-ha-paper]:https://www.suse.com/documentation/sle-ha-12/pdfdoc/book_sleha/book_sleha.pdf
@@ -43,7 +40,7 @@ SUSE published a [detailed description of this performance-optimized setup][sles
 For virtual machine types that are supported for SAP HANA scale-out, check the [SAP HANA certified IaaS directory][sap-hana-iaas-list].
 
 > [!NOTE]
-> This article contains references to the terms *master* and *slave*, terms that Microsoft no longer uses. When these terms are removed from the software, we’ll remove them from this article.
+> This article contains references to the terms *master* and *slave*, terms that Microsoft no longer uses. When these terms are removed from the software, we'll remove them from this article.
 
 There was a technical issue with SAP HANA scale-out in combination with multiple subnets and vNICs and setting up HSR. It's mandatory to use the latest SAP HANA 2.0 patches where this issue was fixed. The following SAP HANA versions are supported: 
 

articles/virtual-machines/workloads/sap/sap-high-availability-architecture-scenarios.md

@@ -1,13 +1,10 @@
 ---
 title: Azure VMs HA architecture and scenarios for SAP NetWeaver | Microsoft Docs
 description: High-availability architecture and scenarios for SAP NetWeaver on Azure Virtual Machines
-services: virtual-machines-windows,virtual-network,storage
 documentationcenter: saponazure
 author: rdeltcheva
 manager: juergent
-editor: ''
 tags: azure-resource-manager
-keywords: ''
 ms.assetid: 887caaec-02ba-4711-bd4d-204a7d16b32b
 ms.service: virtual-machines-sap
 ms.topic: article
@@ -16,7 +13,6 @@ ms.workload: infrastructure-services
 ms.date: 02/26/2020
 ms.author: radeltch
 ms.custom: H1Hack27Feb2017
-
 ---
 
 # High-availability architecture and scenarios for SAP NetWeaver
@@ -93,7 +89,7 @@ ms.custom: H1Hack27Feb2017
 [azure-sla]:https://azure.microsoft.com/support/legal/sla/
 [azure-virtual-machines-manage-availability]:../../windows/manage-availability.md
 [azure-storage-redundancy]:https://azure.microsoft.com/documentation/articles/storage-redundancy/
-[azure-storage-managed-disks-overview]:https://docs.microsoft.com/azure/storage/storage-managed-disks-overview
+[azure-storage-managed-disks-overview]:../../../virtual-machines/managed-disks-overview.md
 
 [planning-guide-figure-100]:media/virtual-machines-shared-sap-planning-guide/100-single-vm-in-azure.png
 [planning-guide-figure-1300]:media/virtual-machines-shared-sap-planning-guide/1300-ref-config-iaas-for-sap.png

articles/virtual-machines/workloads/sap/sap-high-availability-infrastructure-wsfc-file-share.md

@@ -1,13 +1,10 @@
 ---
-title: Azure infrastructure for SAP ASCS/SCS HA with WSFC&file Share | Microsoft Docs
+title: Azure infrastructure for SAP ASCS/SCS HA with WSFC&file Share
 description: Azure infrastructure preparation for SAP high availability using a Windows failover cluster and file Share for SAP ASCS/SCS instances
-services: virtual-machines-windows,virtual-network,storage
 documentationcenter: saponazure
 author: rdeltcheva
 manager: juergent
-editor: ''
 tags: azure-resource-manager
-keywords: ''
 ms.assetid: 2ce38add-1078-4bb9-a1da-6f407a9bc910
 ms.service: virtual-machines-sap
 ms.topic: article
@@ -16,7 +13,6 @@ ms.workload: infrastructure-services
 ms.date: 08/12/2020
 ms.author: radeltch
 ms.custom: H1Hack27Feb2017
-
 ---
 
 # Prepare Azure infrastructure for SAP high availability by using a Windows failover cluster and file share for SAP ASCS/SCS instances
@@ -30,7 +26,7 @@ ms.custom: H1Hack27Feb2017
 [ms-blog-s2d-in-azure]:https://blogs.technet.microsoft.com/filecab/2016/05/05/s2dazuretp5/
 [arm-sofs-s2d-managed-disks]:https://github.com/robotechredmond/301-storage-spaces-direct-md
 [arm-sofs-s2d-non-managed-disks]:https://github.com/Azure/azure-quickstart-templates/tree/master/demos/storage-spaces-direct
-[deploy-cloud-witness]:https://docs.microsoft.com/windows-server/failover-clustering/deploy-cloud-witness
+[deploy-cloud-witness]:/windows-server/failover-clustering/deploy-cloud-witness
 [tuning-failover-cluster-network-thresholds]:https://techcommunity.microsoft.com/t5/Failover-Clustering/Tuning-Failover-Cluster-Network-Thresholds/ba-p/371834
 
 [sap-installation-guides]:http://service.sap.com/instguides