In today’s Ask the Admin, I’ll show you how to access and work with Azure Automation DSC reports.
One of the great things about Azure Automation DSC is not only does it democratize PowerShell DSC and make DSC easier to implement, but it also makes the collection of information about the compliance state of your servers simple, either using the management portal or PowerShell. Unlike PowerShell DSC, which requires you to set up an infrastructure, including a pull server, Azure Automation DSC puts all the pieces into place without you having to configure servers or keep them running 24/7.
For more information on Azure Automation DSC, see Introduction to Azure Automation Desired State Configuration and Getting Started with Azure Automation Desired State Configuration on the Petri IT Knowledgebase.
Let’s start by accessing DSC node reports in the Azure management portal.
In the node’s pane, under Reports, you’ll see a list of available reports for the node. Click on a report to view it.
It’s also possible to get limited information about the resource applied to the node.
The management portal also provides information about DSC configurations.
A pane for the resource will open, where you can see a list of compilation jobs that ran to deploy the configuration to the pull server in the Deployments to Pull Server box. Click on a job to see more details about the deployment. Click on any of the available titles to get more information.
In this article, I showed you how to access DSC node reports in Azure Automation DSC using the management portal. It’s also worth noting that Azure has an activity log that can be accessed from the automation account’s Settings pane, where you can perform queries to get detailed log information about Azure operations.