Defending Entra ID

Every Entra ID Attack Found, Stopped and Proved Held.

Read how each attack on Entra ID works, find it in the sign-in and audit logs, stop it with the control that fits, prove the control held, and check Copilot's answer at every step, from stolen sessions to agents.

What you'll be able to do

✓Read a sign-in to its token and say whether a person did MFA or a token carried it
✓Find password attacks, adversary-in-the-middle theft, device code phishing and consent phishing in the logs, and close each route
✓Hold Conditional Access to what it claims: exclusions, report-only policies, device grants and the sign-ins no policy reached
✓Trace escalation through applications, roles, groups and agents, and say who could have granted what an attacker holds
✓Find what survives a response, from methods and consents to federation and the hybrid seam, and remove it
✓Contain users, applications and agents in one window, prove each step held, and write the report with exposure apart from loss
ARC407 | Included with Specialist, from $29/month | 12 modules and an orientation | 38–42 hours at your own pace | 40 CPE credits

Before you start

Prerequisites
None
Hands-on setup
None. You can complete the course without setting anything up.
Optional
A tenant of your own, for the admin center and Graph PowerShell steps

Course Syllabus

Every module and every lesson. The first three modules are open; the rest open on a click.

Download the full syllabus (PDF)

Phase 1: Foundations, Tokens and Sessions

Module 0Defending Entra IDCourse Preview

Module 0 of Defending Entra ID: what Entra ID is and why attackers want it, its users, groups, applications, devices and roles, how a sign-in works, how attacks on it have changed, what it gives a defender, working with Copilot and its agents, and the evidence a defender reads.

Show 10 lessonsHide lessons
  1. 0.10.1 What Entra ID Is and Why Attackers Want ItPreview
  2. 0.20.2 Users and GroupsPreview
  3. 0.30.3 Applications and Service PrincipalsPreview
  4. 0.40.4 DevicesPreview
  5. 0.50.5 Roles and Privileged AccessPreview
  6. 0.60.6 How a Sign-In WorksPreview
  7. 0.70.7 How Attacks on Entra ID Have ChangedPreview
  8. 0.80.8 What Entra ID Gives a DefenderPreview
  9. 0.90.9 Working With Copilot and Entra's AgentsPreview
  10. 0.100.10 The Evidence a Defender ReadsPreview
Module 1Tokens, Sessions and Protocols

Module 1 of Defending Entra ID: OAuth 2.0 and OpenID Connect, the flows and their traces, the claims inside a token, lifetimes, browser sessions, the PRT, session controls, and following a session across the sign-in logs.

Show 8 lessonsHide lessons
  1. 1.11.1 OAuth 2.0 and OpenID Connect in Entra ID
  2. 1.21.2 The Flows and Their Traces
  3. 1.31.3 Inside a Token
  4. 1.41.4 Lifetimes and the Policies That Set Them
  5. 1.51.5 Browser Sessions
  6. 1.61.6 The Primary Refresh Token in Depth
  7. 1.71.7 Session Controls in Force
  8. 1.81.8 Following a Session Across the Logs

Phase 2: Attacks on Sign-in

Module 2Password Attacks and MFA Abuse

Module 2 of Defending Entra ID: password spray, stuffing and brute force, smart lockout and password protection, finding a spray in the logs, MFA methods and strengths, push fatigue, registration and recovery abuse, Identity Protection, and the response.

Show 8 lessonsHide lessons
  1. 2.12.1 How Passwords Are Attacked
  2. 2.22.2 Smart Lockout and Password Protection
  3. 2.32.3 Finding a Spray in the Logs
  4. 2.42.4 MFA Methods and Their Strength
  5. 2.52.5 MFA Fatigue and Push Abuse
  6. 2.62.6 Abusing Registration and Recovery
  7. 2.72.7 Identity Protection for Password and MFA Attacks
  8. 2.82.8 Responding to a Compromised Password
Module 3Conditional Access as Defense

Module 3 of Defending Entra ID: how Conditional Access evaluates a sign-in, the baseline set, exclusions and emergency access, device and location conditions, resource targeting and its gaps, changing policy safely, and finding sign-ins a policy missed.

Show 8 lessonsHide lessons
  1. 3.13.1 How a Policy Is Evaluated
  2. 3.23.2 The Baseline Set
  3. 3.33.3 Exclusions and Emergency Access
  4. 3.43.4 Device-Based Access
  5. 3.53.5 Locations and Their Limits
  6. 3.63.6 Resources, Apps and Gaps
  7. 3.73.7 Changing Policy Safely
  8. 3.83.8 Finding Who a Policy Missed
Module 4Phishing for Sessions

Module 4 of Defending Entra ID: adversary-in-the-middle phishing and how to find it, phishing-resistant methods, device code phishing, consent phishing, consent settings and AI apps, and responding to a phished session or consent.

Show 8 lessonsHide lessons
  1. 4.14.1 How Adversary-in-the-Middle Works
  2. 4.24.2 Finding an AiTM Sign-in
  3. 4.34.3 Phishing-Resistant Methods
  4. 4.44.4 Device Code Phishing
  5. 4.54.5 Consent Phishing
  6. 4.64.6 Consent Settings and AI Apps
  7. 4.74.7 Responding to Phished Sessions and Consents
  8. 4.84.8 A Phishing Case End to End
Module 5Token Theft and Replay

Module 5 of Defending Entra ID: how session cookies, refresh tokens and the PRT are stolen, finding a replayed session, ID Protection token detections, the PRT under attack, token protection, CAE in a theft case, sessions Entra cannot end, and a case end to end.

Show 8 lessonsHide lessons
  1. 5.15.1 How Tokens Are Stolen
  2. 5.25.2 Finding a Replayed Session
  3. 5.35.3 Token Detections in ID Protection
  4. 5.45.4 The PRT Under Attack
  5. 5.55.5 Token Protection
  6. 5.65.6 CAE in a Theft Case
  7. 5.75.7 Sessions Entra Cannot End
  8. 5.85.8 A Token Theft Case End to End

Phase 3: Escalation and Agents

Module 6Escalation Through Applications

Module 6 of Defending Entra ID: how applications escalate, adding a credential, creating an app and granting it, what an app did, a leaked workload credential, workload identity detections, governing ownership and permissions, and a case end to end.

Show 8 lessonsHide lessons
  1. 6.16.1 How Applications Escalate
  2. 6.26.2 Adding a Credential
  3. 6.36.3 Creating an App and Granting It
  4. 6.46.4 What the App Did
  5. 6.56.5 A Leaked Workload Credential
  6. 6.66.6 Detections for Workload Identities
  7. 6.76.7 Governing Ownership and Permissions
  8. 6.86.8 An Application Escalation Case End to End
Module 7Escalation Through Roles and Groups

Module 7 of Defending Entra ID: how roles escalate, reading role assignments, assignments outside PIM, groups as a route, PIM settings that hold, restricting who manages whom, from Entra into Azure, and a case end to end.

Show 8 lessonsHide lessons
  1. 7.17.1 How Roles Escalate
  2. 7.27.2 Reading Role Assignments
  3. 7.37.3 Assignments Outside PIM
  4. 7.47.4 Groups as a Route
  5. 7.57.5 PIM Settings That Hold
  6. 7.67.6 Restricting Who Can Manage Whom
  7. 7.77.7 From Entra into Azure
  8. 7.87.8 A Role Escalation Case End to End
Module 8Agents as Identities

Module 8 of Defending Entra ID: what an agent is in Entra, the agent inventory, what an agent can reach, reading agent activity, a blueprint credential added and used, detecting a risky agent, controls for agents, and a case end to end.

Show 8 lessonsHide lessons
  1. 8.18.1 What an Agent Is in Entra
  2. 8.28.2 The Agent Inventory
  3. 8.38.3 What an Agent Can Reach
  4. 8.48.4 Reading Agent Activity
  5. 8.58.5 A Blueprint Credential Added and Used
  6. 8.68.6 Detecting a Risky Agent
  7. 8.78.7 Controls for Agents
  8. 8.88.8 An Agent Case End to End

Phase 4: Persistence and the Hybrid Seam

Module 9Persistence and Evasion

Module 9 of Defending Entra ID: what survives a response, methods as persistence, federation backdoors, cross-tenant access and sync, turning off the lights, the agents' own audit trail, controls for the control plane, and the persistence sweep.

Show 8 lessonsHide lessons
  1. 9.19.1 What Survives a Response
  2. 9.29.2 Methods as Persistence
  3. 9.39.3 Federation Backdoors
  4. 9.49.4 Cross-Tenant Access and Synchronization
  5. 9.59.5 Turning Off the Lights
  6. 9.69.6 The Agents' Own Audit Trail
  7. 9.79.7 Controls for the Control Plane
  8. 9.89.8 The Persistence Sweep
Module 10The Hybrid Seam

Module 10 of Defending Entra ID: where the directories meet, the synchronization accounts, password hash sync, pass-through authentication agents, seamless SSO, soft and hard match, cloud-only administrators, and a hybrid case end to end.

Show 8 lessonsHide lessons
  1. 10.110.1 Where the Directories Meet
  2. 10.210.2 The Synchronization Accounts
  3. 10.310.3 Password Hash Sync
  4. 10.410.4 Pass-Through Authentication Agents
  5. 10.510.5 Seamless SSO
  6. 10.610.6 Soft and Hard Match
  7. 10.710.7 Cloud-Only Administrators
  8. 10.810.8 A Hybrid Case End to End

Phase 5: Response and Capstone

Module 11Response

Module 11 of Defending Entra ID: the response order, the Identity Risk Management Agent, containing users, containing applications and agents, rotating secrets, recovering configuration, proving the response held, and a response end to end.

Show 8 lessonsHide lessons
  1. 11.111.1 The Response Order
  2. 11.211.2 The Identity Risk Management Agent
  3. 11.311.3 Containing Users
  4. 11.411.4 Containing Applications and Agents
  5. 11.511.5 Rotating Secrets
  6. 11.611.6 Recovering Configuration
  7. 11.711.7 Proving It Held
  8. 11.811.8 A Response End to End
Module 12Capstone

Module 12 of Defending Entra ID, the capstone: one intrusion from the first alert through the edge, the identity, the cloud backdoor and the agent, to its scope, response and report.

Show 8 lessonsHide lessons
  1. 12.112.1 The First Alert
  2. 12.212.2 The Edge and the Credential
  3. 12.312.3 The Identity
  4. 12.412.4 The Cloud Backdoor
  5. 12.512.5 The Agent
  6. 12.612.6 Scope
  7. 12.712.7 The Response
  8. 12.812.8 The Report

Course Completion

CompletionCourse Exam

Defending Entra ID end-of-course exam: 40 questions in four parts, from tokens and sessions to response, ending on a case study.

Show 1 lessonHide lessons
  1. 1Course Completion. Defending Entra ID

Course overview

Entra ID decides who can reach Microsoft 365, Azure and every application connected to it, so an attacker who holds one of its identities reaches what that identity reaches, often with multifactor authentication already satisfied. This course follows each attack on it to the evidence it leaves, the control that stops it, and the record that proves the control held.

Module 0 sets out the tenant, how a sign-in becomes a token, and the evidence. Modules 1 to 5 cover sessions and the attacks on sign-in: tokens and protocols, password attacks and MFA abuse, Conditional Access as defense, phishing for sessions, and token theft and replay. Modules 6 to 8 follow escalation through applications, roles and groups, and agents. Modules 9 and 10 find what survives a response and where the hybrid seam lets on-premises reach the cloud. Module 11 is the response, and Module 12 a capstone intrusion worked from its first alert to its report.

How this course works

Portal, PowerShell and the record. Each of the 106 lessons shows the admin center and the Microsoft Graph PowerShell for the task it teaches, and proves each finding from the sign-in and audit records. Queries run in the page against the SecOps Range, a month of a tenant's records with real attacks in it. Every product behavior a lesson relies on comes from a Microsoft page it names, with the date it was read.

Copilot, checked. Every lesson delegates work to Copilot and checks its answer against the record, and every practice scenario asks which of an assistant's claims fails and on what. The course treats an assistant as a fast colleague whose work is verified before it becomes a finding.

One case, end to end. The capstone works one intrusion across the edge, an identity, an attacker-built application and an agent: its scope widened from an address to its range, a response in one window, every step proved, and a report with exposure kept apart from loss.

What you will learn

✓ Read a sign-in to its token and say whether a person did MFA or a token carried it
✓ Find password attacks, adversary-in-the-middle theft, device code phishing and consent phishing in the logs, and close each route
✓ Hold Conditional Access to what it claims: exclusions, report-only policies, device grants and the sign-ins no policy reached
✓ Trace escalation through applications, roles, groups and agents, and say who could have granted what an attacker holds
✓ Find what survives a response, from methods and consents to federation and the hybrid seam, and remove it
✓ Contain users, applications and agents in one window, prove each step held, and write the report with exposure apart from loss

Who this course is for

Security engineers, identity administrators and SOC analysts who defend a Microsoft tenant and respond to incidents that run through its identities. You know your way around Microsoft 365 administration; this isn't a beginner course. Entra ID Identity and Access Management covers designing the directory, its access and its governance, and pairs well with this one.

What this course does not cover: designing Conditional Access and identity governance from scratch (Entra ID Identity and Access Management), attacks on Active Directory itself (Defending Active Directory), endpoint forensics on the hosts an intrusion touches, and building custom Copilot agents.

Things you need to know

What are the prerequisites?

Working familiarity with Microsoft 365 administration: users, groups, roles and the admin centers. Module 0 introduces every Entra ID term the course uses. Some KQL helps, and each query is explained where it appears.

What do I need?

A browser for the lessons, the queries, the practice scenarios and the exam. A tenant of your own helps for the admin center and Graph PowerShell steps, with Entra ID P2 for the ID Protection and PIM lessons, but every finding can be made on the SecOps Range without one.

What will I be able to do after this course?

You'll be able to defend Entra ID from its record: find an attack in the sign-in and audit logs, stop it with the control that fits, contain every foothold in one window, prove each step held, and write the incident report with what was exposed kept apart from what was taken.

Usage rights and disclaimer

Course materials: Licensed for individual professional development. You may use the queries, scripts and procedures in your own environment. You may not redistribute course content or share account credentials.

Scripts and procedures: Provided as-is. Containment steps act on real accounts, applications and devices; test them in a test tenant first, and confirm every target before you act on it.

A fictional tenant and documentation: The SecOps Range and the examples are fictional and built for teaching. Portal paths, limits, licenses and preview features change; each lesson names the Microsoft page it read and the date.

COURSE ASSESSMENT

End of Course Exam

Complete the course, then answer forty questions, from tokens and sessions to the response, ending on a case study, in 90 minutes. Pass mark: 70. Earn your certificate with CPE credits.

40questions
90minutes
100points
Take End of Course Exam

Answers are checked on the server. Certificate issued on pass.