Study guide
3.2 Identity Types and Directory Objects
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
3.2 Identity Types and Directory Objects
Key Takeaways Explain This Topic AI
Entra ID secures four identity types: users, service principals (apps), managed identities, and devices.
A service principal is the local identity of an application in a tenant; a managed identity is an automatically managed service principal that removes stored credentials.
Groups come in two membership types (Assigned and Dynamic) and two security types (Security groups and Microsoft 365 groups).
Managed identities come in two flavors: system-assigned (tied to one resource lifecycle) and user-assigned (standalone, shareable across resources).
Device identities (Registered, Entra joined, Entra hybrid joined) let access policies factor in the endpoint, not just the person.
Last updated: June 2026
The four identity types
Microsoft groups the identities Entra ID protects into four categories. SC-900 expects you to recognize all four, because a scenario may never say the word "user."
- Identity type What it represents
- User A human (employee, guest, admin) who signs in
- Service principal The identity of an application or service in a tenant
- Managed identity An auto-managed service principal for Azure resources, with no credentials to store
- Device A computer or phone registered/joined to Entra ID
Users are the most familiar: member users (internal) and guest users (external, with a UPN containing #EXT# ). But applications and automation also need identities — they cannot type a password — and that is where service principals and managed identities come in. Service principals and managed identities together are often called workload identities (non-human identities that apps, services, scripts, and automation use to authenticate and access resources).
The exam likes to test this breadth directly by describing an app, a script, or an Azure service and asking which identity applies — the trap is answering "user" when no human is involved.
Service principals and managed identities
An application object is the global definition of an app (registered once, in its home tenant). A service principal is the local representation of that app inside a specific tenant — it is what gets permissions and is granted access to resources. Think of the app object as the blueprint and the service principal as the instance in your tenant.
A managed identity is a special, automatically managed service principal that lets an Azure resource (a VM, App Service, Function, Logic App, etc.) authenticate to services that support Entra authentication without any developer-managed secret, certificate, or password . This eliminates stored credentials — a major security win and a frequent exam talking point.
- Managed identity type Lifecycle Sharing
- System-assigned Created with, and deleted with, a single Azure resource Tied to that one resource only
- User-assigned A standalone resource created independently Can be shared across multiple Azure resources
Exam cue: "an Azure app needs to access Key Vault/Storage without storing credentials " → managed identity .
Groups: membership and type
Groups let admins manage access for many identities at once instead of one by one. Two dimensions matter on SC-900.
Membership type:
Assigned — an admin manually adds/removes each member.
Dynamic — membership is automatic, driven by rules over user or device attributes (e.g., department -eq "Sales" ); a user joining or leaving the matching condition is added/removed automatically.
Group type:
Security group — used to grant access to resources, apps, and assign roles/licenses.
Microsoft 365 group — provides collaboration resources (shared mailbox, calendar, SharePoint site, Teams) in addition to access; can include guests.
Many people needing the same access → use a group rather than individual assignments.
Membership should follow an HR attribute automatically → dynamic membership.
Need a shared mailbox/Teams for collaboration → Microsoft 365 group .
Device identities
Devices can be identities in Entra ID , which lets access decisions consider the endpoint and not only the person. This is foundational to Conditional Access "require a compliant/managed device" controls covered later.
- Device state Meaning
- Entra registered Personal/BYOD device with a work identity added (bring-your-own)
- Microsoft Entra joined Cloud-only corporate device joined directly to Entra ID
Microsoft Entra hybrid joined Device joined to on-premises AD and registered to Entra ID (common during cloud transition)
Reading pattern for any 3.2 question: first decide human vs. non-human . If non-human (an app, script, or Azure service), think service principal / managed identity / workload identity . If the scenario stresses scale and repeatability , think group (and dynamic if attribute-driven). If it stresses the computer or phone state , think device identity . Choosing the right object before choosing the control is how you avoid the common distractors.
Why object type changes the right answer
The same access story produces a different correct answer when the requesting object changes, so the exam often varies one detail to test whether you noticed. One person needing app access is a user scenario. Many people needing the same access points to a group , and if membership should track an HR attribute it points to a dynamic group. An application that must call an API on its own is a service principal ; if that app is an Azure resource that must do so without stored secrets , the answer shifts to a managed identity .
When the endpoint itself (its compliance or join state) factors into the decision, the relevant object is the device identity .
Identify the requester before choosing the control — don't assume every identity is a person.
Use groups when the problem emphasizes scale; use dynamic groups when it emphasizes automation.
Treat app and automation access as identity problems (workload identities), not network problems.
A credential-free Azure-resource requirement is the strongest single signal for a managed identity .
This discipline — name the principal first — is the single most useful habit for the identity-objects portion of the exam.