Microsoft SC-300 Identity and Access Administrator Exam Prep: Entra ID, Conditional Access and Governance
Revise the four SC-300 domains as of October 2026: user and hybrid identities, authentication and Conditional Access, workload identities and identity governance, then practise on exam-style scenarios.
What you will learn
- Describe the SC-300 exam and configure a Microsoft Entra tenant: roles, administrative units, domains, branding and tenant-wide settings.
- Create and manage users, groups, devices, licences and external identities, including cross-tenant access and synchronization.
- Implement and manage hybrid identity with Entra Connect Sync or Cloud Sync, PHS, PTA, seamless SSO, AD FS migration and Connect Health.
- Plan and manage user authentication: authentication methods, MFA settings, SSPR, Windows Hello for Business, password protection and session revocation.
- Design, test and troubleshoot Conditional Access, manage risk with ID Protection and deploy Global Secure Access.
- Plan workload identities, enterprise apps, app registrations, consent and Defender for Cloud Apps controls.
- Automate identity governance with entitlement management, access reviews and PIM, and monitor identity with logs, KQL and Identity Secure Score.
Modules
- The exam and the Microsoft Entra tenant
- Users, groups, devices, licences and external identities
- Hybrid identity
- User authentication
- Conditional Access, ID Protection and Global Secure Access
- Workload identities and applications
- Identity governance and monitoring
Course facts
- Level
- Exam preparation
- Estimated study time
- about 2 hours
- Final assessment
- 49 questions · Pass mark 70%
- Available in
- English
- Price
- Free. Optional verifiable certificate: $5
- Last updated
- Published by
- AMAADOR ACADEMY
Who this course is for
Microsoft 365 and Azure administrators, identity engineers, security engineers and helpdesk leads who run Microsoft Entra ID and are preparing for the Microsoft SC-300 exam.
Prerequisites
Working knowledge of Azure, Microsoft 365 and Active Directory Domain Services. Microsoft also expects familiarity with PowerShell and KQL. Hands-on practice in a free trial or developer tenant is strongly recommended alongside this course.
Course content
1. The exam and the Microsoft Entra tenant
These facts come from Microsoft Learn: the SC-300 study guide and the Identity and Access Administrator Associate certification page, both checked in November 2026. Microsoft updates the outline several times a year, so check both pages again before you book.
| Item | Confirmed fact |
|---|---|
| Exam | SC-300: Microsoft Identity and Access Administrator |
| Certification | Microsoft Certified: Identity and Access Administrator Associate (intermediate) |
| Skills outline | Skills measured as of 28 October 2026 (English version first) |
| Time | 100 minutes, proctored, may include interactive components |
| Passing score | 700 or greater (scaled score) |
| Renewal | Every 12 months, by a free online assessment on Microsoft Learn |
| Retake | 24 hours after a first failed attempt; longer waits after that |
The four skill areas
- Implement and manage user identities — 20–25%: tenant, roles, users, groups, devices, external users, hybrid identity
- Implement authentication and access management — 25–30% in the skills-at-a-glance list (the detailed section heading of the same guide says 20–25%): methods, MFA, SSPR, Conditional Access, ID Protection, Global Secure Access
- Plan and implement workload identities — 20–25%: managed identities, enterprise apps, app registrations, Defender for Cloud Apps
- Plan and automate identity governance — 20–25%: entitlement management, access reviews, PIM, monitoring
2. Users, groups, devices, licences and external identities
Cloud-only users are created in Entra ID; synchronized users come from AD DS and are edited on-premises. Groups carry access, licences and policies, so the group type matters.
| Group choice | Use it for |
|---|---|
| Security group | Access to apps and resources, Conditional Access targeting, licences |
| Microsoft 365 group | Collaboration: shared mailbox, calendar, Teams, SharePoint site |
| Assigned membership | Owners or admins add members by hand |
| Dynamic user or device membership | Rule on attributes, e.g. (user.department -eq "Sales"); needs Entra ID P1 |
| Role-assignable group | Holding Entra roles; the setting is chosen at creation and cannot be changed later |
A dynamic group cannot also have assigned members, and a role-assignable group cannot use dynamic membership. Only Privileged Role Administrators, Global Administrators and the group’s owners can manage membership of a role-assignable group, which stops a Groups Administrator or helpdesk admin from granting themselves a role.
Custom security attributes
Custom security attributes hold sensitive business data, such as project code or clearance level, on users, service principals and apps. They are grouped into attribute sets. Access is separate from directory roles: Attribute Definition Administrator creates sets and attributes, Attribute Assignment Administrator assigns values. Global Administrators do not get these rights by default. Attributes can drive filters in Conditional Access for apps and ABAC conditions in Azure.
3. Hybrid identity
Hybrid identity means one identity for AD DS and Entra ID. Two Microsoft tools synchronize users, groups and attributes from AD DS to the cloud.
| Question | Microsoft Entra Connect Sync | Microsoft Entra Cloud Sync |
|---|---|---|
| What is installed? | A full sync server with its own database and Synchronization Service Manager | Lightweight provisioning agents; configuration is held in the cloud |
| High availability | A second server in staging mode, switched manually | Several agents active at once |
| Disconnected forests (merger, acquisition) | Harder: needs network line of sight | Designed for it: an agent in each forest |
| Advanced needs | Complex custom sync rules, device writeback, PTA and federation set up from its wizard | Fewer options, but growing |
| Default schedule | Delta sync every 30 minutes | Every two minutes, scheduled by the cloud service |
Both can run in one tenant for different users, which is a common way to move gradually from Connect Sync to Cloud Sync. Microsoft recommends Cloud Sync when it covers your needs.
Before you sync
- Clean AD DS — fix duplicate or invalid UPNs and proxyAddresses (IdFix helps)
- Add UPN suffixes — the AD DS UPN suffix must match a verified custom domain, or users sign in with onmicrosoft.com
- Filter — scope by OU, group or attribute so service accounts and test objects stay on-premises
- Plan writeback — password writeback for SSPR, group writeback if needed
4. User authentication
All methods are now managed in one place: the Authentication methods policy. Microsoft retired management of methods in the legacy MFA and SSPR policies, so exam answers enable, scope and configure methods there, per method and per group.
| Method | Strength | Exam use |
|---|---|---|
| Passkeys (FIDO2) on a security key or in Microsoft Authenticator | Phishing-resistant, passwordless | Admins, high-value users; restrict models by AAGUID |
| Certificate-based authentication (CBA) | Phishing-resistant when bound as multifactor | Smart-card and PIV users, AD FS replacement |
| Windows Hello for Business | Phishing-resistant, passwordless | Users on their own Windows device |
| Microsoft Authenticator push or passwordless | Strong; number matching blocks blind approval | Most users |
| Temporary Access Pass (TAP) | Time-limited passcode | Onboarding a passwordless user, recovery after a lost key |
| SMS and voice | Weakest | Fallback only |
Certificate-based authentication in three settings
- Trust the PKI — upload root and issuing CAs with their CRL location
- Username binding — map a certificate field, such as the SAN principal name, to userPrincipalName or another user attribute
- Authentication binding — mark certificates as single-factor or multifactor, by issuer or policy OID
5. Conditional Access, ID Protection and Global Secure Access
Conditional Access (CA) is the Zero Trust policy engine of Entra ID: if these assignments and conditions match, then apply these controls. It needs Entra ID P1. All matching policies apply together, and a block always wins.
| Part | Options to know |
|---|---|
| Users | Users, groups, directory roles, guests and external users, workload identities (service principals) |
| Target resources | Cloud apps, user actions (register security information, register or join devices), authentication contexts |
| Network | Named locations: IP ranges or countries, trusted or not |
| Conditions | User risk, sign-in risk, device platforms, client apps (legacy authentication), filter for devices, authentication flows |
| Grant | Block, require MFA, require authentication strength, compliant device, hybrid joined device, app protection policy, password change, terms of use |
| Session | App enforced restrictions, Conditional Access App Control, sign-in frequency, persistent browser session, customize CAE, token protection |
Safe roll-out
- Start from a template — e.g. Require MFA for admins, Block legacy authentication
- Exclude emergency access accounts — from policies that could lock everyone out
- Report-only — watch the Report-only results in sign-in logs and the insights workbook
- What If — test a user, app, location and device before enabling
- Turn on — then troubleshoot with the Conditional Access tab of each sign-in log entry
6. Workload identities and applications
A workload identity is an identity used by software: an app, a script, a VM or a pipeline. Choosing the right one removes stored secrets.
| Identity | Use it when |
|---|---|
| System-assigned managed identity | One Azure resource needs access; the identity is created and deleted with the resource |
| User-assigned managed identity | Several resources share one identity, or the identity must exist before the resource (pre-granted access, scale sets) |
| Service principal of an app registration | Code outside Azure, multi-tenant apps, SaaS integrations; use a certificate or workload identity federation rather than a client secret |
| Group managed service account (gMSA) | Windows services on-premises in AD DS |
| User account | Avoid for automation: passwords expire, MFA breaks scripts |
Using a managed identity
- Create — enable system-assigned on the resource, or create a user-assigned identity and attach it
- Grant — give it an Azure RBAC role on the target, e.g. Key Vault Secrets User or Storage Blob Data Reader
- Call — code requests a token from the local endpoint; no secret is stored anywhere
App registrations
Registering an app creates an application object in its home tenant and a service principal in each tenant where it is used. Plan the supported account types (single tenant or multitenant), redirect URIs per platform (web, SPA, mobile), and credentials.
7. Identity governance and monitoring
Identity governance answers three questions: who has access, should they still have it, and who approved it. It needs Entra ID P2 or Microsoft Entra ID Governance licences.
Entitlement management
| Object | What it holds |
|---|---|
| Catalog | A container of resources (groups and Teams, enterprise apps, SharePoint sites) with its own catalog owners, so business units can delegate |
| Access package | A bundle of resource roles that users request as one, e.g. “Project Atlas: Team, SharePoint site, Jira app” |
| Policy | Who can request (internal users, connected organizations, any external user), approval stages, justification, expiry, required terms of use, recurring access reviews |
| Connected organization | A partner tenant or domain whose users may request packages |
For external users, entitlement management can manage the lifecycle: when a guest’s last assignment ends, block sign-in and then remove the guest after a set number of days. Terms of use are PDF documents users must accept, enforced through a Conditional Access grant control; you can require acceptance on every device and re-acceptance after a period.
Access reviews
- Scope — members of groups or Teams, users of an app, access package assignments, or Entra and Azure roles through PIM; optionally guests only, or inactive users
- Reviewers — group owners, managers, selected users, or self-review; multi-stage reviews add a second level
- Schedule — one-time or recurring, with a duration
- On completion — auto apply results; if reviewers don’t respond, choose no change, remove access, approve access or take recommendations
- Monitor — follow progress, send reminders, and when needed stop the review or respond manually as an admin
The full lesson continues in the interactive course on this page.
Sources and references
- Study guide for Exam SC-300: Microsoft Identity and Access Administrator
- Microsoft Certified: Identity and Access Administrator Associate
- Microsoft Entra ID documentation
- What is Conditional Access?
- What is Microsoft Entra Privileged Identity Management?
- Microsoft Entra ID Governance documentation
- Midnight Blizzard: guidance for responders on nation-state attack (Microsoft Threat Intelligence, 25 January 2024)
- Review of the Summer 2023 Microsoft Exchange Online Intrusion
Unofficial practice course. Not affiliated with, endorsed by or sponsored by Microsoft. SC-300, Microsoft Entra and Microsoft Defender are trademarks of their owner. All questions are original and are not real exam items. Check the current exam outline on Microsoft Learn before you book.
All courses · Cybersecurity and IT — Free courses, certificate $5 | AMAADOR ACADEMY