A question that wasn't really about configuration
Rohan's firm, after acquiring a smaller competitor, brought in a consulting architect, Devika, to answer a question that had nothing to do with clicking through the Entra ID portal: should the two companies' identities merge into one tenant, stay separate and federated, or something in between? Every option was technically configurable. The actual hard part was deciding which one was right, weighing tradeoffs AZ-104's hands-on skills alone don't address.
The real shift: design decisions, not configuration steps
This is the fundamental difference between AZ-104 and AZ-305: AZ-104 asks "how do I create this group correctly," AZ-305 asks "should these two organizations share one tenant, and what does that decision cost us later if it's wrong." A wrong configuration is usually fixable in an afternoon. A wrong identity architecture decision can mean a multi-month remediation project. That's why AZ-305 questions read less like tutorials and more like tradeoff scenarios.
Single tenant, multi-tenant, or hybrid: the real tradeoffs
A single, unified tenant simplifies management and gives consistent policy enforcement, but means every acquired company's quirks, naming conventions, existing group structures, security posture, all need reconciling into one system. Keeping tenants separate avoids that painful merge but means managing policy and access consistency across multiple systems indefinitely, and cross-tenant collaboration (Entra B2B) becomes a permanent, ongoing concern rather than a one-time migration cost.
Hybrid identity: when on-premises isn't going away yet
Many real organizations, including the acquired competitor in this scenario, still run an on-premises Active Directory that isn't disappearing overnight. Microsoft Entra Connect synchronizes on-premises identities into Entra ID, letting users authenticate consistently across both worlds during what's often a multi-year transition, not an instant cutover. Designing for this reality, rather than assuming a clean cloud-only slate, is a recurring AZ-305 theme: real architecture accounts for what already exists, not just what's ideal on a whiteboard.
Check your understanding
Five questions, all from this module. Get 4 out of 5 to mark it complete.
1. What made Devika's question fundamentally different from an AZ-104-level task?
2. What is the core difference AZ-305 tests compared to AZ-104?
3. What is a real cost of keeping two organizations' tenants separate after an acquisition?
4. What does Microsoft Entra Connect do?
5. What recurring theme does this module identify in AZ-305 design questions?