The SC-300 blueprint is split across 4 domains. Weights are the official share of the exam; see the official exam guide for the authoritative breakdown.
What you must be able to do. Choose and configure the correct Microsoft Entra identity, group, licensing, external-collaboration, or hybrid-synchronisation mechanism that meets a stated tenant requirement.
In one sentenceThe foundation layer: tenant and role configuration, users, groups, licensing, B2B external identities, and the right hybrid synchronisation technology.
Recall check: answer these from memory first
- Which synchronisation technology fits disconnected multi-forest Active Directory with no full sync server per forest, and why?
- How does group-based licensing change what happens when a user joins or leaves the group?
- When a B2B guest's domain has no Microsoft Entra tenant or Microsoft account, which authentication method is the default?
What it tests. Whether you can stand up and run the identity foundation in a Microsoft Entra tenant: configuring the tenant, roles, administrative units, domains, and settings; creating and managing users, groups, devices, and licences including group-based licensing; bringing in external users through Microsoft Entra B2B collaboration, cross-tenant access, and external identity providers; and wiring hybrid identity with the right synchronisation technology between Active Directory and Microsoft Entra ID.
How to study it. Work in the Microsoft Entra admin centre rather than reading. Create dynamic and assigned groups, attach a licence to a group and watch it flow to members, and scope a role to an administrative unit. Build a B2B invitation and observe the email one-time passcode fallback. Compare Microsoft Entra Cloud Sync and Microsoft Entra Connect Sync against a multi-forest scenario, and trace the passwordless on-premises path through Microsoft Entra Kerberos. Read the docs on cross-tenant synchronisation and on migrating from AD FS to password hash synchronisation.
Easy to confuse
- Microsoft Entra Cloud Sync versus Microsoft Entra Connect Sync. Cloud Sync runs a lightweight Microsoft-managed agent in each forest and performs sync logic in the cloud, so it handles disconnected multi-forest topologies without a full server per forest; Connect Sync is the full on-premises engine needed for complex transformations and large or rich object scenarios. If the requirement stresses lightweight, Microsoft-managed, or disconnected forests, it is Cloud Sync.
- Group-based licensing versus a dynamic membership rule. Group-based licensing assigns a licence to the group object so members gain or lose it automatically, while a dynamic membership rule only decides who is in the group and never grants a licence by itself. The rule controls membership; the licence assignment on the group controls the entitlement.
Worked example from the SC-300 bank
lock_openFree sampleImplement and Manage User Identitieshard
A company has three disconnected Active Directory forests acquired through mergers, each managed by a separate IT team, and wants to synchronise all of them to one Microsoft Entra tenant. The architecture team requires a lightweight, Microsoft-managed provisioning service that avoids deploying a full synchronisation server per forest. Which synchronisation technology meets this requirement?
- ADeploy Microsoft Entra Cloud Sync with a lightweight provisioning agent in each forest, because the service is Microsoft-managed and supports disconnected multi-forest topologies.check_circle Correct
- BDeploy Microsoft Entra Connect Sync on a server in each forest, because only the full sync engine can read objects from multiple disconnected Active Directory forests.
- CDeploy a single Microsoft Entra Connect Sync server with a custom rule set that reaches across all three disconnected forests over the public internet.
- DDeploy Microsoft Entra Connect Health agents in each forest, because the health service can provision identities from disconnected forests into the tenant.
Microsoft Entra Cloud Sync uses lightweight Microsoft-managed agents and is the preferred choice for synchronising disconnected multi-forest Active Directory environments. Cloud Sync places a lightweight provisioning agent in each forest and performs the synchronisation logic in a Microsoft-managed cloud service, so disconnected forests with no trust between them are supported without a full sync server per forest. Connect Sync requires a server and network reachability, and Connect Health only monitors.
Why A is correct: Cloud Sync uses lightweight agents that report to a Microsoft-managed cloud service and natively supports disconnected forests, matching the lightweight multi-forest requirement exactly.
Why B is wrong: Connect Sync can serve multiple forests, but it requires a full synchronisation server and is not the lightweight Microsoft-managed agent service the architecture team asked for.
Why C is wrong: Disconnected forests have no shared trust path for one Connect Sync server to reach them, and reaching across forests over the internet is not a supported synchronisation design.
Why D is wrong: Connect Health only monitors the health and performance of identity synchronisation; it does not provision or synchronise any directory objects into the tenant.
What you must be able to do. Select and configure the precise Conditional Access, authentication, risk, or Global Secure Access control that meets an access requirement with the least administrative effort.
In one sentenceThe access layer: authentication methods, Conditional Access grant and session controls, continuous access evaluation, ID Protection risk policies, and Global Secure Access.
Recall check: answer these from memory first
- Which Conditional Access control forces periodic reauthentication, and how do you limit it to one app?
- What revokes an active session in near real time when an account is disabled, instead of waiting for token expiry?
- Which Windows Hello for Business model gives on-premises Kerberos single sign-on without a per-device certificate?
What it tests. Whether you can plan and enforce how people prove who they are and what they can reach: authentication methods including passwordless and Windows Hello for Business, multifactor authentication, self-service password reset, and password protection; Conditional Access policy assignments, grant controls, and session controls; advanced session management, continuous access evaluation, and protected actions; user and sign-in risk response with Microsoft Entra ID Protection; and Microsoft Entra Global Secure Access for Private Access and Internet Access.
How to study it. Build Conditional Access policies and learn the difference between grant and session controls by configuring both. Set sign-in frequency scoped to a single app, enable continuous access evaluation, and read how it propagates critical events such as account disablement. Configure a Microsoft Entra ID Protection user-risk and sign-in-risk policy and trace what triggers each. Stand up a Windows Hello for Business cloud Kerberos trust deployment in your notes, and follow a Global Secure Access Private Access publish through the private network connector.
Easy to confuse
- Conditional Access grant control versus session control. A grant control decides whether sign-in is allowed and on what terms, such as requiring multifactor authentication or a compliant device; a session control shapes what happens within the granted session, such as sign-in frequency or a persistent browser. If the requirement is about behaviour during the session rather than at the door, it is a session control.
- Continuous access evaluation versus shorter token lifetime or sign-in frequency. Continuous access evaluation pushes critical directory events to resource providers so existing tokens are rejected within minutes; shorter token lifetimes and sign-in frequency still wait for expiry before re-evaluating. If the requirement is near-real-time revocation on a directory change, it is continuous access evaluation.
Worked example from the SC-300 bank
lock_openFree sampleImplement Authentication and Access Managementhard
A security team needs sign-in sessions to a critical finance app to end within minutes when a user account is disabled or its password is reset, instead of waiting for the access token to expire. Token lifetimes are currently around an hour. Which capability should they rely on to revoke active sessions in near real time?
- ALower the access token lifetime to five minutes by configuring a token lifetime policy that the finance app honours on every request.
- BConfigure a sign-in frequency session control of one hour so the user must reauthenticate hourly after the account state changes.
- CRely on continuous access evaluation so the app receives critical event notifications and rejects the token shortly after the account change.check_circle Correct
- DEnable the persistent browser session control so the browser cookie is discarded the moment the account is disabled in the directory.
Continuous access evaluation propagates critical directory events to resource providers so active tokens are rejected in near real time rather than at expiry. Continuous access evaluation establishes a channel where Microsoft Entra ID pushes critical events, such as account disablement and password change, to CAE-capable resource providers, which then invalidate already issued tokens within minutes. Shorter token lifetimes and sign-in frequency still depend on expiry, and persistent browser session governs cookies, so none react to the directory event.
Why A is wrong: Shortening token lifetime narrows the revocation window but still relies on expiry rather than an event, and very short tokens add load and latency without delivering near real-time revocation.
Why B is wrong: Sign-in frequency sets a fixed reauthentication interval and does not react to an account being disabled or a password reset, so an active session would persist until the interval elapses.
Why C is correct: Continuous access evaluation lets resource providers subscribe to critical Microsoft Entra events such as account disable and password reset, then reject existing tokens near real time rather than waiting for expiry.
Why D is wrong: Persistent browser session only governs whether cookies survive browser closure on the client and has no link to directory account-state events, so it cannot revoke a live session.
What you must be able to do. Choose and configure the correct workload identity, enterprise application integration, consent, or Defender for Cloud Apps control that meets an application access requirement.
In one sentenceThe workload layer: managed identities and service principals, enterprise app integration and consent, app registrations and roles, and Defender for Cloud Apps controls.
Recall check: answer these from memory first
- Which workload identity is created and deleted with its Azure resource and needs no managed credential?
- Which Application Proxy pre-authentication setting forces Conditional Access before the back-end is reached?
- Which Defender for Cloud Apps source shows live per-activity matches for a proxied session policy?
What it tests. Whether you can give applications and Azure workloads the right non-human identity and control their access: managed identities versus service principals; integrating enterprise applications including on-premises apps through Application Proxy and SaaS apps with provisioning and single sign-on; managing enterprise application access, user and admin consent, and My Apps collections; app registrations, app authentication, API permissions, and app roles; and monitoring app access with Microsoft Defender for Cloud Apps discovery, connected apps, and Conditional Access app control session policies.
How to study it. Enable a system-assigned managed identity on an Azure virtual machine, grant it access to Key Vault, and contrast its lifecycle with a user-assigned identity and a manually created service principal. Publish an on-premises app through Application Proxy and set Microsoft Entra ID pre-authentication. Configure a My Apps collection. In Microsoft Defender for Cloud Apps, deploy a session policy via Conditional Access app control and read the activity log to confirm matches. Compare the Cloud Discovery dashboard, activity log, files page, and governance log.
Easy to confuse
- System-assigned managed identity versus user-assigned managed identity versus service principal. A system-assigned managed identity is bound to one Azure resource and is created and deleted with it; a user-assigned managed identity is a standalone object you attach to one or more resources and clean up yourself; a manually created service principal carries managed credentials with an independent lifecycle. If the requirement says tied to the resource with nothing to clean up, it is system-assigned.
- Microsoft Entra ID pre-authentication versus pass-through pre-authentication on Application Proxy. Microsoft Entra ID pre-authentication authenticates the user at the service edge first, so Conditional Access runs and unauthenticated traffic never reaches the back-end; pass-through forwards requests to the application, which prompts for its own credentials and bypasses Conditional Access evaluation. If the requirement is enforce Conditional Access before the server, it is Microsoft Entra ID pre-authentication.
Worked example from the SC-300 bank
lock_openFree samplePlan and Implement Workload Identitiesmedium
An Azure virtual machine runs a single application that must read secrets from Azure Key Vault without any credentials stored on the host. The identity team requires that the application's identity be created when the virtual machine is created and removed automatically when the virtual machine is deleted, with no separate object to clean up. Which workload identity should be configured on the virtual machine?
- AA system-assigned managed identity enabled directly on the virtual machine so its lifecycle is tied to the virtual machine resource.check_circle Correct
- BA user-assigned managed identity created in a resource group, then attached to the virtual machine so the application can request tokens for Key Vault.
- CAn app registration with a client secret stored in Key Vault, with the secret read by the application at start-up to authenticate.
- DA service principal created manually with a certificate credential, then referenced by the application running on the virtual machine.
A system-assigned managed identity is bound to a single Azure resource and is created and deleted automatically with that resource, requiring no managed credentials. A system-assigned managed identity is provisioned in Microsoft Entra ID directly on the Azure resource and shares its lifecycle: it appears when the resource is enabled and is removed when the resource is deleted. The platform rotates the underlying credential, so the application acquires tokens without any secret on disk. User-assigned identities, app registrations, and manual service principals all have independent lifecycles or managed credentials, so none satisfy the tie-to-the-resource and no-cleanup requirements.
Why A is correct: A system-assigned managed identity is created with the virtual machine and deleted automatically when the virtual machine is deleted, giving credential-free token access bound to that one resource's lifecycle.
Why B is wrong: A user-assigned managed identity has an independent lifecycle and is not deleted with the virtual machine, so it leaves a standalone object to clean up, which the requirement forbids.
Why C is wrong: An app registration relies on a client secret the team must manage and rotate, which contradicts the no-stored-credentials requirement and is not tied to the virtual machine lifecycle.
Why D is wrong: A manually created service principal with a certificate is an independent object whose credential and lifecycle must be maintained separately, so it is neither credential-free nor automatically removed with the virtual machine.
What you must be able to do. Choose and configure the correct entitlement management, access review, terms of use, PIM, or lifecycle workflow setting that meets a governance or privileged-access requirement.
In one sentenceThe governance layer: entitlement management access packages, access reviews, terms of use, Privileged Identity Management, and lifecycle workflows.
Recall check: answer these from memory first
- Which access review reviewer and action combination makes members self-attest quarterly and removes non-responders?
- Which Microsoft Entra capability stores a legal PDF and enforces dated, renewable acceptance through Conditional Access?
- Which capability schedules joiner tasks such as a Temporary Access Pass relative to the employeeHireDate attribute?
What it tests. Whether you can automate who gets access, for how long, and with what oversight: entitlement management with catalogs and access packages; the lifecycle of external users, terms of use, and connected organisations; access reviews and what happens to undecided members; privileged access with Privileged Identity Management for roles, resources, and groups including activation, approval, audit, and break-glass accounts; lifecycle workflows for joiner, mover, and leaver tasks; and monitoring identity activity with sign-in and audit logs, diagnostic settings, KQL, workbooks, and Identity Secure Score.
How to study it. Build an access package in a catalog, attach an access review where users review their own access, and set the apply-results action so non-responders are removed. Configure a terms of use object and enforce it through a Conditional Access policy. In an access review, test the 'If reviewers don't respond' setting. Configure a PIM role with approval and activation requirements and set up a break-glass account. Create a scheduled lifecycle workflow keyed to employeeHireDate, and explore sign-in and audit logs with KQL.
Easy to confuse
- Access reviews versus entitlement management. Entitlement management grants access up front through request-driven access packages and catalogs with approval and expiry; access reviews periodically re-certify access someone already holds and remove it when no longer justified. If the requirement is provision access on request, it is entitlement management; if it is recertify existing access, it is an access review.
- Terms of use versus an access package custom question. A terms of use object uploads a legal document and enforces dated, renewable, logged acceptance via a Conditional Access policy before access is granted; an access package custom question merely collects a free-text answer at request time with no binding, renewal, or record of legal acceptance. If the requirement is a recorded, renewable legal acceptance, it is terms of use.
Worked example from the SC-300 bank
lock_openFree samplePlan and Automate Identity Governancemedium
A finance team must ensure that every guest user is forced to read and accept a legal disclaimer before they can open the budgeting application, and that acceptance is recorded and renewed every twelve months. The disclaimer wording is provided as a PDF. Which Microsoft Entra capability should the administrator configure to enforce and record this acceptance?
- AConfigure an access package in entitlement management that includes a custom question prompting each guest to type that they accept the disclaimer before requesting the application.
- BConfigure a Microsoft Entra ID Protection user risk policy that requires guests to acknowledge a notice whenever their account is flagged as risky before accessing the application.
- CCreate a terms of use in Microsoft Entra ID by uploading the PDF, set it to require re-acceptance every twelve months, then require it through a Conditional Access policy that targets guest users and the application.check_circle Correct
- DEdit the external collaboration settings to add the disclaimer text to the guest invitation email, so each invited guest reads and confirms the disclaimer when redeeming the invitation.
Terms of use in Microsoft Entra ID uploads a legal document and enforces dated, renewable acceptance at sign-in through a Conditional Access policy. A terms of use object stores the uploaded PDF and its re-acceptance interval, and it becomes enforceable when a Conditional Access policy requires it for chosen users and applications. The user must accept before access is granted, and each acceptance is recorded. Access package questions, Identity Protection prompts, and invitation emails provide none of this binding, logged, renewable behaviour.
Why A is wrong: An access package question collects free-text input during a request, but it does not present an enforced legal document, gate sign-in, or record a renewable acceptance, so it cannot satisfy a binding terms-of-use requirement.
Why B is wrong: Identity Protection acts only when a sign-in or user is judged risky and shows a remediation prompt, not a legal disclaimer, so it neither forces universal acceptance nor stores a dated record of consent.
Why C is correct: Terms of use lets the administrator upload the PDF, configure periodic re-acceptance, and is enforced at sign-in through Conditional Access so guests must accept before reaching the app and the acceptance is logged.
Why D is wrong: Invitation settings customise the redemption email but offer no enforced acceptance gate, no PDF document, and no renewal schedule, so confirming an email does not produce a recorded, periodically renewed agreement.