Study guide
3.2 Identity Management Design
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
3.2 Identity Management Design
Key Takeaways Explain This Topic AI
Three external-identity patterns map to three different scenarios: B2B collaboration (named external individual, guest object created), B2B direct connect (peer-to-peer, mostly Teams shared channels, no guest object), and external tenant/CIAM (consumer sign-up apps).
All internal users can invite guests by default — restricting invitations to specific roles requires an explicit configuration change.
Guest users get restricted directory permissions by default: they can see their own groups and look up users by exact email, but cannot browse the full directory.
Cross-tenant access settings control inbound/outbound B2B access and let a tenant trust a partner's existing MFA/device-compliance claims to avoid redundant challenges.
B2B direct connect is blocked for all external tenants until an administrator explicitly configures cross-tenant access settings to allow it.
Last updated: July 2026
Why External Identity Design Matters on AZ-305
Almost every enterprise Azure environment eventually needs to grant access to people outside its own tenant — a contractor, an auditor, a partner organization, or an app's own customers. AZ-305 tests whether you can pick the right external-identity pattern for a scenario rather than defaulting to "just invite them as a guest" every time. Over-provisioning guest accounts creates licensing costs and audit sprawl; under-provisioning forces users into shared credentials, which is a security anti-pattern the exam expects you to reject.
Microsoft Entra External ID: Three Patterns
Microsoft Entra External ID is the umbrella term for identity solutions involving people outside your own directory. AZ-305 design questions map to three distinct patterns:
Pattern Use case Guest object created in your tenant?
B2B collaboration Invite a named external user (contractor, partner employee) to sign in with their home organization's credentials and access specific resources Yes — a guest user object
B2B direct connect Enable seamless, mutual collaboration between two Microsoft Entra tenants, primarily for Teams shared channels No — no guest object; trust is tenant-to-tenant
External tenant (CIAM) Build a customer-facing application where end users sign up and sign in with social or local accounts No — customers live in a separate, dedicated external tenant, not your workforce tenant
B2B collaboration is the default answer whenever a scenario names a specific external person who needs access to internal resources like a SharePoint site, an app, or an Azure resource. The external user authenticates with their own organization's identity provider (or creates a Microsoft account), and a guest user object is created in your tenant to hold their permissions.
B2B direct connect is the correct answer when the scenario is about two organizations collaborating as peers — most commonly through Teams shared channels — without either side managing guest accounts for the other's staff. No B2B direct connect trust exists until an administrator on each side explicitly configures cross-tenant access settings to allow it; by default, Entra ID blocks all inbound and outbound B2B direct connect capability.
External tenant (CIAM) is the answer when the scenario describes consumers or customers signing up for an application — not employees of another company. This uses a dedicated external tenant, separate from your workforce Entra ID tenant, and supports social identity providers (Google, Facebook) and local account sign-up flows that would never be appropriate inside a corporate workforce directory.
Guest User Defaults and Cross-Tenant Access Settings
By default, all internal users in a tenant can invite external guests — this is a common exam trap, since architects often assume invitations require an administrator. If a design requirement states "only HR can invite external users," that requires explicitly restricting the "guest invite settings" (or delegating to a specific role), because the out-of-the-box behavior is permissive.
Guest accounts land with restricted directory permissions by default: a guest can see their own group memberships and look up other users by exact email address, but cannot browse the full directory the way a member can. This default is intentional and rarely needs to change for a compliant design.
Cross-tenant access settings control B2B collaboration and B2B direct connect at a granular, per-partner-organization level. An architect can configure:
Inbound access — what external users from a specific partner tenant can access in your tenant.
Outbound access — what your users can access when visiting a partner tenant.
Trust settings — whether to trust the MFA and device-compliance claims a partner tenant already performed, avoiding a redundant second MFA challenge for federated external users.
Exam Scenario
A hospital network needs a visiting specialist from a partner clinic (a separate Entra ID tenant) to access one internal clinical application for the duration of a six-week rotation, using her existing partner-tenant credentials, with no new password to manage. The correct recommendation is B2B collaboration : invite the specialist as a guest, scope her access to only the clinical application (ideally through an access package in entitlement management with an automatic expiration date matching the rotation), and configure cross-tenant access settings to trust the partner tenant's MFA claim so she is not forced through a second MFA enrollment. B2B direct connect would be the wrong answer here because the requirement is a single named individual accessing a specific app — not a Teams shared-channel collaboration between the two organizations as a whole.
Common Traps
Reaching for B2B direct connect whenever "another company" is mentioned — it is scoped almost entirely to Teams shared channels, not general resource access.
Assuming CIAM (external tenant) is the answer whenever "external users" appears — CIAM is for consumers of a customer-facing app, not partner-company employees needing internal access.
Forgetting that guest accounts still consume Entra ID P1/P2 licensing (at a discounted ratio) once premium features like Conditional Access are applied to them — a design that scales to thousands of external users needs to account for this cost.
Assuming an administrator must approve every guest invitation — the tenant-wide default allows any member to invite guests unless explicitly restricted.