Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Azure – Role-based access control (RBAC)

Posted on August 20, 2019

Hello, everyone. In our previous post, we introduced Azure AD, covering licenses and also a comparison between Azure AD and Windows Server-based Active Directory. If you haven’t read it yet, click this link. In today’s article, we’ll explain what Azure Role-based Access Control (RBAC) is, what it’s used for, how to customize roles, and how to assign roles to a user using the portal and PowerShell.

What is Azure RBAC?

Azure RBAC is a role-based access control system that allows you to grant a user the access they need based on the role they hold within the company.

How do I identify my role in Azure?

In the Azure portal, sign in with your credential and go to the Azure AD > Roles and Administrators menu. You’ll see your role as shown below:

What are the types of RBAC?

Azure has (default) roles, but you can also customize them according to the company’s needs. You can create a role completely from scratch or customize one using the Azure portal.

How do I create a custom access?

    To create a custom access using the Azure portal, go to the Azure AD > Roles and Administrators menu and select the New custom role option.

Enter the role name and, optionally, a description.

In our custom role, we’ll select only read access to applications in Azure AD.

Click Next.

On the Review + Create tab, review the configured options and click Create.

With the role created, you can tell the difference between a default role and a custom one through the icon or the Type column. These options let you identify which roles were created by an administrator in Azure.

Assigning Roles in Azure

With the role created, let’s assign it to an existing user. In the Azure AD > Roles and Administrators menu, select the role you want to assign to a user. In this view, you can see which assignments exist for the selected role.

Click Add assignment to assign a user to the selected role.

Select a user and click Add.

In the screen below, you can see user Fred’s access assigned to the custom role for the default directory.

You can also identify which roles are assigned to a user through the menu Azure AD > All Users > select the user you want information about and click the Directory role option.

Creating a Custom Role Using PowerShell

Let’s now create a custom role based on a default Azure role using PowerShell, by customizing a .json file.

Let’s connect to Azure using PowerShell. If you don’t know how to connect to Azure, take a look at the article where I show how to configure the PowerShell module for Azure through this link.

Let’s run the command below and export the “Monitoring Contributor” role so we can edit it:

Get-AzRoleDefinition -Name "Monitoring Contributor" | ConvertTo-Json | Out-File C:\windows\temp\MonitoringContributorRole.json

Open the .json file with a code editor. If you don’t have one, I recommend Visual Studio Code, which is free and can be downloaded from this link.

Let’s edit the “Name”, “IsCustom”, “Description”, and “AssignableScopes” fields.

Save the .json document.

Let’s now create a custom role by importing the file we just edited.

 New-AzRoleDefinition -InputFile "C:\windows\temp\MonitoringContributorRole.json" 

Let’s list the existing custom roles using the command below:

 Get-AzRoleDefinition | ? {$_.IsCustom -eq $true} | FT Name, IsCustom 

Summary

In today’s post, we talked about Azure RBAC, how to assign access permissions in Azure with RBAC through the portal and using PowerShell.

In the next article, we’ll talk about custom domains and directories in Azure.

I hope this content has contributed to expanding your knowledge of Azure.

Did you like the post? Like and share it.

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra ID topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}