Cyber Cloud Ops Logo
Microsoft Intune

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro

By Admin User
June 20, 2025
10 min
Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro

Today, we’re exploring how to control the visibility of recent Jump Lists on the Windows Start Menu and Taskbar using an Intune policy.

The Start menu provides a wide range of customization options through Intune, including nearly 41 categories of policy settings. One of these is “Hide Recent Jump Lists”, which allows you to manage whether users can see recently opened files when right-clicking an app pinned to the Start menu or taskbar.

🔐 Why This Setting Matters

Enabling this policy can help enhance privacy and reduce visual clutter, especially in shared-use scenarios such as training rooms, reception kiosks, or shift-based workstations. When applied, the policy:

  • Prevents users from seeing recently opened items in Jump Lists.

  • Automatically disables the toggle in Settings > Personalization > Start (the option becomes grayed out).

  • Helps enforce privacy standards and a clean UI across endpoints.

⚙️ What Happens When the Policy is Enabled?

Once this policy is enabled and the device is rebooted:

  • Jump Lists are no longer visible on both the Start menu and taskbar.

  • The option “Show recently opened items in Jump Lists” in the Settings app becomes grayed out, preventing users from changing it.

  • A system restart is required for the changes to take full effect.

This enforces the configuration at the system level, leaving no room for user override.

📋 What Does the Policy Actually Do?

The "Hide Recent Jump Lists" policy directly interacts with the Start Menu configuration layer through CSP (Configuration Service Provider). It works by targeting this OMA-URI setting:

  • OMA-URI: ./Vendor/MSFT/Policy/Config/Start/HideRecentJumplists

  • Data Type: Integer

  • Value: 1 = Hide Jump Lists 0 = Show Jump Lists (default behavior)

When set to 1, Jump Lists are disabled, and the user-facing toggle is locked down in Settings. This makes it a powerful tool for managing consistency, security, and user experience across corporate endpoints.

📌 CSP Reference

Understanding the underlying CSP is essential when deploying this policy using Intune's custom configuration profiles. The screenshot below (insert here if needed) provides visibility into the actual setting path used by Windows to enforce this behavior.

⚠️ Important Notes

  • This setting is supported on both Windows 10 and Windows 11. The HideRecentJumplists policy works on both operating systems and is enforced through the same OMA-URI path.

  • 🔁 A system reboot is required for the policy to take full effect on the device.

  • 🧪 As always, it's recommended to test the configuration in a pilot group before deploying it at scale in production environments.

Bonus Tip: You can use either the ./Device/... or ./User/... CSP path depending on whether you're targeting device-level or user-level scope via Intune.

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 1 Credits to Microsoft

This is a simple but powerful way to improve endpoint hygiene and privacy. Whether you’re managing shared devices or fine-tuning the user experience, Jump List control is a great example of the precision Intune offers.

Creating the Intune Policy Profile

Now that you've reviewed the CSP details, it's time to create the policy in Intune.

Follow the steps below to begin the deployment process:

Sign in to the Microsoft Intune admin center.

  1. In the left-hand menu, select Devices

  2. Click on Windows Devices under the “By platform” section

  3. Select Configuration

  4. Click + New Policy to begin configuring your policy

  5. Under Platform, select Windows 10 and later

  6. For Profile type, choose Settings catalog

  7. Click Create to proceed

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 2

Once the profile is created, you’ll be able to define the specific setting to manage Jump Lists visibility using the Settings Catalog.

Basic Information of the Policy

After initiating the profile creation, the next step is to complete the Basics section. This involves entering a clear and descriptive policy name, an optional description, and reviewing the platform information.

The Platform is automatically set to Windows 10 and later, so no changes are needed here.

Providing a meaningful name and description will help ensure the policy is easy to identify and maintain in the future, especially in environments with multiple custom configurations.

  • Policy Name: Manage Jump Lists Visibility on Start Menu and Taskbar

  • Description: This policy controls the visibility of recent items in Jump Lists on the Windows Start menu and taskbar. It can be used to enhance privacy, reduce clutter, or standardize the user experience, especially on shared devices.

To help you verify that the policy is working as expected, the following table outlines the exact steps to test Jump List visibility before and after the setting is enforced:

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Table 1
Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 3

Select the Setting Using the Settings Picker

Now that you're in the Configuration settings tab, it's time to add the specific policy setting. Follow the steps below, referencing the image provided:

  1. Click on + Add settings to open the Settings Picker window.

  2. In the search bar, type Hide Recent Jump.

  3. Click Search to locate the available settings.

  4. From the filtered results, select the Start category.

  5. Choose Hide Recent Jumplists (User).

  6. Set the policy to Enabled.

  7. Click Next to continue configuring the profile.

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 4

We're applying this policy at the user level in this example, which is ideal for environments with individual user preferences or profiles.

💡 Tip: By default, this setting appears as "Disabled". In this case, we are switching it to "Enabled" to hide recently opened items from Jump Lists and prevent users from viewing them.

Add Scope Tags to a Policy

Now you are on the next step called Scope Tags. A scope tag is used to assign policies to specific groups within an organization. In this step, you can select a scope tag for the policy. However, I suggest skipping this section because it is not needed for this policy. So, I clicked Next to continue.

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 5

Assigning the Policy

The next step is the Assignments section, where you define which user or device groups will receive the policy.

Since our goal is to target a specific group, this step is essential for proper deployment.

  • Under Include groups, click Add groups.

  • A window will appear showing available Azure AD groups.

  • Use the search bar to quickly locate the group you want to assign the policy to.

  • Select the desired group and confirm your choice.

Once the group is selected, click Next to proceed to the final step.

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 6

Review + Create – Finalizing the Policy

After completing the Assignments step, you'll reach the final stage: Review + Create.

This tab provides a full summary of all the information you've entered, including:

  • Basic details (name, description, platform)

  • Configuration settings you've defined

  • Targeted assignment groups

Carefully review each section to ensure everything is correct and aligned with your deployment goals.

Once everything looks good, click Create to finalize and deploy the policy.

Your configuration will now be applied based on the assignment scope you defined.

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 7

Monitoring Status – Verifying Policy Deployment

After creating and assigning the policy, it's important to monitor whether it has been successfully applied to the target devices.

You can wait for the automatic sync cycle (which may take up to 8 hours), or you can manually trigger a sync using the Company Portal app to accelerate the process.

Once the device has synced, follow these steps to verify the deployment status in the Intune admin center:

  1. Navigate to Devices > Configuration Profiles.

  2. In the list of configuration profiles, use the search bar to locate your policy by name. In this example, we named the policy: 👉 “Manage Jump Lists Visibility on Start Menu and Taskbar”

  3. Click on the policy name to open its details.

  4. Here, you'll see the deployment status, including how many devices have successfully received the policy, how many are pending, and any errors if applicable.

Monitoring ensures the configuration is working as expected and allows for quick troubleshooting if needed.

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro - Fig. 8

Client-Side Verification – Hide Recent Jump Lists Policy

The Hide Recent Jump Lists policy is enforced by the MDM PolicyManager under the Start category. Once deployed via Intune, you can verify whether the policy has been successfully applied directly on the client device using the Event Viewer.

How to Verify on the Client:

  1. Open Event Viewer on the Windows device where the policy was targeted.

  2. Navigate to: Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin

  3. In the right-hand panel, click Filter Current Log.

  4. Filter for Event ID 813, which confirms that a policy has been successfully applied.

  5. Open the event details to check if the HideRecentJumplists policy is listed and reflects the expected value.

Example Log Output (Descriptive Format):

When the policy is applied, an Event ID 813 entry typically includes:

  • Policy Name: HideRecentJumplists (or HideRecentJumplists_User if applied at user level)

  • Policy Area: Start (indicating the category within the CSP structure)

  • Enrollment ID: Unique identifier generated during MDM enrollment (e.g., B1E9301C-8666-412A-BA2F-3BF8A55BFA62)

  • Current User: Usually set to User if deployed at the user level, or Device for device scope

  • Integer Value (Int Value): 0x1 means the policy is Enabled (i.e., hiding recent items), while 0x0 means Disabled

  • Enrollment Type: Commonly shown as 0x6, representing MDM-managed devices

  • Scope: Typically 0x1 for user-level policies, and 0x0 for device-level policies

💡 Important Tip:

⚠️ Note: Values such as Enrollment ID, scope, and user/device context may vary depending on deployment method and session. Always confirm that the policy name (HideRecentJumplists) and the configured value (Enabled or Disabled) match the intended settings defined in Intune.

🛠️ Troubleshooting Tips:

  • ✅ Make sure the device has recently synced with Microsoft Intune

  • 🔄 Confirm the target Azure AD group includes the device or user

  • ⚔️ Check for conflicting settings in other configuration profiles

  • 🔧 Trigger a manual sync via the Company Portal app or the Intune Admin Center

  • 📚 For deeper diagnostics, consult the official Microsoft Learn CSP documentation or enable advanced MDM logs

📚 More Information

To deepen your understanding of configuring and managing the Hide Recent Jump Lists policy using Microsoft Intune, refer to the following official Microsoft Learn resources:

Thank you!

🖥️ Ricardo Barbosa

📘 MCT Microsoft Certified Trainer | ☁️ Cloud Architect

🌐 Technology Director - https://altelix.com

Originally published on LinkedIn · June 20, 2025 · read the original article
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

Modern Endpoint Customization: Manage Windows Jump Lists via Intune Like a Pro | CyberCloudOps Blog