Azure Classic Administrator Roles: Key Concepts and Management

As an Azure Classic administrator, you'll need to understand the different roles and their responsibilities to effectively manage your cloud services. The Co-Administrator role is one such role that allows two or more users to share administrative tasks and responsibilities.

The Co-Administrator role is a key concept in Azure Classic administration, enabling multiple users to collaborate and manage cloud services. This role is particularly useful in scenarios where multiple administrators need to work together to manage a cloud service.

To manage Azure Classic administrator roles, you'll need to understand the concept of Role-Based Access Control (RBAC). RBAC is a security feature in Azure Classic that allows administrators to assign specific permissions to users based on their roles. This ensures that users only have access to the resources and features they need to perform their tasks.

Azure Classic administrator roles are managed through the Azure Management Portal, where you can add, remove, and modify roles as needed.

For another approach, see: How to Create Rbac Role in Azure

Azure Classic Administrator Roles are crucial for managing Azure subscriptions, and understanding their roles can help you navigate the Azure portal with ease.

To view a list of Classic administrators, you need to be an Owner of a subscription and follow the steps outlined in the Azure portal.

As an Owner, you can access the Classic administrators tab to view a list of Co-Administrators. This is a key role that allows you to manage resources and services across a subscription.

Classic administrators can be categorized into two main roles: Service Administrators and Co-Administrators. Service Administrators have the same access as Owners, while Co-Administrators have limited privileges.

Here's a breakdown of the Classic administrator roles:

To remove a Service Administrator, you must have a user assigned the Owner role at subscription scope without conditions. This ensures that the subscription is not left without an administrator.

In some cases, you may need to add a Co-Administrator to manage resources and services alongside the primary Service Administrator. This is especially true for project managers who need to manage resources and services without the full privileges of the Service Administrator.

A different take: Azure Kubernetes Service vs Azure Container Apps

To convert a Co-Administrator to an Owner role, you'll need to sign in to the Azure portal as an Owner of a subscription. This is the easiest way to make the change.

You can find the Co-Administrators by selecting the Classic administrators tab in the Access control (IAM) section of a subscription. From there, you can select the Assign RBAC role link in the Remediate column to convert the Co-Administrator role assignment to the Owner role.

Here's a step-by-step guide to make the change:

Converting a Co-Administrator to Owner Role is a straightforward process that can be done in the Azure portal.

To start, you'll need to sign in as an Owner of the subscription you want to modify.

Sign in to the Azure portal as an Owner of a subscription, and then navigate to the Subscriptions page.

From there, select the subscription you want to work with and click on Access control (IAM).

In the IAM page, select the Classic administrators tab to view a list of Co-Administrators.

To convert a Co-Administrator to an Owner, select the Co-Administrator you want to modify and click on the Assign RBAC role link under the Remediate column.

In the Add role assignment pane, review the role assignment to ensure you're assigning the correct permissions.

Finally, select Review + assign to assign the Owner role and remove the Co-Administrator role assignment.

Consider reading: Azure Role Assignments

Removing a Service Administrator is a crucial step in managing roles within Azure. To do this, you'll need to have a user assigned the Owner role at subscription scope without conditions.

This is important because a subscription Owner has the same access as the Service Administrator, so you'll need to have someone with this level of access to remove the Service Administrator.

To remove the Service Administrator, sign in to the Azure portal as an Owner of a subscription. Once you're signed in, open the Subscriptions page and select a subscription.

Next, select Access control (IAM) and then click on the Classic administrators tab. Here, you can add a check mark next to the Service Administrator to select it for removal.

Finally, click Delete and then select Yes in the message box that appears to confirm the removal.

Note: It's essential to have a user with the Owner role at subscription scope without conditions to avoid orphaning the subscription.

Azure Classic Administrator Roles are divided into two categories: Service Administrator and Co-Administrator.

The Service Administrator has full access to all services and resources within the subscription, including the ability to manage billing and access to all Azure services.

They can also reset passwords for other users and manage user roles.

Co-Administrators have limited access to certain services and resources, but can still manage user roles and reset passwords.

They can also view and manage Azure usage and costs.

A Service Administrator can delegate Co-Administrator roles to other users, giving them the ability to manage specific services and resources.

This allows for a more distributed and collaborative approach to Azure management.

As an Azure Classic Administrator, you'll need to understand the different roles and specialists involved in managing your subscription.

Co-administrators can create, edit, and delete subscriptions, as well as manage billing and support contacts.

They can also reset passwords and manage user permissions.

Co-administrators have the same level of access as the primary administrator.

Service Administrators can manage service settings, such as Active Directory, SQL databases, and virtual networks.

They can also manage service usage and costs.

Service Administrators can view and manage service subscriptions.

Co-Administrators can manage the subscription's settings, but they cannot manage service settings.

The primary administrator can manage all aspects of the subscription, including billing and support contacts.

Expand your knowledge: Find Azure Administrators List

Classic subscription roles are designed to provide specific levels of access and control for administrators.

There are two classic subscription roles: Service Administrator and Co-Administrator. A Service Administrator has full privileges to manage resources and services, while a Co-Administrator has limited privileges but can still manage resources and services alongside the primary Service Administrator.

An operations manager may need to be a Service Administrator to perform a broad range of tasks, including provisioning new resources and configuring existing ones, across an Azure subscription.

A project manager, on the other hand, may only need to be a Co-Administrator to manage resources and services alongside the primary Service Administrator but without the full privileges of the Service Administrator.

To view a list of classic administrators, sign in to the Azure portal as an Owner of a subscription, open Subscriptions, select a subscription, and then select Access control (IAM). From there, select the Classic administrators tab to view a list of Co-Administrators.

Alternatively, you can use the Azure Resource Graph Explorer to query the list of Service Administrators and Co-Administrators. This method requires setting the scope and authorization scope, and running a specific query to list the administrators based on the scope.

On a similar theme: Azure Resource Manager Reader Role