Users and groups in Azure - Commands & Configuration

Introduction

Managing users and groups helps control who can access your cloud resources. It solves the problem of keeping your environment secure by giving the right permissions to the right people.

When you want to give a new team member access to your Azure resources.

When you need to organize users by their roles or departments for easier permission management.

When you want to remove access for someone who no longer works on your project.

When you want to assign permissions to multiple users at once using groups.

When you want to audit who has access to your cloud resources.

Commands

This command creates a new user named Alice Johnson with a secure password in Azure Active Directory.

Terminal

az ad user create --display-name "Alice Johnson" --user-principal-name [e-mail] --password "StrongP@ssw0rd!"

Expected Output

{

  "accountEnabled": true,

  "displayName": "Alice Johnson",

  "mailNickname": "alicejohnson",

  "userPrincipalName": "[e-mail]",

  "id": "12345678-90ab-cdef-1234-567890abcdef"

}

→

--display-name - Sets the full name of the user.

→

--user-principal-name - Sets the user's login name.

→

--password - Sets the user's initial password.

This command creates a new group called Developers to organize users with similar roles.

Terminal

az ad group create --display-name "Developers" --mail-nickname "developers"

Expected Output

{

  "displayName": "Developers",

  "mailNickname": "developers",

  "id": "abcdef12-3456-7890-abcd-ef1234567890"

}

→

--display-name - Sets the name of the group.

→

--mail-nickname - Sets the mail alias for the group.

This command adds the user Alice Johnson to the Developers group using her user ID.

Terminal

az ad group member add --group Developers --member-id 12345678-90ab-cdef-1234-567890abcdef

Expected Output

No output (command runs silently)

→

--group - Specifies the group to add the member to.

→

--member-id - Specifies the user ID to add to the group.

This command lists all members of the Developers group to verify the user was added.

Terminal

az ad group member list --group Developers

Expected Output

[

  {

    "displayName": "Alice Johnson",

    "id": "12345678-90ab-cdef-1234-567890abcdef",

    "userPrincipalName": "[e-mail]"

  }

]

→

--group - Specifies the group to list members from.

Key Concept

If you remember nothing else from this pattern, remember: groups let you manage permissions for many users at once, making access control simpler and safer.

Common Mistakes

Using the user's email instead of their object ID when adding to a group.

The command requires the unique user ID, not the email, so it will fail or add the wrong user.

Use 'az ad user show' to find the user's object ID and use that with '--member-id'.

Creating users without setting a strong password.

Weak passwords reduce security and may be rejected by Azure policies.

Always use a strong password with letters, numbers, and symbols when creating users.

Not verifying group membership after adding users.

You might think the user was added but they were not, causing access issues.

Run 'az ad group member list' to confirm the user is in the group.

Summary

Create users with 'az ad user create' to add people to your Azure directory.

Create groups with 'az ad group create' to organize users by role or team.

Add users to groups with 'az ad group member add' to manage permissions easily.

Verify group members with 'az ad group member list' to ensure correct access.

Practice

1. What is the main purpose of a group in Azure Active Directory?

easy

A. To monitor network traffic

B. To store files and documents

C. To create virtual machines

D. To manage permissions for multiple users together

Solution

1. Step 1: Understand the role of groups

   Groups in Azure AD are used to organize users and assign permissions collectively.

2. Step 2: Compare with other options

   Storing files, creating VMs, and monitoring traffic are unrelated to groups.

3. Final Answer:

   To manage permissions for multiple users together -> Option D

4. Quick Check:

   Groups = Manage multiple users' permissions [OK]

Hint: Groups bundle users for easy permission management [OK]

Common Mistakes:

• Confusing groups with storage or compute resources
• Thinking groups monitor network traffic
• Assuming groups create virtual machines

2. Which Azure CLI command correctly creates a new user named 'alice'?

easy

A. az ad user create --display-name alice

B. az user create --name alice

C. az ad user add --user alice

D. az create user --username alice

Solution

1. Step 1: Identify correct Azure CLI syntax

   The correct command to create a user is 'az ad user create' with a display name parameter.

2. Step 2: Check other options for syntax errors

   Options A, C, and D use incorrect commands or parameters not recognized by Azure CLI.

3. Final Answer:

   az ad user create --display-name alice -> Option A

4. Quick Check:

   Correct CLI user creation = az ad user create --display-name alice [OK]

Hint: Use 'az ad user create' to add users [OK]

Common Mistakes:

• Using 'az user create' instead of 'az ad user create'
• Incorrect parameter names like --name or --username
• Mixing commands from different Azure services

3. Given this Azure CLI command sequence, what is the output?

az ad group create --display-name DevTeam --mail-nickname devteam
az ad user create --display-name Bob
az ad group member add --group DevTeam --member-id Bob

medium

A. Creates group DevTeam but does not add Bob

B. Adds user Bob to group DevTeam successfully

C. Fails because user Bob does not have an ID

D. Returns syntax error on group member add command

Solution

1. Step 1: Analyze user creation command

   The user is created with display name only; no user ID is captured or referenced.

2. Step 2: Check group member add command

   The command requires a member ID, but 'Bob' is a display name, not an ID, causing failure.

3. Final Answer:

   Fails because user Bob does not have an ID -> Option C

4. Quick Check:

   Member add needs user ID, not display name [OK]

Hint: Use user object ID, not display name, to add group members [OK]

Common Mistakes:

• Using display name instead of user ID in member add
• Assuming user creation returns ID automatically
• Ignoring required parameters for group member commands

4. You run this command but get an error:

az ad group member add --group DevTeam --member-id alice

What is the most likely cause?

medium

A. You need to use --member-name instead of --member-id

B. The member ID 'alice' is not a valid object ID

C. The group DevTeam does not exist

D. The Azure CLI is not installed

Solution

1. Step 1: Understand member-id parameter

   The --member-id expects a unique object ID, not a username or display name.

2. Step 2: Evaluate other options

   Group existence error would be different; --member-name is not a valid parameter; CLI installation error would prevent any command.

3. Final Answer:

   The member ID 'alice' is not a valid object ID -> Option B

4. Quick Check:

   Member ID must be object ID, not username [OK]

Hint: Use object ID, not username, for --member-id [OK]

Common Mistakes:

• Using username instead of object ID
• Assuming --member-name is valid
• Ignoring error message details

5. You want to assign a role to all users in a group named 'Admins' using Azure CLI. Which sequence of commands correctly achieves this?

hard

A. az ad group show --group Admins --query id -o tsv | az role assignment create --assignee @- --role Contributor

B. az ad group member add --group Admins --member-id Contributor

C. az ad user create --display-name Admins
az role assignment create --assignee Admins --role Contributor

D. az ad group member list --group Admins | az role assignment create --assignee @- --role Contributor

Solution

1. Step 1: Use best practice for group roles

   Assign RBAC roles directly to the Azure AD group; permissions automatically apply to all members.

2. Step 2: Retrieve and use group object ID

   'az ad group show --group Admins --query id -o tsv | az role assignment create --assignee @- --role Contributor' gets the single-line object ID and pipes it to --assignee.

3. Step 3: Evaluate other options

   A misuses group member add; C creates a user instead of using group; D pipes JSON array from member list, causing invalid --assignee value.

4. Final Answer:

   az ad group show --group Admins --query id -o tsv | az role assignment create --assignee @- --role Contributor -> Option A

5. Quick Check:

   Group object ID -> role assignment [OK]

Hint: Assign roles to Azure AD groups using object ID [OK]

Common Mistakes:

• Assigning roles to individual group members instead of group
• Piping multi-line JSON to single --assignee parameter
• Confusing group membership with RBAC role assignment