Start simple with inventory. Customise the Azure Arc-enabled Servers view and then create a resource graph query that can go across subscriptions.
As well as centralising monitoring and improving security, the most common use case for Azure Arc-enabled Servers is simple asset management.
Azure Arc | Servers
After the agent is installed, verify that the servers have successfully connected in the Azure portal in the Azure Arc service, Servers blade.
Edit the view.
- Remove the default tags
- Add the city, datacentre, cluster and platform tags
Save the view as “Arc Hack”
Set as the default view
Simple Resource Graph query
One of the benefits of onboarding on prem VMs to Azure is the core management plane organisation and reporting. The Kusto queries in Resource Graph Explorer is great for reporting across multiple subscriptions and resource groups.
If you are new to Resource Graph, the quickstart with Azure Portal is a great place to begin.
Create and save a simple Resource Graph query that lists the connected machines
Hint: Look at the properties blade for an Azure Arc-enabled Server to find the provider type and then search the resources in the Resource Graph Explorer.
Refined Resource Graph use (optional)
This is a stretch target.
- Customise the previous query to only show the following fields
Save the query
Add to a workbook and save to the poc_pilot resource group
Hint: Check out the Kusto Query Language’s project operator
Screen share with your proctor to show your
- Azure Arc-enabled Servers in the Azure Portal with the customised view
- Resource Graph KQL query and tabular output
In the next lab you will start looking at monitoring and security.
Help us improve
Azure Citadel is a community site built on GitHub, please contribute and send a pull requestMake a change