-
Notifications
You must be signed in to change notification settings - Fork 964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Change tracking policies to now support all regions that are available #1703
Comments
Hi @steph409, thank you for your feedback. MMA retires on the 31 of August, however, this does not mean that the agent will turn of please see Important Note on what you can expect when you use the MMA or OMS agent after this date. For example, data upload will continue to work for existing agent until February 1 2025.
Good point on the Change Tracking policies, those indeed need to be updated. I will reach out internally to the policy owners and keep you updated. |
@arjenhuitema @jtracey93 should we not work on removing the |
@Springstone yes correct. I got confirmation that
|
@steph409 FYI, PG is updating the built-in policies. We'll keep this open to track. |
Describe the solution you'd like
Hi!
The old log analytics agent will be turned off in august 2024 and moving to AMA quickly is critical. Unfortunately, the change tracking built-in policies that you are using in the enterprise scale have a hard-coded list of supported regions.
Policy definition id: /providers/Microsoft.Authorization/policyDefinitions/4bb303db-d051-4099-95d2-e3e1428a4d2c
This list seems to be outdated. When looking in the portal at the change tracking, there are other regions which can do change tracking, e.g. Germany west central:
Please update the policy so that the change tracking can be rolled out using the enterprise scale, because this is
blocking migration to the new monitoring agent.
The text was updated successfully, but these errors were encountered: