Transition to role-based access control (RBAC) in Azure by 31 August 2024

Question

I created an Azure Account for deployment and have a service Administrator role in side Home > My resource group > Access control (IAM) > Classic administrators, I am the only person using this account as an owner and do not have any co-administrator and another person who is accessing this azure account
I got a mail related to "Transition to role-based access control (RBAC) in Azure by 31 August 2024". Do I need to do any actions related to this and if yes please provide the solution?
if I don't take any action what will happen please guide me to that as well.

Answer 1

Hi @Arpita Pathak ,yes, you do need to take action related to the transition to role-based access control (RBAC) in Azure by 31 August 2024.

RBAC is the recommended way to manage access to Azure resources, and it provides more granular control over permissions than the classic administrator roles.

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.

If you don't take any action, your classic administrator roles will continue to work until 31 August 2024. 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.

Please let me know if you have any questions and I can help you further.

If this answer helps you please mark "Accept Answer" so other users can reference it.

Thank you,

James

Answer 2

@Arpita Pathak

Thank you for reaching out to us on this. I have looked at the screenshot that you have posted in previous comment.

I understand that you are the only service administrator in your tenant. The article that James has provided to you mentions only about co-administrators. However, the same applies to service administrators as well.In RBAC there is only have one owner role and one contributor role on subscription level. These roles are highest privileged role in RBAC on the subscription level. Other built-in roles are used to handle other resources like, VM's, storage etc.

Owner role is the one which is equivalent to service administrator and co-administrator role in classic subscription administrator role.

The rest of the built-in roles allow management of specific Azure resources. For example, the Virtual Machine Contributor role allows the user to create and manage virtual machines. For a list of all the built-in roles, see Azure built-in roles.

You refer below article,

https://learn.microsoft.com/en-us/azure/role-based-access-control/rbac-and-directory-admin-roles#azure-roles

For service administrator, you can have the same user account have owner role assigned on the subscription.

To replace service administrators with new role, you can follow below article,

https://learn.microsoft.com/en-us/azure/role-based-access-control/classic-administrators#step-4-replace-existing-co-administrators-with-owner-role-and-conditions

Note: In the above article it is mentioned as co-administrators, but you can consider the same steps for service administrators as well.

Let me know if you have any further questions

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.