Contoso architecture risk review
Contoso Global Manufacturing needs a senior platform architect to assess tenant sprawl, legacy Exchange hybrid, weak governance, failed sync history, and acquisition risk.
Business context
Learners operate from a real enterprise job-description perspective: platform owner, standards author, troubleshooter, migration planner, and executive advisor.
Technical objective
Review the fictional enterprise case, identify architectural risks, and build the initial decision backlog for the bootcamp.
Student instructions
- 1Open the Contoso case study and topology map.
- 2Classify risks across identity, messaging, collaboration, endpoint, compliance, operations, and M&A integration.
- 3Separate admin tasks from engineer and architect responsibilities.
- 4Create the first architecture decision log entry.
- 5Run Check My Work for risk coverage and handoff clarity.
Troubleshooting
- If the risk list is shallow, map every business symptom to a platform owner and technical control.
- If decisions are tactical only, add architectural tradeoffs and operating-model impact.
Cleanup
- Export the risk register into the student workbook.
- Keep the decision log for later capstone reuse.
Provisioning readiness
Click Launch lab to start the provisioning flow and watch each stage complete.
- Request accepted
- Capacity reserved
- Templates queued
- Validation running
- Workspace ready
Required templates
- Microsoft 365 simulated tenant layer - defined
Validation checks
- Simulated M365 tenant ready: The simulated tenant layer exposes users, groups, licensing, Exchange, Teams, SharePoint, OneDrive, Intune, compliance, and service-health scenarios.
- Architecture package complete: Final package includes current state, risk register, target architecture, identity design, governance model, migration roadmap, monitoring model, RCA, and executive summary.
Expected result
The learner has a risk register, stakeholder map, and decision backlog ready for instructor or AI-tutor review.
Reset policy: Workbook and simulated tenant state can be reset per module. Teardown policy: Simulated tenant data expires with the course lab TTL.