You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Review your security RBAC assignments before 22 October 2025 and make changes or additions as needed.
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:
Review the ServiceHealthResources properties that will require elevated access and make changes or additions before 22 October 2025.
Visit Microsoft Learn to read more about these changes and stay informed about Azure security issues.
The text was updated successfully, but these errors were encountered:
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:
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:
If you’re accessing security advisories in Azure Resource Graph:
Visit Microsoft Learn to read more about these changes and stay informed about Azure security issues.
The text was updated successfully, but these errors were encountered: