Anavem
Languagefr
How to Control Offline Files Sync on User Logoff with Intune Policy

How to Control Offline Files Sync on User Logoff with Intune Policy

Configure Microsoft Intune policies to manage offline files synchronization behavior during user logoff on Windows devices, ensuring data consistency for remote and mobile users.

April 1, 2026 15 min
hardintune 9 steps 15 min

Why Control Offline Files Synchronization During User Logoff?

Offline files synchronization during user logoff is a critical aspect of modern enterprise mobility management. When users work remotely or travel frequently, their devices must maintain data consistency between local cached files and network resources. Without proper synchronization control, organizations face risks including data loss, version conflicts, and compliance issues.

Microsoft Intune's offline files synchronization policies provide administrators with granular control over how Windows devices handle file synchronization when users log off. This capability is essential for organizations supporting remote work, where employees regularly disconnect from corporate networks and need reliable access to business-critical files.

What Are the Key Benefits of Intune Offline Files Management?

Implementing Intune-managed offline files synchronization delivers several organizational benefits. First, it ensures data consistency across all user devices by enforcing standardized synchronization behavior. Second, it provides administrators with centralized control over synchronization timing, reducing the risk of incomplete file transfers that could lead to data corruption or loss.

The policy also addresses performance considerations by allowing organizations to balance data integrity requirements against user experience. Administrators can choose between full synchronization for maximum data consistency or quick synchronization for faster logoff times, depending on their specific business requirements and user workflows.

How Does Intune Administrative Templates Handle Offline Files?

Intune leverages Windows Administrative Templates to manage offline files synchronization through the "Synchronize all offline files before logging off" policy setting. This approach provides the same level of control traditionally available through Group Policy but extends it to cloud-managed devices that may not have direct domain connectivity.

The implementation uses Microsoft's Policy Configuration Service Provider (CSP) framework, ensuring compatibility with modern Windows management practices while maintaining the robust functionality that enterprises require for offline files management in hybrid work environments.

Implementation Guide

Full Procedure

01

Access Intune Admin Center and Create Configuration Profile

Start by signing into the Microsoft Intune admin center with your administrative credentials. Navigate to the configuration profiles section where you'll create a new policy specifically for offline files management.

Open your browser and go to https://endpoint.microsoft.com. Once logged in, follow this navigation path:

Devices > Configuration > +Create > +New Policy

Select the following options:

  • Platform: Windows 10 and later
  • Profile Type: Administrative Templates

Click Create to proceed to the configuration wizard.

Pro tip: Use descriptive naming conventions like "OfflineFiles-SyncOnLogoff-Production" to easily identify policies later when managing multiple configurations.

Verification: Confirm you're in the Administrative Templates creation wizard by checking the breadcrumb navigation shows "Devices > Configuration > Create profile > Administrative Templates".

02

Configure Basic Profile Information

Set up the foundational details for your offline files synchronization policy. This information helps identify and manage the policy across your organization.

Fill in the following fields in the Basics tab:

Name: Offline Files Sync Control Policy
Description: Controls offline files synchronization behavior during user logoff to ensure data consistency for remote workers
Platform: Windows 10 and later

Click Next to proceed to the configuration settings. The name and description you choose here will appear in all policy reports and troubleshooting logs, so make them descriptive enough for other administrators to understand the policy's purpose.

Warning: Avoid generic names like "Policy1" or "Test Policy" in production environments as they make troubleshooting and policy management extremely difficult.

Verification: Review the summary information displays correctly before proceeding to the next step.

03

Locate and Add Offline Files Synchronization Setting

Use the Settings Picker to find the specific offline files policy that controls synchronization behavior during user logoff. This is the core setting that determines how Windows handles offline file updates when users sign out.

In the Configuration settings tab, click Add settings to open the Settings Picker. Use the search functionality to locate the offline files policy:

Search term: "Offline Files"
Setting name: "Synchronize all offline files before logging off"

Select the checkbox next to this setting and click Add selected. The setting will now appear in your configuration profile with three possible states:

  • Not configured: Uses Windows default behavior
  • Enabled: Forces full synchronization during logoff
  • Disabled: Performs only quick synchronization during logoff

Verification: Confirm the setting "Synchronize all offline files before logging off" appears in your configuration settings list with a dropdown showing the three configuration options.

04

Configure Synchronization Behavior Settings

Choose the appropriate synchronization behavior based on your organization's requirements for data consistency versus logoff speed. This decision impacts both user experience and data integrity.

Select one of the following configurations:

Option A: Enable Full Synchronization (Recommended for Critical Data)

Setting: Enabled
Behavior: Complete synchronization of all offline files
Logoff time: Increased (may take several minutes)
Data consistency: Maximum

Option B: Quick Synchronization (Recommended for Performance)

Setting: Disabled
Behavior: Quick synchronization only
Logoff time: Minimal
Data consistency: Good but not guaranteed latest updates

For most enterprise environments handling sensitive data, choose Enabled to ensure complete data synchronization. This guarantees that all offline files are fully updated with network versions before the user logs off.

Pro tip: Test both configurations in a pilot group first. Monitor logoff times and gather user feedback before deploying organization-wide.

Verification: The setting shows your selected configuration (Enabled/Disabled) and displays the expected behavior description.

05

Configure Advanced Offline Files Registry Settings

Enhance your offline files configuration with additional registry-based settings that control cache size, encryption, and logging. These settings provide granular control over offline files behavior.

Create a separate Custom OMA-URI configuration profile for advanced settings. Navigate to:

Devices > Configuration > +Create > +New Policy
Platform: Windows 10 and later
Profile Type: Custom

Add the following OMA-URI settings:

<!-- Enable Offline Files Service -->
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/ADMX_OfflineFiles/Pol_Enabled
Data Type: String
Value: <enabled/>

<!-- Set Cache Size (2GB) -->
OMA-URI: ./Device/Vendor/MSFT/Registry/HKLM/SYSTEM/CurrentControlSet/Services/CSC/Parameters/CacheSize
Data Type: Integer
Value: 2048

<!-- Enable Encryption -->
OMA-URI: ./Device/Vendor/MSFT/Registry/HKLM/SYSTEM/CurrentControlSet/Services/CSC/Parameters/EncryptOfflineFiles
Data Type: Integer
Value: 1
Warning: Registry modifications can impact system stability. Test these settings thoroughly in a non-production environment before deployment.

Verification: Use PowerShell on a test device to confirm registry values are applied correctly: Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\CSC\Parameters"

06

Assign Policy to Target Groups

Deploy your offline files synchronization policy to specific user or device groups based on your organizational structure and requirements. Proper targeting ensures the policy reaches the right users without affecting unnecessary systems.

In the Assignments tab, configure the following:

Include groups: Select target Azure AD groups
Exclude groups: Add any exception groups
Filter type: Device or User based on your requirements

Common assignment strategies:

  • Remote Workers Group: Target users who frequently work offline
  • Mobile Device Group: Target laptops and tablets that travel
  • Department-Specific: Target specific departments with unique data requirements

Click Next and review all settings in the Review + create tab. Verify the policy name, settings configuration, and target assignments are correct.

Pro tip: Start with a small pilot group of 10-20 users to validate the policy works as expected before rolling out to larger groups.

Verification: Check the assignment summary shows the correct number of targeted users/devices and no conflicting group memberships.

07

Deploy and Monitor Policy Application

Complete the policy deployment and establish monitoring to ensure successful application across your target devices. Proper monitoring helps identify issues early and validates policy effectiveness.

Click Create to deploy the policy. The policy will begin applying to target devices within the next sync cycle (typically 8 hours for device policies, or immediately if devices check in).

Monitor policy deployment using these Intune reports:

Navigate to: Devices > Monitor > Device configuration
Select: Your offline files policy
View: Device status and User status tabs

Check for common deployment statuses:

  • Success: Policy applied correctly
  • Error: Policy failed to apply (check error details)
  • Conflict: Another policy is conflicting
  • Not applicable: Device doesn't meet requirements

Force immediate policy sync on test devices using Company Portal or PowerShell:

Get-ScheduledTask | Where-Object {$_.TaskName -eq "PushLaunch"} | Start-ScheduledTask

Verification: On target devices, check that users can no longer modify the offline files synchronization setting manually, confirming policy enforcement.

08

Test and Validate Synchronization Behavior

Perform comprehensive testing to ensure the offline files synchronization policy works correctly in real-world scenarios. Testing validates both the technical implementation and user experience impact.

Execute these test scenarios on pilot devices:

Test 1: Logoff Synchronization Behavior

# Create test offline files
1. Map network drive: \\server\share
2. Make files available offline
3. Modify files while offline
4. Reconnect to network
5. Log off and monitor sync behavior

Test 2: Policy Enforcement Verification

# Check policy application
1. Open Sync Center (Control Panel > Sync Center)
2. Click "Manage offline files"
3. Verify "Sync all offline files when logging on" setting is grayed out
4. Confirm users cannot change the setting

Test 3: Performance Impact Assessment

Measure logoff times before and after policy implementation:

# PowerShell script to monitor logoff duration
$StartTime = Get-Date
# User logs off here
$EndTime = Get-Date
$Duration = $EndTime - $StartTime
Write-Output "Logoff duration: $($Duration.TotalSeconds) seconds"
Pro tip: Document baseline logoff times before implementing the policy to quantify the performance impact and set user expectations appropriately.

Verification: Confirm that offline files sync according to your policy setting (full sync if enabled, quick sync if disabled) and users report acceptable logoff times.

09

Troubleshoot Common Issues and Optimize Performance

Address typical problems that arise with offline files synchronization policies and implement optimizations to improve user experience and system performance.

Common Issue 1: Slow Logoff Times

If users experience excessively long logoff times with full synchronization enabled:

# Check offline files cache size and usage
fsutil behavior query DisableDeleteNotify
fsutil behavior set DisableDeleteNotify 0

# Monitor sync progress
Get-WmiObject -Class Win32_OfflineFilesCache | Select-Object *

Common Issue 2: Sync Conflicts

Resolve file conflicts that prevent successful synchronization:

# View sync conflicts
mobsync.exe /logon

# Reset offline files cache (last resort)
csccmd /enable
csccmd /resid

Common Issue 3: Policy Not Applying

Diagnose policy application failures:

# Check policy application status
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Extension-List\{827D319E-6EAC-11D2-A4EA-00C04F79F83A}"

# Force group policy refresh
gpupdate /force
Warning: Resetting the offline files cache will remove all cached files and require users to re-sync everything. Only use this as a last resort and ensure users have network connectivity.

Verification: Run rsop.msc on affected devices to confirm the offline files policy is being applied correctly and check for any conflicting policies.

Frequently Asked Questions

What happens when Intune offline files sync policy is enabled versus disabled?+
When enabled, the policy forces a complete synchronization of all offline files during user logoff, ensuring maximum data consistency but potentially increasing logoff time. When disabled, only a quick synchronization occurs, providing faster logoffs but with less guarantee that all files reflect the latest network versions. The policy also prevents users from manually changing this setting, ensuring consistent organizational behavior across all managed devices.
Can users override Intune offline files synchronization settings manually?+
No, when the Intune policy is applied (either enabled or disabled), users cannot manually modify the "Synchronize all offline files before logging off" setting through the Windows interface. This enforcement is by design to maintain administrative control and ensure consistent policy application across the organization. Users will find the setting grayed out in the Sync Center and Offline Files configuration dialogs.
How long does offline files synchronization take during user logoff?+
Synchronization time varies significantly based on the number of cached files, file sizes, and network speed. Quick synchronization (disabled policy) typically completes in 30-60 seconds, while full synchronization (enabled policy) can take several minutes to over an hour for users with large offline file caches. Organizations should test with representative user data sets and establish baseline timing expectations before deploying the policy organization-wide.
What are the system requirements for Intune offline files management?+
The system requires Windows 10 or later devices enrolled in Microsoft Intune MDM, an active Intune subscription with administrative access, and network connectivity for policy deployment. Devices must have the offline files feature enabled (available on Windows Pro, Enterprise, and Education editions) and sufficient local storage for the offline files cache. The feature is not available on Windows Home editions or devices configured as Azure AD joined without hybrid connectivity.
How do I troubleshoot offline files sync policy not applying through Intune?+
Start by checking device enrollment status and policy assignment in the Intune admin center under Devices > Monitor > Device configuration. Verify the target device meets Windows version requirements and has the offline files feature available. Use PowerShell commands like 'gpupdate /force' to refresh policies and 'rsop.msc' to view applied policies. Check for conflicting policies, ensure proper Azure AD group membership, and review Intune device sync logs. If issues persist, reset the offline files cache using 'csccmd /resid' as a last resort.

Discussion

Share your thoughts and insights

Sign in to join the discussion