Announcing public preview: Azure Change Tracking & Inventory using Azure Monitor agent (AMA)
What’s New?
The Change Tracking and Inventory service tracks changes to Files, Registry, Software, Services and Daemons and uses the MMA (Microsoft Monitoring Agent)/OMS (Operations Management Suite) agent. This preview supports the new AMA agent and enhances the following:
- Security/Reliability and Scale - The Azure Monitor Agent enhances security, reliability, and facilitates multi-homing experience to store data.
- Simplified onboarding- You can onboard to Virtual Machines directly to Change Tracking (add link) without needing to configure an Automation account. In new experience, there is
- Rules management – Uses Data Collection Rules to configure or customize various aspects of data collection. For example, you can change the frequency of file collection. DCRs let you configure data collection for specific machines connected to a workspace as compared to the "all or nothing" approach of legacy agents.
How to get started?
You can onboard to Change Tracking & Inventory with AMA either via Azure Portal or by using Azury Policy (to onboard at scale). To onboard single VM via portal, click on specific VM name from Virtual Machines -> Change Tracking -> Enable using AMA agent (Preview). To know more about the various methods to enable Change Tracking, click here
Onboarding from Single VM view
Onboarding via DINE Policies (at scale onboarding)
In the public preview, Change Tracking with AMA supports Window Files, Windows Registry and Software data types. We are working towards facilitating the support of Windows services & Linux Daemons by GA. The data configuration can now be regulated at DCR level now. Click here to know more about Data Collection Rules.
You can check out our complete documentation to get more details. We’d love to hear what you like and don’t like about this feature, and where you’d like us to take it. Please click here to Sign Up and try out the new enhancements.
Published on:
Learn moreRelated posts
Which Azure Cosmos DB Role Does My App Need?
In the previous post in the series, we covered the security decisions you make on day one. In this part, we will talk about how to give your a...
Find and fix app issues - Azure Copilot Observability Agent
Cut through alert noise and move from detection to root cause using the Azure Copilot Observability Agent. It autonomously investigates incide...
Azure Functions MCP Extension: What’s New at Build 2026
A roundup of what shipped in the Azure Functions MCP extension since preview: resource and prompt triggers, MCP Apps, built-in MCP authenticat...
Secure Boot certificate updates for Linux on Azure virtual machines
Microsoft has published new guidance for managing Secure Boot certificate updates for Linux on Azure virtual machines, including Trusted Launc...
Soluzione Earns Microsoft Solutions Partner Designation for Digital & App Innovation (Azure)
Soluzione is pleased to announce that it has earned the Microsoft Solutions Partner designation for Digital & App Innovation (Azure). This...
Azure SDK Release (May 2026)
Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (May 2026) app...
How to Use Deep Agents with Azure Cosmos DB – Plan, act, and verify against operational data
Deep Agents is an agent harness built on LangGraph, for agents that need to work through a task over many steps instead of a single LLM call. ...
Retirement of Azure DevOps issuer in Workload identity federation service connections
We are announcing the deprecation of the Azure DevOps issuer in workload identity federation (WIF) service connections, with planned retiremen...