Merge pull request #91122 from craigcaseyMSFT/vcraic1009a

fix broken links from CATS report

Author: PRMerger10

articles/automation/automation-dsc-configuration-based-on-stig.md

@@ -44,7 +44,7 @@ in one large file.
 
 Once the configurations have been generated,
 you can use the
-[DSC Configuration scripts](/powershell/dsc/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).

articles/automation/automation-dsc-diagnostics.md

@@ -79,7 +79,7 @@ After you set up integration with Azure Monitor logs for your Automation State C
 
 The **Log Search** blade opens, and you see a **DscNodeStatusData** operation for each State
 Configuration node, and a **DscResourceStatusData** operation for each [DSC
-resource](/powershell/dsc/resources) called in the Node configuration applied to that node.
+resource](/powershell/scripting/dsc/resources/resources) called in the Node configuration applied to that node.
 
 The **DscResourceStatusData** operation contains error information for any DSC resources that failed.
 

articles/automation/automation-dsc-getting-started.md

@@ -12,7 +12,7 @@ manager: carmonm
 ---
 # Getting started with Azure Automation State Configuration
 
-This article explains how to do the most common tasks with Azure Automation State Configuration, such as creating, importing, and compiling configurations, onboarding machines to manage, and viewing reports. For an overview of what Azure Automation State Configuration is, see [Azure Automation State Configuration Overview](automation-dsc-overview.md). For Desired State Configuration (DSC) documentation, see [Windows PowerShell Desired State Configuration Overview](/powershell/dsc/overview).
+This article explains how to do the most common tasks with Azure Automation State Configuration, such as creating, importing, and compiling configurations, onboarding machines to manage, and viewing reports. For an overview of what Azure Automation State Configuration is, see [Azure Automation State Configuration Overview](automation-dsc-overview.md). For Desired State Configuration (DSC) documentation, see [Windows PowerShell Desired State Configuration Overview](/powershell/scripting/dsc/overview/overview).
 
 This article provides a step-by-step guide to using Azure Automation State Configuration. If you
 want a sample environment that is already set up without following the steps described in this
@@ -29,7 +29,7 @@ To complete the examples in this article, the following are required:
 
 ## Creating a DSC configuration
 
-You create a simple [DSC configuration](/powershell/dsc/configurations) that ensures either the
+You create a simple [DSC configuration](/powershell/scripting/dsc/configurations/configurations) that ensures either the
 presence or absence of the **Web-Server** Windows Feature (IIS), depending on how you assign nodes.
 
 1. Start [VSCode](https://code.visualstudio.com/docs) (or any text editor).
@@ -60,7 +60,7 @@ presence or absence of the **Web-Server** Windows Feature (IIS), depending on ho
     ```
 1. Save the file as `TestConfig.ps1`.
 
-This configuration calls one resource in each node block, the [WindowsFeature resource](/powershell/dsc/windowsfeatureresource), that ensures either the presence
+This configuration calls one resource in each node block, the [WindowsFeature resource](/powershell/scripting/dsc/reference/resources/windows/windowsfeatureresource), that ensures either the presence
 or absence of the **Web-Server** feature.
 
 ## Importing a configuration into Azure Automation
@@ -98,7 +98,7 @@ compiled into one or more node configurations (MOF document), and placed on the
 Server. For a more detailed description of compiling configurations in Azure Automation State
 Configuration, see [Compiling configurations in Azure Automation State Configuration](automation-dsc-compile.md).
 For more information about compiling configurations, see
-[DSC Configurations](/powershell/dsc/configurations).
+[DSC Configurations](/powershell/scripting/dsc/configurations/configurations).
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. On the left, click **All resources** and then the name of your Automation account.
@@ -217,7 +217,7 @@ On the blade for an individual report, you can see the following status informat
 - The name, IP address, and configuration mode of the node.
 
 You can also click **View raw report** to see the actual data that the node sends to the server.
-For more information about using that data, see [Using a DSC report server](/powershell/dsc/reportserver).
+For more information about using that data, see [Using a DSC report server](/powershell/scripting/dsc/pull-server/reportserver).
 
 It can take some time after a node is onboarded before the first report is available. You might
 need to wait up to 30 minutes for the first report after you onboard a node.
@@ -256,6 +256,6 @@ If you no longer want a node to be managed by Azure Automation DSC, you can unre
 
 - [Azure Automation State Configuration overview](automation-dsc-overview.md)
 - [Onboarding machines for management by Azure Automation State Configuration](automation-dsc-onboarding.md)
-- [Windows PowerShell Desired State Configuration Overview](/powershell/dsc/overview)
+- [Windows PowerShell Desired State Configuration Overview](/powershell/scripting/dsc/overview/overview)
 - [Azure Automation State Configuration cmdlets](/powershell/module/azurerm.automation/#automation)
 - [Azure Automation State Configuration pricing](https://azure.microsoft.com/pricing/details/automation/)

articles/automation/automation-dsc-onboarding.md

@@ -64,7 +64,7 @@ Select an Azure virtual machine to onboard.
 
 If the machine does not have the PowerShell desired state extension installed and the power state is running, click **Connect**.
 
-Under **Registration**, enter the [PowerShell DSC Local Configuration Manager values](/powershell/dsc/managing-nodes/metaconfig)
+Under **Registration**, enter the [PowerShell DSC Local Configuration Manager values](/powershell/scripting/dsc/managing-nodes/metaConfig)
 required for your use case, and optionally a node configuration to assign to the VM.
 
 ![onboarding](./media/automation-dsc-onboarding/DSC_Onboarding_6.png)
@@ -123,7 +123,7 @@ can also be onboarded to Azure Automation State Configuration, as long as they h
 [outbound access to Azure](automation-dsc-overview.md#network-planning):
 
 1. Make sure the latest version of [PowerShell Desired State Configuration for Linux](https://github.com/Microsoft/PowerShell-DSC-for-Linux) is installed on the machines you want to onboard to Azure Automation State Configuration.
-1. If the [PowerShell DSC Local Configuration Manager defaults](/powershell/dsc/metaconfig4) match your use case, and you want to onboard machines such that they **both** pull from and report to Azure Automation State Configuration:
+1. If the [PowerShell DSC Local Configuration Manager defaults](/powershell/scripting/dsc/managing-nodes/metaConfig4) match your use case, and you want to onboard machines such that they **both** pull from and report to Azure Automation State Configuration:
 
    - On each Linux machine to onboard to Azure Automation State Configuration, use `Register.py` to onboard using the PowerShell DSC Local Configuration Manager defaults:
 
@@ -157,7 +157,7 @@ The machine this command is run from must have the latest version of [WMF 5](htt
 
 ## Generating DSC metaconfigurations
 
-To generically onboard any machine to Azure Automation State Configuration, a [DSC metaconfiguration](/powershell/dsc/metaconfig)
+To generically onboard any machine to Azure Automation State Configuration, a [DSC metaconfiguration](/powershell/scripting/dsc/managing-nodes/metaConfig)
 can be generated that tells the DSC
 agent to pull from and/or report to Azure Automation State Configuration. DSC
 metaconfigurations for Azure Automation State Configuration can be generated using either a
@@ -369,7 +369,7 @@ After registering a machine as a DSC node in Azure Automation State Configuratio
 number of reasons why you may need to reregister that node in the future:
 
 - For versions of Windows Server prior to Windows Server 2019, each node automatically negotiates a unique certificate for authentication that expires after one year. Currently, the PowerShell DSC registration protocol cannot automatically renew certificates when they are nearing expiration, so you need to reregister the nodes after a year's time. Before reregistering, ensure that each node is running Windows Management Framework 5.0 RTM. If a node's authentication certificate expires, and the node is not reregistered, the node is unable to communicate with Azure Automation and is marked 'Unresponsive.' Reregistration performed 90 days or less from the certificate expiration time, or at any point after the certificate expiration time, will result in a new certificate being generated and used.  A resolution to this issue is included in Windows Server 2019 and later.
-- To change any [PowerShell DSC Local Configuration Manager values](/powershell/dsc/metaconfig4) that were set during initial registration of the node, such as ConfigurationMode. Currently, these DSC agent values can only be changed through reregistration. The one exception is the Node Configuration assigned to the node -- this can be changed in Azure Automation DSC directly.
+- To change any [PowerShell DSC Local Configuration Manager values](/powershell/scripting/dsc/managing-nodes/metaConfig4) that were set during initial registration of the node, such as ConfigurationMode. Currently, these DSC agent values can only be changed through reregistration. The one exception is the Node Configuration assigned to the node -- this can be changed in Azure Automation DSC directly.
 
 Reregistration can be performed in the same way you registered the node initially, using any of the
 onboarding methods described in this document. You do not need to unregister a node from Azure

articles/automation/automation-quickstart-dsc-configuration.md

@@ -38,7 +38,7 @@ There are many different methods to onboard a machine and enable Desired State C
 2. Click **Add** to open the VM select page.
 3. Find the virtual machine you would like to enable DSC for. You can use the search field and filter options to find a specific virtual machine.
 4. Click on the virtual machine, and then select **Connect**
-5. Select the DSC settings appropriate for the virtual machine. If you have already prepared a configuration, you can specify it as *Node Configuration Name*. You can set the [configuration mode](https://docs.microsoft.com/powershell/dsc/metaconfig) to control the configuration behavior for the machine.
+5. Select the DSC settings appropriate for the virtual machine. If you have already prepared a configuration, you can specify it as *Node Configuration Name*. You can set the [configuration mode](https://docs.microsoft.com/powershell/scripting/dsc/managing-nodes/metaConfig) to control the configuration behavior for the machine.
 6. Click **OK**
 
 ![Onboarding an Azure VM to DSC](./media/automation-quickstart-dsc-configuration/dsc-onboard-azure-vm.png)
@@ -60,7 +60,7 @@ Modules contain DSC Resources and many can be found on the [PowerShell Gallery](
 
 This quickstart uses a DSC configuration that configures Apache HTTP Server, MySQL, and PHP on the machine.
 
-For information about DSC configurations, see [DSC configurations](https://docs.microsoft.com/powershell/dsc/configurations).
+For information about DSC configurations, see [DSC configurations](https://docs.microsoft.com/powershell/scripting/dsc/configurations/configurations).
 
 In a text editor, type the following and save it locally as `LAMPServer.ps1`.
 
@@ -139,7 +139,7 @@ In this quickstart, you onboarded a Linux VM to DSC, created a configuration for
 > [!div class="nextstepaction"]
 > [Continuous deployment to a VM using DSC and Chocolatey](./automation-dsc-cd-chocolatey.md)
 
-* To learn more about PowerShell Desired State Configuration, see [PowerShell Desired State Configuration Overview](https://docs.microsoft.com/powershell/dsc/overview).
+* To learn more about PowerShell Desired State Configuration, see [PowerShell Desired State Configuration Overview](https://docs.microsoft.com/powershell/scripting/dsc/overview/overview).
 * To learn more about managing Automation DSC from PowerShell, see [Azure PowerShell](https://docs.microsoft.com/powershell/module/azurerm.automation/)
 * To learn how to forward DSC reports to Azure Monitor logs for reporting and alerting, see [Forwarding DSC Reporting to Azure Monitor logs](https://docs.microsoft.com/azure/automation/automation-dsc-diagnostics) 
 

articles/automation/compose-configurationwithcompositeresources.md

@@ -15,7 +15,7 @@ manager: carmonm
 
 When a resource needs to be managed with more than a single desired state configuration (DSC)
 configuration, the best path is to use [composite
-resources](/powershell/dsc/authoringresourcecomposite). A composite resource is a nested and
+resources](/powershell/scripting/dsc/resources/authoringresourcecomposite). A composite resource is a nested and
 parameterized configuration being used as a DSC resource within another configuration. This allows
 the creation of complex configurations while allowing the underlying composite resources
 (parameterized configurations) to be individually managed and built.

articles/automation/tutorial-configure-servers-desired-state.md

@@ -29,7 +29,7 @@ To complete this tutorial, you will need:
 - An Azure Resource Manager VM (not Classic) running Windows Server 2008 R2 or later. For instructions on creating a VM, see
   [Create your first Windows virtual machine in the Azure portal](../virtual-machines/virtual-machines-windows-hero-tutorial.md)
 - Azure PowerShell module version 3.6 or later. Run `Get-Module -ListAvailable AzureRM` to find the version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/azurerm/install-azurerm-ps).
-- Familiarity with Desired State Configuration (DSC). For information about DSC, see [Windows PowerShell Desired State Configuration Overview](https://docs.microsoft.com/powershell/dsc/overview)
+- Familiarity with Desired State Configuration (DSC). For information about DSC, see [Windows PowerShell Desired State Configuration Overview](/powershell/scripting/dsc/overview/overviews)
 
 ## Log in to Azure
 
@@ -43,7 +43,7 @@ Connect-AzureRmAccount
 
 For this tutorial, we will use a simple DSC configuration that ensures that IIS is installed on the VM.
 
-For information about DSC configurations, see [DSC configurations](/powershell/dsc/configurations).
+For information about DSC configurations, see [DSC configurations](/powershell/scripting/dsc/configurations/configurations).
 
 In a text editor, type the following and save it locally as `TestConfig.ps1`.
 
@@ -73,7 +73,7 @@ Call the `Import-AzureRmAutomationDscConfiguration` cmdlet to upload the configu
 
 A DSC configuration must be compiled into a node configuration before it can be assigned to a node.
 
-For information about compiling configurations, see [DSC configurations](/powershell/dsc/configurations).
+For information about compiling configurations, see [DSC configurations](/powershell/scripting/dsc/configurations/configurations).
 
 Call the `Start-AzureRmAutomationDscCompilationJob` cmdlet to compile the `TestConfig` configuration into a node configuration:
 
@@ -121,7 +121,7 @@ Register-AzureRmAutomationDscNode -ResourceGroupName 'MyResourceGroup' -Automati
 For more information about setting configuration properties for a managed node, see
 [Register-AzureRmAutomationDscNode](/powershell/module/azurerm.automation/register-azurermautomationdscnode).
 
-For more information about DSC configuration settings, see [Configuring the Local Configuration Manager](/powershell/dsc/metaconfig).
+For more information about DSC configuration settings, see [Configuring the Local Configuration Manager](/powershell/scripting/dsc/managing-nodes/metaConfig).
 
 ## Assign a node configuration to a managed node
 
@@ -138,7 +138,7 @@ Set-AzureRmAutomationDscNode -ResourceGroupName 'MyResourceGroup' -AutomationAcc
 This assigns the node configuration named `TestConfig.WebServer` to the registered DSC node named `DscVm`.
 By default, the DSC node is checked for compliance with the node configuration every 30 minutes.
 For information about how to change the compliance check interval, see
-[Configuring the Local Configuration Manager](/PowerShell/DSC/metaConfig).
+[Configuring the Local Configuration Manager](/powershell/scripting/dsc/managing-nodes/metaConfig).
 
 ## Working with Partial Configurations
 

articles/azure-functions/functions-consumption-costs.md

@@ -61,7 +61,7 @@ The following behaviors of your functions can impact the execution time:
 
 ## View execution data
 
-In [your invoice](/billing/billing-download-azure-invoice.md), you can view the cost-related data of **Total Executions - Functions** and **Execution Time - Functions**, along with the actual billed costs. However, this invoice data is a monthly aggregate for a past invoice period. 
+In [your invoice](/azure/billing/billing-download-azure-invoice), you can view the cost-related data of **Total Executions - Functions** and **Execution Time - Functions**, along with the actual billed costs. However, this invoice data is a monthly aggregate for a past invoice period. 
 
 To better understand the cost impact of your functions, you can use Azure Monitor to view cost-related metrics currently being generated by your function apps. You can use either [Azure Monitor metrics explorer](../azure-monitor/platform/metrics-getting-started.md) in the [Azure portal] or REST APIs to get this data.
 

articles/azure-resource-manager/template-tutorial-export-template.md

@@ -13,7 +13,7 @@ ms.author: jgao
 
 # Tutorial: Use exported template from the Azure portal
 
-In this tutorial series, you've created a template to deploy an Azure storage account. In the next two tutorials, you add an *App Service plan* and a *website*. Instead of creating templates from scratch, you learn how to export templates from the Azure portal and how to use sample templates from the [Azure Quickstart templates](/resources/templates/). You customize those templates for your use. This tutorial focuses on exporting templates, and customizing the result for your template. It takes about **14 minutes** to complete.
+In this tutorial series, you've created a template to deploy an Azure storage account. In the next two tutorials, you add an *App Service plan* and a *website*. Instead of creating templates from scratch, you learn how to export templates from the Azure portal and how to use sample templates from the [Azure Quickstart templates](https://azure.microsoft.com/resources/templates/). You customize those templates for your use. This tutorial focuses on exporting templates, and customizing the result for your template. It takes about **14 minutes** to complete.
 
 ## Prerequisites