Study guide
3.6 Password Protection, Self-Service Password Reset, and External Identities
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.6 Password Protection, Self-Service Password Reset, and External Identities
Key Takeaways Explain This Topic AI
Self-Service Password Reset (SSPR) lets users reset or unlock their own accounts after registering authentication methods, cutting help-desk cost.
SSPR with password writeback pushes resets back to on-premises AD in hybrid environments so the change applies everywhere.
Entra Password Protection blocks weak and banned passwords (global and custom banned-password lists) in the cloud and, via agents, in on-premises AD.
Microsoft Entra External ID is the modern brand for external identities: B2B collaboration (guest partners) and the CIAM/customer (formerly Azure AD B2C) scenario.
B2B guest users authenticate with their own home identity and carry a UPN containing the #EXT# tag in your tenant.
Last updated: June 2026
Self-Service Password Reset (SSPR)
Self-Service Password Reset (SSPR) lets users reset or unlock their own accounts without calling the help desk, which lowers support cost and reduces sign-in downtime. To use it, a user must first register one or more authentication methods (for example, the Microsoft Authenticator app, a phone number, or email). When they later forget their password, they prove identity with those registered methods and set a new one.
Administrators control SSPR with settings such as:
Scope — enabled for none, selected groups, or all users.
Number of methods required to reset (e.g., one or two).
Which methods are allowed (Authenticator, phone, email, security questions).
Registration enforcement — require users to register on next sign-in.
A forward-looking SC-900 note: Microsoft's Secure Future Initiative is tightening SSPR so that, from September 7, 2026 , verification must use explicitly registered authentication methods rather than directory-sourced contact attributes — reinforcing the theme that recovery should rely on trusted, user-validated methods.
Password writeback and Entra Password Protection
In hybrid environments, a cloud password reset must also update on-premises Active Directory or users would have mismatched passwords. Password writeback is the Entra Connect feature that writes SSPR changes back down to on-premises AD , so a user who resets in the cloud can immediately use the new password on-premises too.
Microsoft Entra Password Protection reduces weak-password risk by blocking known-weak and banned passwords :
- Feature What it does
- Global banned password list Microsoft-maintained list of common weak passwords, always enforced
- Custom banned password list Organization-specific terms (company name, products) to block
- On-premises enforcement Domain controller agents extend banned-password checks to on-prem AD password changes
- Smart lockout Locks out attackers after bad attempts while distinguishing real users
This is the difference the exam draws: Password Protection prevents weak passwords from being chosen; SSPR handles recovery when a password is forgotten; MFA adds a second proof even when the password is correct.
External identities: Microsoft Entra External ID
Microsoft Entra External ID is the current umbrella brand for working with people outside your organization. It covers two scenarios:
B2B collaboration (business guests) — invite partners, vendors, and contractors as guest users . They sign in with their own home identity (their own organization's account or a one-time passcode), so you never manage their passwords. In your tenant their user type is Guest and their UPN contains the #EXT# tag (e.g., partner_contoso.com#EXT#@yourtenant.onmicrosoft.com ). You then grant guests access to specific apps and resources.
CIAM / customer scenario — a customer-facing identity solution (consumer apps) supporting social and local sign-ups at large scale. This is the modern successor to Azure AD B2C , which as of May 1, 2025 is no longer available for new customers to purchase; new consumer scenarios use Entra External ID.
- External ID scenario Who it's for Key trait
- B2B collaboration Partner/guest workers Guests bring their own identity; #EXT# UPN
- CIAM (customer) Consumers of your apps Social/local sign-up, massive scale (formerly Azure AD B2C)
Choosing the right capability — exam cues
Match the wording to the capability:
Users reset/unlock their own forgotten passwords → Self-Service Password Reset (SSPR) .
Cloud password reset must also update on-premises AD → password writeback .
Block weak or company-specific passwords (cloud and on-prem) → Entra Password Protection (global + custom banned lists).
Let external partners use existing accounts to access your resources → B2B collaboration in External ID .
Sign-in for millions of consumers/customers of your app → External ID customer (CIAM) — the successor to Azure AD B2C .
Common traps: SSPR is recovery , not prevention — don't pick it when the need is to stop weak passwords (that's Password Protection) or add proof (that's MFA). "Azure AD B2C" is the old name for the customer scenario now delivered by Entra External ID. And guests in B2B are authenticated by their own identity provider — you are not creating or managing passwords for them. Keep recovery, prevention, added-proof, and external-access scenarios in distinct lanes and these questions become straightforward.
B2B vs. B2C — the distinction the exam loves
The two External ID scenarios are easy to mix up, so memorize the audience and the trust model:
- B2B collaboration Customer / CIAM (formerly Azure AD B2C)
- Audience Business partners, vendors, contractors Consumers/customers of your apps
Identity used The guest's own work/school or personal account Local accounts or social IdPs (Google, Facebook, Apple)
- Where they live Added as guests in your tenant (#EXT# UPN) Managed in a customer-facing directory/flow
- Scale Tens to thousands of partners Millions of consumers
A quick decision rule: if the external people are business collaborators using existing org accounts , the answer is B2B ; if they are customers/consumers of a public app signing up with social or local accounts, the answer is the customer (CIAM) scenario. Both are delivered today under the single Microsoft Entra External ID brand, so don't be thrown when a question uses that umbrella name — identify the audience to pick the right sub-scenario.