πŸ”’ Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided SC-300 Domain 1
Domain 1 β€” Module 4 of 8 50%
4 of 27 overall

SC-300 Study Guide

Domain 1: Implement and Manage User Identities

  • Your Entra Tenant: Branding, Settings & Domains
  • Entra Roles & Administrative Units
  • Managing Users & Groups
  • Device Registration & Licensing
  • External Identities: Guest Access & B2B
  • Cross-Tenant Access & Synchronisation
  • Hybrid Identity: Connect Sync vs Cloud Sync
  • Hybrid Authentication: PHS, PTA & Seamless SSO

Domain 2: Implement Authentication and Access Management

  • Authentication Methods: Plan & Implement
  • Passwordless & Windows Hello for Business
  • MFA, SSPR & Password Protection
  • Conditional Access: Plan & Build Policies
  • Conditional Access: Advanced Controls & Troubleshooting
  • Entra ID Protection: Risk-Based Security
  • Global Secure Access: Zero Trust Networking

Domain 3: Plan and Implement Workload Identities

  • Workload Identities: Managed Identities & Service Principals
  • Enterprise Apps: SSO, App Proxy & Integration
  • Enterprise Apps: Users, Consent & Collections
  • App Registrations: Build & Secure
  • Defender for Cloud Apps: Discover & Control
  • Defender for Cloud Apps: Policies & OAuth Governance

Domain 4: Plan and Automate Identity Governance

  • Entitlement Management: Catalogs & Access Packages Free
  • Access Requests, Terms of Use & External Lifecycle Free
  • Access Reviews: Plan, Create & Monitor Free
  • PIM: Protect Your Privileged Roles Free
  • PIM: Azure Resources, Groups & Audit Free
  • Identity Monitoring: Logs, KQL & Secure Score Free

SC-300 Study Guide

Domain 1: Implement and Manage User Identities

  • Your Entra Tenant: Branding, Settings & Domains
  • Entra Roles & Administrative Units
  • Managing Users & Groups
  • Device Registration & Licensing
  • External Identities: Guest Access & B2B
  • Cross-Tenant Access & Synchronisation
  • Hybrid Identity: Connect Sync vs Cloud Sync
  • Hybrid Authentication: PHS, PTA & Seamless SSO

Domain 2: Implement Authentication and Access Management

  • Authentication Methods: Plan & Implement
  • Passwordless & Windows Hello for Business
  • MFA, SSPR & Password Protection
  • Conditional Access: Plan & Build Policies
  • Conditional Access: Advanced Controls & Troubleshooting
  • Entra ID Protection: Risk-Based Security
  • Global Secure Access: Zero Trust Networking

Domain 3: Plan and Implement Workload Identities

  • Workload Identities: Managed Identities & Service Principals
  • Enterprise Apps: SSO, App Proxy & Integration
  • Enterprise Apps: Users, Consent & Collections
  • App Registrations: Build & Secure
  • Defender for Cloud Apps: Discover & Control
  • Defender for Cloud Apps: Policies & OAuth Governance

Domain 4: Plan and Automate Identity Governance

  • Entitlement Management: Catalogs & Access Packages Free
  • Access Requests, Terms of Use & External Lifecycle Free
  • Access Reviews: Plan, Create & Monitor Free
  • PIM: Protect Your Privileged Roles Free
  • PIM: Azure Resources, Groups & Audit Free
  • Identity Monitoring: Logs, KQL & Secure Score Free
Domain 1: Implement and Manage User Identities Premium ⏱ ~12 min read

Device Registration & Licensing

Control which devices join your tenant, understand the three join types, and master licence assignment β€” including group-based licensing and conflict resolution.

Device identity β€” why devices need accounts too

β˜• Simple explanation

Devices are like visitors to your building β€” you need to register them before they can get in.

There are three levels of registration:

  • Registered β€” like a visitor badge. The device is known but not fully trusted. Think personal phones used for work email.
  • Joined β€” like an employee ID card. The device is fully managed and trusted. Think company-owned laptops.
  • Hybrid joined β€” the device has BOTH an on-prem AD identity AND an Entra ID identity. Think company laptops at organisations still running Active Directory.

Device identity in Microsoft Entra ID establishes trust between devices and your tenant. Registered devices create a device object in Entra ID, enabling features like Conditional Access device-based policies, SSO, and compliance enforcement via Intune.

The three device identity models serve different scenarios: Entra registered for BYOD, Entra joined for cloud-managed corporate devices, and Hybrid Entra joined for domain-joined devices in hybrid environments.

The three device join types

FeatureEntra RegisteredEntra JoinedHybrid Entra Joined
OwnershipPersonal (BYOD)Organisation-ownedOrganisation-owned
OS supportWindows 10/11, iOS, Android, macOS, LinuxWindows 10/11, macOS 13+, Ubuntu 22.04/24.04, RHEL 8/9Windows 10/11
On-prem AD required
Sign-in methodLocal/personal accountEntra ID credentialsDomain credentials + Entra sync
Device managementOptional (MAM via Intune)Full MDM (Intune)Group Policy + Intune co-management
SSO to cloud resourcesYes (after auth)Yes (primary refresh token)Yes (primary refresh token)
CA supportLimitedFull (compliance, device type)Full (compliance, device type)
Best forPersonal phones and tabletsCloud-first organisationsHybrid environments migrating to cloud

How each join type works

Entra registered (BYOD):

  1. User goes to Settings β†’ Accounts β†’ Access work or school
  2. Adds their work account
  3. Device gets registered in Entra ID β€” user keeps personal device control
  4. Organisation can apply app-level policies (MAM) but not full device management

Entra joined (cloud-managed):

  1. During Windows OOBE (first setup) or Settings β†’ join this device to Entra ID
  2. User signs in with Entra credentials
  3. Device is fully managed β€” organisation controls it via Intune
  4. User gets SSO to all cloud apps via Primary Refresh Token (PRT)

Hybrid Entra joined:

  1. Device is joined to on-premises Active Directory (as usual)
  2. Entra Connect syncs the device object to Entra ID
  3. Device has both an AD computer account AND an Entra device object
  4. Enables cloud features (CA, Intune co-management) for legacy domain-joined devices
ℹ️ Scenario: Jake vs Priya β€” different device strategies

Jake at Coastline Creative (35 people, no on-prem AD): All devices are Entra joined. Laptops are company-owned, fully managed by Intune. Freelancers use personal devices that are Entra registered β€” they get email access via Outlook mobile with app protection policies.

Priya at Meridian Health (5,000 employees, hybrid AD): Workstations in hospitals are Hybrid Entra joined β€” they’re domain-joined for Group Policy but also synced to Entra for Conditional Access. Over time, new devices are being deployed as Entra joined only, skipping the on-prem AD step entirely. This is the cloud migration path.

πŸ’‘ Exam tip: device join decision logic

The exam often gives a scenario and asks which join type to use. Use this decision logic:

  • Personal device (BYOD)? β†’ Entra Registered (always)
  • Corporate device, no on-prem AD? β†’ Entra Joined
  • Corporate device, existing on-prem AD? β†’ Hybrid Entra Joined (migration) or Entra Joined (greenfield)
  • Need full MDM management? β†’ Entra Joined or Hybrid Entra Joined (Registered = MAM only)
  • Conditional Access needs compliant device? β†’ Must be Joined or Hybrid Joined (Registered has limited CA support)
  • Question mentions β€œshared device” or β€œkiosk”? β†’ Entra Joined with shared device mode

Device settings in the Entra admin center

SettingWhat It Controls
Users may join devices to Entra IDAll, Selected users/groups, or None
Users may register their devicesAll, Selected users/groups, or None
Maximum number of devices per userDefault: 50 (reduce for tighter control)
Require MFA to register or join devicesAdditional auth step for device registration
Additional local administrators on Entra joined devicesAdd specific users/groups as local admins

Licensing β€” assign, modify, report

Direct vs group-based licensing

MethodHow It WorksBest For
Direct assignmentManually assign licence to individual userOne-off assignments, exceptions
Group-based licensingAssign licence to a group β€” all members get it automaticallyScalable, automated management

Group-based licensing is the recommended approach:

  1. Create a security group (e.g., β€œM365 E5 Users”)
  2. Assign the M365 E5 licence to the group
  3. Add users to the group β†’ they automatically receive the licence
  4. Remove users from the group β†’ licence is automatically reclaimed
πŸ’‘ Exam tip: licence conflicts and errors

Group-based licensing can hit errors:

  • Not enough licences β€” more group members than available licences. New members enter an error state.
  • Conflicting service plans β€” a user is in two groups that assign licences with overlapping service plans that can’t coexist.
  • Missing usage location β€” users without a usage location can’t receive licences.
  • Missing dependencies β€” some service plans require other plans to be enabled first.

Check for errors: Entra admin center β†’ Licences β†’ select a product β†’ check for users in error state. The exam tests your ability to identify and resolve these conflicts.

Reporting on licences

Where to check licence usage:

  • Entra admin center β†’ Licences β†’ All products β€” see total/assigned/available per SKU
  • Microsoft 365 admin center β†’ Billing β†’ Licences β€” similar view with purchase details
  • Microsoft Graph API / PowerShell β€” programmatic access for reports and automation
# Report on licence assignments using Microsoft Graph PowerShell
Get-MgSubscribedSku | Select-Object SkuPartNumber, ConsumedUnits,
  @{Name="Available"; Expression={$_.PrepaidUnits.Enabled - $_.ConsumedUnits}}
ℹ️ Scenario: Jake optimises licensing at Coastline Creative

Jake discovers that 5 freelancers who left still have M365 Business Premium licences assigned. At $22/user/month, that’s $110/month wasted.

He runs a PowerShell script to find users with licences but no sign-in activity in 90 days, removes the licences, and sets up a dynamic group so licences are automatically assigned based on employment status.

Lesson: Regular licence reporting saves money. Group-based licensing with dynamic groups prevents orphaned licences.

🎬 Video walkthrough

🎬 Video coming soon

Device Registration & Licensing β€” SC-300 Module 4

Device Registration & Licensing β€” SC-300 Module 4

~10 min

Flashcards

Question

What are the three device identity models in Entra ID?

Click or press Enter to reveal answer

Answer

1) Entra Registered β€” BYOD/personal devices (visitor badge). 2) Entra Joined β€” cloud-managed corporate devices (employee ID). 3) Hybrid Entra Joined β€” domain-joined + synced to Entra (both identities). Each provides increasing levels of management and trust.

Click to flip back

Question

What is a Primary Refresh Token (PRT)?

Click or press Enter to reveal answer

Answer

A token issued to Entra Joined and Hybrid Entra Joined devices that enables SSO across cloud applications. The user authenticates once at device sign-in, and the PRT handles subsequent app authentication silently.

Click to flip back

Question

What is group-based licensing?

Click or press Enter to reveal answer

Answer

Assign a licence to a security group β€” all members automatically receive it. When users join the group, they get the licence. When they leave, it's reclaimed. Recommended over direct assignment for scalable management.

Click to flip back

Question

Name three common group-based licensing errors.

Click or press Enter to reveal answer

Answer

1) Not enough licences β€” more members than available licences. 2) Conflicting service plans β€” overlapping plans from multiple groups. 3) Missing usage location β€” users need a country set before licence assignment.

Click to flip back

Knowledge Check

Knowledge Check

Coastline Creative is a cloud-only organisation. Jake wants company laptops to be fully managed by Intune with SSO to all cloud apps. Freelancers should use their own devices but with app protection policies on Outlook. Which device strategy is correct?

Knowledge Check

Priya assigns an M365 E5 licence to a security group. A new nurse is added to the group but doesn't receive the licence. What's the most likely cause?

Knowledge Check

A Meridian Health hospital workstation is joined to the on-premises Active Directory and also has an identity in Entra ID via Entra Connect. Which device identity model is this?


Next up: External Identities: Guest Access & B2B β€” invite contractors, partners, and vendors to collaborate securely without creating internal accounts.

← Previous

Managing Users & Groups

Next β†’

External Identities: Guest Access & B2B

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.