Study guide

2.2 Licenses, External Users, and SSPR

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

2.2 Licenses, External Users, and SSPR

Key Takeaways Explain This Topic AI

Usage location is a common prerequisite for assigning Microsoft cloud licenses to users.

External users are represented as guest objects in the resource tenant and still need authorization to resources.

Self-service password reset depends on scope, authentication methods, registration, and whether password writeback is needed.

Group-based licensing and group-based access solve different problems even when they use the same group object.

Last updated: May 2026

Licenses Are Not Permissions

A license enables a cloud service plan for a user, such as Microsoft 365 or Entra capabilities, but it is not an Azure RBAC assignment. A user can have a license and still be unable to manage a resource group. A user can also have Azure RBAC access without a particular productivity license. Keep these tracks separate.

For license assignment in the portal, use Microsoft Entra ID > Users > select user > Licenses or Microsoft Entra ID > Groups > select group > Licenses for group-based licensing. Before assigning many Microsoft cloud licenses, confirm the user's Usage location . This property identifies the country or region where the services are consumed and is a common prerequisite in Microsoft cloud licensing workflows.

  • Task Better tool choice
  • Assign one license while fixing a user ticket Portal
  • Assign licenses to all members of a department Group-based licensing
  • Audit many license states Script or reports
  • Fix a usage location error Portal for one user, automation for many users

Exam trap: group-based licensing is not the same as group-based Azure RBAC. One group may be used for both if governance allows it, but the effects are different. A license assignment affects service availability. A role assignment affects what Azure resources a principal can manage.

External Users And Guest Accounts

External collaboration in Microsoft Entra ID usually creates a guest user object in your tenant. The external person may authenticate with their home identity provider, but your tenant stores a representation of that user so you can place the guest in groups, assign application access, or assign Azure RBAC.

Portal path: Microsoft Entra ID > Users > New user > Invite external user . After the guest exists, assign access the same way you would for another principal: add to a security group or create an RBAC assignment at the correct scope.

Concept Practical meaning

Home tenant Where the external user's original identity is managed.

Resource tenant Your tenant, where the guest object and access decisions exist.

Invitation redemption The guest accepts and establishes sign-in relationship.

Guest user type Indicates external collaboration; not automatically privileged.

Scenario: A vendor needs to view metrics on one production resource group. Invite the vendor as a guest, add the guest to a security group such as rg-prod-monitor-readers , then assign Monitoring Reader or Reader at that resource group depending on the need. Do not make the vendor a tenant administrator, and do not assign access at subscription scope if the task is limited to one resource group.

A common support issue is directory context. The guest may sign in successfully but be looking at their home tenant or a different directory in the Azure portal. Have the user switch directories from the portal account menu, then verify the guest object and RBAC assignment in your tenant.

Self-Service Password Reset

Self-service password reset lets users reset their own passwords after proving identity with approved authentication methods. The administrator chooses who is enabled, which methods are allowed, how many methods are required, and whether users must register. Portal path: Microsoft Entra ID > Password reset .

SSPR setting Exam relevance

Scope None, Selected, or All users. Selected usually means a group.

Authentication methods Mobile app, phone, email, security questions, and similar options depending on configuration.

Number of methods required Controls reset proof strength.

Registration Users must have usable methods registered before reset works.

Notifications Can alert users or admins about reset events.

On-premises integration Password writeback is needed for hybrid users whose password must update on-premises.

For cloud-only users, SSPR can reset the cloud password if configured. For synchronized hybrid users, the key question is whether the reset must write back to on-premises Active Directory. If yes, the environment needs the right synchronization and password writeback configuration. AZ-104 questions often include a hybrid detail to test this distinction.

Portal And CLI Decision Logic

Use the portal for invitation workflows, individual license fixes, SSPR policy configuration, and checking registration state. Use automation when onboarding many contractors, applying usage locations in bulk, or auditing license assignment failures. Azure CLI can query users and groups, but some licensing and SSPR administration is better handled through Microsoft Graph PowerShell or the Entra admin center.

  • Helpful orientation commands: az ad user show --id vendor_alex_contoso.com#EXT#@fabrikam.onmicrosoft.com
  • az ad group member add --group rg-prod-monitor-readers --member-id <guest-object-id>

az role assignment create --assignee <guest-object-id> --role Reader --scope /subscriptions/<sub-id>/resourceGroups/rg-prod

Notice the order. Create or invite the identity, place it in the right group if using group-based access, then assign the role at the required scope. If the user cannot sign in, troubleshoot identity and redemption. If the user can sign in but cannot view the resource, troubleshoot RBAC and directory context.

Governance Scenarios And Traps

Scenario: A company wants every employee in the Sales department to receive the same cloud service license and Reader access to a reporting resource group. You can use a dynamic security group based on department, assign the license to that group, and assign Reader to that group at the resource group. However, document the dual use. If later the group is changed for licensing reasons, resource access may change too.

Scenario: A newly hired cloud-only user cannot receive a license. The question includes that usage location is blank. The best answer is to set usage location before assigning the license. Assigning Owner on a subscription does not fix a licensing prerequisite.

Scenario: SSPR is enabled for a selected group, but a user outside the group cannot reset a password. The fix is to add the user to the selected group or change the SSPR scope. Resetting the user's Azure RBAC roles is irrelevant.

Scenario: A guest user needs to manage only tags on resources in one resource group. The least-privilege answer is not subscription Contributor. Consider a role that allows the needed resource write operation at the resource group scope, and remember that some operations may require broad write permissions unless a custom role exists. If only built-in roles are offered, choose the least broad built-in role that meets the stated action.