Merge pull request #97279 from john-par/1614298-clean-up-broken-azure-docs-pr-links-11-26

1614298 clean up broken azure docs pr links 11-26

Author: American-Dipper

articles/active-directory/develop/msal-net-use-brokers-with-xamarin-apps.md

@@ -180,7 +180,7 @@ The portal has a new experience app registration portal to help you compute the
 
 MSAL.NET only support the Xamarin.iOS platform at the moment. It doesn't yet support brokers for the Xamarin.Android platform.
 
-The MSAL Android native library already supports it. For details see [Brokered auth in Android](https://docs.microsoft.com/azure/active-directory/develop/brokered-auth.md)
+The MSAL Android native library already supports it. For details see [Brokered auth in Android](brokered-auth.md)
 
 ## Next steps
 

articles/active-directory/users-groups-roles/directory-assign-admin-roles.md

@@ -181,7 +181,7 @@ This role is available for assignment only as an additional local administrator
 
 Users in this role can read basic directory information. This role should be used for:
 * Granting a specific set of guest users read access instead of granting it to all guest users.
-* Granting a specific set of non-admin users access to Azure Portal when “Restrict access to Azure AD portal to admins only” is set to “Yes”.
+* Granting a specific set of non-admin users access to Azure portal when “Restrict access to Azure AD portal to admins only” is set to “Yes”.
 * Granting service principals access to directory where Directory.Read.All is not an option.
 
 ### [Directory Synchronization Accounts](#directory-synchronization-accounts-permissions)
@@ -234,7 +234,7 @@ Users in this role can read settings and administrative information across Micro
 >- [Azure AD portal](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps/menuId/) - Global reader can't read the provisioning mode of an enterprise app.
 >- [M365 admin center](https://admin.microsoft.com/Adminportal/Home#/homepage) - Global reader can't read customer lockbox requests. You won't find the **Customer lockbox requests** tab under **Support** in the left pane of M365 Admin Center.
 >- [M365 Security center](https://security.microsoft.com/homepage) - Global reader can't read sensitivity and retention labels. You won't find **Sensitivity labels**, **Retention labels**, and **Label analytics** tabs in the left pane of the M365 Security center.
->- [Office Security & Compliance Center](https://protection.microsoft.com) - Global reader can't read SCC audit logs or do content search.
+>- [Office Security & Compliance Center](https://sip.protection.office.com/homepage) - Global reader can't read SCC audit logs or do content search.
 >- [Teams admin center](https://admin.teams.microsoft.com) - Global reader cannot read **Teams lifecycle**, **Analytics & reports**, **IP phone device management** and **App catalog**.
 >- [Privileged Access Management (PAM)](https://docs.microsoft.com/office365/securitycompliance/privileged-access-management-overview) doesn't support the Global reader role.
 >- [Azure Information Protection](https://docs.microsoft.com/azure/information-protection/what-is-information-protection) - Global reader is supported [for central reporting](https://docs.microsoft.com/azure/information-protection/reports-aip) only, and when your Azure AD organization isn't on the [unified labeling platform](https://docs.microsoft.com/azure/information-protection/faqs#how-can-i-determine-if-my-tenant-is-on-the-unified-labeling-platform).
@@ -244,7 +244,7 @@ Users in this role can read settings and administrative information across Micro
 
 ### [Group Administrator](#group-administrator)
 
-Users in this role can create/manage groups and its settings like naming and expiration policies. It is important to understand that assigning a user to this role gives them the ability to manage all groups in the tenant across various workloads like Teams, SharePoint, Yammer in addition to Outlook. Also the user will be able to manage the various groups settings across various admin portals like Microsoft Admin Center, Azure Portal, as well as workload specific ones like Teams and SharePoint Admin Centers.
+Users in this role can create/manage groups and its settings like naming and expiration policies. It is important to understand that assigning a user to this role gives them the ability to manage all groups in the tenant across various workloads like Teams, SharePoint, Yammer in addition to Outlook. Also the user will be able to manage the various groups settings across various admin portals like Microsoft Admin Center, Azure portal, as well as workload specific ones like Teams and SharePoint Admin Centers.
 
 ### [Guest Inviter](#guest-inviter-permissions)
 

articles/backup/backup-azure-arm-userestapi-backupazurevms.md

@@ -157,7 +157,7 @@ In the example, the above values translate to:
 
 ### Enabling protection for the Azure VM
 
-After the relevant VM is "cached" and "identified", select the policy to protect. To know more about existing policies in the vault, refer to [list Policy API](https://docs.microsoft.com/rest/api/backup/backuppolicies/list). Then select the [relevant policy](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/get) by referring to the policy name. To create policies, refer to [create policy tutorial](backup-azure-arm-userestapi-createorupdatepolicy.md). "DefaultPolicy" is selected in the below example.
+After the relevant VM is "cached" and "identified", select the policy to protect. To know more about existing policies in the vault, refer to [list Policy API](https://docs.microsoft.com/rest/api/backup/backuppolicies/list). Then select the [relevant policy](/rest/api/backup/protectionpolicies/get) by referring to the policy name. To create policies, refer to [create policy tutorial](backup-azure-arm-userestapi-createorupdatepolicy.md). "DefaultPolicy" is selected in the below example.
 
 Enabling protection is an asynchronous *PUT* operation that creates a 'protected item'.
 

articles/backup/backup-azure-arm-userestapi-createorupdatepolicy.md

@@ -7,7 +7,7 @@ ms.assetid: 5ffc4115-0ae5-4b85-a18c-8a942f6d4870
 ---
 # Create Azure Recovery Services backup policies using REST API
 
-The steps to create a backup policy for an Azure Recovery Services vault are outlined in the [policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate). Let us use this document as a reference to create a policy for Azure VM backup.
+The steps to create a backup policy for an Azure Recovery Services vault are outlined in the [policy REST API document](/rest/api/backup/protectionpolicies/createorupdate). Let us use this document as a reference to create a policy for Azure VM backup.
 
 ## Backup policy essentials
 
@@ -40,10 +40,10 @@ For example, to create a policy for Azure VM backup, following are the component
 
 |Name  |Required  |Type  |Description  |
 |---------|---------|---------|---------|
-|properties     |   True      |  ProtectionPolicy:[AzureIaaSVMProtectionPolicy](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate#azureiaasvmprotectionpolicy)      | ProtectionPolicyResource properties        |
+|properties     |   True      |  ProtectionPolicy:[AzureIaaSVMProtectionPolicy](/rest/api/backup/protectionpolicies/createorupdate#azureiaasvmprotectionpolicy)      | ProtectionPolicyResource properties        |
 |tags     |         | Object        |  Resource tags       |
 
-For the complete list of definitions in the request body, refer to the [backup policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate).
+For the complete list of definitions in the request body, refer to the [backup policy REST API document](/rest/api/backup/protectionpolicies/createorupdate).
 
 ### Example request body
 
@@ -148,7 +148,7 @@ It returns two responses: 202 (Accepted) when another operation is created, and
 
 |Name  |Type  |Description  |
 |---------|---------|---------|
-|200 OK     |    [Protection PolicyResource](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate#protectionpolicyresource)     |  OK       |
+|200 OK     |    [Protection PolicyResource](/rest/api/backup/protectionpolicies/createorupdate#protectionpolicyresource)     |  OK       |
 |202 Accepted     |         |     Accepted    |
 
 ### Example responses

articles/backup/backup-azure-monitoring-use-azuremonitor.md

@@ -32,7 +32,7 @@ In the monitoring section, select **Diagnostic settings** and specify the target
 
 ![The Recovery Services vault's diagnostic setting, targeting Log Analytics](media/backup-azure-monitoring-laworkspace/diagnostic-setting-new.png)
 
-You can target a Log Analytics workspace from another subscription. To monitor vaults across subscriptions in a single place, select the same Log Analytics workspace for multiple Recovery Services vaults. To channel all the information that's related to Azure Backup to the Log Analytics workspace, choose **Resource Specific** in the toggle that appears, and select the following events - **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupAlerts**, **AddonAzureBackupPolicy**, **AddonAzureBackupStorage**, **AddonAzureBackupProtectedInstance**. Please refer to [this article](https://aka.ms/AA6jkus) for more details on configuring LA Diagnostics Settings.
+You can target a Log Analytics workspace from another subscription. To monitor vaults across subscriptions in a single place, select the same Log Analytics workspace for multiple Recovery Services vaults. To channel all the information that's related to Azure Backup to the Log Analytics workspace, choose **Resource Specific** in the toggle that appears, and select the following events - **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupAlerts**, **AddonAzureBackupPolicy**, **AddonAzureBackupStorage**, **AddonAzureBackupProtectedInstance**. Please refer to [this article](backup-azure-diagnostic-events.md) for more details on configuring LA Diagnostics Settings.
 
 > [!IMPORTANT]
 > After you finish the configuration, you should wait 24 hours for the initial data push to finish. After that initial data push, all the events are pushed as described later in this article, in the [frequency section](#diagnostic-data-update-frequency).

articles/cognitive-services/LUIS/luis-how-to-publish-app.md

@@ -41,7 +41,7 @@ By using both publishing slots, this allows you to have two different versions o
 
 ### Publishing regions
 
-The app is published to all regions associated with the LUIS prediction endpoint resources added in the LUIS portal from the **Manage** -> **[Azure Resources](/luis-how-to-azure-subscription.md#assign-a-resource-to-an-app)** page. 
+The app is published to all regions associated with the LUIS prediction endpoint resources added in the LUIS portal from the **Manage** -> **[Azure Resources](luis-how-to-azure-subscription.md#assign-a-resource-to-an-app)** page. 
 
 For example, for an app created on [www.luis.ai](https://www.luis.ai), if you create a LUIS resource in two regions, **westus** and **eastus**, and add these to the app as resources, the app is published in both regions. For more information about LUIS regions, see [Regions](luis-reference-regions.md).
 

articles/cognitive-services/Speech-Service/how-to-audio-content-creation.md

@@ -38,7 +38,7 @@ This diagram shows the steps it takes to tune and export customized speech-to-te
 
 Follow these steps to create a Speech resource and connect it with Speech Studio.
 
-1. Follow these instructions to [sign up for an Azure account](https://docs.microsoft.com/azure/cognitive-services/speech-service/get-started#new-azure-account) and [create a Speech resource](https://docs.microsoft.com/azure/cognitive-services/speech-service/get-started#create-a-speech-resource-in-azure). Make sure that your pricing tier is set to **S0**. If you are using one of the Neural voices, make sure that you create your resource in a [supported region](regions.md#standard-and-neural-voices).
+1. Follow these instructions to [sign up for an Azure account](get-started.md#try-the-speech-service-using-a-new-azure-account) and [create a Speech resource](https://docs.microsoft.com/azure/cognitive-services/speech-service/get-started#create-a-speech-resource-in-azure). Make sure that your pricing tier is set to **S0**. If you are using one of the Neural voices, make sure that you create your resource in a [supported region](regions.md#standard-and-neural-voices).
 2. Sign into [Audio Content Creation](https://aka.ms/audiocontentcreation).
 3. Select an existing project, or click **Create New**.
 4. You can modify your subscription at any time with the **Settings** option, located in the top nav.

articles/cognitive-services/Speech-Service/how-to-custom-speech.md

@@ -38,7 +38,7 @@ This diagram highlights the pieces that make up the [Custom Speech portal](https
 
 ## Set up your Azure account
 
-A Speech Services subscription is required before you can use the [Custom Speech portal](https://speech.microsoft.com/customspeech) to create a custom model. Follow these instructions to create a standard Speech Services subscription: [Create a Speech Subscription](https://docs.microsoft.com/azure/cognitive-services/speech-service/get-started#new-azure-account).
+A Speech Services subscription is required before you can use the [Custom Speech portal](https://speech.microsoft.com/customspeech) to create a custom model. Follow these instructions to create a standard Speech Services subscription: [Create a Speech Subscription](get-started.md#try-the-speech-service-using-a-new-azure-account).
 
 > [!NOTE]
 > Please be sure to create standard (S0) subscriptions, free trial (F0) subscriptions are not supported.

articles/cognitive-services/Speech-Service/quickstarts/text-to-speech/async-synthesis-long-form-audio.md

@@ -25,7 +25,7 @@ This quickstart requires:
 
 * Python 2.7.x or 3.x.
 * [Visual Studio](https://visualstudio.microsoft.com/downloads/), [Visual Studio Code](https://code.visualstudio.com/download), or your favorite text editor.
-* An Azure subscription and a Speech service subscription key. [Create an Azure account](https://docs.microsoft.com/azure/cognitive-services/speech-service/get-started#new-azure-account) and [create a speech resource](https://docs.microsoft.com/azure/cognitive-services/speech-service/get-started#create-a-speech-resource-in-azure) to get the key. When creating the Speech resource, make sure that your pricing tier is set to **S0**, and location is set to a [supported region](../../regions.md#standard-and-neural-voices).
+* An Azure subscription and a Speech service subscription key. [Create an Azure account](../../get-started.md#try-the-speech-service-using-a-new-azure-account) and [create a speech resource](https://docs.microsoft.com/azure/cognitive-services/speech-service/get-started#create-a-speech-resource-in-azure) to get the key. When creating the Speech resource, make sure that your pricing tier is set to **S0**, and location is set to a [supported region](../../regions.md#standard-and-neural-voices).
 
 ## Create a project and import required modules
 

articles/cognitive-services/index.yml

@@ -188,7 +188,7 @@ additionalContent:
           - text: .NET
             url: https://docs.microsoft.com/dotnet/api/overview/azure/cognitiveservices/client?view=azure-dotnet
           - text: Go
-            url: https://godoc.org/github.com/azure/azure-sdk-for-go/services/cognitiveservices
+            url: https://godoc.org/github.com/Azure/azure-sdk-for-go/services/cognitiveservices
           - text: Java
             url: https://docs.microsoft.com/java/api/overview/azure/cognitiveservices/client?view=azure-java-stable
           - text: Node.js