Open jtracey93 opened 2 years ago
Currently working with the Azure Monitor product group to determine potential fixes / solutions to these.
Just in the way of a quick update on these, I am working with the respective product groups to progress.
As regards the Azure Migrate issue we are trying to locate the team who manage custom image metadata provisioning.
For the Gen2 and Windows 2022 we are in discussions with the team who manage the agents and are discussing options around AMA suitability and timescales.
If anyone else is experiencing issues related to any of these please respond to this thread so we can capture these.
Thanks Paul
Hello
Just to highlight my customers are running into the same issues when deploying Gen2 or Server 2022 virtual machines against Enterprise-scale best practices. (Azure policy enforcement)
timelines for the new AMA agent would be appreciated. :)
Just to provide an update on this as its been rumbling on for sometime, Monitor engineering team have confirmed they won't be adding Gen2 or Server 2022 for current built-in policy. They have confirmed that AMA will support these and they are working hard to provide parity and I expect a lot of the features to light up this CY. Please look to work with your Microsoft counterparts to help planning your migration from MMA to AMA.
Trigger ADO Sync 1
Trigger ADO Sync 2
Summary
This issue combines multiple issues and feedback received in relation to Azure Monitor agents (Log Analytics & Dependency agents) for VMs in ESLZ into a single issue for ease of tracking and updates.
Linked Issues
Others