Domain 1 of 5 · Chapter 1 of 3

Manage Microsoft Entra users and groups

Who can change the directory: Microsoft Entra roles

A help-desk lead holds the Owner role on every Azure subscription in the company, opens the Microsoft Entra admin center to create an account for a new hire, and is refused. Nothing is broken: by default, Azure roles and Microsoft Entra roles don't span Azure and Microsoft Entra ID[1], except when a Global Administrator elevates their access to Azure resources[1] (see Manage access to Azure resources). Microsoft Entra ID (formerly Azure Active Directory) is the identity service that stores your organization's users, groups and devices; one instance of it is a tenant, also called a directory. Azure roles control permissions to manage Azure resources, while Microsoft Entra roles control permissions to manage Microsoft Entra resources[1] such as users, groups, passwords, licenses and domains. Azure roles are assigned through Azure RBAC (role-based access control); Microsoft Entra roles were formerly called Azure AD roles.

This topic covers the directory side: creating and maintaining users and groups, assigning product licenses, onboarding external users and configuring self-service password reset. Assigning Azure roles to users and groups at a scope is covered in Manage access to Azure resources, and subscriptions, Azure Policy, locks, tags and management groups in Manage Azure subscriptions and governance.

Least-privileged Microsoft Entra role per directory task

Microsoft names a least-privileged role for each routine directory task, and recommends limiting Global Administrator, a highly privileged role, to emergency scenarios or cases where no existing role fits[2].

Task Least-privileged role named by Microsoft
Create a user User Administrator[3]
Invite an external guest Guest Inviter[3]
Assign Microsoft Entra roles Privileged Role Administrator[3]
Create groups and manage membership Groups Administrator or User Administrator[4]
Assign product licenses to a group Groups Administrator, License Administrator or User Administrator[5]
Add and verify a custom domain name Domain Name Administrator[6]
Configure self-service password reset Authentication Policy Administrator[7]
Turn on password writeback for self-service password reset Hybrid Identity Administrator[8]
Reset an external user's redemption status Helpdesk Administrator[9]

In the table, password writeback writes cloud password changes back to an on-premises directory[10] (see Password writeback for hybrid users), and an external user's redemption status records whether they have redeemed the invitation[11] (see B2B collaboration users and the invitation lifecycle).

The takeaway: beyond default user permissions (member users can create security groups and Microsoft 365 groups[12] unless group creation settings disable it) and ownership (a user can manage properties, ownership, and membership of groups that the user owns[12]), directory tasks need Microsoft Entra roles such as the table's; see Who may create groups and Owners versus members. An Azure role such as Contributor or Owner doesn't grant directory permissions by default.

Source of authority: where each object is edited

Every user and group has a source of authority: the system in which its properties must be changed. Some objects that appear in Microsoft Entra ID can't be managed in the Microsoft Entra admin center at all, so finding the source of authority is the first step of any edit.

Synchronized users

Many organizations synchronize accounts from on-premises Active Directory Domain Services (AD DS, the Windows Server directory) into Microsoft Entra ID with Microsoft Entra Connect. For users whose source of authority is Windows Server Active Directory, you must use Windows Server Active Directory to update their identity, contact info or job info, and then wait for the next synchronization cycle before the changes take effect[13]. The same guidance allows cloud edits of Microsoft Entra ID attributes such as Usage location, and says that a few synchronized attributes (User Principal Name, On Premises Immutable ID and Account Enabled) can be changed in the cloud but shouldn't be, except in an emergency. To tell the two kinds of users apart, look at the Directory synced property: it is Yes for an account homed in on-premises Active Directory and synchronized, No for a cloud-only account, and Microsoft Graph exposes it as onPremisesSyncEnabled[11].

Synchronized and mail-enabled groups

Groups synced from on-premises Active Directory can only be managed on-premises, and distribution lists and mail-enabled security groups can only be managed in the Exchange admin center or the Microsoft 365 admin center[14]. You also can't add groups to a group synced with on-premises Active Directory[4]. A distribution list (distribution group) emails a group of people, while a mail-enabled security group also grants access to resources such as SharePoint[15].

Objects created in the cloud

Users and groups created in Microsoft Entra ID are edited in the Microsoft Entra admin center, as the figure below shows alongside the synchronized and mail-enabled cases, by an administrator holding a suitable role from the table in the previous section, for example User Administrator for user profiles[13] or Groups Administrator for group settings[4].

When a scenario describes a change to an attribute whose source of authority remains on-premises, the fix is the on-premises edit plus a synchronization cycle, not a repeated cloud edit.

Where is the object managed?Synchronizedfrom on-premisesAD DSEdit in AD DS,wait for syncDistribution listor mail-enabledsecurity groupExchange admincenter orMicrosoft 365admin centerCreated inthe cloudMicrosoft Entraadmin center
Source of authority for Microsoft Entra users and groups: where to edit each kind of object (Microsoft Learn groups and user-profile guidance)

Creating a cloud user

Creating a single cloud user uses a tabbed New user page, but two choices on it decide what the user can do on day one: the sign-in name and whether the account is enabled.

The Basics tab

As at least a User Administrator, browse to Entra ID > Users and select New user > Create new user[3], then complete these fields:

The Properties tab holds identity (including User type, Member or Guest), job information, contact information, parental controls and settings[3], all of which can be added after creation. The Assignments tab can add the user to up to 20 groups or roles and to one administrative unit[3] (see Administrative units scope delegated administration below). A UPN also has length rules: up to 64 characters before the @ symbol, up to 48 after it, and 113 in total[16].

The takeaway: the required fields give a user a sign-in identity, and Account enabled controls whether that identity can sign in yet.

Adding a custom domain for sign-in names

A new tenant has only its initial domain, such as contoso.onmicrosoft.com, and you can't change or delete the initial domain name, but you can add your organization's DNS name as a custom domain name and set it as primary[6]. The custom domain is what lets users sign in as alain@contoso.com. The process, shown in the figure below, proves that you own the domain:

  1. Sign in as at least a Domain Name Administrator and select Domain names > Add custom domain[6].
  2. Copy the DNS information Microsoft Entra ID displays and create the TXT or MX record for your domain at your domain registrar[6].
  3. Select Verify. DNS records must propagate first, which can take an hour or more[6], so wait and retry if verification fails.
  4. Select the domain in the UPN menu when you create or edit users.

Hosting the domain's zone somewhere, including in Azure DNS, doesn't verify anything by itself: verification succeeds only when the specific TXT or MX record exists and you select Verify. A domain name can only be verified in one directory[6]; if another tenant already verified it, you must delete it from that directory before the new tenant can verify it.

The takeaway: a verified custom domain is a prerequisite for organizational sign-in names, and verification depends on the DNS record, not on where the zone is hosted.

1. Add the custom domain name2. Publish the TXT or MX record3. Select Verify4. Use the domain in UPNs
Custom domain verification in Microsoft Entra ID: add the name, publish the DNS record, verify, then use it in sign-in names

Managing Microsoft Entra groups

Groups let you grant access, roles and licenses to many users at once instead of one at a time, and you can manage two types of groups in the Microsoft Entra admin center[14]. Choosing the type is the first decision, because it can't be undone.

Security group Microsoft 365 group
Purpose Manage access to shared resources Provide collaboration opportunities, with a group email address
Members Users, devices, service principals, and other groups (nesting) Users only, including people outside your organization
Owners Users and service principals Users and service principals

The rows summarize Microsoft's group types overview[14]. A service principal is the security principal that represents an application[17]. A Microsoft 365 group is not an Exchange distribution list: distribution lists and mail-enabled security groups are managed in Exchange, as Source of authority above explains.

Creating a group

As at least a Groups Administrator or User Administrator, select Groups > All groups > New group[4], pick the Group type, enter a name and an optional description, choose a Membership type, and optionally add owners and members. Selecting the Microsoft 365 group type enables the Group email address option[4]. The Membership type is explained in the next section, and switching Microsoft Entra roles can be assigned to the group to Yes lets you use the group to assign Microsoft Entra roles to members[4], as Role-assignable groups below explains.

Owners versus members

A group has two separate lists. Owners manage the group: an owner can manage properties of the group, such as the name, and manage group membership, but can add or remove members only if the group's membership type is Assigned[12]. Group ownership is neither the Azure Owner role nor a Microsoft Entra role: ownership of individual objects is a source of access separate from role assignments[12]. Members receive what the group is used for, such as access assignments, role assignments and licenses. Being an owner doesn't make someone a member; Microsoft Graph documentation notes that an owner who must also make changes in the group's team needs to be added as a member too[18]. Add a person to both lists when they must run the group and also receive its benefits. Microsoft recommends at least two owners per group[14] so that management doesn't depend on one person.

What you can change later

Under Properties you can edit the group name, description and membership type, but you can't change the group type; to change it you must delete the group and create a new one[4]. That membership-type edit has an exception: if the group has Microsoft Entra roles can be assigned to the group enabled, you can't change its membership type[4]. The Object ID can't be changed either, but you can copy it for use in PowerShell commands[4]. Because the object ID stays fixed while the display name can be edited, scripts should identify a group by its object ID.

Nesting groups

A security group can be added as a member of another security group, but nested groups don't gain access to shared resources and applications that are assigned to the parent group[4]: when you assign a group to an application, for example, the assignment doesn't cascade to nested groups[19]. Azure role assignments work differently: role assignments are transitive for groups[20], so a user in a nested group gets the permissions of a role assigned to the parent group (see How a role assignment grants access in Manage access to Azure resources). Microsoft lists several nesting cases as unsupported, including adding security groups to Microsoft 365 groups, adding Microsoft 365 groups to any other group, applying licenses to nested security groups, and adding groups as members of a role-assignable group.

Who may create groups

By default, member users can create security groups and Microsoft 365 groups[12]. The default-permission settings change that: setting Create security groups to No stops users from creating security groups, while anyone with at least User Administrator still can; setting Create Microsoft 365 groups to No blocks users, and Some allows only a selected set of users[12]. Don't use Restrict access to Microsoft Entra administration portal for this purpose: it is not a security measure and doesn't block programmatic access through PowerShell or the Microsoft Graph API[12].

The takeaway: choose the group type by purpose because it is permanent, maintain owners and members as separate lists, and control who creates groups with the group creation settings rather than a portal restriction.

Membership types: Assigned, Dynamic User, Dynamic Device

Every group has one of three membership types, and the type decides who keeps the member list current:

Microsoft defines these three membership types for groups[14], and the table Group membership types: Assigned vs Dynamic User vs Dynamic Device near the end of this topic compares them side by side.

How dynamic membership is evaluated

When the attributes of a user or a device change, the system evaluates all rules for dynamic membership groups in the directory; objects that satisfy a rule are added and objects that no longer satisfy it are removed. You can't manually add or remove a member of a dynamic membership group[22]. An administrator who needs one extra person in such a group must change either the rule or that person's attributes.

A rule can target users or devices, but can't contain both[22], so one dynamic group never mixes the two, and the object type brings further limits:

Licensing and attribute security

Dynamic membership groups require a Microsoft Entra ID P1 license (or an Intune for Education license) for each unique user who is a member of one or more dynamic groups. The licenses don't have to be assigned to those users, but the organization must own enough to cover them, and devices in device-based groups need no license[22].

A dynamic group is only as trustworthy as the attributes in its rule. Microsoft advises auditing who can write each attribute a rule uses, in Microsoft Entra ID and in on-premises Active Directory, and restricting self-service write access to attributes used in security-sensitive groups[22]. If users can edit their own department, a rule on department lets them pick their own group, and with it whatever access the group grants.

The takeaway: Assigned lists are maintained by people, dynamic lists only by their rule, and a dynamic rule targets either users or devices.

Writing dynamic membership rules

A dynamic membership rule is a true-or-false expression that Microsoft Entra ID evaluates for each user or each device. The simplest rule is a single expression of the form <Property> <Operator> <Value>, where the property is written as <object>.<property>[22].

Listing: a single-expression rule for a Dynamic User group

user.department -eq "Sales"

In this listing user is the object type, department is the attribute, -eq is the equals operator and "Sales" is the value. The body of a rule can't exceed 3,072 characters[22]. The portal's rule builder supports up to five expressions and only user-based rules; device rules, rules with -contains and rules that set operator precedence need the text box[22].

Comparison operators

Operator What it does
-eq, -ne Equals, not equals
-startsWith, -notStartsWith The value begins, or doesn't begin, with the text
-endsWith, -notEndsWith The value ends, or doesn't end, with the text
-contains, -notContains Partial string match anywhere in the value
-match, -notMatch Regular expression match
-in, -notIn The value equals, or doesn't equal, any item in a bracketed list

The operator list comes from Microsoft's supported expression operators table[22], and regex and string operations aren't case sensitive[22]. Choose the narrowest operator for an allowlist: user.department -in ["Sales","Marketing"] admits exactly those two departments, whereas user.department -contains "Sales" also admits any department whose name merely includes Sales, such as Presales.

Testing for a missing value

Use -eq or -ne to compare against null, and put quotation marks around null only if you want it read as a literal string[22]. So user.mail -ne null finds users who have a mail value, while user.mail -ne "null" compares against the four-letter text null. Don't use the -not operator with null; it causes an error[22].

Collections: -any and -all

Some attributes hold several values, such as proxyAddresses, otherMails and assignedPlans. On these multi-value properties, -any is satisfied when at least one item matches and -all when every item matches[22], and the underscore _ stands for each value in a string collection[22].

Listing: collection rules from the Microsoft Learn dynamic membership reference

(user.proxyAddresses -any (_ -startsWith "contoso"))
user.assignedPlans -any (assignedPlan.servicePlanId -eq "efb87545-963c-4e0d-99df-69c6916d9eb0" -and assignedPlan.capabilityStatus -eq "Enabled")

The first rule in the listing matches users with at least one proxy address that starts with contoso. The second matches users who have the Exchange Online (Plan 2) service plan in an Enabled state[22]; servicePlanId and capabilityStatus are properties of each item in assignedPlans, which is why both conditions sit inside the same -any. The -contains operator does partial string matches but not matches for items in a collection[22], so it can't replace -any.

Operator precedence

From highest to lowest, the precedence is: the comparison operators, then -not, then -and, then -or, then -any and -all[22]. Put parentheses around alternatives whenever one restriction must apply to all of them.

Listing: grouping two departments under one country restriction

user.country -eq "US" -and (user.department -eq "Marketing" -or user.department -eq "Sales")

This is Microsoft's own precedence example[22]: both departments must be in the US. Without the parentheses, -and binds first, so the rule reads as (US and Marketing) or Sales, and a Sales user in any country qualifies.

The takeaway: use exact operators (-eq, -in) for allowlists, unquoted null for missing values, -any or -all for collections, and parentheses around every -or that must sit under a shared restriction.

Role-assignable groups

A role-assignable group is a security or Microsoft 365 group that can hold Microsoft Entra roles, so that joining the group gives a person the role. For example, a Contoso_Helpdesk_Administrators group can be assigned the Helpdesk Administrator role, and people who join the group are assigned the role indirectly[21].

To create one, switch Microsoft Entra roles can be assigned to the group to Yes while creating the group[4]; in Microsoft Graph the same setting is the isAssignableToRole property. The rules are strict because group membership becomes role membership:

By default, Privileged Role Administrators manage the membership of a role-assignable group, and you can delegate that by adding group owners[21]. A deleted role-assignable group is soft-deleted and can be restored within 30 days[21]. For restore steps, Microsoft links to the general group restore article[21], which marks cloud security group soft delete and restore as preview[23] (see Deleting and restoring a group below).

Assigning Azure roles to a group is a separate system from Microsoft Entra roles, covered in Manage access to Azure resources.

The takeaway: make a group role-assignable at creation, keep its membership Assigned with no nested groups, and let Privileged Role Administrators or delegated owners manage members.

Bulk operations with CSV templates

Suppose an onboarding wave brings hundreds of new employees, a project needs many existing users added to its group, and partner contacts need invitations. Microsoft Entra ID supports bulk user create and delete operations[24], and bulk user creation and bulk import of group members share one workflow, as the figure below shows:

  1. Download the CSV (comma-separated values) template from the operation's page.
  2. Preserve the column headings exactly as downloaded[24] and enter one object per row.
  3. Upload the file; validation starts, and if there are errors you must fix them before you can submit the job[24].
  4. Submit the job.
  5. Review the job on the Bulk operation results page, where the Status column shows In Progress, Succeeded or Failed, and the # Success, # Failure and Total Requests values list each line item with the reason for any failure[25]. You can also download a results CSV that shows the status of each row[25].

The operations differ in what a row means and what the job does:

Operation Where Required template columns Result
Bulk create users Users > Bulk create Name [displayName] Required, User name [userPrincipalName] Required, Initial password [passwordProfile] Required New internal member accounts
Bulk import group members The group's Members page > Bulk operations > Import members Member object ID or user principal name [memberObjectIdOrUpn] Required Existing users added to that one group

For bulk create, only Name, User name and Initial password are required[24], and the operation creates internal member accounts with the passwords specified in the CSV file and sends no invitation emails[24]. For member import, open the group, select Members, then Bulk operations > Import members, and enter either a user principal name or an object ID on each row[25]; group owners can also bulk import members into groups they own[25].

Two details differ between the templates. The user-creation template lets you keep its examples row[24], but for member import you must remove the examples row and replace it with your own entries[25]. And initial passwords must comply with the active password policy[24], described in Cloud password rules and expiration below.

The third case, partner contacts, is not a bulk create. External users are people from outside your organization who keep their own sign-in, covered in B2B collaboration users below, and to bulk invite external guest users and send invitation emails, Microsoft points to a separate Bulk invite B2B users procedure[24]. Uploading partner addresses to Bulk create would create internal, password-backed accounts instead of invitations.

The takeaway: choose the operation by what each row represents. A new internal account is Bulk create, an existing account joining a group is Import members, and an external person who keeps their own identity is a bulk invitation.

1. Download the CSV template2. Add one row per object3. Upload; fix validation errors4. Submit the bulk job5. Review Bulk operation results
The shared workflow for Bulk create users and Bulk import group members in the Microsoft Entra admin center

Disabling, deleting, and restoring users and groups

Removing a person's ability to sign in and removing the object itself are different operations, and the difference decides what you can undo.

Disabling a user

The Settings category of a user's profile is where you decide whether the user can sign in[13]. Clearing Account enabled prevents the user from signing in, and the setting can be changed back after the user is created[3]. The object stays in the directory, so disabling suits a leave of absence or an investigation, and re-enabling the same account reverses the sign-in block; a dynamic group whose membership rule tests the accountEnabled property[22] adds or removes the user when Account enabled changes (see How dynamic membership is evaluated).

Deleting and restoring a user

User Administrators can delete non-admin users, Helpdesk Administrators and other User Administrators; Privileged Authentication Administrators can delete any user, including other administrators[3]. A deleted user no longer appears on the All users page, stays on the Deleted users page for the next 30 days, and can be restored during that time[3]; any licenses the user consumed are made available to other users[3]. To recover an accidentally deleted account, restore it within those 30 days. Creating a new account with the same user principal name produces a different directory object, not the original one.

Deleting and restoring a group

A deleted Microsoft 365 group or cloud security group is retained, but not visible, for 30 days from the deletion date so that the group and its contents can be restored. Distribution groups aren't covered, and the 30-day period isn't customizable[23]. Soft delete and restore for cloud security groups is in preview and available only in public clouds[23], so Microsoft 365 group restore is the established case.

To restore, open Groups > All groups > Deleted groups and select Restore group, or select Delete permanently to purge the group[23]. Only a group that wasn't permanently purged can come back, and if the group contains documents, SharePoint sites or other persistent objects, fully restoring the group and its contents can take up to 24 hours[23]. Global Administrators, Groups Administrators, Partner Tier 2 Support and Intune Administrators can restore any of these groups; User Administrators and Partner Tier 1 Support can restore any except groups assigned to the Global Administrator role; a user can restore groups they own[23].

The figure below traces these states. The takeaway: disable to block sign-in reversibly, restore within 30 days to get the original user or Microsoft 365 group back (for cloud security groups, restore is in preview), and remember that a re-created object with the same name is a new object without the old one's contents.

Active user orMicrosoft 365 groupDisable orre-enableDelete orrestoreDisabled usersign-in blockedSoft-deletedkept 30 daysAfter 30 daysor purgePermanentlydeleted
Lifecycle of a Microsoft Entra user or Microsoft 365 group: disabling a user, soft delete with a 30-day restore window, then permanent deletion

Administrative units scope delegated administration

A regional help desk should reset passwords for its own region's users only. An administrative unit is the Microsoft Entra container for that: it can contain only users, groups or devices, and it restricts the permissions in a role to any portion of the organization you define[26]. You assign a role such as Helpdesk Administrator with the administrative unit as its scope; if you assign a role to a user without administrative unit scope, the scope of the role is the entire tenant[26].

An Azure management group is a different thing with a similar purpose: management groups provide a governance scope above subscriptions[27], so they organize Azure subscriptions rather than directory users, as covered in Manage Azure subscriptions and governance.

A group in the unit doesn't bring its members

Adding a group to an administrative unit brings the group itself into the management scope of the unit, but not the members of the group[26]. A User Administrator scoped to the unit can manage the group's name and membership, but can't manage the user properties or authentication methods of the group's members, or reset their passwords, unless those users are added directly as members of the administrative unit[26]. The figure below shows the difference.

Scope, not isolation

Administrative units apply scope only to management permissions. They don't prevent members or administrators from using their default user permissions to browse other users, groups or resources outside the administrative unit[26]. The Microsoft 365 admin center filters out users outside a scoped administrator's units, but you can browse other users in the Microsoft Entra admin center, PowerShell and other Microsoft services[26]. An administrative unit therefore can't hide one region's users from another region's administrators.

Other rules

The takeaway: to let a scoped administrator manage users, put the users themselves in the unit, and treat the unit as a management boundary, not a visibility boundary.

Administrative unitGroup: West Salesmanage name, membersUser added directlyedit, reset passwordMember ofgroup only,not in unit:no reset
Administrative unit scope: a group in the unit brings the group, not its members; only users added directly are manageable by the scoped administrator

Assigning product licenses and service plans

Microsoft 365 and Microsoft Entra ID features are bought as products, such as Office 365 E3, each purchased as a number of licenses. A product bundles service plans, such as Exchange Online (Plan 2), and service plans aren't the same as licenses or products[22]. Assigning a product license to a user entitles that user to the product's enabled service plans.

Where and with which role

Licenses are assigned in the Microsoft 365 admin center, either per user on the Active users page or per product on the Licenses page, where you can add up to 20 users and groups at a time and select Turn apps and services on or off to choose service plans[28]. You must be at least a License Administrator or User Administrator to assign licenses to users[28], and at least a Groups Administrator, License Administrator or User Administrator to assign licenses to groups[5]. For automation, the Microsoft Graph PowerShell SDK can assign or unassign licenses to groups with Set-MgGroupLicense[5]. An Azure role such as Contributor plays no part, because license assignment is a directory and Microsoft 365 operation rather than an Azure resource operation.

Usage location comes first

Some Microsoft services aren't available in all locations, so before a license can be assigned to a user, the administrator must specify the user's location setting[5]. That setting is the user's Usage location, a two-letter country or region code[22], not their office or postal address. For group-based licensing, users without a specific location inherit the location of the tenant[5], which can be wrong in a multinational organization, so Microsoft recommends setting it during user creation.

Unassigning is not cancelling

Unassigning a license makes the seat reusable, but the subscription keeps the same number of purchased licenses: if you unassigned licenses and don't plan to reassign them, consider removing them from your subscription so you aren't paying for more licenses than you need[28].

Removing a user's license is also not the same as deleting the user. When a license is removed, Exchange Online data associated with the account is normally held for 30 days and then deleted, subject to retention policies and labels; the mailbox is no longer searchable with eDiscovery tools[28]. Unlicensed OneDrive accounts can be archived and become subject to deletion for nonpayment even if the Entra user has not been deleted[29]. Conversely, deleting a user account makes its license immediately available to assign to someone else[28].

The takeaway: set Usage location, assign products and service plans in the Microsoft 365 admin center or with Microsoft Graph PowerShell, and reduce the purchased quantity separately when the goal is a lower bill.

How group-based licensing is processed

Group-based licensing means assigning a product to a group instead of to each user: if you have security groups, mail-enabled groups or Microsoft 365 groups, you can assign or unassign licenses for those groups on the Licenses page in the Microsoft 365 admin center[5]. Membership then drives licensing, which pairs well with dynamic membership groups that automatically manage licensing for users who meet specific criteria[14].

Who receives a license

The group is an assignment mechanism, not a shared seat: each user member needs an available license of its own. Three consequences follow:

Processing happens in the background

Group-based licensing can produce errors in the background; unlike direct user assignment, where errors appear immediately, it records the failure on the user object and surfaces it later in the admin portal[5]. A license shown on the group therefore doesn't prove that every member is licensed. For a large group, such as 100,000 users, processing license changes can take a long time[5].

Moving a user between licensed groups

Order matters, as the figure below shows. Add the user to the destination group first, confirm the new license is applied on the user's Licenses page, and then remove the user from the original group. If you remove the user from the source group first, the user is unlicensed until group-based licensing finishes processing the new group's assignment[5].

Finding and fixing errors

In the Microsoft 365 admin center, go to Billing > Licenses, select the product, and select the Errors & issues tab to see the users who have license assignment problems[5]. Microsoft's problems-and-solutions table lists ten common cases:

Issue Cause Fix
Not enough licenses Too few available licenses for a product assigned to the group Buy more, remove unused direct assignments, or free licenses from other groups or users
Conflicting service plans A plan conflicts with one the user already has through another product, such as Office 365 E1 assigned directly and E3 through a group Disable one conflicting plan, remove the redundant direct license, or adjust the group assignment
Other products depend on this license Another assigned product, such as Audio Conferencing on Skype for Business, depends on the plan being removed Remove or reassign the dependent service before removing the prerequisite
Usage location isn't allowed Usage location is missing or set to an unsupported country or region Set the correct Usage location, or remove users in unsupported locations from the group
Duplicate proxy addresses Two users share a proxy address, so Exchange Online licensing fails Correct the duplicate proxy address, then reprocess
Mail and ProxyAddresses attribute changes Updating license assignment can recalculate the user's mail and proxyAddresses Correct the underlying source of the attribute change
LicenseAssignmentAttributeConcurrencyException in audit logs Several groups tried to assign the same license to a user concurrently No action; processing is retried and resolves automatically
More than one product license assigned to a group One product's failure can stop the group's other products from being assigned Find the product that caused the failure
Licensed group is deleted Licenses must be removed first; a dependent direct license can turn an inherited license into a direct one Check affected users for direct assignments
Products with prerequisites or add-ons An add-on assigned without its prerequisite plan fails Assign the prerequisite and the add-on in the same group

All ten rows summarize Microsoft's group-based licensing problems and solutions[5]. Two of them deserve emphasis. A dependency can keep a user licensed after a cleanup, because the inherited license might be converted into a direct assignment so the dependent service keeps working[5]. And a conflict can come from an older direct assignment rather than the newest group, so review the user's full set of products.

After fixing the cause, select the affected group or user on the Errors & issues tab and choose Reprocess[5]; Reprocess handles up to 20 users at a time[5].

The takeaway: buying seats fixes only capacity errors. Conflicts need a service plan change, dependencies need the right removal order, address errors need a directory fix, and the concurrency exception needs nothing.

1. Add user to destination group2. Confirm the license is applied3. Remove user from source groupRemoving first leaves the userunlicensed until processing ends
Moving a user between licensed groups without a gap in licensing (Microsoft 365 admin center group-based licensing guidance)

B2B collaboration users and the invitation lifecycle

Partner engineers need your internal app, and they already have accounts at their own company. Microsoft Entra B2B (business-to-business) collaboration covers this case: an external user is invited to sign in to your workforce tenant with their own credentials, and a user object is created for the B2B collaboration user in the same directory as your employees[11]. That object can be added to groups and assigned to applications like an employee's.

Two independent properties: UserType and Identities

Microsoft classifies users by how they authenticate (internally or externally) and by their relationship to your organization (guest or member), which gives four kinds: external guest, external member, internal guest and internal member[11]. Everyday usage, including this topic and setting names such as Guest invite settings, calls any invited external user a guest, because typically a Microsoft Entra B2B user and guest user are synonymous, and a B2B collaboration user is added with UserType set to Guest by default[11]; an external member is the exception to that default. Two properties record these axes:

Identities and UserType are independent properties[11]. Changing an external user's UserType to Member changes their relationship and default permissions, not where their password lives: external members authenticate to their home Microsoft Entra tenant, and if they forget their password, the administrator in their home tenant resets it[3].

The invitation lifecycle

The figure below traces the lifecycle.

  1. Invite. Select Users > New user > Invite external user and enter the email address, display name and an optional invitation message[3]. When the invitation is initially sent, an account is created in your tenant without credentials[11], so the object is already in Users before the guest responds.
  2. Pending acceptance. Until redemption, the profile shows an Invitation state of Pending acceptance[11]; select Resend invitation in the B2B collaboration tile to send another email[3] instead of creating a second identity.
  3. Redeemed. After the guest accepts, the Identities property is updated based on the guest's identity provider[11]. The guest's UPN has a fixed shape: the guest's email, then #EXT#, then your tenantname.onmicrosoft.com, as in john_contoso.com#EXT#@fabrikam.onmicrosoft.com[11].
  4. Reset redemption. When a guest wants a different email and identity provider, their home account was deleted and re-created, or they moved company but need the same access, reset the redemption status and reinvite them, which keeps the object ID, group memberships and app assignments; when they redeem, the UPN doesn't change but the sign-in name changes to the new email[9]. For a new address, first make sure it is in the user's mail or otherMails property[9]. Helpdesk Administrator is the least-privileged role for the reset[9]. The older method, deleting the guest and inviting again, creates a new object that lacks those memberships and assignments.

Email one-time passcode

Email one-time passcode authenticates B2B guests who can't be authenticated through Microsoft Entra ID, a Microsoft account or a social identity provider: the guest requests a temporary passcode sent to their email address[30]. It is on by default for new tenants and for existing tenants that haven't explicitly turned it off; if you disable it, users are prompted to create a Microsoft account instead[30]. A passcode is valid for 30 minutes, and a session expires after 24 hours, after which the guest receives a new passcode[30]. Partners without a Microsoft account therefore don't need internal passwords created for them.

The takeaway: an invitation creates the object at once, UserType never decides where credentials live, and reset redemption changes a guest's sign-in identity without losing their access.

Invite external useruser object createdInvitation sentInvitation state:Pending acceptanceGuest redeemsRedeemed: Identitiesshows guest's providerSign-in changesReset redemption statussame object, new inviteRe-invite
Lifecycle of a B2B collaboration invitation: invitation, Pending acceptance, redemption, and reset redemption status

Controlling external access: two setting families

Two separate groups of settings decide what external users can do, and many questions hinge on picking the right one. Cross-tenant access settings manage B2B collaboration and B2B direct connect with other Microsoft Entra organizations, while external collaboration settings include options for restricting guest user access, specifying who can invite guests, and allowing or blocking domains[31]. B2B collaboration is the guest-object model described in the previous section; B2B direct connect is the other model, a mutual trust relationship with another Microsoft Entra organization[31] that, for example, provides access to Microsoft Teams shared channels, which B2B guest users can't use[11].

External collaboration settings

These settings are under Entra ID > External Identities > External collaboration settings, and the admin center needs a role that can update them, such as Global Administrator or External Identity Provider Administrator[2]. Three of their controls matter here (among others).

Guest user access decides how much of the directory guests can read:

This control governs reading the directory only. It doesn't remove access that a guest holds through an application assignment or an Azure role assignment, and guest users can still be added to administrator roles regardless of this setting[12].

Guest invite settings decide who can send invitations. By default, all users in your organization, including B2B collaboration guest users, can invite external users[2]. The four options are anyone in the organization, including guests and non-admins; member users and users assigned to specific admin roles; only users assigned the User Administrator or Guest Inviter role[2]; and no one in the organization, including admins[2]. The Guest Inviter role lets an individual invite guests without a higher-privilege administrator role, even when only specific admin roles can invite[2].

Collaboration restrictions allow or block invitations by domain:

Cross-tenant access settings

A partner user opening your app is inbound traffic from your side and outbound traffic from the partner's side, so your inbound settings and the partner's outbound settings both apply, as the figure below shows. Changing your own outbound settings does nothing for partners coming in. Outbound access settings control whether your users can access resources in an external organization, and inbound access settings control whether users from external Microsoft Entra organizations can access resources in your organization; both can apply to everyone or to specific users, groups and applications[31].

Inbound trust settings decide whether your Conditional Access policies trust multifactor authentication (MFA), compliant device and Microsoft Entra hybrid joined device claims from an external organization. When you trust MFA, your MFA policies still apply, but users who already completed MFA in their home tenant don't repeat it[31]. Conditional Access policies are if-then statements: if a user wants to access a resource, then they must complete an action such as MFA[33]; designing them is outside this topic.

The initial default settings are: B2B collaboration enabled for all your internal users, with MFA and device claims from other Microsoft Entra organizations not trusted; B2B direct connect blocked inbound and outbound; and no organizations added[31]. Organizational settings, added for a specific partner, take precedence over the defaults[31]. Configuring cross-tenant access settings needs at least Security Administrator, and trust settings or targeting specific users, groups or applications need a Microsoft Entra ID P1 license[31].

The takeaway: who may invite, which domains may be invited and what guests can read are external collaboration settings; which direction of access is allowed with another Microsoft Entra organization, and whether its MFA is trusted, are cross-tenant access settings.

Partner's Microsoft Entra tenantPartner userto your app:partner outbound+ your inboundYour userto partner app:your outbound+ partner inboundYour Microsoft Entra tenantinbound trust: MFA, device claims
Cross-tenant access settings: which tenant's inbound and outbound settings apply to each direction of B2B collaboration

Cloud password rules and expiration

A password reset succeeds only if the new password passes the password policy, so the policy is worth knowing before configuring self-service reset. When self-service password reset (SSPR) is used to change or reset a password in Microsoft Entra ID, the password policy is checked, and if the password doesn't meet the requirements the user is prompted to try again[16].

The policy below applies to user accounts that are created and managed directly in Microsoft Entra ID[16]:

Setting Value
Length Minimum 8 and maximum 256 characters[16]
Complexity Three of four types: lowercase, uppercase, numbers (0-9) and symbols[16]
Not allowed Unicode characters[16]
Maximum password age No expiration by default; a tenant created before 2021 has a 90-day expiration by default[16]
Change history The last password can't be used again when the user changes a password[16]
Reset history The last password can be used again when the user resets a forgotten password[16]
Lockout By default, locked out for one minute after 10 counted unsuccessful attempts, with longer lockouts after further failures; the threshold and duration are configurable, and repeated use of the same bad password does not increment the counter[16]

Because the expiration default depends on the tenant's age, check it rather than assume: Get-MgDomain shows the current policy, and the Update-MgDomain cmdlet from the Microsoft Graph PowerShell module changes it[16]. For an individual account, the never-expire value can be set with Update-MgUser[16], and Microsoft's check looks for DisablePasswordExpiration in the user's PasswordPolicies. By default, only accounts that aren't synchronized through Microsoft Entra Connect can be configured not to expire[16]. Apart from custom banned passwords and lockout parameters, password expiration is the only part of the policy that can be changed[16].

The takeaway: verification methods prove who the user is, and the password policy decides whether the new password is acceptable. Changing the number of methods required to reset (see How SSPR decides whether a user can reset below) never relaxes length or complexity.

Turning on SSPR for a group of users

Self-service password reset (SSPR) gives users the ability to change or reset their password, with no administrator or help desk involvement[7], and to unblock a locked account. Turning it on means deciding who is in scope, making sure they are licensed, and getting them registered.

Licensing by scenario

Microsoft lists which products include each SSPR scenario[34]:

Scenario Microsoft Entra ID Free Microsoft 365 Business Standard Microsoft 365 Business Premium Microsoft Entra ID P1 or P2
Cloud-only user changes a known password Yes Yes Yes Yes
Cloud-only user resets a forgotten password No Yes Yes Yes
Synchronized user changes or resets with on-premises writeback No No Yes Yes

Although some unlicensed users may technically be able to access SSPR, a license is required for any user you intend to benefit from the service[34]. Microsoft Entra ID P2 adds nothing to SSPR that P1 lacks in this table, so P1 is enough when it covers the scenario.

Targeting

As at least an Authentication Policy Administrator, browse to Entra ID > Password reset and, on Properties, set Self service password reset enabled to None, Selected or All[7]. Selected supports a staged rollout, but you can currently enable only one Microsoft Entra group for SSPR in the admin center, and nested groups are supported[7], so build one group whose nested groups hold everyone in the pilot. SSPR targeting thus reaches members of nested groups, unlike group-based licensing, where only users in the first-level group are assigned licenses[5] (Who receives a license above). Test with a non-administrator account[7], because administrators follow a different reset policy (see the next section).

Registration and reconfirmation

Users must register verification methods before they can reset. When Require users to register when signing in is enabled, users who sign in through modern authentication or a web browser to Microsoft 365, the Microsoft Entra admin center, Access Panel, federated applications or custom applications are prompted to register; when it isn't, they can register manually[35]. Reconfirmation is available only when registration is required, and accepts 0 to 730 days; 0 means users are never asked to reconfirm their authentication information[35], not that SSPR is off. Users must sign in before they can reconfirm[35].

Notifications and the helpdesk link

The takeaway: license every intended user for their scenario, target one group (which may contain nested groups), require registration, and route support requests through the helpdesk link.

How SSPR decides whether a user can reset

When a user starts a reset, Microsoft Entra ID runs a series of checks before guiding the user through the reset[35], traced in the figure below:

  1. Is the user enabled for SSPR? If not, the user is asked to contact their administrator[35].
  2. Has the user defined data for enough of the methods the administrator policy enables, one or two depending on the policy? If not, the user is advised to contact their administrator[35]. If a Microsoft Entra administrator role is assigned to the user, the strong two-gate policy is enforced[35], which requires two pieces of authentication data[16] (see The administrator policy).
  3. Is the password managed on-premises, through federation, pass-through authentication or password hash synchronization? If so, the user can proceed only if SSPR writeback is configured[35], and only while the writeback service is running[10]. Password hash synchronization lets users sign in with their on-premises password, pass-through authentication validates it through an on-premises agent, and federation hands authentication to a trusted system such as Active Directory Federation Services (AD FS)[36].
  4. The user verifies, chooses a new password, and the password policy is checked[16].

Method count and method categories

The number of methods required to reset can be set to one or two[35]. A user who hasn't registered the minimum number sees an error page and must ask an administrator to reset the password[35]. Raising the requirement from one to two leaves anyone with a single registered method unable to reset or unlock[35], and changing which methods are available can leave users without the minimum amount of data unable to use SSPR[35].

For SSPR, Microsoft Authenticator, software OATH tokens and hardware OATH tokens count as a single authentication method, so a user can't combine them to satisfy a requirement for two methods[35]. Microsoft lists the methods available for SSPR as Microsoft Authenticator push notifications, hardware OATH tokens (preview), software OATH tokens, SMS, voice call and email OTP[35]. That list omits security questions, also a method limited to password reset[37], which can only be enabled by using the legacy SSPR policy[37].

Where methods are enabled

The Authentication methods policy is the recommended way to manage authentication methods[37], and beginning September 30, 2025, authentication methods can't be managed in the legacy MFA and SSPR policies[37], apart from security questions (above). Enabling a method makes it available; it doesn't put users in SSPR scope or register them, and after migration the Number of methods required to reset control and the SSPR administrator policy stay active in the legacy SSPR policy[37].

The administrator policy

Accounts with a Microsoft Entra administrator role follow a separate reset policy:

The takeaway: a user can reset only when in scope, registered for enough methods (two gates for administrators in most production tenants), and, for an on-premises password, served by working writeback.

Enabled for SSPR?YesNoEnough methodsregistered?YesNoPassword managedon-premises?YesNoWriteback deployedand running?YesNoSet new password,policy checkedContactyouradministrator
Checks Microsoft Entra ID runs before allowing a self-service password reset, after Microsoft Learn's SSPR how-it-works sequence

Password writeback for hybrid users

Password writeback allows password changes in the cloud to be written back to an on-premises directory in real time, by using either Microsoft Entra Connect or Microsoft Entra Connect cloud sync[10]. Microsoft Entra Connect's synchronization service is named Microsoft Entra Connect Sync, as opposed to the separate Microsoft Entra Connect cloud sync: you can configure SSPR to write back through Microsoft Entra Connect Sync agents and Microsoft Entra Connect provisioning agents (cloud sync)[8]. Without writeback, a synchronized user whose password is managed in on-premises AD DS can't complete SSPR, as the previous section's check 3 showed.

Turning it on with Microsoft Entra Connect

Writeback is enabled in two places:

  1. In the Microsoft Entra Connect configuration wizard, on the Optional features page, select Password writeback[8].
  2. In the Microsoft Entra admin center, as at least a Hybrid Identity Administrator, browse to Entra ID > Password reset > On-premises integration and check Write back passwords to your on-premises directory[8].

The same On-premises integration page[8] holds an optional setting: Allow users to unlock accounts without resetting their password, set to Yes, offers an unlock-only option alongside reset-and-unlock; set to No, users can only perform the combined operation[35], and by default a password reset also unlocks the account[35].

The account Microsoft Entra Connect uses to reach AD DS also needs on-premises permissions: Reset password, Change password, Write permissions on lockoutTime and pwdLastSet, and the Unexpire Password extended right on the root object of each domain in the forest[8]. The password permissions are granted for descendant user objects, and Unexpire Password must be applied to This object and all descendant objects, This object only, or All descendant objects, or the permission isn't displayed[8]. Without these permissions, writeback might appear to be configured correctly while users get errors managing their on-premises passwords from the cloud[8], and password write permissions must be inherited by descendant objects[8]. Assigning a cloud role such as Hybrid Identity Administrator gives that account no AD DS permission.

What writeback provides

Supported and unsupported reset paths

Reset path Written back to AD DS?
End user resets through the password reset portal Yes
Administrator resets a user's password in the Microsoft Entra admin center Yes
Administrator resets a user's password through the Microsoft Graph authenticationMethod resetPassword operation Yes
Administrator resets a user's password in the Microsoft 365 admin center No
End user resets their own password with PowerShell or the Microsoft Graph API No

The rows come from Microsoft's supported and unsupported writeback operations lists[10]. The pattern is about the entry point, not about cloud versus on-premises: an administrator using the Graph authenticationMethod resetPassword operation gets writeback when configured, a Graph API self-reset by an end user does not.

Limits to remember

The takeaway: on the Microsoft Entra Connect path walked through above (cloud sync, named in the opening, is the other supported tool), hybrid SSPR needs writeback enabled in the configuration wizard and in Password reset, the right AD DS permissions for the connector account, a supported reset path, and users outside protected groups and staged-rollout groups.

Group membership types: Assigned vs Dynamic User vs Dynamic Device

Decision pointAssignedDynamic UserDynamic Device
Who adds and removes membersFor ordinary groups: group owners, Groups Administrator or User Administrator; for role-assignable groups: Privileged Role Administrator by default, or delegated group ownersThe membership rule; manual changes are blockedThe membership rule; manual changes are blocked
Objects that can be membersSecurity group: users, devices, service principals, nested groups. Microsoft 365 group: users onlyUsers onlyDevices only
Group types that offer itSecurity and Microsoft 365Security and Microsoft 365Security only
Allowed for a role-assignable groupYes (required)NoNo
Microsoft Entra ID P1 licensingNeeded for a role-assignable groupOne license per unique user memberNo license needed for device members
Example ruleNone: members are listed by handuser.department -eq "Sales"device.deviceOSType -eq "Windows"

Decision tree

Group will holdMicrosoft Entraroles?YesSecurity orMicrosoft 365 groupmade role-assignableat creation,Assigned membershipNoNeeds a groupemail address andcollaboration?YesMicrosoft 365group: Assignedor Dynamic UserNoMembers listedby hand?YesAssignedsecurity groupNoRule targetsusers or devices?UsersDevicesDynamic Usersecurity groupDynamic Devicesecurity group

Sharp facts the exam loves — give these one last read before exam day.

Cheat sheet

Sharp facts the exam loves — scan these before test day.

Cloud user creation establishes a sign-in identity and an initial account state

A new internal Microsoft Entra user needs a unique user principal name, a display name, and an initial password. The UPN uses a domain available in the tenant, while the mail nickname and display name serve different purposes. Account enabled is selected by default; clear it when creating an account that must not yet sign in. User Administrator is the least-privileged built-in administrator role for creating ordinary users.

Trap Using an Azure subscription Contributor assignment to create directory users, because Azure resource permissions do not authorize directory administration.

2 questions test this
A custom sign-in domain must be verified in one tenant before use

When users need an organizational UPN suffix, add the custom domain and verify ownership using the supplied DNS TXT or MX record. A domain can be verified in only one Microsoft Entra directory at a time, so an existing verification elsewhere must be resolved first. The original tenantname.onmicrosoft.com domain remains and cannot be changed or deleted; Domain Name Administrator can manage custom domains without broader directory administration.

Trap Creating an Azure DNS zone as proof of tenant domain ownership, because adding a zone does not complete the Microsoft Entra verification challenge.

3 questions test this
Synchronized user properties must be changed at their authoritative source

A user synchronized from Windows Server Active Directory retains that directory as the source of authority for synchronized identity, contact, and job properties. Update those properties on-premises and allow synchronization to carry the changes into Microsoft Entra ID. Cloud-managed users can instead be updated directly in Microsoft Entra ID; the Directory synced or onPremisesSyncEnabled property helps identify the applicable management path.

Trap Repeatedly editing a synchronized department in the cloud, because the authoritative on-premises value controls the synchronized attribute.

2 questions test this
Disabling an account blocks sign-in without deleting its directory object

When an internal user's account must remain in the directory but must not be available for sign-in, set Account enabled to false. This is an account-state change rather than a user deletion, and it can be reversed by enabling the same account. A deleted user instead enters the deleted-users lifecycle and releases consumed licenses.

2 questions test this
Deleted users have a 30-day recovery window and release their licenses

Microsoft Entra ID keeps a deleted user in Deleted users for 30 days, during which the account can be restored. Deletion makes licenses consumed by that user available to other users. Choose restoration within that window when recovering an accidentally deleted account, rather than treating an identically named new account as a recovery of the original object.

Trap Recreating a user with the old UPN to recover the old identity, because a new account is a different directory object.

2 questions test this
Bulk creation imports internal users, while bulk invitations onboard external collaborators

When creating many internal accounts, use the Microsoft Entra bulk-create CSV template and preserve its downloaded column headings. Name, User name, and Initial password are required, with one user per row; validate the upload and review the operation results. Bulk creation creates internal member accounts and sends no invitation emails, so use the external bulk-invite workflow when users should redeem invitations with their existing identities.

Trap Uploading partner email addresses through Bulk create to send B2B invitations, because bulk creation provisions internal password-backed member accounts.

2 questions test this
Administrative units scope directory administration without expanding a group's membership into that scope

An administrative unit contains selected Microsoft Entra users, groups, or devices so that an administrator role can be delegated over that subset of the tenant. Adding a group brings administration of that group, such as its name and membership, into scope. To let the scoped administrator manage the member users' properties or reset their passwords, add those users themselves to the administrative unit as well.

Trap Using an Azure management group to delegate regional user administration, which scopes Azure subscriptions and resources rather than directory user objects.

Administrative units limit delegated management without hiding the rest of the directory

An administrative unit scopes delegated management permissions but does not create a directory-visibility isolation boundary. Its members and scoped administrators retain their default user permissions to browse users, groups, and other directory resources outside the unit. The Microsoft 365 admin center filters a scoped administrator's user list, but that interface filtering does not revoke the ability to browse other users through the Microsoft Entra admin center, PowerShell, or other Microsoft services.

2 questions test this
Security groups and Microsoft 365 groups support different membership and collaboration needs

Use a security group to manage access for directory objects such as users, devices, and service principals. Use a Microsoft 365 group for user collaboration with a group email address and associated Microsoft 365 resources. Microsoft 365 group members are users, including permitted external users, rather than devices or nested groups.

Trap Choosing a Microsoft 365 group to collect managed devices, because that group type supports user membership only.

2 questions test this
Group ownership delegates management separately from membership

A group's Owners and Members lists represent different relationships. Ownership delegates group management, whereas membership is what group-based access and licensing consume. Add a person to both lists when that person must administer the group and also receive its member benefits; adding an owner alone does not establish membership.

Trap Replacing the Members list with department managers to delegate maintenance, because membership grants group benefits rather than establishing the Owners relationship.

2 questions test this
Group type and object ID remain fixed when editable group properties change

Microsoft Entra group properties allow updates to the name, description, and eligible membership configuration, but not the group type or object ID. Replacing a security group with a Microsoft 365 group therefore requires a new group rather than a property edit. Use the existing object ID when automation must continue identifying a group after a display-name change.

2 questions test this
Role-assignable groups require privileged creation and assigned membership

When a group will carry Microsoft Entra administrator roles, enable Microsoft Entra roles can be assigned to the group during group creation. This requires Microsoft Entra ID P1 or P2 and at least Privileged Role Administrator. The group uses Assigned membership, and groups cannot be added as members of a role-assignable group. These restrictions concern Microsoft Entra role delegation, not a requirement for every security group used with Azure RBAC.

Trap Creating a dynamic department group for Microsoft Entra administrator-role assignment, because role-assignable groups require assigned membership.

2 questions test this
A group's source and type determine where administrators can manage it

Manage ordinary cloud security and Microsoft 365 groups in the Microsoft Entra admin center using an appropriate role such as Groups Administrator or User Administrator. Groups synchronized from on-premises Active Directory must be managed on-premises. Distribution lists and mail-enabled security groups instead require the Exchange or Microsoft 365 management path, even though their directory objects are visible in Microsoft Entra ID.

Trap Editing an on-premises-synchronized group's membership in the Microsoft Entra admin center, because synchronization does not transfer membership authority to the cloud.

2 questions test this
Bulk membership imports add existing directory objects to a selected group

To add many existing users to a group, open that group's Members page and choose Bulk operations > Import members. Download the membership CSV template, preserve its full column header, remove any example row, and enter one member object ID or user principal name per row, with at least two users in the file. Fix upload-validation errors before submitting the job, then inspect Bulk operation results or download the results CSV to identify individual additions and failures.

Trap Using the bulk-create user template for a membership change, which supplies new-account properties rather than the selected group's member identifiers.

2 questions test this
Member users can create directory groups unless tenant settings restrict creation

Microsoft Entra member users can create security groups and Microsoft 365 groups by default. Restrict the corresponding group-creation settings when ordinary members should not create them; Microsoft 365 group creation can also be limited to a selected set of users, while appropriately privileged directory administrators retain creation rights. These settings govern creation of directory groups, independently of delegated ownership of an existing group and Azure management-group creation controls.

Trap Using Restrict access to Microsoft Entra administration portal as the creation restriction, which adds browsing friction without blocking programmatic group creation.

2 questions test this
Deleted Microsoft 365 groups can be restored with their contents for 30 days

When a Microsoft 365 group is accidentally deleted, select the retained group under Deleted groups and use Restore group to recover it and its contents. The retention window is 30 days from deletion and cannot be customized; a permanently purged group is no longer available for restoration. Restoring associated content can take up to 24 hours. Microsoft documents cloud security group soft delete and restoration separately as a public-cloud preview, so distinguish that extension from the established Microsoft 365 group recovery behavior.

Trap Creating a replacement Microsoft 365 group with the original display name, which creates a different directory object rather than recovering the deleted group's retained contents.

2 questions test this
Dynamic membership follows attribute rules rather than manual additions

When membership must track changing user or device attributes, use a dynamic membership group. Microsoft Entra ID reevaluates rules after relevant attribute changes and adds or removes objects according to the result; administrators cannot manually add or remove members of that dynamic group. Protect write access to attributes used in access-sensitive rules, because changing those attributes can change group eligibility.

Trap Giving users self-service write access to an attribute that controls a privileged resource group, because the attribute becomes an indirect membership control.

3 questions test this
A dynamic membership rule targets users or devices, not both

A dynamic security group can evaluate user attributes or device attributes, but one rule cannot mix users and devices into a single dynamic membership population. Microsoft 365 groups support dynamic users only. Device rules can reference device properties but cannot derive membership from the department or other user attributes of the device owner.

Trap Filtering a dynamic device group with user.department, because device membership rules cannot evaluate the owner's user attributes.

3 questions test this
Dynamic scalar rules distinguish exact values, patterns, lists, and missing values

Dynamic membership expressions use property, operator, and value, such as user.department -eq "Sales". Use -in with a bracketed list for several acceptable values, -startsWith for a prefix, and -match for a regular expression; string matching is case-insensitive. Compare a missing value with -eq null or -ne null without quotes, because "null" is a literal string rather than the absence of a value.

Trap Using -contains for an exact department allowlist, because substring matching can admit departments outside the intended set.

3 questions test this
Collection attributes require membership expressions over their elements

For multivalued dynamic-rule properties, use -any or -all to evaluate elements rather than treating the collection as a scalar string. For example, user.proxyAddresses -any (_ -startsWith "SMTP:") checks for a matching address, while assignedPlans rules can examine servicePlanId and capabilityStatus together. The -contains string operator performs a partial string match and is not a substitute for collection membership evaluation.

Trap Comparing an entire proxyAddresses collection to one address using scalar equality, because each collection element must be evaluated through the collection expression.

4 questions test this
Parentheses control how dynamic membership combines alternatives and restrictions

Dynamic membership evaluates comparison operators before -not, then -and, then -or. Use parentheses when a restriction must apply to several alternative matches: user.country -eq "US" -and (user.department -eq "Sales" -or user.department -eq "Marketing") restricts both departments to the United States. Without the grouping, an -or branch can qualify independently of a preceding -and restriction.

Trap Appending an ungrouped -or exception to a location-restricted rule, because that alternative can qualify without satisfying the location condition.

2 questions test this
Unassigning a product license frees a seat without reducing purchased capacity

Use the Microsoft 365 admin center's user licensing controls for individual assignments or Billing > Licenses to manage assignments for a selected product. Removing a user's license makes the seat reusable but does not itself remove that purchased seat from the subscription, so reduce purchased capacity separately when the goal is lower license charges. License removal is also distinct from user deletion and can affect service access and service-specific data retention, so plan it as an entitlement change rather than treating it as a universal account-removal operation.

Trap Unassigning unused seats and assuming the subscription's purchased license count has decreased, because entitlement assignment and billed capacity are separate settings.

2 questions test this
Group licensing consumes licenses for direct user members, not group containers

Group-based licensing applies product licenses to the group's direct user members, including guest users when a product license is assigned to them. A group owner who is not also a member receives no license through that ownership. Nested-group users are not licensed through the parent group's assignment, so place users directly in the licensed group when they must receive its licenses.

Trap Allocating one product license to cover an entire security group, because the group is an assignment mechanism rather than a shared license seat.

2 questions test this
Product licensing is managed through Microsoft 365 administration or Microsoft Graph

Use Billing > Licenses in the Microsoft 365 admin center to assign or unassign products for groups and to enable or disable individual apps and services. License Administrator, Groups Administrator, and User Administrator can perform group license assignment. Microsoft Graph PowerShell offers Set-MgGroupLicense for automation, so a directory administrator does not need an Azure resource-management role to assign Microsoft 365 licenses.

Trap Assigning an Azure RBAC Contributor role to activate Microsoft 365 services, because resource authorization does not assign a product license.

2 questions test this
License eligibility depends on usage location rather than contact address

Set a user's Usage location to the correct country or region before assigning services whose availability varies by location. Group-based licensing uses the tenant location when a user has no explicit usage location, which can be inappropriate in a multinational tenant. Resolve an unsupported-location error by correcting eligibility and the user's usage location rather than changing an unrelated postal-address field.

Trap Changing a user's office street address to resolve a service-country licensing error, because service eligibility uses Usage location.

2 questions test this
A group license assignment can succeed as configuration while individual users remain unlicensed

Group-based license processing can record user-level failures in the background, including insufficient available licenses. Inspect the product's Errors & issues view to identify affected users and free unused licenses or obtain sufficient capacity before reprocessing. When multiple products are assigned to one group, investigate the failing product because its assignment problem can also prevent the other products in that group from being applied to the user.

Trap Treating the presence of a license on the group as proof that every member is licensed, because individual assignment failures are recorded separately.

2 questions test this
Conflicting service plans must be reconciled across a user's product assignments

When product assignments expose conflicting service plans, resolve the conflict by disabling a conflicting plan, removing an unnecessary direct assignment, or adjusting the group assignment. Review the user's full assignment set rather than only the newest group, because an existing direct product can be the source of the conflict. Selecting individual apps and services allows the needed product assignment to remain while an incompatible component is disabled.

Trap Buying more seats for a service-plan conflict, because additional capacity does not reconcile incompatible enabled plans.

2 questions test this
License prerequisites control both add-on assignment and prerequisite removal

An add-on service can require an enabled prerequisite service plan. Assign the prerequisite with the add-on when necessary, and remove or reassign dependent services before removing their prerequisite. Dependency protection can prevent license removal or preserve a required entitlement through a direct assignment, so inspect the remaining dependencies when a user stays licensed after a group-related cleanup.

Trap Disabling the base service before removing its dependent add-on, because the dependent entitlement still requires that prerequisite.

2 questions test this
Directory address defects can prevent Exchange-related license assignment

Duplicate proxy addresses can cause Exchange Online licensing to fail even when license capacity and usage location are valid. Correct the conflicting directory addresses and then reprocess the affected assignment. License changes can also recalculate mail and proxyAddresses values, so investigate the source of those attributes when assignment processing exposes an address problem.

Trap Moving the affected user into another licensed group to fix a duplicate proxy address, because changing the assignment source leaves the conflicting directory value intact.

2 questions test this
Moving between licensed groups requires overlap until the new assignment is applied

When transferring a user between licensed groups without interrupting services, add the user to the destination group first, confirm the new assignment on the user's Licenses page, and then remove the user from the source group. Group membership and licensing changes are processed asynchronously, so an immediate remove-then-add sequence can leave a period without entitlement. After correcting a genuine licensing error, use Reprocess rather than assuming a configuration edit has already completed processing.

Trap Removing the old licensed membership before confirming the replacement entitlement, because asynchronous processing leaves no guaranteed overlap.

2 questions test this
Concurrent group license assignments can produce a transient error that retries automatically

LicenseAssignmentAttributeConcurrencyException can appear in audit logs when multiple groups try to assign the same product license to a user concurrently. Microsoft Entra ID retries processing and resolves this concurrency issue automatically, so this specific error requires no manual action. Distinguish it from persistent assignment errors whose underlying capacity, service-plan, or directory-data problem must first be corrected.

Trap Buying additional product seats in response to the concurrency exception, which addresses license capacity rather than simultaneous assignment processing.

Cross-tenant access settings distinguish incoming guests from employees visiting other organizations

Use inbound cross-tenant settings to control external Microsoft Entra users reaching your resources, and outbound settings to control your users reaching an external organization's resources. Organization-specific settings override your defaults and can narrow access to selected users, groups, and applications. Initially B2B collaboration is enabled, B2B direct connect is blocked, and external MFA or device claims are not trusted; inbound trust settings can accept those claims without turning off your own access requirements. Invitation permissions and guest directory visibility remain external collaboration settings rather than these directional access controls.

Trap Changing outbound access to admit a partner's users to your tenant, because incoming partner access is governed by your inbound settings and the partner's outbound settings.

3 questions test this
A B2B user's identity provider and UserType describe independent properties

Microsoft Entra B2B collaboration creates a user object in the resource tenant while an external identity provider authenticates the collaborator. UserType describes the relationship and default privilege level in the host tenant, not where the credentials are stored. An external user can be a Guest or Member, and changing UserType alone does not convert external authentication into a locally managed password.

Trap Changing UserType to Member to take over a partner's password administration, because credential authority is independent of that relationship property.

3 questions test this
Inviting a B2B user creates the object before the invitation is redeemed

A B2B invitation creates a user object in the resource directory before the guest accepts it. Pending acceptance indicates that redemption has not completed; resend the invitation when appropriate rather than creating another identity. Redemption updates the object's identity-provider information, and the guest object commonly has a UPN containing #EXT# under the resource tenant's onmicrosoft.com domain.

Trap Waiting for redemption before looking for the guest object in Users, because the invitation already created that object.

3 questions test this
Guest directory visibility is configured separately from application and Azure resource access

External collaboration settings offer member-equivalent guest visibility, limited visibility by default, or the most restrictive access to the guest's own directory object. Choose the restrictive setting when guests should not browse other users or group memberships. Access to an application or an Azure resource still requires its own assignment; directory visibility is not an authorization grant to workloads.

Trap Using the most restrictive directory visibility setting as a substitute for removing a guest's Azure role assignment, because directory browsing restrictions do not revoke that resource permission.

3 questions test this
Invitation policy and the Guest Inviter role together control who can onboard guests

External collaboration settings can allow everyone, members and specified administrators, only specified administrators, or no one to invite guests. The default permits all users, including guests, to invite external collaborators. When invitations are limited to specified administrator roles, use Guest Inviter to delegate invitation capability without granting broader user administration; the no-one setting blocks invitations even for administrators.

Trap Granting Groups Administrator solely to delegate B2B invitations, because Guest Inviter is the purpose-specific invitation role.

3 questions test this
B2B domain allowlists and blocklists govern invitations without revoking redeemed guests

Use an allowlist to permit invitations only to named domains, or a blocklist to allow other domains while rejecting named ones; an organization cannot configure both list types together. Domain restrictions do not retroactively apply to guests who already redeemed their invitations, but can block redemption of a still-pending invitation. Both domain restrictions and cross-tenant access settings are checked at invitation time, and SharePoint or OneDrive sharing lists remain separate controls.

Trap Adding a domain to the B2B blocklist to remove an already redeemed guest's current assignments, because the list is an invitation restriction rather than an access-revocation workflow.

3 questions test this
Email one-time passcodes support guests without another usable identity provider

When an invited B2B user has no usable Microsoft Entra, Microsoft account, or configured federated identity, email one-time passcode can authenticate the guest through access to their mailbox. This fallback is enabled by default for new tenants and existing tenants that have not explicitly disabled it; disabling it prompts eligible new invitees to create a Microsoft account instead. A passcode lasts 30 minutes, and an email-OTP session expires after 24 hours, after which a new passcode is required.

Trap Provisioning a local employee password for every partner lacking a Microsoft account, because B2B email OTP can provide authentication without creating that internal account.

3 questions test this
Resetting redemption changes a guest's sign-in binding while preserving the object

When a guest changes identity provider, changes email, or has the home account recreated, reset redemption status and reinvite the existing guest. This retains the object ID, group memberships, and app assignments; after redemption the sign-in email can change while the resource-tenant UPN remains unchanged. Add the new address to mail or otherMails as required before reinviting the existing object.

Trap Deleting and reinviting a guest to preserve all existing access links, because deleting the object discards the identity those links reference.

3 questions test this
Password writeback depends on the reset operation's supported entry point

For a hybrid end-user password reset that must reach AD DS, use the SSPR password-reset portal or a supported administrator reset through the Microsoft Entra admin center. A supported administrator-initiated Microsoft Graph authentication-method reset also supports writeback, but an administrator reset from the Microsoft 365 admin center does not. End users resetting their own passwords through the Microsoft Graph API are not a supported writeback path, so the mere use of a cloud API does not establish equivalent hybrid behavior.

Trap Using the Microsoft 365 admin center for an administrator reset that must write back to AD DS, because that entry point does not support password writeback.

1 question tests this
SSPR can target all users or a selected group, including nested members

Microsoft Entra SSPR supports None, Selected, or All user targeting. The admin center selects one group for Selected targeting, and nested groups are supported, allowing a staged rollout without enabling every user. Use at least Authentication Policy Administrator to configure the service, and test ordinary-user behavior with a non-administrator account because administrator reset policy differs.

Trap Creating several independent Selected-group entries in the SSPR portal, because the portal selects one group and wider grouping is achieved through its supported membership structure.

2 questions test this
SSPR licensing distinguishes known-password changes, forgotten-password resets, and writeback

Microsoft Entra ID Free permits a cloud user who knows the password to change it, but does not provide ordinary cloud-only forgotten-password reset. Microsoft 365 Business Standard supports cloud-only reset, while hybrid password change or reset with on-premises writeback requires Microsoft Entra ID P1, P2, or Microsoft 365 Business Premium. License every intended beneficiary; P2 is not necessary when P1 already satisfies the required SSPR capability.

Trap Choosing Microsoft 365 Business Standard for hybrid password writeback because it supports cloud-only reset, since its reset entitlement does not include on-premises writeback.

2 questions test this
SSPR requires enough registered, enabled verification methods at reset time

The SSPR policy requires either one or two authentication methods, and the user must have sufficient usable methods registered before resetting or unlocking. Increasing the requirement or disabling a previously registered method can leave a user unable to reset until registration is corrected or an administrator assists. Microsoft Authenticator, software OATH, and hardware OATH count as one authentication-method category for SSPR, so combining those token methods cannot satisfy a two-method requirement.

Trap Counting an Authenticator notification and an OATH code as two independent SSPR methods, because they count as the same SSPR method category.

2 questions test this
Authentication method availability is managed in the centralized Authentication methods policy

Configure allowed verification methods through the Microsoft Entra Authentication methods policy rather than the legacy MFA or SSPR method-management controls, except that security questions remain managed in the legacy SSPR policy. Microsoft ended method management in those legacy policies beginning September 30, 2025, with that security-questions exception. SSPR enablement, required-method count, registration, and writeback remain separate SSPR configuration decisions; enabling a method alone does not enroll every user in password reset.

Trap Enabling an MFA method and treating every user as SSPR-enabled, because authentication-method availability and password-reset targeting are separate controls.

2 questions test this
SSPR registration prompting and periodic reconfirmation keep recovery information usable

Require users to register when signing in to prompt registration during supported sign-ins; otherwise users can register manually through the SSPR setup portal. Periodic reconfirmation is available when sign-in registration prompting is enabled and accepts 0 through 730 days. A value of 0 disables reconfirmation prompts, not SSPR itself, and users must sign in before the reconfirmation workflow can occur.

Trap Setting reconfirmation to 0 to demand confirmation at every sign-in, because zero means users are never asked to reconfirm on that schedule.

2 questions test this
Administrator SSPR has a separate policy and tenant disable control

Microsoft Entra administrator SSPR uses a separate administrator reset policy that prohibits security questions. Set AllowedToUseSspr to false on the tenant authorization policy to disable administrator SSPR. When disabled, administrators cannot reset passwords through SSPR even if the ordinary-user password reset policy includes them; ordinary-user targeting does not override that administrator restriction.

Trap Adding an administrator to the ordinary-user SSPR target group to bypass AllowedToUseSspr set to false, because user targeting cannot override the administrator SSPR disable control.

2 questions test this
Hybrid SSPR needs working writeback and enforces on-premises password policy synchronously

When passwords are managed in on-premises AD DS, enable password writeback through Microsoft Entra Connect or cloud sync as well as SSPR. Writeback supports hybrid authentication models and synchronously checks on-premises password history, complexity, age, and filters before committing the reset, giving immediate failure feedback. Communication is outbound over port 443, without inbound firewall rules; an unavailable writeback service prevents the on-premises-managed password from being reset through SSPR.

Trap Enabling password hash synchronization alone for cloud-initiated resets, because synchronization to the cloud does not implement the reverse writeback operation.

2 questions test this
SSPR user notifications and administrator-reset notifications reach different recipients

Enable user reset notifications to send the resetting user an email using the primary and alternate addresses, falling back to the UPN when those are unavailable. Enable notifications about other administrators' resets to notify Global Administrators at their primary email addresses. These settings provide awareness of completed reset events; a custom helpdesk contact is a separate customization rather than an arbitrary recipient list for administrator notifications.

Trap Using the notify-all-admins reset option as an arbitrary helpdesk distribution-list subscription, because its recipients are Global Administrators rather than a configurable group of support staff.

2 questions test this
Cloud password rules and expiration settings are distinct from reset verification

Cloud-managed Microsoft Entra passwords must contain 8 through 256 characters and satisfy three of four character categories: lowercase, uppercase, numbers, and symbols. Current new tenants default to no password expiration, whereas tenants created before 2021 defaulted to 90 days, so inspect the domain policy rather than assuming one age limit. Use Microsoft Graph domain settings for domain expiration policy and the user's DisablePasswordExpiration password policy for a per-user exception; successful SSPR verification still requires an acceptable new password.

Trap Changing the required number of SSPR methods to fix a rejected new password, because verification requirements do not relax password complexity or length.

2 questions test this
Security-group staged rollout is an exception to supported SSPR password writeback

SSPR writeback to an on-premises domain is not supported for users in a security group with staged rollout enabled. It can work in individual cases, but Microsoft does not guarantee consistent operation in that configuration. Include this support boundary when checking hybrid reset readiness, even if the chosen authentication model otherwise supports writeback.

Administrator SSPR normally requires two verification gates even when ordinary users need only one

Microsoft Entra administrator SSPR normally enforces a fixed two-gate verification policy rather than inheriting the ordinary-user method count. In an established tenant with a custom domain or synchronized identities, an account assigned an affected Microsoft Entra administrator role must provide two pieces of authentication data, even if ordinary users need only one. Microsoft documents one-gate exceptions during the first 30 days of a trial subscription, or when a tenant has no custom domain and Microsoft Entra Connect is not synchronizing identities. Check the administrator policy and these exceptions when explaining why an administrator's reset experience differs from an ordinary user's.

Trap Changing the centralized Authentication methods policy to weaken administrator SSPR verification, although the administrator reset policy is independent of that policy.

2 questions test this
Password writeback needs connector permissions on eligible AD DS accounts as well as feature enablement

For Microsoft Entra Connect Sync password writeback, enable Password writeback in the synchronization wizard and then enable Write back passwords to your on-premises directory under SSPR On-premises integration. Delegate Reset password, Change password, Write lockoutTime, and Write pwdLastSet to the AD DS connector account, with password-write permissions inherited by the descendant user objects that it manages. Also grant the Unexpire Password extended right on each domain's root object in the forest, using an appropriate inheritance scope such as This object and all descendant objects; missing effective permissions can make resets fail despite apparently correct cloud settings. The writeback service account cannot reset passwords for on-premises users belonging to protected AD DS groups, so distinguish that account-protection boundary from an ordinary missing connector permission or a Microsoft Entra administrator verification requirement.

Trap Granting the operator Hybrid Identity Administrator to repair connector-account access-denied errors, although cloud configuration authority does not supply the connector account's AD DS permissions.

2 questions test this
SSPR can unlock an on-premises account without replacing its known password

When a user knows the password but needs to unlock an on-premises AD DS account through SSPR, set Allow users to unlock accounts without resetting their password to Yes under Password reset > On-premises integration in a working writeback deployment. This separate setting offers unlock-only recovery as well as a combined password reset and unlock. With the setting at No, users can only perform the combined operation; a password reset normally unlocks the account as part of that recovery.

Trap Reducing the SSPR authentication-method requirement, which changes identity verification rather than enabling the separate unlock-only recovery operation.

2 questions test this

Also tested in

References

  1. https://learn.microsoft.com/en-us/azure/role-based-access-control/rbac-and-directory-admin-roles
  2. https://learn.microsoft.com/en-us/entra/external-id/external-collaboration-settings-configure
  3. https://learn.microsoft.com/en-us/entra/fundamentals/how-to-create-delete-users
  4. https://learn.microsoft.com/en-us/entra/fundamentals/how-to-manage-groups
  5. https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-group-licenses
  6. https://learn.microsoft.com/en-us/entra/fundamentals/add-custom-domain
  7. https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-enable-sspr
  8. https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-enable-sspr-writeback
  9. https://learn.microsoft.com/en-us/entra/external-id/reset-redemption-status
  10. https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-writeback
  11. https://learn.microsoft.com/en-us/entra/external-id/user-properties
  12. https://learn.microsoft.com/en-us/entra/fundamentals/users-default-permissions
  13. https://learn.microsoft.com/en-us/entra/fundamentals/how-to-manage-user-profile-info
  14. https://learn.microsoft.com/en-us/entra/fundamentals/concept-learn-about-groups
  15. https://learn.microsoft.com/en-us/microsoft-365/admin/create-groups/compare-groups
  16. https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-policy
  17. https://learn.microsoft.com/en-us/entra/identity-platform/app-objects-and-service-principals
  18. https://learn.microsoft.com/en-us/graph/api/group-post-owners?view=graph-rest-1.0
  19. https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/assign-user-or-group-access-portal
  20. https://learn.microsoft.com/en-us/azure/role-based-access-control/overview
  21. https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/groups-concept
  22. https://learn.microsoft.com/en-us/entra/identity/users/groups-dynamic-membership
  23. https://learn.microsoft.com/en-us/entra/identity/users/groups-restore-deleted
  24. https://learn.microsoft.com/en-us/entra/identity/users/users-bulk-add
  25. https://learn.microsoft.com/en-us/entra/identity/users/groups-bulk-import-members
  26. https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/administrative-units
  27. https://learn.microsoft.com/en-us/azure/governance/management-groups/overview
  28. https://learn.microsoft.com/en-us/microsoft-365/admin/manage/assign-licenses-to-users
  29. https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
  30. https://learn.microsoft.com/en-us/entra/external-id/one-time-passcode
  31. https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-overview
  32. https://learn.microsoft.com/en-us/entra/external-id/allow-deny-list
  33. https://learn.microsoft.com/en-us/entra/identity/conditional-access/overview
  34. https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-licensing
  35. https://learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-howitworks
  36. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/choose-ad-authn
  37. https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-methods-manage
  38. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-staged-rollout