Merge pull request #287847 from sdwheeler/sdw-w314665-aadsc

Add include file for AADSC retirement announcement.

Author: v-shils

articles/automation/automation-dsc-cd-chocolatey.md

@@ -14,19 +14,21 @@ ms.service: azure-automation
 
 **Applies to:** :heavy_check_mark: Windows PowerShell 5.1
 
-> [!NOTE]
-> Before you enable Automation State Configuration, we would like you to know that a newer version of DSC is now generally available, managed by a feature of Azure Policy named [guest configuration](../governance/machine-configuration/overview.md). The guest configuration service combines features of DSC Extension, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Guest configuration also includes hybrid machine support through [Arc-enabled servers](/azure/azure-arc/servers/overview).
+[!INCLUDE [azure-automation-dsc-end-of-life](~/includes/dsc-automation/azure-automation-dsc-end-of-life.md)]
 
 > [!IMPORTANT]
-> This article refers to a solution that is maintained by the Open Source community. Support is only available in the form of GitHub collaboration, and not from Microsoft.
+> This article refers to a solution that is maintained by the Open Source community. Support is only
+> available in the form of GitHub collaboration, and not from Microsoft.
 
-Managing many servers is a challenge and difficulty lies in managing [configuration data](/powershell/dsc/configurations/configdata) as it involves organizing information across logical constructs like location, type, and environment. 
+Managing many servers is a challenge and difficulty lies in managing [configuration data][04] as it
+involves organizing information across logical constructs like location, type, and environment.
 
 ## Community project: Datum
 
-[Datum](https://github.com/gaelcolas/Datum) is a community maintained solution that has been created to resolve this challenge. Datum builds on great ideas from other configuration management platforms and implements the same type of solution for PowerShell DSC. Information is [organized in to text files](https://github.com/gaelcolas/Datum#3-intended-usage) based on logical ideas.
-
-Listed below are few examples:
+[Datum][09] is a community maintained solution created to resolve this challenge. Datum builds on
+great ideas from other configuration management platforms and implements the same type of solution
+for PowerShell DSC. Information is [organized in to text files][11] based on the following logical
+ideas.
 
 - Settings that should apply globally
 - Settings that should apply to all servers in a location
@@ -36,19 +38,37 @@ Listed below are few examples:
 
 ## Configure data at scale
 
-Follow the below steps to configure data at scale for Azure Automation State Configuration:
+Use the following steps to configure data at scale for Azure Automation State Configuration:
 
-1. The information is organized in your preferred file format. For example, *JSON*, *Yaml*, or *PSD1*.
-1. The cmdlets are provided to generate configuration data files by [consolidating the information](https://github.com/gaelcolas/Datum#datum-tree) from each file in to single view of a server or server role.
-1. After you generate the data files, you can use them with [DSC Configuration scripts](/powershell/dsc/configurations/write-compile-apply-configuration) to generate *MOF* files and [upload the MOF files to Azure Automation](./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation).
-1. Register your servers from either [on-premises](./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines)
-or [in Azure](./automation-dsc-onboarding.md#enable-azure-vms) to pull configurations.
+1. Organize the information in your preferred file format. For example, *JSON*, *Yaml*, or *PSD1*.
+1. Use the cmdlets to generate configuration data files by [consolidating the information][12] from
+   each file in to single view of a server or server role.
+1. Use the generated files with [DSC Configuration scripts][05] to generate *MOF* files and
+   [upload the MOF files to Azure Automation][03].
+1. To pull configurations, register your servers from either [on-premises][02] or [in Azure][01].
 
-To download the solution, go to [PowerShell Gallery](https://www.powershellgallery.com/packages/datum/) or select **Project site** to view the [documentation](https://github.com/gaelcolas/Datum#2-getting-started--concepts).
+To download the solution, go to [PowerShell Gallery][13] or select **Project site** to view the
+[documentation][10].
 
 
 ## Next steps
 
-- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview](/powershell/dsc/overview).
-- Find out about PowerShell DSC resources in [DSC Resources](/powershell/dsc/resources/resources).
-- For details of Local Configuration Manager configuration, see [Configuring the Local Configuration Manager](/powershell/dsc/managing-nodes/metaconfig).
+- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview][07].
+- To find PowerShell DSC resources, see [DSC Resources][08].
+- For details of Local Configuration Manager configuration, see
+  [Configuring the Local Configuration Manager][06].
+
+<!-- link references -->
+[01]: ./automation-dsc-onboarding.md#enable-azure-vms
+[02]: ./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines
+[03]: ./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation
+[04]: /powershell/dsc/configurations/configdata
+[05]: /powershell/dsc/configurations/write-compile-apply-configuration
+[06]: /powershell/dsc/managing-nodes/metaconfig
+[07]: /powershell/dsc/overview
+[08]: /powershell/dsc/resources/resources
+[09]: https://github.com/gaelcolas/Datum
+[10]: https://github.com/gaelcolas/Datum#2-getting-started--concepts
+[11]: https://github.com/gaelcolas/Datum#3-intended-usage
+[12]: https://github.com/gaelcolas/Datum#datum-tree
+[13]: https://www.powershellgallery.com/packages/datum/

articles/automation/automation-dsc-compile.md

@@ -14,35 +14,58 @@ ms.service: azure-automation
 
 > **Applies to:** :heavy_check_mark: Windows PowerShell 5.1
 
-> [!NOTE]
-> Before you enable Automation State Configuration, we would like you to know that a newer version of DSC is now generally available, managed by a feature of Azure Policy named [guest configuration](../governance/machine-configuration/overview.md). The guest configuration service combines features of DSC Extension, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Guest configuration also includes hybrid machine support through [Arc-enabled servers](/azure/azure-arc/servers/overview).
+[!INCLUDE [azure-automation-dsc-end-of-life](~/includes/dsc-automation/azure-automation-dsc-end-of-life.md)]
 
 > [!IMPORTANT]
->  The article refers to a solution that is maintained by the Open Source community. Support is only available in the form of GitHub collaboration, not from Microsoft.
+> The article refers to a solution that is maintained by the Open Source community. Support is only
+> available in the form of GitHub collaboration, not from Microsoft.
 
-This article explains how to create configuration from existing servers for an Azure Automation state configuration. To create configurations from an existing servers is a challenging task as you need to know the right settings and the order they must be applied to ensure that configuration is successful.  
+This article explains how to create configuration from existing servers for an Azure Automation
+state configuration. Creating configurations from an existing server is a challenging task. You need
+to know the right settings and the order to apply them to ensure that the configuration is
+successful.
 
-## Community project: ReverseDSC 
+## Community project: ReverseDSC
 
- The [ReverseDSC](https://github.com/microsoft/reversedsc) is a community maintained solution created to work in this area beginning with the SharePoint. The solution builds on the [SharePointDSC resource](https://github.com/powershell/sharepointdsc) and extends it to orchestrate by [gathering information](https://github.com/Microsoft/sharepointDSC.reverse#how-to-use) from existing servers running SharePoint.
-
-The latest version has multiple [extraction modes](https://github.com/Microsoft/SharePointDSC.Reverse/wiki/Extraction-Modes) to determine the level of information to include. The result of using the solution is generating
-[Configuration Data](https://github.com/Microsoft/sharepointDSC.reverse#configuration-data) that must be used with SharePointDSC configuration scripts.
+ The [ReverseDSC][07] is a community maintained solution created to work in this area beginning with
+ the SharePoint. The solution builds on the [SharePointDSC resource][12] and extends it to
+ orchestrate by [gathering information][11] from existing servers running SharePoint.
 
+The latest version has multiple [extraction modes][09] to determine the level of information to
+include. The result of using the solution is generating [Configuration Data][10] that must be used
+with SharePointDSC configuration scripts.
 
 ## Create configuration from existing servers for an Azure Automation state configuration
 
-Follow the steps to create a configuration from existing servers for an Azure Automation state configuration:
+Use the following steps to create a configuration from existing servers:
 
-1. After you generate the data files, you can use them with [DSC Configuration scripts](/powershell/dsc/overview) to generate *MOF* files.
-1. upload the [MOF files to Azure Automation](./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation).
-1. Register your servers from either [on-premises](./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines)
-or [in Azure](./automation-dsc-onboarding.md#enable-azure-vms) to pull configurations.
+1. After you generate the data files, use the files with [DSC Configuration scripts][05] to generate
+   **MOF** files.
+1. Upload the [MOF files to Azure Automation][03].
+1. To pull the configurations, register your servers from either [on-premises][02] or
+   [in Azure][01].
 
-For more information on ReverseDSC, visit the [PowerShell Gallery](https://www.powershellgallery.com/packages/ReverseDSC/) and download the solution or select **Project Site** to view the [documentation](https://github.com/Microsoft/sharepointDSC.reverse).
+For more information on ReverseDSC, visit the [PowerShell Gallery][13] and download the solution or
+select **Project Site** to view the [documentation][08].
 
 ## Next steps
 
-- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview](/powershell/dsc/overview).
-- Find out about PowerShell DSC resources in [DSC Resources](/powershell/dsc/resources/resources).
-- For details of Local Configuration Manager configuration, see [Configuring the Local Configuration Manager](/powershell/dsc/managing-nodes/metaconfig).
+- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview][05].
+- To find PowerShell DSC resources, see [DSC Resources][06].
+- For details of Local Configuration Manager configuration, see
+  [Configuring the Local Configuration Manager][04].
+
+<!-- link references -->
+[01]: ./automation-dsc-onboarding.md#enable-azure-vms
+[02]: ./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines
+[03]: ./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation
+[04]: /powershell/dsc/managing-nodes/metaconfig
+[05]: /powershell/dsc/overview
+[06]: /powershell/dsc/resources/resources
+[07]: https://github.com/microsoft/reversedsc
+[08]: https://github.com/Microsoft/sharepointDSC.reverse
+[09]: https://github.com/Microsoft/SharePointDSC.Reverse/wiki/Extraction-Modes
+[10]: https://github.com/Microsoft/sharepointDSC.reverse#configuration-data
+[11]: https://github.com/Microsoft/sharepointDSC.reverse#how-to-use
+[12]: https://github.com/powershell/sharepointdsc
+[13]: https://www.powershellgallery.com/packages/ReverseDSC/

articles/automation/automation-dsc-config-data-at-scale.md

@@ -13,53 +13,49 @@ ms.service: azure-automation
 
 > Applies To: Windows PowerShell 5.1
 
-> [!NOTE]
-> Before you enable Automation State Configuration, we would like you to know that a newer version of DSC is now generally available, managed by a feature of Azure Policy named [guest configuration](../governance/machine-configuration/overview.md). The guest configuration service combines features of DSC Extension, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Guest configuration also includes hybrid machine support through [Arc-enabled servers](/azure/azure-arc/servers/overview).
+[!INCLUDE [azure-automation-dsc-end-of-life](~/includes/dsc-automation/azure-automation-dsc-end-of-life.md)]
 
-Creating configuration content for the first time can be challenging.
-In many cases, the goal is to automate configuration of servers following a "baseline" that hopefully aligns to an industry recommendation.
+Creating configuration content for the first time can be challenging. In many cases, the goal is to
+automate configuration of servers following a "baseline" that hopefully aligns to an industry
+recommendation.
 
 > [!NOTE]
-> This article refers to a solution that is maintained by the Open Source community.
-> Support is only available in the form of GitHub collaboration, not from Microsoft.
+> This article refers to a solution that's maintained by the Open Source community. Support is only
+> available in the form of GitHub collaboration, not from Microsoft.
 
 ## Community project: PowerSTIG
 
-A community project named
-[PowerSTIG](https://github.com/microsoft/powerstig)
-aims to resolve this issue by generating DSC content based on
-[public information](https://public.cyber.mil/stigs/)
-provided about STIG (Security Technical Implementation Guide),
+A community project named [PowerSTIG][08] aims to resolve this issue by generating DSC content based
+on [public information][11] provided about STIG (Security Technical Implementation Guide),
 
-Dealing with baselines is more complicated than it sounds.
-Many organizations need to
-[document exceptions](https://github.com/microsoft/powerstig#powerstigdata)
-to rules and manage that data at scale.
-PowerSTIG addresses the problem by providing
-[Composite Resources](https://github.com/microsoft/powerstig#powerstigdsc)
-to address each area of the configuration
-rather than trying to address the entire range of settings
-in one large file.
+Dealing with baselines is more complicated than it sounds. Many organizations need to
+[document exceptions][09] to rules and manage that data at scale. PowerSTIG addresses the problem by
+providing [Composite Resources][10] to address each area of the configuration rather than trying to
+address the entire range of settings in one large file.
 
-Once the configurations have been generated,
-you can use the
-[DSC Configuration scripts](/powershell/dsc/configurations/configurations)
-to generate MOF files
-and
-[upload the MOF files to Azure Automation](./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation).
-Then register your servers from either
-[on-premises](./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines)
-or [in Azure](./automation-dsc-onboarding.md#enable-azure-vms)
-to pull configurations.
+After you create the configurations, you can use the [DSC Configuration scripts][04] to generate MOF
+files and [upload the MOF files to Azure Automation][03]. To pull configurations, register your
+servers from either [on-premises][02] or [in Azure][01].
 
-To try out PowerSTIG, visit the
-[PowerShell Gallery](https://www.powershellgallery.com)
-and download the solution or click "Project Site"
-to view the
-[documentation](https://github.com/microsoft/powerstig).
+To try out PowerSTIG, visit the [PowerShell Gallery][12] and download the solution or select
+**Project Site** to view the [documentation][08].
 
 ## Next steps
 
-- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview](/powershell/dsc/overview).
-- Find out about PowerShell DSC resources in [DSC Resources](/powershell/dsc/resources/resources).
-- For details of Local Configuration Manager configuration, see [Configuring the Local Configuration Manager](/powershell/dsc/managing-nodes/metaconfig).
+- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview][06].
+- To find PowerShell DSC resources, see [DSC Resources][07].
+- For details of Local Configuration Manager configuration, see [Configuring the Local Configuration Manager][05].
+
+<!-- link references -->
+[01]: ./automation-dsc-onboarding.md#enable-azure-vms
+[02]: ./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines
+[03]: ./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation
+[04]: /powershell/dsc/configurations/configurations
+[05]: /powershell/dsc/managing-nodes/metaconfig
+[06]: /powershell/dsc/overview
+[07]: /powershell/dsc/resources/resources
+[08]: https://github.com/microsoft/powerstig
+[09]: https://github.com/microsoft/powerstig#powerstigdata
+[10]: https://github.com/microsoft/powerstig#powerstigdsc
+[11]: https://public.cyber.mil/stigs/
+[12]: https://www.powershellgallery.com