more fixed links

Author: David Curwin

articles/backup/azure-policy-configure-diagnostics.md

@@ -6,13 +6,13 @@ ms.date: 02/14/2020
 ---
 # Configure Vault Diagnostics settings at scale
 
-The reporting solution provided by Azure Backup leverages Log Analytics (LA). For the data of any given vault to be sent to LA, a [diagnostics setting](https://aka.ms/AzureBackupDiagnosticsDocs) needs to be created for that vault.
+The reporting solution provided by Azure Backup leverages Log Analytics (LA). For the data of any given vault to be sent to LA, a [diagnostics setting](https://docs.microsoft.com/azure/backup/backup-azure-diagnostic-events) needs to be created for that vault.
 
 Often, adding a diagnostics setting manually per vault can be a cumbersome task. In addition, any new vault created also needs to have diagnostics settings enabled in order to be able to view reports for this vault. 
 
 To simplify the creation of diagnostics settings at scale (with LA as the destination), Azure Backup provides a built-in [Azure Policy](https://docs.microsoft.com/azure/governance/policy/). This policy adds an LA diagnostics setting to all vaults in a given subscription or resource group. The following sections provide instructions on how to use this policy.
 
-## Supported Scenarios 
+## Supported Scenarios
 
 * The policy can be applied at one time to all Recovery Services vaults in a particular subscription (or to a resource group within the subscription). The user assigning the policy needs to have 'Owner' access to the subscription to which the policy is assigned.
 
@@ -43,6 +43,7 @@ To assign the policy for vaults in the required scope, follow the steps below:
 ![Policy Assignment Basics](./media/backup-azure-policy-configure-diagnostics/policy-assignment-basics.png)
 
 7. Under **Parameters**, enter the following information:
+
 * **Profile Name** - The name that will be assigned to the diagnostics settings created by the policy.
 * **Log Analytics Workspace** - The Log Analytics Workspace to which the diagnostics setting should be associated. Diagnostics data of all vaults in the scope of the Policy assignment will be pushed to the specified LA Workspace.
 
@@ -63,7 +64,7 @@ The remediation task is applied to vaults that are non-compliant according to th
 * No diagnostics setting is present for the vault.
 * Diagnostic settings are present for the vault but neither of the settings has **all of** the Resource specific events enabled with LA as destination, and **Resource specific** selected in the toggle. 
 
-So even if a user has a vault with the AzureBackupReport event enabled in AzureDiagnostics mode (which is supported by Backup Reports), the remediation task will still apply to this vault, since the Resource specific mode is the recommended way of creating diagnostics settings, [going forward](https://aka.ms/AzureBackupDiagnosticsDocs#legacy-event). 
+So even if a user has a vault with the AzureBackupReport event enabled in AzureDiagnostics mode (which is supported by Backup Reports), the remediation task will still apply to this vault, since the Resource specific mode is the recommended way of creating diagnostics settings, [going forward](https://docs.microsoft.com/azure/backup/backup-azure-diagnostic-events#legacy-event).
 
 Further, if a user has a vault with only a subset of the six Resource specific events enabled, the remediation task will apply for this vault, since Backup Reports will work as expected only if all of the six Resource specific events are enabled.
 
@@ -76,6 +77,7 @@ Further, if a user has a vault with only a subset of the six Resource specific e
 > Note that the remediation task will **not** fail if the existing diagnostics setting as only AzureBackupReport enabled with Workspace X as the destination, since in this case, there will be no overlap between the events enabled by the existing setting and the events enabled by the setting created by the remediation task.
 
 ## Next Steps
-- [Learn how to use Backup Reports](https://aka.ms/AzureBackupReportDocs)
-- [Learn more about Azure Policy](https://docs.microsoft.com/azure/governance/policy/)
-- [Use Azure Policy to auto-enable backup for all VMs in a give scope](https://docs.microsoft.com/azure/backup/backup-azure-auto-enable-backup)
+
+* [Learn how to use Backup Reports](https://docs.microsoft.com/azure/backup/configure-reports)
+* [Learn more about Azure Policy](https://docs.microsoft.com/azure/governance/policy/)
+* [Use Azure Policy to auto-enable backup for all VMs in a give scope](https://docs.microsoft.com/azure/backup/backup-azure-auto-enable-backup)

articles/backup/backup-azure-auto-enable-backup.md

@@ -11,9 +11,9 @@ One of the key responsibilities of a Backup or Compliance Admin in an organizati
 
 Today, Azure Backup provides a built-in policy (using Azure Policy) that can be assigned to **all Azure VMs in a specified location within a subscription or resource group**. When this policy is assigned to a given scope, all new VMs created in that scope are automatically configured for backup to an **existing vault in the same location and subscription**. The user can specify the vault and the retention policy to which the backed up VMs should be associated.
 
-## Supported Scenarios 
+## Supported Scenarios
 
-* The built-in policy is currently supported only for Azure VMs. Users must take care to ensure that the retention policy specified during assignment is a VM retention policy. Refer to [this](https://aka.ms/PolicySupportedSKUs) document to see all the VM SKUs supported by this policy.
+* The built-in policy is currently supported only for Azure VMs. Users must take care to ensure that the retention policy specified during assignment is a VM retention policy. Refer to [this](https://docs.microsoft.com/azure/backup/backup-azure-policy-supported-skus) document to see all the VM SKUs supported by this policy.
 
 * The policy can be assigned to a single location and subscription at a time. To enable backup for VMs across locations and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of location and subscription.
 
@@ -51,4 +51,4 @@ To assign the policy to the required scope, please follow the below steps:
 
 ## Next Steps
 
-[Learn more about Azure Policy](https://docs.microsoft.com/azure/governance/policy/overview)
+[Learn more about Azure Policy](https://docs.microsoft.com/azure/governance/policy/overview)

articles/backup/backup-azure-backup-sharepoint.md

@@ -96,7 +96,7 @@ After you have configured DPM and the SharePoint farm as explained previously, S
     ![Select data protection method](./media/backup-azure-backup-sharepoint/select-data-protection-method1.png)
 
    > [!NOTE]
-   > The disk protection method helps to meet short recovery-time objectives. Azure is an economical, long-term protection target compared to tapes. For more information, see [Use Azure Backup to replace your tape infrastructure](https://azure.microsoft.com/documentation/articles/backup-azure-backup-cloud-as-tape/)
+   > The disk protection method helps to meet short recovery-time objectives. Azure is an economical, long-term protection target compared to tapes. For more information, see [Use Azure Backup to replace your tape infrastructure](./backup-azure-backup-cloud-as-tape.md)
    >
    >
 5. On the **Specify Short-Term Goals** page, select your preferred **Retention range** and identify when you want backups to occur.

articles/backup/backup-azure-delete-vault.md

@@ -22,7 +22,7 @@ You can't delete a Recovery Services vault that has dependencies, such as protec
 
   ![Delete the protected server error.](./media/backup-azure-delete-vault/error-message.jpg)
 
-- If backup items are in soft deleted state below warning message appears and you will have to wait until they are permanently deleted. For more information, see this [article](https://aka.ms/SoftDeleteCloudWorkloads).
+- If backup items are in soft deleted state below warning message appears and you will have to wait until they are permanently deleted. For more information, see this [article](https://docs.microsoft.com/azure/backup/backup-azure-security-feature-cloud).
 
    ![Delete the vault error.](./media/backup-azure-delete-vault/error-message-soft-delete.png)
 

articles/backup/backup-azure-diagnostic-events.md

@@ -16,14 +16,15 @@ You can configure diagnostics settings for a Recovery Services Vault via the Azu
 ## Diagnostics Events Available for Azure Backup Users
 
 Azure Backup provides the following diagnostic events, each of which provides detailed data on a specific set of backup-related artifacts:
+
 * CoreAzureBackup
 * AddonAzureBackupAlerts
 * AddonAzureBackupProtectedInstance
 * AddonAzureBackupJobs
 * AddonAzureBackupPolicy
-* AddonAzureBackupStorage 
+* AddonAzureBackupStorage
 
-[Data Model for Azure Backup Diagnostics Events](https://aka.ms/diagnosticsdatamodel)
+[Data Model for Azure Backup Diagnostics Events](https://docs.microsoft.com/azure/backup/backup-azure-reports-data-model)
 
 Data for these events can be sent to either a storage account, LA workspace, or an Event Hub. If you are sending this data to an LA Workspace, you need to select the **Resource Specific** toggle in the **Diagnostics Setting** screen (see more information in the sections below).
 
@@ -32,6 +33,7 @@ Data for these events can be sent to either a storage account, LA workspace, or
 Aligning with the Azure Log Analytics roadmap, Azure Backup now allows you to send vault diagnostics data to dedicated LA tables for Backup. These are referred to as [Resource Specific tables](https://docs.microsoft.com/azure/azure-monitor/platform/resource-logs-collect-workspace#resource-specific).
 
 To send your vault diagnostics data to LA:
+
 1.	Navigate to your vault and click on **Diagnostic Settings**. Click **+ Add Diagnostic Setting**.
 2.	Give a name to the Diagnostics setting.
 3.	Check the box **Send to Log Analytics** and select a Log Analytics Workspace.
@@ -79,4 +81,4 @@ The below image shows an example of a user having three diagnostic settings for
 
 ## Next steps
 
-[Learn the Log Analytics Data Model for the Diagnostics Events](https://aka.ms/diagnosticsdatamodel)
+[Learn the Log Analytics Data Model for the Diagnostics Events](https://docs.microsoft.com/azure/backup/backup-azure-reports-data-model)

articles/backup/backup-azure-diagnostics-mode-data-model.md

@@ -13,7 +13,7 @@ Use the Log Analytics data model to create custom alerts from Log Analytics.
 > [!NOTE]
 >
 > This data model is in reference to the Azure Diagnostics Mode of sending diagnostic
-> events to Log Analytics (LA). To learn the data model for the new Resource Specific Mode, you can refer to the following article: [Data Model for Azure Backup Diagnostic Events](https://aka.ms/diagnosticsdatamodel)
+> events to Log Analytics (LA). To learn the data model for the new Resource Specific Mode, you can refer to the following article: [Data Model for Azure Backup Diagnostic Events](https://docs.microsoft.com/azure/backup/backup-azure-reports-data-model)
 
 ## Using Azure Backup data model
 

articles/backup/backup-azure-mabs-troubleshoot.md

@@ -15,12 +15,12 @@ Use the information in the following tables to troubleshoot errors that you enco
 We recommend you perform the below validation, before you start troubleshooting Microsoft Azure Backup Server (MABS):
 
 - [Ensure Microsoft Azure Recovery Services (MARS) Agent is up to date](https://go.microsoft.com/fwlink/?linkid=229525&clcid=0x409)
-- [Ensure there is network connectivity between MARS agent and Azure](https://aka.ms/AB-A4dp50)
+- [Ensure there is network connectivity between MARS agent and Azure](https://docs.microsoft.com/azure/backup/backup-azure-mars-troubleshoot#the-microsoft-azure-recovery-service-agent-was-unable-to-connect-to-microsoft-azure-backup)
 - Ensure Microsoft Azure Recovery Services is running (in Service console). If necessary, restart and retry the operation
-- [Ensure 5-10% free volume space is available on scratch folder location](https://aka.ms/AB-AA4dwtt)
+- [Ensure 5-10% free volume space is available on scratch folder location](https://docs.microsoft.com/azure/backup/backup-azure-file-folder-backup-faq#whats-the-minimum-size-requirement-for-the-cache-folder)
 - If registration is failing, then ensure the server on which you are trying to install Azure Backup Server is not already registered with another vault
 - If Push install fails, check if DPM agent is already present. If yes, then uninstall the agent and retry the installation
-- [Ensure no other process or antivirus software is interfering with Azure Backup](https://aka.ms/AA4nyr4)<br>
+- [Ensure no other process or antivirus software is interfering with Azure Backup](https://docs.microsoft.com/azure/backup/backup-azure-troubleshoot-slow-backup-performance-issue#cause-another-process-or-antivirus-software-interfering-with-azure-backup)<br>
 - Ensure that the SQL Agent service is running and set to automatic in MAB server<br>
 
 ## Invalid vault credentials provided

articles/backup/backup-azure-manage-windows-server.md

@@ -267,4 +267,4 @@ The Backup Storage tile in the dashboard shows the storage consumed in Azure. St
 
 * [Restore Windows Server or Windows Client from Azure](backup-azure-restore-windows-server.md)
 * To learn more about Azure Backup, see [Azure Backup Overview](backup-introduction-to-azure-backup.md)
-* Visit the [Azure Backup Forum](https://go.microsoft.com/fwlink/p/?LinkId=290933)
+

articles/backup/backup-azure-mars-troubleshoot.md

@@ -15,11 +15,11 @@ This article describes how to resolve errors you might see during configuration,
 We recommend that you check the following before you start troubleshooting Microsoft the Azure Recovery Services (MARS) agent:
 
 - [Ensure the MARS agent is up to date](https://go.microsoft.com/fwlink/?linkid=229525&clcid=0x409).
-- [Ensure you have network connectivity between the MARS agent and Azure](https://aka.ms/AB-A4dp50).
+- [Ensure you have network connectivity between the MARS agent and Azure](https://docs.microsoft.com/azure/backup/backup-azure-mars-troubleshoot#the-microsoft-azure-recovery-service-agent-was-unable-to-connect-to-microsoft-azure-backup).
 - Ensure MARS is running (in Service console). If you need to, restart and retry the operation.
-- [Ensure 5% to 10% free volume space is available in the scratch folder location](https://aka.ms/AB-AA4dwtt).
-- [Check if another process or antivirus software is interfering with Azure Backup](https://aka.ms/AB-AA4dwtk).
-- If scheduled backup fails but manual backup works, see [Backups don't run according to schedule](https://aka.ms/ScheduledBackupFailManualWorks).
+- [Ensure 5% to 10% free volume space is available in the scratch folder location](https://docs.microsoft.com/azure/backup/backup-azure-file-folder-backup-faq#whats-the-minimum-size-requirement-for-the-cache-folder).
+- [Check if another process or antivirus software is interfering with Azure Backup](https://docs.microsoft.com/azure/backup/backup-azure-troubleshoot-slow-backup-performance-issue#cause-another-process-or-antivirus-software-interfering-with-azure-backup).
+- If scheduled backup fails but manual backup works, see [Backups don't run according to schedule](https://docs.microsoft.com/azure/backup/backup-azure-mars-troubleshoot#backups-dont-run-according-to-schedule).
 - Ensure your OS has the latest updates.
 - [Ensure unsupported drives and files with unsupported attributes are excluded from backup](backup-support-matrix-mars-agent.md#supported-drives-or-volumes-for-backup).
 - Ensure the clock on the protected system is configured to the correct time zone.
@@ -28,7 +28,7 @@ We recommend that you check the following before you start troubleshooting Micro
   - Ensure the agent is uninstalled on the server and that it's deleted from the portal.
   - Use the same passphrase that was initially used to register the server.
 - For offline backups, ensure Azure PowerShell 3.7.0 is installed on both the source and the copy computer before you start the backup.
-- If the Backup agent is running on an Azure virtual machine, see [this article](https://aka.ms/AB-AA4dwtr).
+- If the Backup agent is running on an Azure virtual machine, see [this article](https://docs.microsoft.com/azure/backup/backup-azure-troubleshoot-slow-backup-performance-issue#cause-backup-agent-running-on-an-azure-virtual-machine).
 
 ## Invalid vault credentials provided
 

articles/backup/backup-azure-reports-data-model.md

@@ -214,5 +214,5 @@ This table provides details about storage-related fields.
 
 ## Next steps
 
-- [Learn how to send diagnostics data to Log Analytics](https://aka.ms/AzureBackupDiagnosticsDocs)
+- [Learn how to send diagnostics data to Log Analytics](https://docs.microsoft.com/azure/backup/backup-azure-diagnostic-events)
 - [Learn how to write queries on Resource specific tables](https://docs.microsoft.com/azure/backup/backup-azure-monitoring-use-azuremonitor#sample-kusto-queries)