SC-300: Microsoft Identity and Access Administrator — 30-Day Study Program
- Target exam: SC-300 (skills measured as of 27 April 2026), leading to the Identity and Access Administrator Associate certification
- Time budget: ~2 h/weekday, ~4 h/weekend day ≈ 75 h total
- Assumed baseline: Strong PowerShell, working knowledge of AD DS, M365 admin, basic KQL
Every topic below links to the relevant Microsoft Learn documentation. Read the linked page, then do the lab — the links are the study material, not a bibliography.
Domain weightings (drive your effort allocation)
| Domain | Weight | Days allocated |
|---|---|---|
| 1. Implement and manage user identities | 20–25% | Days 1–7 |
| 2. Implement authentication and access management | 25–30% | Days 8–15 |
| 3. Plan and implement workload identities | 20–25% | Days 16–21 |
| 4. Plan and automate identity governance | 20–25% | Days 22–27 |
| Review, practice exams, remediation | — | Days 28–30 |
Domain 2 gets the most days — it carries the highest weight and Conditional Access is the most heavily scenario-tested area on this exam.
Day 0 (before you start): Lab environment
You cannot pass SC-300 on reading alone. Build a lab:
- Tenant: Create a fresh Entra tenant via the Entra admin center, or use an existing dev/test tenant. The old free M365 Developer Program is restricted; if you have a Visual Studio Enterprise subscription you get a dev tenant through it. Otherwise a free Entra tenant + M365 Business Premium trial works. (What is Microsoft Entra?)
- Licensing: Activate the Microsoft Entra ID P2 trial (or Entra Suite trial if available) — mandatory for PIM, ID Protection, access reviews, entitlement management. (Licensing fundamentals)
- Azure subscription: Free trial or PAYG with spending cap — needed for managed identities, PIM for Azure resources, Log Analytics, diagnostic settings.
- Hybrid lab (optional but recommended): One Windows Server VM running AD DS + Entra Connect. Hyper-V locally or a small Azure VM (deallocate when not in use).
- Tooling:
Install-Module Microsoft.Graph; install the Global Secure Access client on a test VM later in Week 2. - Break-glass account: Create one on day 0, exclude it from every CA policy you build. This is both lab hygiene and an exam objective.
Daily structure (repeat every study day)
- Block A (60–90 min): MS Learn modules + docs for the day's topics
- Block B (45–60 min): Hands-on lab in your tenant — do everything in the portal and in Graph PowerShell where applicable
- Block C (15 min): 10–15 practice questions on today's topic; log wrong answers in an error journal (topic, why wrong, correct concept)
The error journal is your Day 28–30 remediation input. Don't skip it.
WEEK 1 — Domain 1: User identities (Days 1–7)
Day 1 — Tenant, roles, administrative units
- Configure tenant properties, user/group/device settings, company branding, custom domains (Entra ID + M365 verification flow)
- Built-in roles vs custom Entra roles; role assignable scopes; assign roles and evaluate effective permissions
- Administrative units: when to use, restricted management AUs, scoped role assignments
- Lab: Create a custom role with
microsoft.directory/users/password/update; create an AU, scope a Helpdesk Admin to it; verify effective permissions withGet-MgRoleManagementDirectoryRoleAssignment
Day 2 — Users, groups, custom security attributes
- User types (member/guest), group types (security/M365), membership types (assigned/dynamic), group nesting limits, group expiration
- Dynamic membership rule syntax (memorize operators:
-eq,-contains,-match,-any), plusmemberOfrules - Custom security attributes: attribute sets, permissions model (who can define vs assign)
- Lab: Build dynamic groups from
departmentanduserType; define an attribute set + attribute, assign to users, filter with Graph
Day 3 — Bulk operations, licensing, devices
- Bulk create/invite/delete via admin center CSV; same via
New-MgUserloops and Graph batch requests - Group-based licensing (now managed from the M365 admin center), license conflict/error states,
Set-MgUserLicenseand PowerShell/Graph licensing examples - Device identity: Entra registered vs Entra joined vs hybrid joined — know the decision matrix cold
- Lab: Bulk-create 20 users from CSV via PowerShell with error handling; assign licenses via group; join a test VM to Entra
Day 4 — External identities (B2B)
- External collaboration settings, guest invite restrictions, guest user access levels
- Invite flow (individual, bulk, self-service sign-up), guest lifecycle
- Cross-tenant access settings: inbound/outbound trust, B2B collaboration vs B2B direct connect, trust settings for MFA/compliant devices
- Lab: Invite a guest from a personal tenant; configure cross-tenant access to trust home-tenant MFA; test the difference
Day 5 — Cross-tenant sync, external IdPs
- Cross-tenant synchronization: configuration, provisioning scope, attribute mapping — know it's built on the provisioning engine
- Federation with SAML/WS-Fed IdPs, Google federation for B2B
- Lab: If you have two tenants, configure cross-tenant sync; otherwise walk the full config in the portal and screenshot each blade
Day 6 — Hybrid identity I
- Entra Connect Sync vs Cloud Sync — read the decision guide and feature comparison (group writeback, device writeback, filtering options, agent architecture). Exam loves "which sync tool for scenario X"
- PHS vs PTA vs federation: security posture, DR characteristics, leaked-credential detection (PHS only) — the choose an authentication method guide is the exam's mental model
- Seamless SSO mechanics (Kerberos ticket to AZUREADSSOACC)
- Lab: If hybrid lab exists: install Entra Connect with PHS + express settings, then enable PTA staged rollout. Otherwise: John Savill's hybrid identity video + docs walkthrough
Day 7 — Hybrid identity II + Week 1 review
- Migrate from AD FS: staged rollout, decommission path
- Entra Connect Health: agents, alerts, sync insights
- Review: 30–40 mixed Domain 1 questions; update error journal
- Checkpoint: Can you explain PHS vs PTA vs federation trade-offs, AU vs custom role use cases, and cross-tenant access settings without notes? If not, re-do before Week 2.
WEEK 2 — Domain 2: Authentication and access management (Days 8–15)
Day 8 — Authentication methods
- Authentication methods policy (the modern one — legacy MFA/SSPR policies are being retired; know the migration)
- Methods: FIDO2 passkeys, Microsoft Authenticator (number matching, additional context), certificate-based auth (CBA), Temporary Access Pass, OATH tokens
- Authentication strengths (built-in + custom)
- Lab: Enable TAP, onboard a test user passwordlessly with a passkey; create a custom authentication strength requiring phishing-resistant MFA
Day 9 — MFA, SSPR, WHfB, password protection
- Tenant-wide MFA settings, per-user MFA vs CA-based MFA (know why per-user is legacy)
- SSPR: registration and gates, writeback requirements for hybrid
- Windows Hello for Business deployment models (cloud Kerberos trust is the modern answer)
- Entra password protection: global/custom banned lists, on-prem agent architecture
- Entra Kerberos for hybrid (Azure Files scenarios), account disable +
Revoke-MgUserSignInSession - Lab: Configure SSPR for a pilot group; configure banned password list; revoke a session and observe token behaviour
Days 10–11 — Conditional Access (two full days — highest-yield topic)
- Policy anatomy: assignments (users, target resources, network, conditions) → grant/session controls. Start from the CA overview
- Named locations (IP ranges, countries, trusted locations — see the block-by-location policy), device platforms, client apps, filter for devices
- Grant controls: MFA, authentication strength, compliant device, hybrid joined, ToU, AND/OR logic
- Session controls: sign-in frequency and persistent browser, CAE strict enforcement, app-enforced restrictions, CA App Control
- Authentication context (tie-in to SharePoint sensitivity labels and PIM; developer guidance), protected actions
- Report-only mode, What If tool, CA insights workbook, policy templates and common policies
- Lab: Build: (1) require phishing-resistant MFA for admins, (2) block legacy auth, (3) require compliant device for M365, (4) authentication context + protected action for CA policy management itself. Test each with What If, deploy report-only first, review sign-in log CA tab
Day 12 — Entra ID Protection
- ID Protection overview: user risk vs sign-in risk; risk detections (leaked creds, impossible travel, token anomalies)
- Risk-based CA policies vs legacy ID Protection policies (Microsoft's guidance: use CA)
- Remediation: self-remediation via MFA/password change, admin dismiss/confirm compromise — and how to investigate risk
- MFA registration campaign, risky workload identities (requires Workload ID Premium)
- Lab: Create user-risk and sign-in-risk CA policies; simulate risk with Tor browser sign-in; investigate and remediate in the Risky users blade
Day 13 — Global Secure Access
- Architecture: SSE, traffic forwarding profiles (Private Access, Internet Access, M365)
- GSA client deployment, Private Access app segments vs Quick Access, Entra Private Network Connector
- Internet Access web content filtering, universal CA / compliant network check
- Lab: Deploy GSA client on a test VM, enable the M365 profile, create a Private Access app to an internal RDP/SMB target if you have the hybrid lab
Day 14 — Domain 2 consolidation lab
- Full scenario build: zero-trust baseline (block legacy auth, require MFA all users, phishing-resistant for admins, risk policies, compliant device for sensitive apps, break-glass exclusions everywhere)
- Troubleshoot deliberately: lock a test user out, diagnose via sign-in logs → CA tab
Day 15 — Domain 2 review
- 40–50 mixed questions on auth + CA + ID Protection + GSA; error journal
- Checkpoint: Given a scenario table (user, location, device, app), can you predict which CA policies apply and the resulting access decision? This is the core exam skill — the CA deployment planning guide is good revision.
WEEK 3 — Domain 3: Workload identities (Days 16–21)
Day 16 — Identity types for workloads
- Workload identities overview — decision matrix: system-assigned MI vs user-assigned MI (managed identities, best-practice guidance) vs service principal vs user account vs (group) managed service accounts
- Lab: Create both MI types; assign to a VM/Function; use the VM's MI to reach Azure services — read a Key Vault secret and list a storage container (
Connect-AzAccount -Identity)
Day 17 — Enterprise applications
- App registration vs enterprise application (application object vs service principal) — this distinction underpins half of Domain 3. See also what is application management
- Tenant-level settings (user consent settings, admin consent workflow), app-level settings (assignment required, visibility)
- Roles: Application Administrator vs Cloud Application Administrator vs owner
- App collections (My Apps), assigning users/groups/app roles
- Lab: Add a gallery SaaS app, configure SAML SSO with claims customization, require assignment, assign via group
Day 18 — Application Proxy + SaaS integration
- App Proxy architecture: connectors, connector groups, pre-authentication (Entra vs passthrough), KCD for SSO to IWA apps
- Header-based and SAML SSO via App Proxy — SSO options compared
- SCIM provisioning to SaaS apps: attribute mappings, scoping filters, provisioning logs
- Lab: If hybrid lab: publish an internal IIS site via App Proxy with Entra pre-auth + CA. Configure SCIM provisioning on a gallery app (many offer free dev tenants)
Day 19 — App registrations
- Register an app: single vs multi-tenant, redirect URIs, certificates vs secrets (and why certs win), federated credentials
- API permissions: delegated vs application — know this cold, including consent implications
- Expose an API, app roles, scopes; admin consent grant flow
- Lab: Register an app, add delegated
User.Read+ applicationUser.Read.All, grant admin consent, define an app role, call Graph with the client credentials flow from PowerShell
Day 20 — Defender for Cloud Apps
- Cloud discovery: log upload, Defender for Endpoint integration, snapshot reports; sanction/unsanction; cloud app catalog + risk scores. Start at the product overview
- App connectors, Conditional Access App Control (session policies: block download, monitor), access policies
- OAuth app policies (risky consent detection, app governance)
- Lab: Onboard the M365 connector, create a session policy blocking downloads on unmanaged devices via CA App Control, review discovered apps
Day 21 — Domain 3 review
- 40 questions; error journal
- Checkpoint: Delegated vs application permissions, app object vs SP, MI selection matrix, App Proxy pre-auth modes — all explainable without notes.
WEEK 4 — Domain 4: Identity governance (Days 22–27)
Day 22 — Entitlement management I
- Entitlement management overview: catalogs (resources, owners), access packages (policies, questions, approvals, lifecycle)
- Multiple policies per package (internal vs connected org vs any external), and approval settings
- Lab: Build a catalog with a group + app, create an access package with two-stage approval and 90-day expiry, request it as a test user
Day 23 — Entitlement management II
- Connected organizations, external user lifecycle (block sign-in/delete after package expiry)
- Terms of use: per-app via CA, per-access-package, re-acceptance
- Lifecycle workflows if time permits (joiner/mover/leaver — appears in newer question pools)
- Lab: Create a ToU, attach to a CA policy and an access package; configure external user lifecycle settings
Day 24 — Access reviews
- Access reviews overview — review targets: groups, apps, access packages, PIM roles; reviewer types (self, manager, selected)
- Multi-stage reviews, auto-apply, "if reviewer doesn't respond" behaviour, inactive user recommendations
- Lab: Create a quarterly guest review on a group with auto-remove on deny; manually respond and apply the results
Day 25 — PIM
- PIM overview: eligible vs active, permanent vs time-bound; role settings (MFA/auth context, justification, approval, ticket, max duration)
- PIM for Entra roles, PIM for Azure resources (management group/subscription/RG scope), PIM for Groups (and why: to gate app/AD roles via group membership)
- Approval flow, audit history, alerts (e.g., roles assigned outside PIM)
- Break-glass accounts: exclusions, monitoring for their use
- Lab: Make a user eligible for User Administrator with approval + authentication context; activate it; review audit history; configure PIM for a group
Day 26 — Monitoring, logs, KQL
- Sign-in logs (interactive/non-interactive/SP/MI), audit logs, provisioning logs — retention limits per licence
- Diagnostic settings → Log Analytics / storage / Event Hubs
- KQL against
SigninLogs,AuditLogs: filter by CA result, risk, app (how to analyse activity logs, log query basics). Practice: failed sign-ins by user last 7 days; CA failures by policy - Workbooks (CA insights, sign-in analysis), usage & insights, Identity Secure Score (improvement actions, score mechanics)
- Lab: Route logs to a Log Analytics workspace, write 5 KQL queries, pin one to a workbook, action one Secure Score recommendation
Day 27 — Domain 4 review
- 40 questions; error journal
- Checkpoint: Entitlement management object model (catalog → package → policy), access review outcomes, PIM settings matrix, which log answers which question.
Days 28–30 — Full review and exam readiness
Day 28 — Full practice exam #1
- Free official Microsoft Practice Assessment, linked from the SC-300 certification page — do it timed, closed-book
- Score by domain; spend the rest of the day re-studying your two weakest objective groups using the error journal
Day 29 — Full practice exam #2 + gap remediation
- Second full-length attempt (MeasureUp official practice test is the highest-fidelity paid option)
- Target: consistently ≥80% before sitting the real exam (pass mark is 700 scaled, roughly ~70%)
- Re-lab anything you got wrong that has a hands-on component — muscle memory beats re-reading
Day 30 — Light review + logistics
- Skim error journal end-to-end; re-read the CA and PIM settings matrices
- Review exam mechanics: ~40–60 questions, case studies, possible lab-style items; you get Microsoft Learn access during the exam — practice searching Learn quickly for exact settings names, don't plan to rely on it
- Book/sit the exam. Online proctored or Pearson VUE centre (Albury–Wodonga: nearest centres may be Wagga/Melbourne — online proctoring is usually the practical option; check room requirements)
Resource stack (in priority order)
- Microsoft Learn — SC-300 official learning paths (free, maps 1:1 to objectives; follow the course SC-300T00 outline)
- Your lab tenant — non-negotiable
- Microsoft Learn Practice Assessment (free, official)
- John Savill's SC-300 Study Cram (YouTube) — watch at Week 4 start as consolidation, not as primary learning
- MeasureUp SC-300 — optional paid practice exam
- Microsoft Graph PowerShell docs — do every lab task twice: portal, then PowerShell
Exam-technique notes
- Scenario questions usually hinge on least privilege and lowest licence that satisfies the requirement — when two answers both work, pick the cheaper/lesser-privileged one
- "Minimize administrative effort" = the most managed/automated option (Cloud Sync over Connect where features allow, dynamic groups over assigned, group-based licensing, access packages over manual assignment)
- Know licence gates: P1 (CA, group-based licensing basics), P2 (PIM, ID Protection, access reviews, entitlement management), Workload ID Premium (workload identity risk, CA for workload identities), Entra Suite (GSA Private/Internet Access + governance bundle)
- Case studies: read the requirements first, then mine the environment description only for what each question needs