Basic Troubleshooting: The BitLocker Recovery Screen

Basic Troubleshooting: The BitLocker Recovery Screen

Reading Time: 5 minutes

The call starts with a blue screen asking for a recovery key, and a user who has never heard the word BitLocker. They think the laptop is broken, or hacked. Basic troubleshooting for a BitLocker recovery screen is two jobs: Get the user back in, then figure out why it asked so it does not happen again tomorrow.

I covered where to find BitLocker keys before. This post is the whole phone call for basic troubleshooting of BitLocker recovery, from the blue screen to closing the ticket.

What the screen is telling you

BitLocker encrypts the drive and uses the TPM chip to unlock it at startup. If something about the boot process changed, the TPM refuses to unlock the drive. Windows asks for the 48-digit recovery key instead. The screen also shows a Recovery key ID, which tells you which key to look up.

The blue BitLocker recovery screen asking for the recovery key for this drive, with instructions to use number keys or F1 to F10, the Recovery key ID, and a note to contact the organization's help desk
The default BitLocker recovery screen, with the Recovery key ID under the input box. Source: Microsoft Learn.

Basic troubleshooting for BitLocker recovery starts with that ID. Have the user read you the first 8 characters. That is enough to match the right key. On PCs joined to Entra ID, the screen may also point the user to aka.ms/aadrecoverykey.

The Alt key trick

On Windows 11 24H2 and newer, pressing Alt on the recovery screen opens Additional recovery information. It shows an error code that names the cause. E_FVE_SECURE_BOOT_DISABLED, for example, means Secure Boot got turned off. Other codes point to a missing TPM, a changed boot configuration, or too many wrong PINs. Put the code in the ticket.

The BitLocker Additional recovery information screen with the error category and code Protector E_FVE_SECURE_BOOT_DISABLED highlighted, followed by mismatched PCR 7 details
Press Alt on Windows 11 24H2 or newer to see why recovery started. Source: Microsoft Learn.

Get the user back in

Let the user do it

If your company allows it, users can get their own key from a phone or another computer. On the Company Portal website, they go to Devices, pick the PC, click Get recovery key, then Show recovery key. They can also use myaccount.microsoft.com, under Devices, then View BitLocker Keys. The key hides again after 5 minutes.

Look it up yourself

  1. Intune admin center > Devices > All devices, and open the PC.
  2. Under Monitor, click Recovery keys.
  3. Match the key ID to the one on the user's screen and click Show recovery key.
A device Recovery keys page under Monitor listing a BitLocker key ID, a Show recovery key link, and the drive type Operating system drive
The Recovery keys page for a device. This screenshot uses the older admin center branding. Source: Microsoft Learn.

The Entra admin center shows the same key under Entra ID > Devices > All devices, on the device page. Helpdesk Administrator, Cloud Device Administrator, and Intune Administrator can all read keys, and every view gets logged. Hybrid joined PCs may only have the key in Active Directory. Look on the BitLocker Recovery tab of the computer object, or right-click the domain and use Find BitLocker Recovery Password with those first 8 characters.

Reading the key out loud

The key is 48 digits in eight groups of six. Read it one group at a time and have the user type as you go. Number keys work, and so do F1 through F10, with F10 as zero. Dashes are optional. A typo in one group gets caught right there, so nobody has to start over.

Why it happened

  • BIOS or firmware update: The most common cause. Updates change the boot measurements the TPM checks.
  • BIOS settings changed: Someone turned off Secure Boot, cleared the TPM, or turned it off.
  • Boot order changed: USB, DVD, or network boot moved ahead of the hard drive. Docking and undocking can trigger it on some setups.
  • Hardware swap: A new motherboard means a new TPM, so the old seal will never match.
  • Too many wrong PINs or sign-in attempts, if your policy sets a limit.
  • Windows updates: A known issue in the April 2026 update KB5083769 made some PCs with custom BitLocker group policy ask for the key once. KB5089549 fixed it.

Ask the user what happened right before. Did a manufacturer update pop up? Did someone change a BIOS setting or boot from a USB stick? The answer goes in the ticket.

Stop it from coming back

If the same PC asks for the key on every restart, the TPM never re-sealed after the change. Sign in, open PowerShell as admin, and suspend and resume BitLocker. Microsoft's docs say this re-seals the key to the current boot setup. Restart once to make sure the prompt is gone.

Suspend-BitLocker -MountPoint "C:" -RebootCount 0
Resume-BitLocker -MountPoint "C:"

Before a planned BIOS update, run Suspend-BitLocker with -RebootCount 2, so it stays paused through the update's extra restarts.

Rotate the key

A key that someone read out over the phone is no longer a secret. Rotate it. In Intune, open the device and choose BitLocker key rotation. On the current device page it sits under Secure, and older layouts put it in the three dots menu. Help Desk Operator can do it. Rotation only works if the BitLocker policy turns on client-driven recovery password rotation and saves keys to Entra ID.

No key found

If Intune says No BitLocker key found for this device, check Entra ID and Active Directory too. If the key is nowhere, nobody can get that data back. Microsoft Support cannot recover or recreate it, and the only option left is a reset that erases the PC. Deleting a device in Entra ID also deletes its keys. Never clean up a device record while someone is stuck at this screen.

The basic troubleshooting checklist for BitLocker recovery

  1. Get the first 8 characters of the Recovery key ID, plus the Alt screen error code on 24H2 or newer.
  2. Point the user to Company Portal or My Account if self-service is allowed.
  3. Otherwise, find the key in Intune, Entra ID, or Active Directory, and read it in groups of six.
  4. Ask what changed: a BIOS update, BIOS settings, boot order, or hardware.
  5. If it keeps asking, suspend and resume BitLocker.
  6. Rotate the key afterward.
  7. Write the cause in the ticket.

What can we learn as a person

The recovery screen looks like a disaster, but the TPM is doing exactly what it was built for. Something about the boot changed, and it cannot tell whether that change is safe. So it locks everything and waits for someone with the key.

My brain does the same thing. A new manager, a new routine, a change in plans I did not see coming, and everything locks up. Nothing is wrong. The measurements just do not match what I sealed against. And if I never re-seal to the new normal, I hit the same blue screen every morning.

What change in your life is your TPM still flagging? And who do you call when you need someone to read you the key?

Win32 App Supersedence and Dependencies in Intune

Win32 App Supersedence and Dependencies in Intune

Reading Time: 5 minutes

7-Zip 22 is on 400 laptops, version 23 is out, and security wants the old one gone by Friday. Upload the new version and assign it, and you might end up with both on every machine. Win32 app supersedence tells Intune the new app replaces the old one, and dependencies make sure anything the app needs installs first.

Everything here leans on detection rules. If yours are shaky, read my post on Intune detection rules first, because supersedence trusts them completely.

Update or replace

Win32 app supersedence only works between Win32 apps. The new app can be a newer version of the same thing or a different app entirely. The Uninstall previous version toggle decides how it behaves.

  • No, an update: Intune installs the new app on top. Whether the old one goes away depends on the new installer. Use this when the vendor's installer upgrades in place.
  • Yes, a replacement: Intune uninstalls the old app first, then installs the new one. It does this even if the old app is not assigned to anyone anymore.

If a device never had the old app, it gets the new one. Company Portal only shows the newer app, so users do not see two versions to pick from.

Set up supersedence

  1. Upload the new version under Apps > All Apps > Create, pick Windows app (Win32), and work through the wizard.
  2. On the Supersedence step, click Add, pick the old app, and set Uninstall previous version.
  3. On Assignments, assign the new app. A superseding app does not inherit the old app's groups.
  4. Click Review + create.
The Intune Add App wizard for a Windows app Win32 showing the steps App information, Program, Requirements, Detection rules, Dependencies, Supersedence, and Assignments
The Win32 app wizard. Dependencies and Supersedence each get their own step. Source: Microsoft Learn.

For a Win32 app already in Intune, open it, go to Properties, and click Edit next to Supersedence. Setting this up takes the Relate permission under Mobile apps. The built-in Application Manager role has it.

Chains and limits

Supersedence chains. If B supersedes A and C supersedes B, then C wins over both. Microsoft caps a supersedence graph at about 10 apps, and its own docs say 10 in one spot and 11 in another. Retire old versions before the chain gets that long.

Auto-update for Available apps

Required apps upgrade on their own. Available apps need one more step. Edit the new app's Available for enrolled devices assignment and tick Auto-update.

  • It only updates users who installed the old app from Company Portal.
  • It takes two check-ins, roughly 8 to 16 hours, and the user has to be signed in.
  • Changing that assignment later, like removing the user from the group, wipes the user's consent. Adding them back does not bring auto-update back.
The Intune Edit assignment pane for an Available for enrolled devices assignment with the Auto-update checkbox ticked and outlined in red
The Auto-update checkbox on an Available assignment. Source: Microsoft Learn.

Dependencies

A dependency is something the app needs before it can install, like a Visual C++ runtime or .NET. Add them on the Dependencies step of the wizard, or under Properties for an app you already have.

  • Automatically install set to Yes: Intune installs the dependency first if it is missing. You do not have to assign the dependency on its own.
  • Automatically install set to No: Intune only checks for it. If it is missing, the main app is not even attempted.

Dependencies have to be Win32 apps too. One dependency graph can hold up to 100 apps, counting dependencies of dependencies. Intune installs the deepest dependencies first, but it does not promise any order between apps at the same level. If runtime B needs runtime A, make A a dependency of B instead of listing them side by side.

Dependencies do nothing on uninstall. Removing the main app leaves the runtime behind. You also cannot delete an app while another app depends on it.

When the two collide

Supersedence wins over dependencies. If app A depends on B and you supersede B with C, Intune reports a conflict. If C replaces A, B stays on the device. Keep both simple, and do not supersede a shared runtime that other apps depend on.

See the whole picture

Open any Win32 app and click Relationship viewer, right next to Device install status. It draws the app with everything it depends on and everything it supersedes. Single lines are dependencies, and double lines are supersedence.

The Intune Relationship viewer showing 7-Zip 23 superseding 7-Zip 22 and depending on three other apps, with a legend for dependency and supersedence lines
The Relationship viewer for 7-Zip 23, showing what it supersedes and what it depends on. Source: Microsoft Learn.

Install status only shows for apps that are assigned. A dependency that rides along with Automatically install has no numbers of its own unless you assign it too.

When it goes wrong

  • Old app still there after a replace: Its detection rule still finds it. Intune uninstalls, checks again, sees it, and refuses to install the new app. Fix the detection rule or the uninstall command.
  • Uninstall command fails: Environment variables like %ProgramFiles% are not expanded in the uninstall command. Use a wrapper script.
  • PowerShell scripts misbehave: powershell.exe in the install or uninstall field runs as 32-bit. Use %SystemRoot%\Sysnative\WindowsPowerShell\v1.0\powershell.exe for 64-bit.
  • 0x87D1041C: The app installed, but detection could not find it afterward. Apps that update themselves and no longer match the detection version cause this a lot.
  • One or more dependent apps failed to be installed: Check the dependency's own install status, or read the logs.
  • Pending a device reboot: An earlier install asked for a hard restart. Nothing else installs until the PC restarts.
  • A dependency that fails gets three tries, five minutes apart, then waits for the daily re-check.

On the PC, AppWorkload.log in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs shows detection, applicability, and the install for each app. Open it with CMTrace. To speed things up, sync from Company Portal under Settings, or restart the Microsoft Intune Management Extension service. When an install fails, Collect diagnostics in the install details pulls the logs for you.

A clean Win32 app supersedence routine

Upload the new version, check its detection rule, and add supersedence with Uninstall previous version set on purpose. Assign the new app to the same groups and tick Auto-update on Available assignments. Check the Relationship viewer before you go home.

What can we learn as a person

The supersedence case that gets me is the replacement that never finishes. Intune uninstalls the old app, checks again, and the detection rule still says it is there. So the new one never installs.

I did that with exercise for years. New routine, new shoes, the full replacement. Then I checked myself with the old detection rule, the one that said I am not a gym person, and it still came back true. The new version never got a chance.

What old detection rule are you still running on yourself? And what would it look for if you rewrote it for the version you are trying to install?

Intune App Configuration Policies for Outlook and Edge

Intune App Configuration Policies for Outlook and Edge

Reading Time: 4 minutes

A user adds their personal Gmail to the work Outlook app, and now company email and coupon spam share an inbox on a phone that leaves the building every night. Intune app configuration policies fix that kind of thing. They push settings into an app, like which accounts Outlook allows or which homepage Edge opens, without the user touching anything.

If the difference between managing a device and managing an app is fuzzy, start with whether Intune is MAM or MDM.

Managed devices vs managed apps

There are two kinds of app configuration policy, and picking the wrong one is the most common mistake.

  • Managed devices: For enrolled phones where Intune deployed the app. On iPhone, the app has to be installed through Intune. On Android, it has to come from Managed Google Play. Only this kind can lock Outlook to work accounts or set up the email account for the user.
  • Managed apps: For apps built with Intune's app SDK, like Outlook, Edge, and Teams, whether the phone is enrolled or not. It pairs with app protection policies and handles general app settings.
A flowchart for Outlook mobile that routes account setup and work-or-school-only accounts to a managed devices app configuration policy and general app settings to a managed apps app configuration policy
Microsoft's chart for Outlook: Account setup goes in managed devices, general settings go in managed apps. Source: Microsoft Learn.

Create one

  1. Intune admin center > Apps > Configuration > Create, then pick Managed devices or Managed apps.
  2. Name it. For managed devices, pick the platform and the targeted app. For managed apps, find the app under Select public apps.
  3. On Settings, use the configuration designer, or paste XML on iPhone and JSON on Android.
  4. Assign it to groups, then click Review + create.
The Intune app configuration policy Device enrollment type dropdown showing the Managed devices and Managed apps options
Picking between managed devices and managed apps. Source: Microsoft Learn.

In the designer, each row is a configuration key, a value type, and a value. Keys are case sensitive. One wrong capital letter and the app ignores that line.

Tokens

Tokens fill in user details for you. {{userprincipalname}} becomes the user's sign-in name, and {{mail}} becomes their email address. On iPhone, managed devices policies also support device tokens like {{deviceid}} and {{serialnumber}}. Managed apps policies have a shorter list with no device tokens.

Example: Outlook only allows work accounts

This one needs a managed devices policy, and Outlook has to be installed through Intune.

  1. Create a managed devices policy for iOS/iPadOS and target Microsoft Outlook.
  2. In the configuration designer, set Configure email account settings to Yes and Authentication type to Modern authentication.
  3. Set Username attribute to User Principal Name and Email address attribute to Primary SMTP Address.
  4. Set Allow only work or school accounts to Require.
  5. Do the same for Android Enterprise.

Under the hood, iPhone uses IntuneMAMAllowedAccountsOnly set to Enabled, with IntuneMAMUPN set to {{userprincipalname}}. Android uses com.microsoft.intune.mam.AllowedAccountUPNs. In the same designer you can turn on Focused Inbox, the external recipients MailTip, and blocking of external images.

Outlook on iOS and Android showing a notification that says Your IT admin has changed your app settings
Outlook tells the user when IT changes its settings. Source: Microsoft Learn.

Example: Edge homepage and bookmarks

Edge settings fit a managed apps policy. Pick both the iOS and Android Edge apps, then open Edge configuration settings. The keys behind the designer look like this:

  • com.microsoft.intune.mam.managedbrowser.homepage: The homepage shortcut, like your intranet.
  • com.microsoft.intune.mam.managedbrowser.bookmarks: Bookmarks written as Title|URL, with || between each one.
  • com.microsoft.intune.mam.managedbrowser.AllowListURLs and BlockListURLs: Sites users can or cannot open, separated by pipes. If you set both, only the allow list counts.

With a managed apps policy, users have to sign in to Edge with their work account before the settings apply.

Check whether it applied

  • Per device: Devices > All devices, open the device, and click App configuration.
  • Per policy: Open it under Apps > Configuration and look at the status by device and by user.
  • On the phone: Open Edge, type about:intunehelp, and tap View Intune App Status. It lists the policies each app received.

Managed apps check in every 30 minutes when an app protection policy is also assigned, and every 12 hours when it is not. Changes can take up to 8 hours to reach a signed-in user. Signing out of the app and back in usually speeds it up.

When it does not apply

  • Wrong kind of policy: A managed devices policy does nothing if the user installed the app from the App Store or Play Store on their own.
  • App not managed on iPhone: Intune can only configure apps it deployed. On unsupervised iPhones, the user gets asked to let Intune take over the app.
  • Two policies, same key, different values: Intune has no tiebreaker. Use one policy per app per user.
  • Typo in a key: Keys are case sensitive, so check every capital letter.
  • Android line-of-business app updated: The old policy does not carry over to the new version. Create a new one.
  • No Intune license, or no Company Portal on an Android phone.
  • Status says succeeded but nothing changed: The app decides what to do with each setting. Check the vendor's documentation.

Getting Intune app configuration policies right

Before you build Intune app configuration policies, decide whether you need managed devices or managed apps. Lock Outlook to work accounts with a managed devices policy, push Edge and general Outlook settings with managed apps, and keep one policy per app. Check about:intunehelp when something looks off.

What can we learn as a person

One line in Microsoft's docs made me laugh. When two app configuration policies push different values for the same key, Intune has no conflict resolution. It just leaves you with a mess.

I get those all the time. Work pushes Evenings = On call. Home pushes Evenings = Family. Same key, different values, and I try to apply both. Nobody gets what they configured, and I end up in an error state, apologizing to everyone.

Which key in your life has two policies fighting over it? And who gets to decide which one actually applies?

Basic Troubleshooting: Autopilot Stuck on the Enrollment Status Page

Basic Troubleshooting: Autopilot Stuck on the Enrollment Status Page

Reading Time: 5 minutes

The new laptop has said Setting up your device for work for two hours. The user is on the phone, the progress has not moved, and their manager wants to know if the laptop is broken. Basic troubleshooting for an Autopilot ESP problem comes down to finding which app or policy the page is waiting on, and why.

If Autopilot itself is new to you, start with how Intune Autopilot works. This post picks up where that one stops, with basic troubleshooting for the Autopilot ESP.

What the Enrollment Status Page is

The Enrollment Status Page, or ESP, is that Setting up your device for work screen. It holds the user there until apps and policies finish, so nobody gets a half-built PC. It has three phases:

  • Device preparation: Joining the organization's network and registering for mobile management. Self-deploying and pre-provisioned devices also secure the hardware with the TPM here.
  • Device setup: Security policies, certificates, network connections, and apps assigned to the device.
  • Account setup: The same four things for the user, after they sign in.
The Windows Setting up your device for work screen showing Device preparation, Device setup, and Account setup all marked Complete
The Enrollment Status Page with all three phases complete. Source: Microsoft Learn.

Most basic troubleshooting for an Autopilot ESP hang starts with knowing which phase stopped. The first two phases are the device part. Account setup is the user part.

The settings that decide how it behaves

ESP profiles live in the Intune admin center under Devices > Device onboarding > Enrollment, on the Windows tab, under Enrollment Status Page.

  • Show app and profile configuration progress: Turn this on. The default profile hides progress, and a spinner tells you nothing.
  • Show an error when installation takes longer than specified number of minutes: The default is 60.
  • Turn on log collection and diagnostics page for end users: Gives the user a Collect logs button, plus a diagnostics page on Windows 11.
  • Block device use until all apps and profiles are installed: The user waits for everything.
  • Block device use until these required apps are installed if they are assigned to the user/device: All, or Selected with up to 100 apps. This only filters what the ESP waits for. It does not assign anything.
  • Allow users to reset device if installation error occurs, and Allow users to use device if installation error occurs: What the user can do on the error screen.
  • Install Windows quality updates (might restart the device): Adds 20 to 40 minutes after the ESP. It is on by default in new profiles.

Profiles have priorities. Intune applies the device-targeted profile first, then the user one, then Default. Target ESP profiles at device groups, because blocking apps in a user-targeted profile get ignored during the device phase.

Read the screen

Click Show details on the stuck phase. Each line says what it is waiting on, like Apps (2 of 5 installed). A line that says Error is your culprit.

The Device setup phase of the Enrollment Status Page in an Error state with the Apps line showing Error highlighted
Device setup stopped because of an app. Source: Microsoft Learn.
  • Stuck on Identifying: The user usually has no Intune license.
  • 0x800705b4 in Device preparation: A timeout. In self-deploying mode, it usually means no TPM 2.0, like on a virtual machine.
  • 0x801c03ea: TPM attestation failed.
  • 0x80180014: The device was used for self-deploying or pre-provisioning before. Unblock it in the Windows Autopilot devices list.
  • 0x80070774: A hybrid join problem.
  • 0xc1036501: The device has more than one MDM configuration.

Get the logs

  • On the error screen, click Collect logs and save them to a USB drive.
  • On Windows 11, press Ctrl+Shift+D to open the Windows Autopilot diagnostics page. It shows network, Autopilot settings, and enrollment status, with an Export logs button.
  • Press Shift+F10 for a command prompt during setup, then run the command below.
mdmdiagnosticstool.exe -area Autopilot -cab C:\Users\Public\Documents\autopilot.cab
The Windows Autopilot diagnostics page during setup showing Network Connectivity, Autopilot Settings, and Enrollment Status sections with an Export logs button
The Windows Autopilot diagnostics page, opened with Ctrl+Shift+D on Windows 11. Source: Microsoft Learn.

Copy that file to your own PC. Microsoft's Get-AutopilotDiagnostics script reads it and lists what the ESP was tracking:

Install-Script -Name Get-AutopilotDiagnostics -Force
Get-AutopilotDiagnostics -CABFile C:\Temp\autopilot.cab

Find the stuck app

The registry tracks everything the ESP waits on, under HKLM\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking. Under Device\Setup\Apps\Tracking\Sidecar, each Win32 app has an InstallationState. A 1 means not installed, 2 is in progress, 3 is done, and 4 is an error. A 4 stops the ESP. Take that app's ID to AppWorkload.log in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs.

Registry Editor showing a Win32App key under the Enrollment Status Tracking Sidecar key with an InstallationState value of 3
A Win32 app's InstallationState in the registry. A 3 means it finished. Source: Microsoft Learn.

From the admin side, Devices > Monitor > Windows Autopilot deployments covers the last 30 days. The failed app's Device install status shows its error code. Collect diagnostics on the device pulls logs remotely, and Autopilot failures upload a set of logs on their own.

The usual causes

  • Mixing Win32 and line-of-business MSI apps: Both use the Windows installer and collide with Another installation is in progress. Package everything as Win32.
  • Microsoft 365 Apps with the built-in app type: Microsoft recommends packaging it as Win32 for the ESP.
  • Too many apps for the time limit: Raise the timeout or block on fewer apps. Only block on what the user needs on day one.
  • An app that restarts the PC on its own: Let Intune handle restarts. They work in Device setup but not in Account setup.
  • User-context scripts: They may not run during the ESP.
  • Hybrid join: Adds about 40 minutes on top of the timeout.
  • Security policies like AppLocker, App Control, or password rules: These can force restarts or break automatic sign-in during setup.
  • The clock is off: Run w32tm /resync /force from Shift+F10.
  • Conditional Access requiring a compliant device during setup: Target compliance policies at devices, not just users.

Get the user working

If Allow users to use device if installation error occurs is on, the user can continue and pick up the missing apps later. If Allow users to reset device is on, a reset starts Autopilot over. For a single broken app, fixing the app and resetting is usually faster than waiting. For new rollouts, Autopilot device preparation skips the ESP entirely and handles mixed app types.

The basic troubleshooting checklist for Autopilot ESP

  1. Note the phase, the line in Error, and any error code.
  2. If it says Identifying, check the user's Intune license.
  3. Collect logs from the error screen or with mdmdiagnosticstool.
  4. Find the app with InstallationState 4 and read AppWorkload.log.
  5. Check the Windows Autopilot deployments report and the app's install status.
  6. Look for mixed MSI and Win32 apps, restarts inside apps, and a timeout that is too short.
  7. Fix the cause, then reset and run Autopilot again.

What can we learn as a person

My favorite ESP advice from Microsoft is to only block on the apps people need on day one. Everything else can install after the user is already working.

I set my own ESP to block on everything. I could not start a new hobby until I had the right gear, could not apply for the job until the resume was perfect, could not rest until the inbox was empty. Sixty minutes went by, then a year, and the screen still said Setting up your device for work.

What are you blocking on that could install after you start? And what would happen if you let yourself use the device with a few apps still pending?

OneDrive Known Folder Move with Intune

OneDrive Known Folder Move with Intune

Reading Time: 5 minutes

A laptop dies on a Tuesday, and the user's first question is whether the stuff on their desktop is gone. If it only lived on that desktop, yes. OneDrive Known Folder Move quietly moves Desktop, Documents, and Pictures into OneDrive, so the next dead laptop is a hardware problem instead of a data problem.

Windows settings backup brings back a user's settings on a new PC, and Microsoft's own FAQ for it says user files are OneDrive's job.

What Known Folder Move does

The known folders are Desktop, Documents, and Pictures, plus Screenshots and Camera Roll inside Pictures. Known Folder Move points those folders at OneDrive. Users keep working in the same places they always have. The files get backed up and show up on any device they sign in to. The OneDrive app now calls this folder backup, so users may know it by that name. Music and Videos are not covered by the admin policies.

Set it up in Intune

  1. Grab your tenant ID from the Microsoft Entra admin center, under Overview, in the Tenant ID box.
  2. Intune admin center > Devices > Manage devices > Configuration > Create > New Policy.
  3. Set Platform to Windows 10 and later and Profile type to Settings catalog.
  4. Click Add settings, pick the OneDrive category, and add the settings below.
  5. Assign the policy and click Create.
The Intune settings catalog Create profile page for Windows 10 and later with the settings picker open on the OneDrive category and Silently move Windows known folders to OneDrive selected
Picking the OneDrive settings in the Intune settings catalog. Source: Microsoft Learn.

The settings

  • Silently move Windows known folders to OneDrive: Enabled. Set Desktop, Documents, and Pictures to True, paste the tenant ID, and decide whether users get a notification afterward. Two settings have almost the same name, so pick the one with five sub-settings.
  • Prompt users to move Windows known folders to OneDrive: Add the tenant ID. Microsoft recommends pairing it with the silent setting, so users get a prompt if the silent move fails.
  • Prevent users from redirecting their Windows known folders to their PC: Enabled, so users cannot turn it back off.
  • Silently sign in users to the OneDrive sync app with their Windows credentials: Enabled. Without a sign-in, nothing moves.
  • Use OneDrive Files On-Demand: Enabled, so files show up without filling the disk.

Use the device versions of these settings, not the ones marked User. Assign to user groups and the settings follow the user to any enrolled PC. Assign to device groups and they apply to anyone who signs in to that PC.

Roll it out in waves

For PCs already in use, Microsoft says to keep the silent move to 1,000 devices a day and 4,000 a week. The prompt version can go to 5,000 a day. Users with huge folders can choke the internet line, so temporarily set Limit the sync app upload rate to a percentage of throughput. New PCs can get the silent policy from day one.

What the user sees

With the silent policy, not much. The folders move, the OneDrive icon is a blue cloud, and a notification may say it is done. With the prompt policy, OneDrive asks them to back up their folders.

A OneDrive activity center card saying Your IT department wants you to back up your folders with a Back up these folders button
The prompt users see when IT asks them to back up their folders. Source: Microsoft Learn.
The OneDrive Back up folders on this device dialog showing Documents, Pictures, and Desktop turned on and ready to back up, with I'll do it later and Start backup buttons
The folder backup dialog, with Desktop, Documents, and Pictures ready to go. Source: Microsoft Learn.

To check on a PC, click the OneDrive cloud, open Settings, go to the Sync and backup tab, and click Manage backup. Each folder shows whether it is backed up.

Silent sign-in has rules

  • The PC has to be Entra joined or hybrid joined.
  • Microsoft's docs say silent sign-in will not work for users who require multifactor authentication. If it keeps failing, look at your Conditional Access rules.
  • If you federate sign-ins, it has to be AD FS.
  • If it worked, OneDrive shows a blue cloud. If it failed, the user gets the Set up OneDrive screen instead.

Why folders do not move

  • Old folder redirection: Known Folder Move does not work if Group Policy folder redirection points the folders somewhere else, like a network share. Copy the share into OneDrive with Migration Manager first, without ticking Preserve file share permissions. Then turn off the redirection policy and turn on the move.
  • Already redirected to another company's OneDrive: Turn that off first, or the user gets an empty desktop.
  • 0x80070005, An unknown error occurred: The Group Policy Prohibit User from manually redirecting Profile Folders is on. Set it to Not Configured.
  • Path too long: The full path has to stay under 260 characters.
  • Bad names: Names that start with a space or contain characters like \ : / * ? < > " | cannot sync. Files over 250 GB cannot sync either.
  • Folder contains a reparse point: A junction or symlink is sitting in the folder.
  • File is open and cannot be moved: Close it and try again. Outlook data files are a classic. They do get moved, but Outlook may complain afterward because it still looks in the old spot.
  • Pictures will not back up: Screenshots and Camera Roll need to be selected for syncing too.
  • Important folders aren't in the default locations: One known folder sits inside another.

Check from the admin side

The OneDrive sync health reports show this across the whole company. In the Microsoft 365 Apps admin center, go to Health > OneDrive Sync and click Setup to get a Tenant Association Key. Add Enable sync health reporting for OneDrive and Sync Admin Reports to your Intune profile, with the key pasted in. Reports take up to three days to show up. The Devices tab then lists which known folders moved on each PC, and the Issues tab lists errors by how many devices they hit.

On a single PC, the policy lands in the registry at HKLM\SOFTWARE\Policies\Microsoft\OneDrive. KFMSilentOptIn holds your tenant ID, and SilentAccountConfig and FilesOnDemandEnabled should be 1.

Rolling out OneDrive Known Folder Move

Turn on silent sign-in and Files On-Demand, then add the silent move for Desktop, Documents, and Pictures, with the prompt as a backup. Block users from turning it off. Clean up old folder redirection before you start, roll out in waves, and watch the sync health report.

What can we learn as a person

Users barely notice OneDrive Known Folder Move, and that is the best part. The desktop stays the desktop. Their files just stop living in only one place.

For a long time, everything I learned about my own bad weeks lived on one local drive, my head. What helped, what made it worse, which warning signs showed up first. When that drive crashed, the lessons went with it. A journal changed that. Same thoughts, same folders, but now there is a copy I can open when the hardware is having a rough day.

What lives only on your local drive right now? And where could you back it up so it survives the next crash?

Intune Remote Actions Beyond Wipe: Diagnostics, BitLocker, Defender, and Device Query

Intune Remote Actions Beyond Wipe: Diagnostics, BitLocker, Defender, and Device Query

Reading Time: 6 minutes

Most people know the scary buttons on a device page: Wipe, Retire, and Fresh Start. I covered those in Intune wipe vs fresh start vs retire. The rest of the menu gets ignored, and that is a shame. Intune remote actions like Collect diagnostics, BitLocker key rotation, and device query close a lot of tickets without anyone touching the laptop.

Where remote actions live

Go to Intune admin center > Devices > All devices and pick a device. The actions sit across the top of the page, and the rest hide under the three dots. The newer device view groups them into menus like Remote actions, Secure, and Microsoft Defender, so the exact spot moves around a little.

An Intune device page with the more actions menu open showing Sync, Restart, Fresh Start, Quick scan, Full scan, Update Windows Defender security intelligence, and BitLocker key rotation highlighted
The device action menu in the older layout. The newer view groups the same actions into menus. Source: Microsoft Learn.

Windows devices get Sync, Restart, Collect diagnostics, BitLocker key rotation, Rotate local admin password, Quick Scan, Full Scan, Update Windows Defender security intelligence, Locate device, Pause Config Refresh, Run remediation, and New remote assistance session. They also get the destructive ones. Remote lock is not available for Windows, only for phones, tablets, and Macs.

The everyday ones

  • Sync: Tells the device to check in with Intune right now. On Windows and iOS, the Device sync status tab shows how it went.
  • Restart: Usually starts within 5 minutes, and the user may not get a warning. Tell them before you click it.
  • Rename: This one is on the Properties tab under Edit, not in the action menu. It does not work on hybrid joined devices, and names cannot have spaces or be all numbers.
  • Locate device: On Windows, this only works if a settings catalog policy allows apps to access location.
  • Run remediation: Runs one of your remediation scripts on that device right now.
  • Pause Config Refresh: On Windows 11, stops Intune from putting settings back for up to 24 hours. That gives you room to test a change. Pause it again for 0 minutes to resume.

Collect diagnostics

This is the one to learn first. Instead of asking a user to find log files, you click Collect diagnostics, confirm, and Intune pulls a zip of everything useful off the device. It works on company-owned Windows devices.

The zip includes dsregcmd /status, ipconfig /all, the certificate stores, MDM diagnostics, Defender support files, and event logs for Application, System, Setup, BitLocker, and Windows Hello for Business. It also grabs the Intune Management Extension logs and Windows Update logs. When it finishes, open the device's Device diagnostics page, click the three dots next to the entry, and choose Download.

Collections stay for 28 days, with up to 10 per device. The whole feature can be turned off under Tenant administration > Device diagnostics, so check there if the button is missing. If the device does not pick up the request within 24 hours, the collection fails. A firewall blocking the Microsoft blob storage addresses that end in lmsas.blob.core.windows.net causes upload failures too.

Rotate BitLocker keys

Once you read a BitLocker recovery key to a user over the phone, that key has been out in the world. BitLocker key rotation makes a new one so the old key stops working. I covered where to find BitLocker keys in an earlier post.

Rotation needs Windows 10 1909 or newer, or Windows 11, and three settings in your BitLocker policy. Turn on client-driven recovery password rotation for Entra joined devices, or Entra and hybrid joined devices. Set Save BitLocker recovery information to Microsoft Entra ID to Enabled. Set Store recovery information in Microsoft Entra ID before enabling BitLocker to Required. After the rotation, the new key shows up under the device's Recovery keys page.

Defender actions

  • Quick scan: Checks memory, startup items, and running processes.
  • Full scan: Checks every file and process. It takes a while and slows the device down.
  • Update Windows Defender security intelligence: Pulls the latest Defender definitions down to the device.

For many devices at once, go to Endpoint security > Antivirus and use the Unhealthy endpoints or Active malware tabs. They let you run scans or restarts on up to 100 devices. Results show up in Reports > Microsoft Defender Antivirus.

Device query

Device query lets you ask a device a question and get the answer back in seconds. Is that file there? What does that registry key say? What errors hit the Application log today? You write the question in KQL, the same query language used across Microsoft's security tools, or let Copilot write it for you.

Pick the device and click Device query under Monitor. The device has to be company-owned Windows, Entra joined or hybrid joined, and set up in Endpoint analytics. It needs Intune Advanced Analytics, which is part of the Intune Suite. Since July 1, 2026, Microsoft 365 E3 and E5 include Advanced Analytics too, and existing tenants get access by August 2026. The Help Desk Operator role cannot run it, so give the helpdesk a custom role with the Managed devices Query permission.

FileInfo('c:\windows\system32\drivers\etc\hosts') | take 10
WindowsEvent(Application, 1d) | take 1
The Device query page for a single device in Intune, with a list of properties to query and a Copilot-generated KQL query checking whether the device is protected by BitLocker
Device query on a single device, with a query Copilot wrote from a plain English question. Source: Microsoft Learn.

Querying many devices at once

Devices > Device query runs one question across many devices. It covers Windows, iOS, macOS, and company-owned Android. Windows devices need a properties catalog policy so they report the data ahead of time. You get 10 queries a minute and 1,000 a month, and you can export the results or add every device in them to a group.

Tpm | where Enabled != true
OsVersion | summarize DevicesCount = count() by OsVersion
The Devices Device query page in Intune with a Copilot-generated KQL query listing company-owned Windows devices enrolled in the last 30 days
Device query across many devices from Devices > Device query. Source: Microsoft Learn.

Bulk actions and who did what

Go to Devices > All devices > Bulk device actions, pick the operating system and the action, add up to 100 devices, and click Review + create. On Windows, bulk works for Sync, Restart, Rename, Collect diagnostics, Autopilot reset, Retire, Wipe, and Delete. Collect diagnostics caps out at 25 devices. Each tenant can only wipe 500 devices a day and retire or delete 1,000.

To see whether an action finished, check the device actions report under Devices > Monitor. It shows the status and who started each action. To see who did something, go to Tenant administration > Audit logs and filter on the Device category. If nothing shows up in the audit log, the user probably did it themselves from the Company Portal. Wipe, retire, and delete can also require a second admin's approval through Multi Admin Approval.

When an action is stuck or greyed out

  • Stuck on Pending: The device is offline. Actions wait for the next check-in.
  • Greyed out: The platform does not support it, like Remote lock on Windows or Pause Config Refresh on Windows 10.
  • Greyed out on one device but not another: Rename does not work on hybrid joined devices, and diagnostics and device query need a company-owned device.
  • Missing for one admin: Their role lacks the permission. Help Desk Operator covers most actions, but not device query or Pause Config Refresh.

Make Intune remote actions part of every ticket

Make Collect diagnostics the first step on any Windows ticket you cannot solve in five minutes. Rotate BitLocker keys after every recovery, and keep a few device queries saved for the questions you ask every week. Those three Intune remote actions alone save a lot of walking to desks.

What can we learn as a person

Pause Config Refresh is a small action with a nice idea behind it. Normally Windows keeps putting your settings back. Change something, and a little later it snaps back to policy. Pause it, and for up to 24 hours you get room to try something without being corrected.

That button does not exist in my head. Every time I try something new, a little voice reapplies the old policy. You don't do that. That's not how you are. Back to baseline before the experiment ever gets a chance to work.

What would you try if you paused your own config refresh for one day? And whose policy is it that keeps snapping you back?