Study guide
4.2 Signals and Controls
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
4.2 Signals and Controls
Key Takeaways Explain This Topic AI
Signals (assignments/conditions) include user/group, target resource or user action, network/location, device platform, client app, filter for devices, and sign-in or user risk.
Grant controls include block, require MFA, require authentication strength, compliant device, Entra hybrid joined device, approved client app, app protection policy, password change, and terms of use.
Session controls include app-enforced restrictions, Conditional Access App Control via Defender for Cloud Apps, sign-in frequency, persistent browser session, and token protection.
MFA can be both an authentication method and a Conditional Access grant control, depending on how the scenario frames it.
All assignments are combined with AND, and multiple grant controls default to requiring all selected controls.
Last updated: June 2026
Signals: the conditions Entra evaluates
A signal is a piece of context Conditional Access collects in Phase 1 and uses to decide whether a policy applies. In the policy editor these live under Assignments and Conditions . The signals SC-900 expects you to recognize are:
Signal What it describes
Users / groups / roles Who the policy includes or excludes (all users, groups, directory roles, guests, workload identities)
- Target resources Which cloud apps, user actions, or authentication contexts are in scope
- Network IP ranges, named locations, geographies, trusted vs. untrusted networks
- Device platforms iOS, Android, Windows, macOS, Linux (from user-agent, not fully trusted)
- Client apps Browser vs. mobile/desktop clients; used to block legacy authentication
- Filter for devices Targets devices by attributes/properties
- Sign-in risk / user risk Risk levels supplied by Microsoft Entra ID Protection (requires P2)
Signals never grant standing access by themselves — they only decide whether the policy's controls fire. They are why this topic sits with Zero Trust and identity rather than pure network security.
Grant controls: what the policy requires
After conditions match, Entra applies an access control . The first choice is binary: Block access or Grant access . Block is the most powerful control and stops Phase 2 immediately. If access is granted, the admin can require one or more grant controls :
Require multifactor authentication — the most common control.
Require authentication strength — forces a specific method set, e.g. phishing-resistant MFA (FIDO2, Windows Hello, certificate).
Require device to be marked as compliant — Intune compliance.
Require Microsoft Entra hybrid joined device .
Require approved client app and Require app protection policy — mobile app protection.
Require password change — used to remediate compromised accounts.
Require terms of use — user must accept a ToU document.
When several controls are selected, the default is Require all the selected controls (AND); admins can switch to Require one of the selected controls (OR), e.g. "compliant device OR MFA."
Session controls and MFA's dual role
Beyond grant decisions, session controls limit what a user can do after access is granted:
App-enforced restrictions (Exchange Online, SharePoint Online — limited vs. full access).
Conditional Access App Control — routes the session through Microsoft Defender for Cloud Apps to block download/print of sensitive files or require labeling.
Sign-in frequency — how often the user must reauthenticate.
Persistent browser session — whether "stay signed in" is allowed.
Token protection — binds the refresh token to the device.
A classic SC-900 nuance is that MFA appears in two places . In the authentication chapter, MFA is an authentication method that proves identity. In Conditional Access, "Require MFA" is a grant control applied when conditions match. The capability is identical; only the framing changes. If a question says "all users must use MFA," that is authentication/security defaults; if it says "require MFA only when signing in from outside the corporate network," that is a Conditional Access control.
A quick elimination method
Label each phrase in the question:
Wording about context (location, device, client, risk) → a signal/condition .
Wording about a requirement or action (must do MFA, must be compliant, blocked) → a control .
Wording about continued need over time → governance / access reviews (Section 4.4–4.5).
Wording about temporary admin elevation → Privileged Identity Management (Section 4.5).
This keeps you from picking a familiar product just because it shares the objective area. The exam rewards the most specific identity capability.
Context phrase → signal.
Required action phrase → control.
Recertification phrase → access review.
Elevated-role phrase → PIM.
Worked example: reading a policy in plain language
Consider a realistic policy and translate each part into the signal-and-control vocabulary. " This single policy is one of Microsoft's most recommended baseline rules because legacy authentication protocols cannot perform MFA and are a top vector for password-spray attacks.
Now a second policy: for the Finance group, accessing the finance application, from any location, require MFA and require a compliant device, all selected controls. The signals are the user group, the target app, and location; the controls are two grant controls combined with AND. Because Conditional Access combines multiple policies with AND as well, a Finance user who is also subject to the legacy-auth block policy must satisfy both rule sets.
A common trap is the emergency access (break-glass) account . Best practice is to exclude at least one cloud-only Global Administrator account from all Conditional Access policies so a misconfigured policy or an MFA outage cannot lock every admin out. If a question asks how to avoid a tenant-wide lockout, excluding break-glass accounts is the answer.
Legacy-auth block: a baseline policy that stops protocols that cannot do MFA.
Combined controls default to require all (AND).
Break-glass accounts are excluded to prevent lockout.
Report-only mode lets you preview a policy's effect before enforcing it.
Reading every policy as signal → condition → control turns even unfamiliar wording into a quick elimination exercise: identify what is known about the request, what makes the policy match, and what the policy then enforces.