Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: ✔️ Windows PowerShell 5.1
Note
Azure Automation State Configuration will be retired on September 30, 2027, please transition to Azure Machine Configuration by that date. For more information, see the blog post announcement. 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.
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 Azure.
This article explains how to create configurations to manage the following scenarios:
- Create a web server
- Create a DNS server
- Create a server that runs SharePoint
- Configure a SQL cluster
- Manage firewall settings
- Manage password settings
We recommend that you package the configuration as a Composite Resource before you share it with others as creating composite resources for the first time can be a tedious effort.
A CompositeResource is a community maintained solution that automates the process of creating a new module from your configuration.
Follow the steps to create a composite resource module:
- Ensure the configuration script is loaded in your PowerShell session by dot sourcing the script.
- Rather than running the configuration to generate a MOF file, use the command provided by the CompositeResource module to automate a conversion. The command loads the contents of your configuration, gets the list of parameters, and generates a new module. After you generate a module, you can increment the version and add release notes each time you make changes and publish it to your own PowerShellGet repository.
- Use the module in the Composable Authoring Experience in Azure, or add them to DSC Configuration scripts to generate MOF files and upload the MOF files to Azure Automation.
- Register your servers from either on-premises or in Azureto pull configurations.
Note
The latest update to the project has also published runbooks for Azure Automation to automate the process of importing configurations from the PowerShell Gallery.
For more information on how to automate the creation of composite resources for DSC, see PowerShell Gallery and download the solution or select Project Site to view the documentation.
- To understand PowerShell DSC, see Windows PowerShell Desired State Configuration overview.
- For more information about PowerShell DSC resources, see DSC Resources.
- For information about Local Configuration Manager configuration, see Configuring the Local Configuration Manager.