This module moves from principle recognition to applied mapping. You'll review the specific native Microsoft 365 controls that implement each Zero Trust principle, then complete a mapping worksheet that pairs each principle with its corresponding control, mirroring the job task directly and producing a reference artifact you can use in future security conversations.

This module introduces the six cloud-only Microsoft 365 authentication methods as a structured decision framework. You'll learn what each method is, whether it is passwordless, which platforms it supports, and the key distinctions that determine when each method is the right choice, building the comparison foundation.

This module moves from method recognition to applied recommendation. You'll watch a realistic service-desk scenario walk through the decision framework across three distinct user profiles, then complete a written recommendation activity where you select and justify the appropriate authentication method for a new set of user profiles—mirroring the job task directly.

This module establishes the conceptual foundation for Conditional Access policy configuration. You'll learn what Conditional Access is, how Named Locations define the geographic boundaries a policy enforces, and how the policy evaluation logic determines whether a sign-in is allowed or blocked, building the understanding you need before configuring any policy.

This module moves from policy logic to applied configuration. You'll review the step-by-step sequence for creating the Named Location approved list and the "Block-Non-Trusted-Regions" Conditional Access policy in the Microsoft Entra admin center, then follow the full configuration and testing sequence, documenting the outcome at each step and confirming the policy blocks access from an unapproved country as expected.

This module introduces the Identity Secure Score—what it measures, how it's calculated, and how to read the dashboard. You'll learn to navigate the key sections of the Secure Score view, understand what each metric represents, and recognize the difference between a recommendation that's eligible for prioritization and one that should be filtered out before you ever weigh impact and effort.

This module moves from dashboard literacy to applied analysis. You'll watch a realistic walkthrough of the prioritization process using a provided dashboard scenario, then complete a written analysis activity where you interpret a dashboard snapshot, apply the high-impact, low-effort framework, and produce a prioritized quick-wins submission—mirroring the job task of recording the top three quick wins and submitting them to a team lead.

This module introduces Privileged Identity Management and the just-in-time access model it enforces. You'll learn what PIM is, why standing admin privileges create a security risk, how JIT access reduces that risk, and how the MFA approval requirement adds a verification layer before elevation is granted.

This module moves from PIM concepts to applied configuration. You'll review the step-by-step sequence for enabling PIM, assigning the Helpdesk Admin role as an eligible assignment, and configuring the activation settings—then follow the full activation flow to confirm MFA prompts before elevation is granted. A walkthrough-based activity is provided for all learners; an optional live practice path is available for learners with trial access to an Entra ID P2 or Microsoft 365 E5 tenant.

In this project, you'll produce a Security Posture Assessment, a structured analysis document that evaluates the identity and security posture of a simulated Microsoft 365 tenant, identifies prioritized findings, and documents escalation recommendations for the identity/security team. The assessment integrates the Zero-Trust mapping, authentication method analysis, Conditional Access review, Secure Score prioritization, and PIM awareness skills built across the course into a single professional deliverable that mirrors the kind of security review a junior Microsoft 365 admin would submit to an identity/security team lead. All findings are documented as observations and escalation recommendations, not configuration decisions or policy actions the learner owns independently.