2.5. Reflection Checkpoint
Key Takeaways
- Pick identity objects by the deciding difference: mail contact vs mail user (sign-in?), external access vs guest access (account in your tenant?), distribution vs security vs Microsoft 365 group (mail, permission or workspace?).
- Reduce standing privilege: least-privilege roles, PIM eligible assignments (P2 for everyone involved, approvers included) and administrative units — restricted management AUs only at creation.
- Manage methods only in the Authentication methods policy; require strong methods with Conditional Access authentication strengths; build risk policies in Conditional Access (the legacy ID Protection policies retired 1 October 2026).
- Defender for Office 365: presets beat custom policies; Plan 1 (now in E3) gives real-time detections, while Plan 2 gives Threat Explorer, AIR and Attack simulation training.
- Purview: labels lock (EXTRACT decides Copilot), DLP guards (Copilot location: Custom template, its own policy), retention archives (policies only for Teams and Copilot), DSPM observes AI activity.
Connecting Forward
Phase 3 applies this foundation to AI services directly. You'll configure Copilot's tenant settings, data readiness and web search, then govern agents through Microsoft Entra Agent ID and Agent 365 — where Conditional Access, access packages, Purview and Defender reappear, aimed at a new kind of principal.
Self-Check Questions
- A guest from a partner company must open files in your team and must satisfy your MFA requirement without being prompted twice. Which collaboration model, and which cross-tenant setting, do you need?
- After a Copilot rollout, an auditor asks how you ensure Highly Confidential documents can't be summarized, even by people allowed to read them. Give two independent controls from this phase and explain how each one works.