DEMO Azure Role Based Access Control – Azure RBAC DEMO step by step

Managing access to cloud resources is an important capability for any organization that uses the cloud. Azure role-based access control (Azure RBAC) helps you manage who has access to Azure resources, what users can do with those resources, and what areas they have access to.
DEMO of role-based access control in Azure
Azure RBAC is an authorization system based on Azure Resource Manager that enables fine-grained access management for Azure resources.

This video provides a quick overview of Azure RBAC DEMO Step by step explanation of Azure Role Based Access Control or RBAC

What can I do with Azure RBAC?
Here are some examples of what you can do with Azure RBAC:

Allow one user to manage virtual machines in a subscription and another user to manage virtual networks
Allow a DBA group to manage SQL databases in a subscription.
Allow a user to manage all resources in a resource group, such as virtual machines, websites, and subnets.
Allow an application to access all resources in a resource group

How Azure RBAC works
You control access to resources with Azure RBAC by creating role assignments. This is an important concept to understand – it's how permissions are enforced. A role assignment consists of three elements: security principal, role definition, and scope.

Security principal
A security principal is an object that represents a user, group, service principal, or managed identity that requests access to Azure resources. You can assign a role to each of these security principals.

Role definition
A role definition is a collection of permissions. It is usually referred to simply as a role. A role definition lists the operations that can be performed, such as read, write, and delete. Roles can be high-level, such as owner, or specific, such as virtual machine reader.

Azure includes several built-in roles that you can use. For example, the Virtual Machine Contributor role allows a user to create and manage virtual machines. If the built-in roles do not meet your organization's specific needs, you can create your own custom Azure roles.
Azure has data operations that allow you to grant access to data within an object. For example, if a user has read access to a storage account, they can read the blobs or messages in that storage account.
Scope
Scope is the set of resources to which access is applied. When you assign a role, you can further restrict the actions allowed by defining a scope. This is useful if you want to make someone a site contributor, but only for a group of resources.

In Azure, you can specify a scope at four levels: management group, subscription, resource group, or resource. Scopes are structured in a parent-child relationship. You can assign roles at each of these scope levels.

Role assignments
A role assignment assigns a role definition to a user, group, service principal, or managed identity at a specific scope to grant access. Access is granted by creating a role assignment, and access is revoked by removing a role assignment.

The following diagram shows an example of a role assignment. In this example, the Marketing group has been assigned the Contributor role for the Pharma Sales resource group. This means that users in the Marketing group can create or manage any Azure resource in the Pharma Sales resource group. Marketing users do not have access to resources outside the Pharma Sales resource group unless they are part of another role assignment.

Multiple role assignments
So what happens if you have multiple overlapping role assignments? Azure RBAC is an additive model, so your effective permissions are the sum of your role assignments. Consider the following example where a user is assigned the Contributor role at the subscription scope and the Reader role on a resource group. The sum of the Contributor and Reader permissions is effectively the Contributor role on the resource group. Therefore, in this case, the Reader role assignment has no effect.
Reject assignments
Previously, Azure RBAC was a pure allow model with no deny, but now Azure RBAC supports limited deny assignments. Similar to a role assignment, a deny assignment adds a set of deny actions to a user, group, service principal, or managed identity at a specific scope to deny access. A role assignment defines a set of allowed actions, while a deny assignment defines a set of disallowed actions. In other words, deny assignments prevent users from performing certain actions even if a role assignment grants them access. Deny assignments take precedence over role assignments.

#PaddyMaddy #cloudComputing #azuretutorial #microsoftazuretutorialforbeginners #azureforbeginners #azurebasics #microsoftazuretraining #Az900 #AZ500, #microsoftazurecertification, #AZ303 #az300 #az104 #paddyMaddy #azuretraining

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.