Skip to content
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

INFO: Upcoming changes on Azure Resource Health #132

Open
jkroepke opened this issue Jan 24, 2025 · 0 comments
Open

INFO: Upcoming changes on Azure Resource Health #132

jkroepke opened this issue Jan 24, 2025 · 0 comments

Comments

@jkroepke
Copy link
Contributor

We got a mail from Azure today. It seems there is a new API version which needs to be used after 22 October.


To ensure sensitive security advisories are only received by people with elevated permissions, we’re making changes to role-based access control (RBAC) in Azure Service Health beginning 22 April 2025. To make the changes, we’ll:

  • Introduce a new version of the Resource Health API on 22 April 2025 which makes sure security advisory event details will be accessible only to privileged users.
  • Enable RBAC for security advisory events in the Azure portal on 22 October 2025.
  • Enable RBAC for security advisory events in Azure Resource Graph on 22 October 2025.

To avoid disruption, please ensure the right users have access by following the steps below.

Required action

If you’re accessing security advisories using the Azure portal:

If you monitor the health of your resources or services using the Resource Health API, including viewing security advisories:

  • Update to the new Resource Health API before old versions are deprecated, starting on 22 October 2025.
  • Use FetchEventDetails to view sensitive security information going forward.

If you’re accessing security advisories in Azure Resource Graph:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant