Cyber Cloud Ops Logo
Microsoft Intune

Hardening Windows Endpoints: Storage Sense Configuration with Microsoft Intune

By Admin User
August 14, 2026
13 min
Hardening Windows Endpoints: Storage Sense Configuration with Microsoft Intune

A forgotten download folder can hold more forensic evidence than a full audit log.

Windows accumulates data constantly: temporary installer files, browser caches, items sitting in the Recycle Bin, and downloads nobody remembers requesting. Storage Sense is the built-in Windows feature designed to clean this up automatically, based on thresholds you define rather than leaving it to chance or user memory.

Left unmanaged, that accumulation is not just a disk space problem. Stale files linger long after their purpose has expired, expanding the window during which sensitive documents, cached credentials, or leftover installers remain recoverable on disk.

The AllowStorageSenseGlobal setting controls whether Storage Sense is enabled at all on a device. When turned on, Windows begins evaluating storage pressure and automatically clears eligible temporary files, recycle bin contents, and unused downloads according to the configured cadence.

Enforcing this through Microsoft Intune removes the guesswork. Instead of relying on individual users to enable Storage Sense manually (or never doing so), every managed endpoint applies the same cleanup behavior, at the same thresholds, without exception.

The result is an environment where local storage stays lean, residual data has a shorter shelf life, and IT no longer depends on manual cleanup tickets to keep endpoints healthy.

Why This Policy Matters

Attackers and forensic investigators alike look for what a system was doing recently, and stale local files are often the easiest evidence to find. Uncontrolled disk accumulation also degrades performance over time, creating support overhead that has nothing to do with security but consumes the same IT hours.

Storage Sense closes this gap quietly, in the background, without requiring end-user action or awareness.

Without this policy:

  • Temporary files and cached data persist indefinitely, extending the exposure window for sensitive content
  • Recycle Bin items remain recoverable long after deletion was intended, undermining assumptions of data removal
  • Disk space pressure builds silently until users experience slowdowns or failures, generating avoidable support tickets
  • Cleanup depends entirely on individual user habits, resulting in wildly inconsistent storage hygiene across the fleet

With this setting enforced through Intune:

  • Storage Sense runs automatically on every managed device, with no dependency on user action
  • Temporary and stale files are cleared on a predictable, organization-defined cadence
  • Disk space pressure is proactively managed, reducing performance-related support requests
  • Storage hygiene becomes a fleet-wide, auditable standard rather than an individual habit

This configuration aligns with modern security principles such as defense in depth, endpoint hardening, proactive threat detection, and Zero Trust architecture.

Security Governance

Security governance ensures that hardening controls are consistently applied, monitored, and aligned with organizational standards.

Without centralized governance, settings such as this one can drift across devices, leaving blind spots that attackers can exploit.

Managing the Allow Storage Sense setting through Microsoft Intune brings several governance benefits:

  • Centralized enforcement of the control across all managed Windows endpoints
  • Consistent configuration aligned with corporate security baselines
  • Clear visibility into deployment status and configuration compliance
  • Defined ownership and accountability through scope tags and role-based administration
  • An auditable policy lifecycle from creation to enforcement and validation

This level of governance ensures that the control is handled in a controlled and transparent manner, reinforcing compliance with internal security policies and regulatory frameworks.

Windows CSP Overview

This section explains how the setting is exposed at the operating system level and how Microsoft Intune interacts with it. The configuration is powered by the Windows Policy Configuration Service Provider (CSP) framework, specifically the Storage area.

AllowStorageSenseGlobal
ScopeEditionsApplicable OS
✅ Device
❌ User
✅ Pro
✅ Enterprise
✅ Education
✅ IoT Enterprise / IoT Enterprise LTSC
✅ Windows 10, version 1903 [10.0.18362] and later
Device📋 Copy
./Device/Vendor/MSFT/Policy/Config/Storage/AllowStorageSenseGlobal

Storage Sense can automatically clean some of the user's files to free up disk space. By default, Storage Sense is automatically turned on when the machine runs into low disk space and is set to run whenever the machine runs into storage pressure. This cadence can be changed in Storage settings or set with the "Configure Storage Sense cadence" group policy.

Enabled:

Storage Sense is turned on for the machine, with the default cadence as 'during low free disk space'. Users can't disable Storage Sense, but they can adjust the cadence (unless you also configure the "Configure Storage Sense cadence" group policy).

Disabled:

Storage Sense is turned off the machine. Users can't enable Storage Sense.

Not Configured:

By default, Storage Sense is turned off until the user runs into low disk space or the user enables it manually. Users can configure this setting in Storage settings.

Description Framework Properties

This section defines how the configuration behaves at a technical level within the CSP framework.

Property nameProperty value
Formatint
Access TypeAdd, Delete, Get, Replace
Default Value0

Allowed Values

This section defines the valid configuration values supported by the setting. It accepts the following options:

ValueDescription
1Allow.
0 (Default) (Default)Block.

Group Policy Mapping

For organizations operating in hybrid environments, this CSP setting maps to a corresponding Group Policy configuration.

NameValue
NameSS_AllowStorageSenseGlobal
Friendly NameAllow Storage Sense
LocationComputer Configuration
PathSystem > Storage Sense
Registry Key NameSoftware\Policies\Microsoft\Windows\StorageSense
Registry Value NameAllowStorageSenseGlobal
ADMX File NameStorageSense.admx

Security Considerations

Before enabling this policy, administrators should understand how it behaves and plan for its impact.

  • Once enabled centrally, users cannot disable Storage Sense locally, so cleanup cadence should reflect real business needs rather than an arbitrary default
  • Aggressive cadences can remove files from the Downloads folder or Recycle Bin that users still expect to find, so pilot testing with representative user groups is essential
  • The setting requires Windows 10 version 1903 or later; earlier builds will report the policy as not applicable
  • Storage Sense operates independently of Defender and BitLocker, and should be treated as a complementary hygiene control rather than a replacement for data loss prevention

A phased, pilot-first deployment is recommended to validate the behavior in a controlled group and avoid unexpected impact before rolling the setting out across production devices.

How to Configure Allow Storage Sense Using Intune (Settings Catalog)

You can enforce this policy centrally using the Intune Settings Catalog, ensuring that Storage Sense runs automatically on every managed device is applied consistently across all managed Windows devices.

To begin, sign in to the Microsoft Intune admin center and follow the steps below, as illustrated in the screenshots.

Create the Configuration Profile

In the Microsoft Intune admin center:

  • Navigate to Devices Windows Configuration
  • Select + Create policy

In the Create a profile pane:

  • Platform: Windows 10 and later
  • Profile type: Settings catalog

Click Create to continue.

Creating the Settings Catalog configuration profile with Microsoft Intune
Storage Sense Hardening with Microsoft Intune - Fig. 01

At this stage, you have created the foundation of a Settings Catalog policy. In the next steps, you will search for and configure the setting that enables Storage Sense and enforces automatic cleanup on managed devices.

Define Basic Profile Details

After clicking Create, the next step is to define the basic details of the configuration profile. This stage is essential for long-term management, clarity, and governance within Microsoft Intune, especially in environments with multiple endpoint hardening policies and security baselines.

Providing a clear Name and a concise but meaningful Description ensures that the purpose of the policy is immediately understood by administrators and security teams in the future. As shown in the screenshot, configure the fields as follows.

Name: WIN – Endpoint Hardening – Storage Sense
Description: This policy enables Storage Sense and defines thresholds for automatic cleanup of temporary files, recycle bin contents, and unused downloads on managed Windows endpoints. Reducing local accumulation of stale data lowers disk pressure and limits the residual footprint of sensitive files after use. It complements Defender and BitLocker controls by keeping endpoint storage state predictable and reducing manual cleanup tickets.
Defining the policy name and description in the Basics tab with Microsoft Intune
Storage Sense Hardening with Microsoft Intune - Fig. 02

The Platform field is already pre-selected as Windows, so no changes are required. Once the name and description are defined, click Next to proceed to the configuration settings.

Configure the Setting Using the Settings Picker

With the profile basics defined, the next step is to configure the policy using the Settings picker, where you select the exact Windows setting you want to enforce. To open the Settings picker panel, click Add settings.

By default, Storage Sense remains off until a user manually enables it or the device runs into low disk space, leaving cleanup entirely to chance.

In the search field at the top of the Settings picker, type Storage Sense Global, and then click Search to filter the results.

From the returned results, select the category Storage, and then choose the setting Allow Storage Sense Global. Once selected, the setting is automatically added to the configuration profile. Back on the configuration page, change the value from its default state to Enabled.

When enabled, Windows automatically turns on Storage Sense with its default cadence and begins clearing eligible temporary files, recycle bin contents, and unused downloads without user intervention. This ensures that:

  • Cleanup runs consistently across every managed device, regardless of individual user settings
  • Disk pressure and residual data footprint are proactively reduced before they become a problem
  • The organization has a predictable, auditable baseline for local storage hygiene

This configuration aligns with modern endpoint hardening practices and supports Zero Trust security principles.

Selecting and enabling the setting with Microsoft Intune
Storage Sense Hardening with Microsoft Intune - Fig. 03

Configure Scope Tags (Optional)

Scope tags are used to control who can view and manage this policy within the Microsoft Intune admin center. They are particularly useful in environments with delegated administration, multiple IT teams, or regional management models.

As shown in the screenshot, the Default scope tag is selected. This is the standard and recommended configuration for most environments, as it ensures the policy is visible to all administrators who have access to Intune.

Optionally, custom scope tags can be assigned if you need to:

  • Restrict policy visibility to specific IT roles or teams
  • Enforce administrative separation of duties
  • Support delegated or region-based Intune management

If no additional scope tags are required, keep the Default selection and click Next to continue.

Keeping the Default scope tag with Microsoft Intune
Storage Sense Hardening with Microsoft Intune - Fig. 04

Assignments – Storage Sense

After configuring the policy settings, the next step is to assign the policy to the appropriate target group. Assignments define which devices will receive and enforce this configuration, ensuring the policy is applied in a controlled and intentional manner.

In the Assignments tab, click Add groups under Included groups and search for the group you want to target. This approach allows you to deploy the policy gradually, starting with test devices before expanding to production.

As shown in the screenshot, the policy is assigned to the following group: GRP – MS365Education – Test Computers.

Once the group is selected, verify the following:

  • The group appears under Included groups
  • The group status is Active
  • No assignment filters are applied (unless explicitly required)

At this stage, no Excluded groups are configured, which is appropriate for controlled test deployments.

Assigning the policy to the target group with Microsoft Intune
Storage Sense Hardening with Microsoft Intune - Fig. 05

After confirming the assignment, click Next to proceed to the Review + Create step.

Review + Create – Final Validation

The Review + Create step is the final checkpoint before deploying the policy. This is where you validate that all configurations are correct and aligned with your intended endpoint hardening objective.

Pay special attention to the following items:

  • Policy name and description: confirm that the policy clearly reflects its purpose, enabling Storage Sense to enforce automatic local cleanup on managed devices
  • Configuration settings: verify that Allow Storage Sense is set to Enabled, under Storage
  • Scope tags: ensure the correct scope tag is assigned. In this example, the Default scope tag is used
  • Assignments: confirm the policy is assigned to the intended group, GRP – MS365Education – Test Computers, and that no unintended exclusions are configured

Once everything has been validated, click Create to finalize and deploy the policy to the assigned devices.

Reviewing and creating the policy with Microsoft Intune
Storage Sense Hardening with Microsoft Intune - Fig. 06

Monitor Policy Deployment Status

After creating and assigning the WIN – Endpoint Hardening – Storage Sense configuration profile, the next step is to verify its deployment status. This validation confirms that the policy has been successfully applied and that automatic Storage Sense cleanup is active on the targeted devices.

Although Microsoft Intune can take up to 8 hours to automatically deliver configuration profiles, deployment often occurs much faster. If needed, you can accelerate the process by:

  • Triggering a manual device sync from the Company Portal
  • Initiating a sync directly from the Microsoft Intune admin center

Intune provides clear indicators to evaluate the policy deployment status: Succeeded (devices have applied the policy), In progress (devices are still processing), Error (the policy failed and requires investigation), and Not applicable (the device does not support the configuration).

When devices report Succeeded, it confirms that Storage Sense is actively enforced on the endpoint, ensuring that stale temporary files, recycle bin contents, and unused downloads are cleared on a predictable cadence.

Monitoring the policy deployment status with Microsoft Intune
Storage Sense Hardening with Microsoft Intune - Fig. 07

Client-Side Verification via Event Viewer

After the device has synced with Intune, you can perform a client-side verification to confirm that the policy was successfully applied. Windows records Intune policy processing events locally, allowing administrators to confirm policy enforcement without relying only on the Intune portal.

  • Open Event Viewer on the target device
  • Navigate to Applications and Services Logs Microsoft Windows DeviceManagement-Enterprise-Diagnostics-Provider Admin
  • Select Filter Current Log
  • Look for Event ID 813 or Event ID 814, which indicate successful processing of Intune configuration policies
  • Open the event details and confirm that the Storage setting was applied

For deeper validation, you can confirm the effective setting directly on the device. Check the registry path HKLM\SOFTWARE\Policies\Microsoft\Windows\StorageSense\AllowStorageSenseGlobal and confirm the value is set to 1, or open Settings > System > Storage on the device and verify that Storage Sense appears as enabled and greyed out for user editing.

Remember that once enforced through policy, the toggle in Storage settings becomes read-only for the end user, confirming the setting is being managed centrally rather than locally.

Why This Matters for Endpoint Security

Local storage is often overlooked in endpoint security conversations, which tend to focus on network traffic, identity, or malware detection. Yet the files sitting quietly on disk are frequently the easiest target once an attacker or an unauthorized user gains local access.

Without automated cleanup, every managed device slowly becomes a growing archive of temporary data, cached artifacts, and deleted-but-recoverable files, an expanding blind spot that no firewall or antivirus rule addresses.

By enforcing Allow Storage Sense through Microsoft Intune and validating the configuration locally, organizations ensure that:

  • Residual sensitive data has a shorter lifespan on every managed endpoint
  • Disk hygiene becomes a consistent, fleet-wide standard rather than a user-dependent habit
  • Support overhead tied to low disk space incidents is measurably reduced
  • Storage-related hardening complements existing Defender and BitLocker controls, not replaces them

This configuration provides strong security value without disrupting standard user workflows when properly validated and deployed.

Key Takeaway

Good endpoint hardening is not only about blocking threats, it is also about reducing the amount of exploitable data sitting idle on disk.

Enforcing Allow Storage Sense through Microsoft Intune guarantees that every managed device applies the same cleanup cadence, without depending on individual user awareness or discipline.

Combined with centralized deployment and client-side validation, the organization gains a predictable, auditable storage baseline across the entire Windows fleet.

And in modern security architecture, controlling residual data footprint is not optional, it is essential.

More Information

For additional technical details, refer to the official Microsoft documentation below:

Thank you for reading!

🖥️ Ricardo Barbosa

🏆️ Microsoft MVP | 📘 Microsoft Certified Trainer (MCT)

☁️ Intune & Cloud Architect | 💼 Technology Director at Altelix.com

💬 Follow me for more Windows endpoint hardening and Intune content.

Tags:
MicrosoftIntune
EndpointManagement
Windows11
DeviceManagement
ModernWorkplace
MEM
ITPro
ZeroTrust
MVPBuzz
Keep reading

The full Hardening Windows Endpoints series

One control at a time, with the exact policy paths, the detection and remediation scripts, and the reporting to prove it worked across the fleet.

Browse all articles
Need a hand

Rolling this out across a real fleet?

Reading the guide is the easy part. Designing it for thousands of devices, piloting it without breaking production and proving compliance afterwards is the hard part. That is what we do at ISolutions CloudX.

Talk to ISolutions CloudX

Written by Ricardo Barbosa, Microsoft MVP and MCT. New guide every Wednesday and Friday. Follow on LinkedIn to get the next one.

Posts Sugeridos

Hardening Windows Endpoints: Storage Sense Configuration with Microsoft Intune | CyberCloudOps Blog