Study guide
12.1 Configure Just-in-Time Protection
SC-401: Administering Information Security in Microsoft 365 Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current SC-401 Exam Facts 1.2 Scoring, Retakes, and Annual Renewal 1.3 Role, Blueprint, and Prep Path
2 Data Classification Foundations
2.1 Identify Sensitive Information Requirements 2.2 Translate Requirements into Sensitive Info Types 2.3 Create and Manage Custom Sensitive Info Types
3 Specialized Classification Methods
3.1 Document Fingerprinting 3.2 Exact Data Match Sensitive Info Types 3.3 Trainable Classifiers
4 Classification Monitoring and OCR
4.1 Monitor Classification with Data Explorer and Content Explorer 4.2 Configure OCR Support for Sensitive Info Types
5 Sensitivity Label Design
5.1 Roles and Permissions for Sensitivity Labels 5.2 Define and Create Sensitivity Labels for Items and Containers 5.3 Protection Settings and Content Marking
6 Label Policies, Containers, and Defender for Cloud Apps
6.1 Configure Publishing Policies for Sensitivity Labels 6.2 Configure Auto-Labeling Policies 6.3 Apply Sensitivity Labels to Containers 6.4 Apply Sensitivity Labels with Microsoft Defender for Cloud Apps
7 Information Protection Client and Scanner
7.1 Plan and Implement the Microsoft Purview Information Protection Client 7.2 Manage Files with the Information Protection Client 7.3 Bulk Classification with the Information Protection Scanner
8 Microsoft Purview Message Encryption
8.1 Design and Implement Microsoft Purview Message Encryption 8.2 Design and Implement Advanced Message Encryption
9 DLP Policy Design
9.1 Design Data Loss Prevention Policies 9.2 Roles and Permissions for Data Loss Prevention 9.3 Create and Manage DLP Policies
10 Adaptive Protection, DLP Precedence, and MDCA File Policies
10.1 Configure DLP Policies for Adaptive Protection 10.2 Interpret DLP Policy and Rule Precedence 10.3 Create File Policies in Defender for Cloud Apps Using DLP
11 Endpoint DLP Configuration
11.1 Device Requirements for Endpoint DLP Including Extensions 11.2 Configure Advanced DLP Rules for Devices 11.3 Configure Endpoint DLP Settings
12 Just-in-Time Protection and Endpoint Monitoring
12.1 Configure Just-in-Time Protection 12.2 Monitor Endpoint Activities
13 Retention Labels and Adaptive Scopes
13.1 Plan Information Retention and Disposition with Retention Labels 13.2 Create and Manage Adaptive Policy Scopes 13.3 Create Retention Labels for Data Lifecycle Management
14 Publishing, Auto-Apply, and Retention Precedence
14.1 Publish Retention Labels 14.2 Auto-Apply Retention Labels 14.3 Retention Precedence and Policy Lookup
15 Retention Policies and Recovering Retained Content
15.1 Create and Configure Retention Policies 15.2 Recover Retained Content in Microsoft 365
16 Insider Risk Management Foundation
16.1 Roles and Permissions for Insider Risk Management 16.2 Plan and Implement Insider Risk Management Connectors 16.3 Integrate Insider Risk Management with Microsoft Defender for Endpoint
17 IRM Settings, Indicators, and Templates
17.1 Configure Insider Risk Management Settings 17.2 Configure Policy Indicators 17.3 Select an Appropriate Policy Template
18 IRM Policies, Forensic Evidence, and Adaptive Protection
18.1 Create and Manage Insider Risk Management Policies 18.2 Manage Forensic Evidence Settings 18.3 Enable Insider Risk Levels for Adaptive Protection
19 IRM Alerts, Cases, and Workflow
19.1 Manage Insider Risk Alerts and Cases 19.2 Insider Risk Workflow and Notice Templates
20 Purview Audit and Activity Explorer
20.1 Assign Microsoft Purview Audit (Premium) User Licenses 20.2 Investigate Activities with Microsoft Purview Audit 20.3 Configure Audit Retention Policies 20.4 Analyze Purview Activities with Activity Explorer
21 DLP, Insider Risk, and Defender XDR Alert Response
21.1 Respond to DLP Alerts in the Microsoft Purview Portal 21.2 Investigate Insider Risk Activities in the Microsoft Purview Portal 21.3 Respond to Purview Alerts in Microsoft Defender XDR
22 MDCA File Policy Alerts and eDiscovery
22.1 Respond to Defender for Cloud Apps File Policy Alerts 22.2 Perform Searches by Using eDiscovery
23 Protecting Content Used by AI Services
23.1 Implement Purview Controls for AI Services 23.2 Implement Microsoft 365 Workload Controls for AI
24 Data Security Posture Management for AI
24.1 Prerequisites for DSPM for AI 24.2 Manage Roles and Permissions for DSPM for AI 24.3 Configure DSPM for AI Policies 24.4 Monitor Activities in DSPM for AI
12.1 Configure Just-in-Time Protection
Key Takeaways Explain This Topic AI
Just-in-time (JIT) protection blocks egress on never-evaluated or stale-classification files until Endpoint DLP finishes policy evaluation; it does not replace Devices-scoped DLP policies.
Configure JIT in the Microsoft Purview portal under Settings > Data Loss Prevention > Just-in-time protection, and allow at least an hour for setting changes—including disable—to reach clients.
Fallback Allow versus Block applies when classification or evaluation fails; it does not switch JIT Block versus JIT Audit for in-scope users.
If Network share coverage and exclusions is off, JIT applies only to local files; enabling both extends JIT to network shares and mapped drives.
JIT events appear in Activity explorer with JIT triggered set to true and do not create DLPRuleMatch events or alerts.
Last updated: August 2026
12.1 Configure Just-in-Time Protection
Quick Answer: Microsoft Purview just-in-time (JIT) protection is an Endpoint data loss prevention (Endpoint DLP) control that detects and blocks egress on JIT candidate files —items that have never been classified or that have a stale classification —until cloud policy evaluation finishes. Configure it in the Microsoft Purview portal under Settings > Data Loss Prevention > Just-in-time protection . The Fallback action in case of failure ( Allow users to complete actions versus Block users from completing actions ) applies only when classification or evaluation fails ; it does not decide whether JIT Block or JIT Audit runs for in-scope users.
Why SC-401 tests this control
Endpoint DLP can enforce Block or Block with override only after it knows whether a file matches a Devices-scoped policy. Classification is not instantaneous. A user who copies an unclassified spreadsheet to USB, prints a newly downloaded PDF, or uploads a file whose last evaluation used an old policy version can complete the egress before the current cloud policy is applied. JIT closes that gap by holding the egress while evaluation runs.
JIT is not a replacement for Endpoint DLP policies, not a substitute for Microsoft Defender for Endpoint removable-storage device control, and not an alert generator. Official documentation states that JIT does not create a DLPRuleMatch event or an alert . On the exam, treat JIT as a timing and coverage control that sits on top of the Devices-scoped policies you designed in the Endpoint DLP configuration chapter.
JIT candidate files and stale classification
Microsoft uses these terms in the JIT conceptual article:
Stale classification: A classification that was not produced by the current DLP policy version. After you update a policy, previously classified files stay stale until Endpoint DLP reevaluates them.
JIT candidate file: A file that DLP has not evaluated, or that has a stale classification.
JIT audit: After JIT is enabled, Endpoint DLP writes an Activity explorer event for the candidate file with JIT triggered = true and Enforcement mode = Audit .
JIT block: The egress is blocked and the event uses Enforcement mode = Block , still with JIT triggered = true .
JIT blocks egress when all of the following are true:
The user attempts an egress on a never-classified or stale item.
The user is in the JIT scope .
At least one DLP policy defines Block or Block with override for that egress activity.
The destination is not an allowed printer, USB group, network share, or URL.
Policy evaluation does not finish inside the documented resume window (Microsoft describes a five-second evaluation window before the JIT in-progress experience).
If the user is out of JIT scope , or no Block / Block with override exists for the activity, or the destination is already allowed, JIT does not block . Microsoft still records a JIT audit event in several of those cases so you can measure candidate-file volume before you tighten scope.
Supported platforms and client versions
JIT protection for Endpoint DLP supports:
- Windows 10
- Windows 11
- macOS (the three most recent released major versions)
Deploy Microsoft Defender antimalware client 4.18.23080 or later before you enable JIT. Microsoft documents an improved end-user experience in 4.18.25080 or later ; the resume timings and toast names in the conceptual article are written for that later client. Allow at least an hour for JIT setting updates—including disabling JIT—to reach clients.
To inventory client versions, Microsoft documents a Microsoft Defender portal Advanced hunting query against DeviceRegistryEvents for MsMpEng.exe . You can also open Data Loss Prevention > Diagnostics and use the Endpoint DLP not working card to check whether a specific device meets the JIT prerequisite. The device health report under Settings > Device onboarding > Device report includes a Device readiness for feature visualization that currently covers Just-in-time protection and Paste to supported browsers .
How to turn JIT on
Sign in to the Microsoft Purview portal.
Go to Settings > Data Loss Prevention > Just-in-time protection .
Under Choose which locations to monitor , select Devices .
Under Fallback action in case of failure , start with Allow users to complete actions .
Microsoft's deployment guidance is explicit: configure and deploy Endpoint DLP policies first , then enable JIT. Enabling JIT against unclassified files before policies exist produces avoidable holds while evaluation runs and does not add a policy verdict.
Fallback action: the exam trap
- Fallback setting When it applies What happens if evaluation fails
- Allow users to complete actions Classification or policy evaluation does not complete Egress is allowed
- Block users from completing actions Classification or policy evaluation does not complete Egress is blocked
Microsoft's caution: do not choose Block until you understand the impact on users and help-desk volume.
Keep these two levers separate:
JIT Block versus JIT Audit for candidate files is controlled by whether the user is in JIT scope and whether a policy uses Block / Block with override—not by the fallback dropdown.
Fallback is the enforcement mode when evaluation fails . Microsoft also applies it after the JIT in progress extra wait if evaluation still has not finished.
Either fallback still writes telemetry to Activity explorer .
If an exam item says classification failed on a JIT-scoped device, the answer is the fallback setting. If it says the user is in JIT scope and evaluation is still running , the answer is the JIT hold , not fallback.
Timing, resume, and toasts
Microsoft documents this sequence for the 4.18.25080 or later client:
Evaluation starts.
Activities that support pause and resume and finish within three seconds apply the policy action. For audit , the copy resumes with no toast. For block or block with override , the user sees the policy message.
Items that need more time get two additional seconds (about five seconds total).
If evaluation still is not done, Endpoint DLP blocks the activity, shows the Just-in-time in progress toast (a notification, not an alert), and logs a JIT block event.
The in-progress state waits up to 30 more seconds .
If evaluation finishes in that window, the user sees Just-in-time evaluation complete and must retry the activity.
If evaluation still does not finish, the fallback action is applied.
Resume within three seconds is documented only for:
- Copy to a removable media
- Copy to a network share
The user must repeat these after evaluation completes:
- Copy or move using Remote Desktop Protocol (RDP)
- Copy or move using an unallowed Bluetooth app
- Copy to clipboard (JIT Audit by default )
Copy to clipboard is JIT Audit by default. The additional setting Control copying to clipboard can block clipboard copy while JIT is evaluating . Microsoft warns that this setting can hurt productivity; test it before you enable it broadly.
Egress activities JIT can audit or block
JIT audits and blocks these user egress activities on protected items:
- Copy to a removable media
- Copy to a network share
- Copy or move using RDP
- Copy or move using a blocked Bluetooth app
- Copy to clipboard (JIT Audit by default)
- Upload to a restricted cloud service domain
JIT is not the control that classifies files at rest on a file server. Server onboarding, Enable Endpoint DLP for Windows Servers , and on-premises repository DLP remain separate topics.
Network share coverage and JIT
Network share coverage and exclusions lives under Endpoint DLP settings, not inside the JIT blade. It extends Devices-scoped DLP to new and edited files on network shares and mapped drives . If JIT is also enabled, JIT coverage and exclusions are extended to those same shares and drives. Exclude a specific UNC path for all monitored devices with Exclude these network share paths .
Microsoft publishes this matrix:
- Network share coverage Just-in-time protection Resultant behavior
- Enabled Disabled Devices-scoped DLP policies apply to network shares and mapped drives the device connects to
- Disabled Enabled JIT applies only to files on storage that is local to the endpoint
- Enabled Enabled Devices-scoped DLP and JIT both apply to network shares and mapped drives
If JIT is on but users still exfiltrate unclassified files over a mapped drive, the exam answer is often enable Network share coverage and exclusions , not that JIT is broken. JIT also does not block when the destination is already an allowed network share group, printer group, USB group, or URL—those allowed-group exceptions short-circuit the JIT hold.
Network share coverage complements DLP on-premises repository actions; it does not replace them. Devices-scoped actions protect the endpoint's copy/move/print path. On-premises repository policies protect data at rest in file shares and SharePoint document libraries when that location is in scope.
Exclusions: JIT-only versus Endpoint DLP-wide
Fine-tune JIT with:
- App exclusions for Windows — maximum 50 apps
- App exclusions for Mac — maximum 50 apps
- File extension exclusions — those extensions are not evaluated by JIT
- File path exclusions for Windows / Mac — those locations are not evaluated by JIT
Microsoft contrasts JIT path exclusions with Data loss prevention > Settings > Endpoint settings > File path exclusions for Windows :
JIT file path exclusions skip JIT only . Endpoint DLP still classifies and protects files in those folders.
Endpoint settings file path exclusions skip all Endpoint DLP classification and protection under those folders.
If the requirement is do not JIT-hold developer build folders, but still apply USB block policies, use JIT path exclusions. If the requirement is never inspect or restrict anything under a scratch volume, use Endpoint settings path exclusions.
Offline Windows devices
On Windows , policies already on the device keep applying to files that were already classified as sensitive after the device goes offline. With JIT enabled and the fallback in block mode, a new file created offline is prevented from being shared until the device reconnects to the data classification service and evaluation completes. Policy updates made while the device is offline apply after it reconnects. Microsoft states that this offline JIT behavior is not supported on macOS .
Staged rollout Microsoft documents
Confirm antimalware version and JIT feature readiness.
Publish Devices-scoped policies (simulation, then enforce).
Enable JIT with Allow fallback and a small user scope .
In Activity explorer, count unique devices firing JIT events ( N ) versus devices in the deployment scope ( S ). N/S estimates how many machines may see a JIT block when you expand scope.
Add app, path, and extension exclusions; decide whether Control copying to clipboard is worth the productivity cost.
Only then consider Block fallback.
Exam traps
Enabling JIT does not by itself block USB copy; you still need a Devices-scoped rule with Block or Block with override for that activity.
Fallback Allow versus Block is not the same as JIT Audit versus JIT Block.
JIT path exclusions are not the same as Endpoint settings path exclusions.
JIT toasts are not alerts ; do not hunt JIT holds on the DLP Alerts dashboard.
Do not invent unpublished numeric caps (for example a tenant-wide maximum of JIT-scoped users). Microsoft publishes the 50-app exclusion ceilings and the 3 / 5 / 30 second evaluation windows; it does not publish a fixed maximum device count for JIT.
- Official resources
- Learn about Endpoint DLP just-in-time protection
- Get started with Endpoint DLP just-in-time protection
- Configure endpoint DLP settings (network share coverage)