Identity directory

As explained in Azure Security

An identity directory is a store of identity-related information for users, groups, applications, and other entities.

An identity directory stores identity-related information for users, groups, applications, and other entities. In Azure, the tenant’s dedicated directory supports identity and access management (IAM) for tenant resources, helping authorized identities reach the right resources at the right time. section 2.1.1

The Azure directory and subscription relationship provides these operational benefits:

• One Azure tenant can contain multiple Azure subscriptions. section 2.1.1
• Each Azure subscription associates with one Azure AD directory. section 2.1.1
• Identities stored in the tenant directory can be used across its Azure subscriptions. section 2.1.1
• The same directory stores application identities, called service principals, for applications accessing Azure resources. section 2.1.3

Creating a directory user

In a lab environment, create Bob Miller with Azure CLI by supplying a display name, password, unique user principal name, and a requirement to change the password at next sign-in. The username must use a verified tenant domain. Creating users in a corporate environment is not recommended for this exercise. section 2.1.3

Figure 2.2 The relationship between Azure AD and Azure subscriptions

Use the relationship figure to visualize how one tenant directory connects with multiple Azure subscriptions. section 2.1.1

How Azure Security covers it

How deep it goes

Defines tenancy and subscription relationships, then demonstrates directory-backed users and applications without covering directory internals.

Examples

Uses Bob Miller and Charlie, Azure CLI user creation, and representative user output.

What it assumes

Assumes an Azure subscription and tenant while teaching directory-backed users and applications from the identity-store level.

What you can do after

Operate Azure AD identities with unique usernames, passwords, display names, and application service principals.

How it connects

Connects Azure tenants, Azure subscriptions, IAM, user principals, and service principals.

liveBookmanning.com

Read Azure Security on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.