Convert to Azure role-based access control (RBAC)

Question

I got the following mail but do not know what I have to do? Can someone please help me.

Convert to Azure role-based access control (RBAC) 

You're receiving this additional notice because you use Azure classic administrator roles. Azure classic administrator roles were retired on 31 August 2024 and are no longer supported. If you still have active Co-Administrator or Service Administrator role assignments, convert these roles to Azure RBAC immediately.

Required action

To avoid service disruptions, convert classic admin roles that still need access to your subscription to Azure RBAC roles immediately. If you do not take action, your subscription may become ownerless and you could lose access to it. 

Help and support

If you have questions, ask community experts in Microsoft Q&A. If you have a support plan and you need technical help, open the Azure portal and select the question mark icon at the top of the page.  _Learn more about service retirements that may impact your resources in the Azure Retirement Workbook. Please note that retirements may not be visible in the workbook for up to two weeks after being announced.  _Please help us improve our communication by telling us what you think about this email in a survey.

Answer 1

Hello @Jens Bäuerle

Essentially you are being notified that one or more user accounts for one or more Azure Subscriptions you manage has an administrator and/or co-administrator assignment.

Classic resources and classic administrators will be retired on August 31, 2024. Starting April 30, 2025, you won't be able to add new Co-Administrators. This date was recently extended. Remove unnecessary Co-Administrators and use Azure RBAC for fine-grained access control.

Microsoft recommends that you manage access to Azure resources using Azure role-based access control (Azure RBAC). However, if you're still using the classic deployment model, you'll need to use a classic subscription administrator role: Service Administrator and Co-Administrator. For information about how to migrate your resources from classic deployment to Resource Manager deployment, see Azure Resource Manager vs. classic deployment.

To transition to RBAC, you will need to create custom roles that define the specific permissions needed for your users to perform their tasks. You can then assign these roles to your users or groups.

To get started, you can follow the steps outlined in this document.

Similar Q&A article:
Transition-to-role-based-access-control-(rbac)-in - Article 1
Transition-to-role-based-access-control-(rbac)-in - Article 2
Transition-to-role-based-access-control-(rbac)-in -Article 3

If you don't take any action, your classic administrator roles will continue to work until 30 April 2025. After that date, any users or groups assigned to classic administrator roles will lose access to those roles, and you will need to transition to RBAC to manage access to your resources.

If you don't have any "Classic Administrators" in Your subscriptions, but You have still received this email then please do check this Q&A article: https://learn.microsoft.com/en-us/answers/questions/1616658/transition-to-role-based-access-control-(rbac)-in
https://learn.microsoft.com/en-us/answers/questions/2236415/classic-administrators-x-rbac

I hope this clarifies things.

Please remember to "Accept Answer", so that others in the community facing similar issues can easily find the answers.