Add include file for AADSC retirement announcement.

sdwheeler · sdwheeler · commit b2854ba29cab · 2024-10-03T15:20:40.000-04:00
diff --git a/articles/automation/automation-dsc-cd-chocolatey.md b/articles/automation/automation-dsc-cd-chocolatey.md
@@ -11,8 +11,7 @@ ms.service: azure-automation
 
 # Set up continuous deployment with Chocolatey
 
-> [!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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 In a DevOps world, there are many tools to assist with various points in the continuous integration
 pipeline. Azure Automation [State Configuration](automation-dsc-overview.md) is a welcome new addition to the options that DevOps teams can employ.
diff --git a/articles/automation/automation-dsc-compile.md b/articles/automation/automation-dsc-compile.md
@@ -11,8 +11,7 @@ ms.service: azure-automation
 
 # Compile DSC configurations in Azure Automation State Configuration
 
-> [!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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 You can compile Desired State Configuration (DSC) configurations in Azure Automation State Configuration in the following ways:
 
diff --git a/articles/automation/automation-dsc-config-data-at-scale.md b/articles/automation/automation-dsc-config-data-at-scale.md
@@ -14,13 +14,12 @@ 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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.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.
 
-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](/powershell/dsc/configurations/configdata) as it involves organizing information across logical constructs like location, type, and environment.
 
 ## Community project: Datum
 
diff --git a/articles/automation/automation-dsc-config-from-server.md b/articles/automation/automation-dsc-config-from-server.md
@@ -14,15 +14,14 @@ 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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.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.
 
-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. 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.
 
-## 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.
 
diff --git a/articles/automation/automation-dsc-configuration-based-on-stig.md b/articles/automation/automation-dsc-configuration-based-on-stig.md
@@ -13,8 +13,7 @@ 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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.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.
diff --git a/articles/automation/automation-dsc-create-composite.md b/articles/automation/automation-dsc-create-composite.md
@@ -14,8 +14,7 @@ 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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 > [!IMPORTANT]
 > This article refers to a solution that is maintained by the Open Source community and support is only available in the form of GitHub collaboration, not from Microsoft.
@@ -29,15 +28,15 @@ This article, explains on creating **scenarios** that manage groups of settings,
 - Manage firewall settings
 - Manage password settings
 
-We recommend that you package the configuration as a [Composite Resource](/powershell/dsc/resources/authoringresourcecomposite) before you share it with others as creating composite resources for the first time can be a tedious effort. 
- 
+We recommend that you package the configuration as a [Composite Resource](/powershell/dsc/resources/authoringresourcecomposite) before you share it with others as creating composite resources for the first time can be a tedious effort.
+
 ## Community project - CompositeResource
 
-A [CompositeResource](https://github.com/microsoft/compositeresource) is a community maintained solution that 
+A [CompositeResource](https://github.com/microsoft/compositeresource) is a community maintained solution that
 has been created to resolve this challenge. Composite Resource automates the process of creating a new module from your configuration.
 
 
-## Create a composite resource module 
+## Create a composite resource module
 
 Follow the steps to create a composite resource module:
 
diff --git a/articles/automation/automation-dsc-diagnostics.md b/articles/automation/automation-dsc-diagnostics.md
@@ -4,15 +4,14 @@ description: This article tells how to send Desired State Configuration reportin
 services: automation
 ms.subservice: desired-state-config
 ms.date: 08/20/2024
-ms.topic: how-to 
+ms.topic: how-to
 ms.custom: devx-track-azurepowershell
 ms.service: azure-automation
 ---
 
 # Integrate Azure Automation State Configuration with Azure Monitor Logs
 
-> [!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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 Azure Automation State Configuration retains node status data for 30 days. You can send node status data to [Azure Monitor Logs](/azure/azure-monitor/logs/data-platform-logs) if you prefer to retain this data for a longer period. Compliance status is visible in the Azure portal or with PowerShell, for nodes and for individual DSC resources in node configurations.
 
@@ -49,7 +48,7 @@ To begin importing data from Azure Automation State Configuration into Azure Mon
     {
         Connect-AzAccount
     }
-    
+
     # If you have multiple subscriptions, set the one to use
     # Select-AzSubscription -SubscriptionId "<SUBSCRIPTIONID>"
     ```
@@ -66,7 +65,7 @@ To begin importing data from Azure Automation State Configuration into Azure Mon
    ```powershell
    # Find the ResourceId for the Automation account
    $AutomationResourceId = (Get-AzResource `
-      -ResourceType 'Microsoft.Automation/automationAccounts' | 
+      -ResourceType 'Microsoft.Automation/automationAccounts' |
       WHERE {$_.Name -eq $automationAccount}).ResourceId
    ```
 
@@ -75,7 +74,7 @@ To begin importing data from Azure Automation State Configuration into Azure Mon
    ```powershell
     # Find the ResourceId for the Log Analytics workspace
     $WorkspaceResourceId = (Get-AzResource `
-        -ResourceType 'Microsoft.OperationalInsights/workspaces' | 
+        -ResourceType 'Microsoft.OperationalInsights/workspaces' |
         WHERE {$_.Name -eq $law}).ResourceId
    ```
 
@@ -147,7 +146,7 @@ To learn more about constructing log queries to find data, see [Overview of log
 One advantage of using Azure Monitor Logs is that you can search for failed checks across nodes. To find all instances of DSC resources that have failed, use the following query:
 
 ```kusto
-AzureDiagnostics 
+AzureDiagnostics
 | where Category == "DscNodeStatus"
 | where OperationName == "DscResourceStatusData"
 | where ResultType == "Failed"
@@ -158,8 +157,8 @@ AzureDiagnostics
 To visualize your DSC node status history over time, you can use this query:
 
 ```kusto
-AzureDiagnostics 
-| where ResourceProvider == "MICROSOFT.AUTOMATION" 
+AzureDiagnostics
+| where ResourceProvider == "MICROSOFT.AUTOMATION"
 | where Category == "DscNodeStatus"
 | where ResultType != "started"
 | summarize count() by ResultType
diff --git a/articles/automation/automation-dsc-extension-history.md b/articles/automation/automation-dsc-extension-history.md
@@ -11,8 +11,7 @@ ms.service: azure-automation
 
 # Work with Azure Desired State Configuration extension version history
 
-> [!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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 The Azure Desired State Configuration (DSC) VM [extension](/azure/virtual-machines/extensions/dsc-overview) is updated as-needed to support enhancements and new capabilities delivered by Azure, Windows Server, and the Windows Management Framework (WMF) that includes Windows PowerShell.
 
diff --git a/articles/automation/automation-dsc-getting-started.md b/articles/automation/automation-dsc-getting-started.md
@@ -11,8 +11,7 @@ ms.service: azure-automation
 
 # Get started with Azure Automation State Configuration
 
-> [!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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 This article provides a step-by-step guide for doing the most common tasks with Azure Automation State Configuration, such as creating, importing, and compiling configurations, enabling machines to manage, and viewing reports. For an overview State Configuration, see [State Configuration overview](automation-dsc-overview.md). For Desired State Configuration (DSC) documentation, see [Windows PowerShell Desired State Configuration Overview](/powershell/dsc/overview).
 
@@ -199,7 +198,7 @@ The DSC node can take any of the following six values as follows:
 
 >[!NOTE]
 >- **RefreshFrequencyMins** - It defines the frequency of node contacting the agent service and can be provided as part of onboarding to DSC. It takes a maximum value of 10080 minutes.
->- Node will be marked as **Unresponsive** if the node does not contact the agent service for 1440 minutes (1 Day). We recommend that you use **RefreshFrequencyMins** value < 1440 minutes, else the node would show in a false **Unresponsive** state. 
+>- Node will be marked as **Unresponsive** if the node does not contact the agent service for 1440 minutes (1 Day). We recommend that you use **RefreshFrequencyMins** value < 1440 minutes, else the node would show in a false **Unresponsive** state.
 
 ## View reports for managed nodes
 
diff --git a/articles/automation/automation-dsc-onboarding.md b/articles/automation/automation-dsc-onboarding.md
@@ -11,8 +11,7 @@ ms.custom:
 
 # Enable Azure Automation State Configuration
 
-> [!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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 This topic describes how you can set up your machines for management with Azure Automation State Configuration. For details of this service, see [Azure Automation State Configuration overview](automation-dsc-overview.md).
 
diff --git a/articles/automation/automation-dsc-overview.md b/articles/automation/automation-dsc-overview.md
@@ -11,8 +11,7 @@ ms.topic: overview
 
 # Azure Automation State Configuration overview
 
-> [!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 [Azure Machine Configuration](../governance/machine-configuration/overview.md). The Azure Machine Configuration service combines features of DSC Extension, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Azure Machine Configuration also includes hybrid machine support through [Arc-enabled servers](/azure/azure-arc/servers/overview).
+[!INCLUDE [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 Azure Automation State Configuration is an Azure configuration management service that allows you to write, manage, and
 compile PowerShell Desired State Configuration (DSC) [configurations](/powershell/dsc/configurations/configurations) for nodes in any cloud or on-premises datacenter. The service also imports [DSC Resources](/powershell/dsc/resources/resources), and assigns configurations to target nodes, all in the cloud. You can access Azure Automation State Configuration in the Azure portal by selecting **State configuration (DSC)** under **Configuration Management**.
diff --git a/articles/automation/automation-dsc-remediate.md b/articles/automation/automation-dsc-remediate.md
@@ -11,8 +11,7 @@ ms.date: 07/17/2019
 
 # Remediate noncompliant Azure Automation State Configuration servers
 
-> [!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 [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
 
 When servers are registered with Azure Automation State Configuration,
 the configuration mode is set to `ApplyOnly`, `ApplyAndMonitor`, or `ApplyAndAutoCorrect`. If the mode isn't set to `ApplyAndAutoCorrect`,
@@ -36,7 +35,7 @@ Update-DscConfiguration -Wait -Verbose
 
 ## Correct drift of Linux virtual machines
 
-For Linux virtual machines, you don't have the option of using the `Run` command. You can only correct drift for these machines by repeating the registration process. 
+For Linux virtual machines, you don't have the option of using the `Run` command. You can only correct drift for these machines by repeating the registration process.
 
 For Azure nodes, you can correct drift from the Azure portal or using Az module cmdlets. Details about this process are documented in [Enable a VM using Azure portal](automation-dsc-onboarding.md#enable-a-vm-using-azure-portal).
 
diff --git a/articles/automation/compose-configurationwithcompositeresources.md b/articles/automation/compose-configurationwithcompositeresources.md
@@ -10,6 +10,8 @@ ms.service: azure-automation
 ---
 # Compose DSC configurations
 
+[!INCLUDE [aadsc-eol](~/includes/dsc-automation/aadsc-eol.md)]
+
 When you need to manage resource with more than a single desired state configuration (DSC), the best path is to use [composite resources](/powershell/dsc/resources/authoringresourcecomposite). A composite resource is a nested and parameterized configuration being used as a DSC resource within another configuration. Use of composite resources allows you to create complex configurations while allowing the underlying composite resources to be individually managed and built.
 
 Azure Automation enables the [import and compilation of composite resources](automation-dsc-compile.md). Once you've imported composite resources into your Automation account, you can use Azure Automation State Configuration through the **State Configuration (DSC)** feature in the Azure portal.
diff --git a/articles/automation/quickstarts/dsc-configuration.md b/articles/automation/quickstarts/dsc-configuration.md
diff --git a/articles/automation/state-configuration/remove-node-and-configuration-package.md b/articles/automation/state-configuration/remove-node-and-configuration-package.md
diff --git a/articles/automation/troubleshoot/desired-state-configuration.md b/articles/automation/troubleshoot/desired-state-configuration.md
diff --git a/articles/automation/tutorial-configure-servers-desired-state.md b/articles/automation/tutorial-configure-servers-desired-state.md
diff --git a/articles/governance/machine-configuration/whats-new/migrating-from-azure-automation.md b/articles/governance/machine-configuration/whats-new/migrating-from-azure-automation.md
diff --git a/includes/dsc-automation/aadsc-eol.md b/includes/dsc-automation/aadsc-eol.md
