Action required: Convert Azure classic administrator roles to Azure RBAC roles

Andrew Rivera (HE/HIM) 0 Reputation points Microsoft Employee
2025-01-09T15:53:13.85+00:00

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 be orphaned (become ownerless).

If you have a question, please post it in this thread.

Azure Role-based access control
Azure Role-based access control
An Azure service that provides fine-grained access management for Azure resources, enabling you to grant users only the rights they need to perform their jobs.
858 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Goutam Pratti 1,310 Reputation points Microsoft Vendor
    2025-01-09T18:56:21.09+00:00

    Hello @Andrew Rivera (HE/HIM) ,

    Thank you for reaching out Microsoft Q&A and sharing details.

    Yes, as per the documentation Azure classic administrator roles retired on August 31, 2024.

    If your organization has any active Co-Administrator or Service Administrator roles, you need to transition them to Azure role-based access control (RBAC) roles by then. Azure Service manager and all Azure classic resources also retire on that date.

    To avoid potential disruptions in service, transition any classic administrator roles that still need access to your subscription to Azure RBAC roles. For more information, see Prepare for Co-Administrators retirement.

    After August 31, 2024:

    • When you create an Azure subscription, the classic Service Administrator role isn't assigned to the subscription. Instead, the user creating the subscription is assigned the Azure RBAC Owner role.
    • During the Azure subscription Change Directory operation, the user isn't assigned the Service Administrator role. Instead, the user completing the Change Directory action is assigned the Azure RBAC Owner role.
    • For situations that require changing or removing Service Administrators, ensure that the subscription has Azure RBAC owners assigned on it. If you're a subscription Azure RBAC owner, you can remove the current Service administrator using the information at Service Administrator retirement. If you aren't a subscription RBAC owner, ask your subscription Azure RBAC owner or a global administrator to update or remove the intended service administrator on the subscription. Or you can ask them to give you an Azure RBAC role so that you can update or remove the Service Administrator.

    If you are encountering any issues, you can provide details....

    for additional information follow: https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/classic-administrator-retire?source=recommendations

    Do let us know if you any further queries.


    Regards,
    Goutam Pratti.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.