Why Azure AD tenants and directories? - Purpose & Use Cases

The Big Idea

What if managing hundreds of users could be as easy as clicking a button?

The Scenario

Imagine you run a company with many teams, each using different apps and services. You try to manage all user accounts and permissions by writing down details on paper or spreadsheets.

Every time someone joins or leaves, you have to update multiple lists manually.

The Problem

This manual way is slow and confusing. You might forget to remove access for someone who left, or give too many permissions by mistake.

It's hard to keep track of who can do what, and fixing errors takes a lot of time.

The Solution

Azure AD tenants and directories organize all users and permissions in one secure place.

This lets you easily add or remove users, control access to apps, and keep everything safe and tidy without manual chaos.

Before vs After

✗ Before

UserList = ['Alice', 'Bob']
# Manually update permissions in multiple places

✓ After

tenant = AzureAD.createTenant('MyCompany')
tenant.addUser('Alice')
tenant.assignRole('Alice', 'AppUser')

What It Enables

With Azure AD tenants, you can securely manage all users and apps in one place, saving time and avoiding mistakes.

Real Life Example

A school uses Azure AD tenants to give students and teachers access to different learning apps, easily adding new users each semester and removing old ones without hassle.

Key Takeaways

Manual user management is slow and error-prone.

Azure AD tenants centralize user and permission control.

This makes managing access faster, safer, and simpler.

Practice

1. What is an Azure AD tenant primarily used for?

easy

A. To store virtual machines in the cloud

B. To manage users and control access within an organization

C. To host websites publicly

D. To create databases for applications

Solution

1. Step 1: Understand Azure AD tenant purpose and identify correct use case

   An Azure AD tenant is a dedicated space for managing identities and access. It is not for hosting websites, storing VMs, or databases but for user and access management.

2. Final Answer:

   To manage users and control access within an organization -> Option B

3. Quick Check:

   Azure AD tenant = user and access management [OK]

Hint: Azure AD tenant = user and access management space [OK]

Common Mistakes:

• Confusing tenant with storage or hosting services
• Thinking tenant is a database service
• Assuming tenant manages virtual machines

2. Which of the following is the correct Azure CLI command to list all Azure AD tenants you have access to?

easy

A. az ad tenant list

B. az login tenant list

C. az tenant show

D. az account tenant list

Solution

1. Step 1: Recall Azure CLI commands for tenants and identify correct one

   The command to list tenants is under 'az account' namespace, not 'az ad'. 'az account tenant list' lists all tenants you have access to.

2. Final Answer:

   az account tenant list -> Option D

3. Quick Check:

   List tenants = az account tenant list [OK]

Hint: Use 'az account tenant list' to see all tenants [OK]

Common Mistakes:

• Using 'az ad tenant list' which is invalid
• Confusing 'az login' with tenant listing
• Using 'az tenant show' which does not exist

3. Given the following Azure CLI output snippet after running az account tenant list:

[{"tenantId": "1111-2222-3333-4444", "isDefault": true}, {"tenantId": "5555-6666-7777-8888", "isDefault": false}]

What does the isDefault field indicate?

medium

A. The tenant that is deleted

B. The tenant with the most users

C. The tenant currently active for your Azure session

D. The tenant with the highest subscription cost

Solution

1. Step 1: Understand 'isDefault' meaning and eliminate incorrect options

   'isDefault' marks which tenant is currently active in your Azure CLI session. It does not relate to user count, cost, or deletion status.

2. Final Answer:

   The tenant currently active for your Azure session -> Option C

3. Quick Check:

   isDefault = active tenant [OK]

Hint: 'isDefault' means active tenant in session [OK]

Common Mistakes:

• Thinking 'isDefault' means largest tenant
• Assuming it means deleted tenant
• Confusing it with billing or cost info

4. You run the command az ad tenant list but get an error saying the command is not found. What is the most likely cause?

medium

A. The Azure CLI does not have a direct 'az ad tenant list' command

B. You are not logged in to Azure CLI

C. Your account has no tenants

D. The Azure CLI version is too new

Solution

1. Step 1: Check command availability and verify other causes

   'az ad tenant list' is not a valid Azure CLI command; tenant listing is under 'az account'. Login issues or no tenants would give different errors; CLI version too new is unlikely to remove commands.

2. Final Answer:

   The Azure CLI does not have a direct 'az ad tenant list' command -> Option A

3. Quick Check:

   Invalid command = no 'az ad tenant list' [OK]

Hint: Tenant list is under 'az account', not 'az ad' [OK]

Common Mistakes:

• Assuming login error causes command not found
• Thinking no tenants causes command error
• Blaming CLI version without checking command docs

5. You want to create a new Azure AD tenant for a subsidiary company and assign a custom domain name. Which steps should you follow to do this correctly?

hard

A. Create a new tenant in Azure portal, then add and verify the custom domain in that tenant

B. Add the custom domain to your current tenant, then create a new subscription for the subsidiary

C. Create a new subscription, which automatically creates a tenant with the custom domain

D. Use Azure CLI to rename your existing tenant to the subsidiary's domain

Solution

1. Step 1: Create new Azure AD tenant and add custom domain

   Use the Azure portal to create a separate tenant for the subsidiary company. Within the new tenant, add the subsidiary's custom domain and verify ownership.

2. Final Answer:

   Create a new tenant in Azure portal, then add and verify the custom domain in that tenant -> Option A

3. Quick Check:

   New tenant + verify domain = correct process [OK]

Hint: New tenant first, then add custom domain inside it [OK]

Common Mistakes:

• Adding domain to wrong tenant
• Assuming subscription creation creates tenant with domain
• Trying to rename existing tenant domain