3.4.2. Security Actions: Defender Intelligence, BitLocker Keys, and LAPS Passwords
💡 First Principle: A secret that has been shared is no longer secret. The moment a help desk reads a BitLocker recovery key or a local admin password to someone, that credential should be replaced — and rotating it remotely does that without touching the device or the user's data. Defender actions follow the same logic of refreshing protection from a distance: update the signatures, then look.
Microsoft Defender Antivirus actions run on Windows from the device's Microsoft Defender menu:
- Update Windows Defender security intelligence refreshes the antivirus security intelligence files, so the next scan uses current definitions.
- Quick scan checks the places malware usually hides — memory, startup folders and running processes.
- Full scan checks all files and running processes; use it when you suspect the device is compromised.
Quick and full scans need the Remote tasks/Windows defender permission, which Help Desk Operator and Endpoint Security Manager include.
BitLocker key rotation (Secure > BitLocker key rotation) replaces the recovery key for the operating system drive — for example, right after the help desk has read a key to a user. It needs Windows 10 version 1909 or later or Windows 11, and the device's BitLocker policy must already support it:
- Client-driven recovery password rotation set to enable rotation on Entra joined devices (or on Entra joined and hybrid joined devices).
- Save BitLocker recovery information to Microsoft Entra ID enabled.
- Store recovery information in Microsoft Entra ID before enabling BitLocker set to Required.
The action needs the Remote tasks/Rotate BitLockerKeys permission. Viewing keys is a separate right: keys appear at the device > Monitor > Recovery keys, each view writes an audit entry, and the reader needs the Entra permission to read BitLocker keys, which the Cloud Device Administrator, Helpdesk Administrator and Global Administrator roles include. Entra ID stores at most 200 recovery keys per device; at that limit, silent encryption fails because the key can't be backed up.
Rotate local admin password works with Windows LAPS, which you configure through Endpoint security > Account protection > Local admin password solution (Windows LAPS), with LAPS also enabled in Microsoft Entra ID. The device action rotates the password outside the policy's schedule, from the device's ... menu, and its status moves from Pending to Complete. Its requirements trip people up:
- It needs three permissions: Managed devices Read, Organization Read and Remote tasks Rotate Local Admin Password.
- It fails on any device that hasn't successfully backed up its account and password, even though the action appears for every Windows device.
- An Entra joined device must be online when you request the rotation.
- It can't be run as a bulk action — one device at a time.
- A manual rotation resets the password-age clock. With a 30-day policy, a manual rotation on October 20 moves the next automatic rotation to November 19 (11 days to October 31, then 19 more).
To view the password (device > Monitor > Local admin password), an admin needs the Entra permission to read device local credentials, which Cloud Device Administrator includes. If the policy backs the password up to on-premises Active Directory instead of Entra ID, it can't be viewed in Intune at all — and the backup directory must match the device's join type, or the backup silently fails.
⚠️ Exam Trap: "Select all affected devices and run a bulk Rotate local admin password" is impossible — LAPS password rotation isn't supported as a bulk action, and neither is BitLocker key rotation. Both are rotated one device at a time from that device's page.
Reflection Question: A technician read a laptop's local admin password over the phone this morning, and the rotate action now fails on that device. Name two reasons the rotation could fail, and explain what a successful manual rotation does to the next scheduled one.