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

ktoliver · web-flow · commit e3ad3c726d82 · 2019-11-19T15:46:42.000-08:00
1614298, clean up broken azure docs pr links 11-19
diff --git a/articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-powershell.md b/articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-powershell.md
@@ -35,7 +35,7 @@ In this article, you learn how to create, list and delete a user-assigned manage
 - Install [the latest version of Azure PowerShell](/powershell/azure/install-az-ps) if you haven't already.
 - If you are running PowerShell locally, you also need to: 
     - Run `Connect-AzAccount` to create a connection with Azure.
-    - Install the [latest version of PowerShellGet](/powershell/gallery/installing-psget#for-systems-with-powershell-50-or-newer-you-can-install-the-latest-powershellget).
+    - Install the [latest version of PowerShellGet](/powershell/scripting/gallery/installing-psget#for-systems-with-powershell-50-or-newer-you-can-install-the-latest-powershellget).
     - Run `Install-Module -Name PowerShellGet -AllowPrerelease` to get the pre-release version of the `PowerShellGet` module (you may need to `Exit` out of the current PowerShell session after you run this command to install the `Az.ManagedServiceIdentity` module).
     - Run `Install-Module -Name Az.ManagedServiceIdentity -AllowPrerelease` to install the prerelease version of the `Az.ManagedServiceIdentity` module to perform the user-assigned managed identity operations in this article.
 
diff --git a/articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-ua-arm.md b/articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-ua-arm.md
@@ -45,7 +45,7 @@ You learn how to:
 - To perform the required resource creation and role management steps in this tutorial, your account needs "Owner" permissions at the appropriate scope (your subscription or resource group). If you need assistance with role assignment, see [Use Role-Based Access Control to manage access to your Azure subscription resources](/azure/role-based-access-control/role-assignments-portal).
 - [Install the latest version of the Azure PowerShell module](/powershell/azure/install-az-ps). 
 - Run `Connect-AzAccount` to create a connection with Azure.
-- Install the [latest version of PowerShellGet](/powershell/gallery/installing-psget#for-systems-with-powershell-50-or-newer-you-can-install-the-latest-powershellget).
+- Install the [latest version of PowerShellGet](/powershell/scripting/gallery/installing-psget#for-systems-with-powershell-50-or-newer-you-can-install-the-latest-powershellget).
 - Run `Install-Module -Name PowerShellGet -AllowPrerelease` to get the pre-release version of the `PowerShellGet` module (you may need to `Exit` out of the current PowerShell session after you run this command to install the `Az.ManagedServiceIdentity` module).
 - Run `Install-Module -Name Az.ManagedServiceIdentity -AllowPrerelease` to install the prerelease version of the `Az.ManagedServiceIdentity` module to perform the user-assigned identity operations in this article.
 
diff --git a/articles/application-gateway/migrate-v1-v2.md b/articles/application-gateway/migrate-v1-v2.md
@@ -61,7 +61,7 @@ This command also installs the required Az modules.
 
 ### Install using the script directly
 
-If you do have some Azure Az modules installed and can't uninstall them (or don't want to uninstall them), you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw nupkg file. To install the script from this nupkg file, see [Manual Package Download](https://docs.microsoft.com/powershell/gallery/how-to/working-with-packages/manual-download).
+If you do have some Azure Az modules installed and can't uninstall them (or don't want to uninstall them), you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw nupkg file. To install the script from this nupkg file, see [Manual Package Download](/powershell/scripting/gallery/how-to/working-with-packages/manual-download).
 
 To run the script:
 
diff --git a/articles/automation/automation-dsc-config-from-server.md b/articles/automation/automation-dsc-config-from-server.md
@@ -63,6 +63,6 @@ to view the
 
 ## Next steps
 
-- [Windows PowerShell Desired State Configuration Overview](/powershell/dsc/overview/overview)
-- [DSC Resources](/powershell/dsc/resources/resources)
+- [Windows PowerShell Desired State Configuration Overview](/powershell/scripting/dsc/overview/overview)
+- [DSC Resources](/powershell/scripting/dsc/resources/resources)
 - [Configuring The Local Configuration Manager](/powershell/scripting/dsc/managing-nodes/metaconfig)
diff --git a/articles/automation/automation-dsc-configuration-based-on-stig.md b/articles/automation/automation-dsc-configuration-based-on-stig.md
@@ -61,6 +61,6 @@ to view the
 
 ## Next steps
 
-- [Windows PowerShell Desired State Configuration Overview](/powershell/dsc/overview/overview)
-- [DSC Resources](/powershell/dsc/resources/resources)
+- [Windows PowerShell Desired State Configuration Overview](/powershell/scripting/dsc/overview/overview)
+- [DSC Resources](/powershell/scripting/dsc/resources/resources)
 - [Configuring The Local Configuration Manager](/powershell/scripting/dsc/managing-nodes/metaconfig)
diff --git a/articles/automation/automation-dsc-create-composite.md b/articles/automation/automation-dsc-create-composite.md
@@ -29,7 +29,7 @@ Examples would be:
 
 If you are interested in sharing this work with others,
 the best option is to package the configuration as a
-[Composite Resource](/powershell/dsc/resources/authoringresourcecomposite).
+[Composite Resource](/powershell/scripting/dsc/resources/authoringresourcecomposite).
 Creating composite resources for the first time can be overwhelming.
 
 > [!NOTE]
@@ -64,7 +64,7 @@ you can use them in the
 [Composable Authoring Experience](/azure/automation/compose-configurationwithcompositeresources)
 in Azure,
 or add them to 
-[DSC Configuration scripts](/powershell/dsc/configurations/configurations)
+[DSC Configuration scripts](/powershell/scripting/dsc/configurations/configurations)
 to generate MOF files
 and
 [upload the MOF files to Azure Automation](/azure/automation/tutorial-configure-servers-desired-state#create-and-upload-a-configuration-to-azure-automation).
@@ -85,6 +85,6 @@ to view the
 
 ## Next steps
 
-- [Windows PowerShell Desired State Configuration Overview](/powershell/dsc/overview/overview)
-- [DSC Resources](/powershell/dsc/resources/resources)
-- [Configuring The Local Configuration Manager](/powershell/dsc/managing-nodes/metaconfig)
+- [Windows PowerShell Desired State Configuration Overview](/powershell/scripting/dsc/overview/overview)
+- [DSC Resources](/powershell/scripting/dsc/resources/resources)
+- [Configuring The Local Configuration Manager](/powershell/scripting/dsc/managing-nodes/metaconfig)
diff --git a/articles/automation/automation-dsc-overview.md b/articles/automation/automation-dsc-overview.md
@@ -75,9 +75,9 @@ The DSC Linux extension supports all the Linux distributions listed under [Suppo
 ### DSC requirements
 
 For all Windows nodes running in Azure,
-[WMF 5.1](https://docs.microsoft.com/powershell/wmf/setup/install-configure)
+[WMF 5.1](https://docs.microsoft.com/powershell/scripting/wmf/setup/install-configure)
 will be installed during onboarding.  For nodes running Windows Server 2012 and Windows 7,
-[WinRM will be enabled](https://docs.microsoft.com/powershell/dsc/troubleshooting/troubleshooting#winrm-dependency).
+[WinRM will be enabled](https://docs.microsoft.com/powershell/scripting/dsc/troubleshooting/troubleshooting#winrm-dependency).
 
 For all Linux nodes running in Azure,
 [PowerShell DSC for Linux](https://github.com/Microsoft/PowerShell-DSC-for-Linux)
@@ -95,7 +95,7 @@ the following port and URLs are required for State Configuration (DSC) to commun
 
 This provides network connectivity for the managed node to communicate with Azure Automation.
 If you are using DSC resources that communicate between nodes,
-such as the [WaitFor* resources](https://docs.microsoft.com/powershell/dsc/reference/resources/windows/waitForAllResource),
+such as the [WaitFor* resources](https://docs.microsoft.com/powershell/scripting/dsc/reference/resources/windows/waitForAllResource),
 you will also need to allow traffic between nodes.
 See the documentation for each DSC resource to understand those network requirements.
 
diff --git a/articles/automation/automation-runbook-gallery.md b/articles/automation/automation-runbook-gallery.md
@@ -44,7 +44,7 @@ You can only import directly from the PowerShell Gallery using the Azure portal.
 
 ### Adding a PowerShell runbook to the gallery
 
-Microsoft encourages you to add runbooks to the PowerShell Gallery that you think would be useful to other customers. The PowerShell Gallery accepts PowerShell modules and PowerShell scripts. You can add a runbook by [uploading it to the PowerShell Gallery](/powershell/gallery/how-to/publishing-packages/publishing-a-package).
+Microsoft encourages you to add runbooks to the PowerShell Gallery that you think would be useful to other customers. The PowerShell Gallery accepts PowerShell modules and PowerShell scripts. You can add a runbook by [uploading it to the PowerShell Gallery](/powershell/scripting/gallery/how-to/publishing-packages/publishing-a-package).
 
 > [!NOTE]
 > Graphical runbooks are not supported in PowerShell Gallery.
diff --git a/articles/automation/automation-windows-hrw-install.md b/articles/automation/automation-windows-hrw-install.md
@@ -134,9 +134,9 @@ To receive detailed information about the installation, use the **-Verbose** swi
 
 Runbooks can use any of the activities and cmdlets defined in the modules that are installed in your Azure Automation environment. These modules are not automatically deployed to on-premises computers, so you must install them manually. The exception is the Azure module, which is installed by default and provides access to cmdlets for all Azure services and activities for Azure Automation.
 
-Because the primary purpose of the Hybrid Runbook Worker feature is to manage local resources, you most likely need to install the modules that support these resources. For information on installing Windows PowerShell modules, see [Installing Modules](/powershell/developer/windows-powershell). 
+Because the primary purpose of the Hybrid Runbook Worker feature is to manage local resources, you most likely need to install the modules that support these resources. For information on installing Windows PowerShell modules, see [Installing Modules](/powershell/scripting/developer/windows-powershell). 
 
-Modules that are installed must be in a location referenced by the **PSModulePath** environment variable so that the hybrid worker can automatically import them. For more information, see [Modifying the PSModulePath Installation Path](/powershell/developer/windows-powershell).
+Modules that are installed must be in a location referenced by the **PSModulePath** environment variable so that the hybrid worker can automatically import them. For more information, see [Modifying the PSModulePath Installation Path](/powershell/scripting/developer/windows-powershell).
 
 ## Next steps
 
diff --git a/articles/automation/index.yml b/articles/automation/index.yml
@@ -60,7 +60,7 @@ landingContent:
       - linkListType: concept
         links:
           - text: PowerShell DSC
-            url: /powershell/dsc/overview/overview
+            url: /powershell/scripting/dsc/overview/overview
       - linkListType: quickstart
         links:
           - text: Create a DSC Configuration from Group Policy
diff --git a/articles/automation/shared-resources/modules.md b/articles/automation/shared-resources/modules.md
@@ -77,7 +77,7 @@ The following is a listing of cmdlets in the internal `Orchestrator.AssetManagem
 
 ## Add a connection type to your module
 
-You can provide a custom [connection type](../automation-connections.md) for you to use in your Automation Account by adding an optional file to your module. This file is a metadata file specifying an Azure Automation connection type to be used with the module's cmdlets in your Automation Account. To achieve this, you must first know how to author a PowerShell module. For more information on module authoring, see [How to Write a PowerShell Script Module](/powershell/developer/module/how-to-write-a-powershell-script-module).
+You can provide a custom [connection type](../automation-connections.md) for you to use in your Automation Account by adding an optional file to your module. This file is a metadata file specifying an Azure Automation connection type to be used with the module's cmdlets in your Automation Account. To achieve this, you must first know how to author a PowerShell module. For more information on module authoring, see [How to Write a PowerShell Script Module](/powershell/scripting/developer/module/how-to-write-a-powershell-script-module).
 
 ![Use a custom connection in the Azure portal](../media/modules/connection-create-new.png)
 
diff --git a/articles/automation/troubleshoot/desired-state-configuration.md b/articles/automation/troubleshoot/desired-state-configuration.md
@@ -30,7 +30,7 @@ steps to help you diagnose the issue.
    - **Logic Errors**
 
 2. **View DSC logs on your Node:** If your configuration compiles successfully, but fails when applied to a Node, you can find
-   detailed information in the logs. For information about where to find DSC logs, see [Where are the DSC Event Logs](/powershell/dsc/troubleshooting/troubleshooting#where-are-dsc-event-logs).
+   detailed information in the logs. For information about where to find DSC logs, see [Where are the DSC Event Logs](/powershell/scripting/dsc/troubleshooting/troubleshooting#where-are-dsc-event-logs).
 
    Furthermore, the [xDscDiagnostics](https://github.com/PowerShell/xDscDiagnostics) can assist you in parsing detailed information
    from the DSC logs. If you contact support, they will require these logs to diagnose your issue.
@@ -39,7 +39,7 @@ steps to help you diagnose the issue.
 
    To install **xDscDiagnostics** on your Azure machine, you can use [az vm run-command](/cli/azure/vm/run-command) or [Invoke-AzVMRunCommand](/powershell/module/azurerm.compute/invoke-azurermvmruncommand). You can also use the **Run command** option from the portal, by following the steps found in [Run PowerShell scripts in your Windows VM with Run Command](../../virtual-machines/windows/run-command.md).
 
-   For information on using **xDscDiagnostics**, see [Using xDscDiagnostics to analyze DSC logs](/powershell/dsc/troubleshooting/troubleshooting#using-xdscdiagnostics-to-analyze-dsc-logs), as well as [xDscDiagnostics Cmdlets](https://github.com/PowerShell/xDscDiagnostics#cmdlets).
+   For information on using **xDscDiagnostics**, see [Using xDscDiagnostics to analyze DSC logs](/powershell/scripting/dsc/troubleshooting/troubleshooting#using-xdscdiagnostics-to-analyze-dsc-logs), as well as [xDscDiagnostics Cmdlets](https://github.com/PowerShell/xDscDiagnostics#cmdlets).
 3. **Ensure your Nodes and Automation workspace have the required modules:** Desired State Configuration depends on modules installed on the Node.  When using Azure Automation State Configuration, import any required modules into your automation account using the steps listed in [Import Modules](../shared-resources/modules.md#import-modules). Configurations can also have a dependency on specific versions of modules.  For more information, see, [Troubleshoot Modules](shared-resources.md#modules).
 
 ## Common errors when working with Desired State Configuration (DSC)
diff --git a/articles/automation/troubleshoot/shared-resources.md b/articles/automation/troubleshoot/shared-resources.md
@@ -23,7 +23,7 @@ A module is stuck in the **Importing** state when you import or update your modu
 
 #### Cause
 
-Importing PowerShell modules is a complex multi-step process. This process introduces the possibility of a module not importing correctly. If this issue occurs, the module you're importing can be stuck in a transient state. To learn more about this process, see [Importing a PowerShell Module]( /powershell/developer/module/importing-a-powershell-module#the-importing-process).
+Importing PowerShell modules is a complex multi-step process. This process introduces the possibility of a module not importing correctly. If this issue occurs, the module you're importing can be stuck in a transient state. To learn more about this process, see [Importing a PowerShell Module](/powershell/scripting/developer/module/importing-a-powershell-module#the-importing-process).
 
 #### Resolution
 
diff --git a/articles/automation/tutorial-configure-servers-desired-state.md b/articles/automation/tutorial-configure-servers-desired-state.md
@@ -143,19 +143,19 @@ For information about how to change the compliance check interval, see
 ## Working with Partial Configurations
 
 Azure Automation State Configuration supports usage of
-[partial configurations](/powershell/dsc/pull-server/partialconfigs).
+[partial configurations](/powershell/scripting/dsc/pull-server/partialconfigs).
 In this scenario, DSC is configured to manage multiple configurations independently,
 and each configuration is retrieved from Azure Automation.
 However, only one configuration can be assigned to a node per automation account.
 This means if you are using two configurations for a node you will require two automation accounts.
 
 For details about how to register a partial configuration from pull service,
 see the documentation for
-[partial configurations](https://docs.microsoft.com/powershell/dsc/pull-server/partialconfigs#partial-configurations-in-pull-mode).
+[partial configurations](https://docs.microsoft.com/powershell/scripting/dsc/pull-server/partialconfigs#partial-configurations-in-pull-mode).
 
 For more information about how teams can work together to collaboratively manage servers
 using configuration as code see
-[Understanding DSC's role in a CI/CD Pipeline](/powershell/dsc/overview/authoringadvanced).
+[Understanding DSC's role in a CI/CD Pipeline](/powershell/scripting/dsc/overview/authoringadvanced).
 
 ## Check the compliance status of a managed node
 
diff --git a/articles/azure-resource-manager/deployment-manager-tutorial.md b/articles/azure-resource-manager/deployment-manager-tutorial.md
@@ -49,7 +49,7 @@ To complete this article, you need:
 
 * Some experience with developing [Azure Resource Manager templates](./resource-group-overview.md).
 * Azure PowerShell. For more information, see [Get started with Azure PowerShell](https://docs.microsoft.com/powershell/azure/get-started-azureps).
-* Deployment Manager cmdlets. To install these prerelease cmdlets, you need the latest version of PowerShellGet. To get the latest version, see [Installing PowerShellGet](/powershell/gallery/installing-psget). After installing PowerShellGet, close your PowerShell window. Open a new elevated PowerShell window, and use the following command:
+* Deployment Manager cmdlets. To install these prerelease cmdlets, you need the latest version of PowerShellGet. To get the latest version, see [Installing PowerShellGet](/powershell/scripting/gallery/installing-psget). After installing PowerShellGet, close your PowerShell window. Open a new elevated PowerShell window, and use the following command:
 
     ```powershell
     Install-Module -Name Az.DeploymentManager
diff --git a/articles/azure-resource-manager/programmatically-create-subscription.md b/articles/azure-resource-manager/programmatically-create-subscription.md
@@ -152,7 +152,7 @@ In the response, you get back a `subscriptionOperation` object for monitoring. W
 
 ### [PowerShell](#tab/azure-powershell)
 
-First, install this preview module by running `Install-Module Az.Subscription -AllowPrerelease`. To make sure `-AllowPrerelease` works, install a recent version of PowerShellGet from [Get PowerShellGet Module](/powershell/gallery/installing-psget).
+First, install this preview module by running `Install-Module Az.Subscription -AllowPrerelease`. To make sure `-AllowPrerelease` works, install a recent version of PowerShellGet from [Get PowerShellGet Module](/powershell/scripting/gallery/installing-psget).
 
 Run the [New-AzSubscription](/powershell/module/az.subscription) command below, replacing `<enrollmentAccountObjectId>` with the `ObjectId` collected in the first step (```747ddfe5-xxxx-xxxx-xxxx-xxxxxxxxxxxx```). If you'd like to specify owners, learn [how to get user object IDs](grant-access-to-create-subscription.md#userObjectId).
 
diff --git a/articles/governance/blueprints/how-to/manage-assignments-ps.md b/articles/governance/blueprints/how-to/manage-assignments-ps.md
@@ -21,7 +21,7 @@ with the [Azure PowerShell Docker image](https://hub.docker.com/r/azuresdk/azure
 The Azure Blueprints module requires the following software:
 
 - Azure PowerShell 1.5.0 or higher. If it isn't yet installed, follow [these instructions](/powershell/azure/install-az-ps).
-- PowerShellGet 2.0.1 or higher. If it isn't installed or updated, follow [these instructions](/powershell/gallery/installing-psget).
+- PowerShellGet 2.0.1 or higher. If it isn't installed or updated, follow [these instructions](/powershell/scripting/gallery/installing-psget).
 
 ### Install the module
 
diff --git a/articles/governance/index.yml b/articles/governance/index.yml
@@ -112,7 +112,7 @@ additionalContent:
             - text: Azure SDK for .NET
               url: /dotnet/api/overview/azure/managementgroups
             - text: Azure SDK for Node
-              url: /javascript/api/azure-arm-resource/managementgroups
+              url: /javascript/api/@azure/arm-managementgroups/managementgroups
         - title: Azure Policy
           links:
             - text: Azure CLI
diff --git a/articles/governance/resource-graph/first-query-powershell.md b/articles/governance/resource-graph/first-query-powershell.md
@@ -28,7 +28,7 @@ The Azure Resource Graph module requires the following software:
 
 - Azure PowerShell 1.0.0 or higher. If it isn't yet installed, follow [these instructions](/powershell/azure/install-az-ps).
 
-- PowerShellGet 2.0.1 or higher. If it isn't installed or updated, follow [these instructions](/powershell/gallery/installing-psget).
+- PowerShellGet 2.0.1 or higher. If it isn't installed or updated, follow [these instructions](/powershell/scripting/gallery/installing-psget).
 
 ### Install the module
 
diff --git a/articles/machine-learning/studio/deploy-consume-web-service-guide.md b/articles/machine-learning/studio/deploy-consume-web-service-guide.md
diff --git a/articles/storage/blobs/data-lake-storage-quickstart-create-account.md b/articles/storage/blobs/data-lake-storage-quickstart-create-account.md
diff --git a/articles/storage/files/storage-files-release-notes.md b/articles/storage/files/storage-files-release-notes.md
diff --git a/articles/storage/files/storage-how-to-create-premium-fileshare.md b/articles/storage/files/storage-how-to-create-premium-fileshare.md
