365 Backup · BitLocker

The device is deleted.The keyis still there.

Entra ID stores BitLocker recovery keys on the device object. If the device is deleted, the keys are lost with it once the retention period ends, and Microsoft support cannot bring them back. Conbool backs up each key once, separately encrypted, and reveals it only to authorized people, with a log entry.

When a BitLocker key is missing

Four cases from an administrator's day to day.

The device was cleaned up, then the laptop turns up again

Old devices get deleted in Entra ID and Intune. Once the retention period in the recycle bin ends, Microsoft deletes the object for good, BitLocker keys included. If the laptop later sits in the storeroom showing the recovery screen, there is no key left.

An update suddenly asks for the key

Firmware and BIOS updates, a replaced motherboard or a changed boot order can trigger the recovery screen. Then all that matters is whether the 48-digit key can be found quickly.

Support cannot help

Microsoft states explicitly that support can neither provide nor regenerate a lost recovery key. Without the key, the data on the drive is lost.

Who retrieved the key?

A recovery key opens an entire drive. Who saw it and when must still be provable months later.

Recovery keysbacked up
214backed up
9device deleted
2revealed
NB-SALES-07 · Operating system drivehidden
NB-STOCK-02 · Device deleted in Entrabacked up

The figures are an example. Every retrieval is logged with name, time, identifier and device.

Hidden until someone asks

One key, one retrieval, one entry.

Backed up keys stay hidden. Whoever needs one confirms the retrieval and sees exactly that one key.

Separately encrypted, in no export

Reveal only with its own permission

Every retrieval logged with name, time and device

Hidden again after one minute

How the key backup works

Part of the Entra ID backup, on the same schedule as the other sources.

1. Read once

Microsoft records every retrieval of a key in the Entra ID audit log. Conbool therefore reads each key exactly once, when it is new, instead of on every run. That keeps genuine retrievals visible in the log.

2. Store separately encrypted

The key is not part of the readable directory state or any export. It is encrypted individually with its own data key. The directory state shows only the device, drive type, identifier and creation time.

3. Reveal on purpose

In the portal, an authorized person opens the device, confirms the retrieval and sees the key. After one minute it is hidden again. The retrieval is logged with name, time, identifier and device.

What defines the key backup

Six points that count when it matters.

Survives deletion of the device

The backed up key is kept even after the device object in Entra ID has been permanently deleted, for as long as the retention period of your directory backup. Under a legal hold it is kept longer.

Revealing requires its own permission

Owners, security admins, backup administrators, backup helpdesk and IT helpdesk can reveal a key. Mail admins cannot, and a custom role only if you explicitly grant it the permission to reveal BitLocker keys.

Log first, then the key

The log entry is created before the key is shown. If it cannot be written, no key is displayed. A retrieval without a trace is not possible.

Rate limit

One key per retrieval, at most ten retrievals per hour and person, and a cap per account and day. Anyone trying to pull keys in bulk is slowed down.

In no export

The directory state can be downloaded as JSON or ZIP. The keys are never in it, only their metadata.

Deleted with the unit

The keys are encrypted with the key of the backup unit. If the unit is deleted on request, the BitLocker keys become unreadable too, with no separate deletion path.

With and without a separate backup

What is possible in each case.

 
With Conbool
Microsoft 365 without an add-on service
Key after the device is permanently deleted
yes, within the retention period
no
Key retrievable if the directory was damaged
yes, from the backup
no
Retrieval with confirmation and automatic hiding
yes
no
Rate limit for retrievals
yes, per person and per account
not by default
Where the copy is stored
Germany, separately encrypted
only on the device object

Statements about Microsoft 365 follow the publicly documented features of Entra ID. Deleted devices stay in the recycle bin there for a limited time and are then permanently deleted along with their keys.

Frequently asked questions

Where do the keys come from?
From Entra ID. Windows devices joined to Entra ID store their BitLocker recovery keys there, for example through an Intune policy. What Entra ID does not have, Conbool cannot back up: keys that exist only in on-premises Active Directory or on paper are not included.
Does Conbool write keys back to Entra ID?
No. A recovery key is needed to open a drive, not to be placed back in the directory. It is shown in the portal and can be copied.
Who may reveal a key?
Owners, security admins, backup administrators, backup helpdesk and IT helpdesk. Mail admins only see that a key is backed up; so does a custom role unless you explicitly grant it the permission.
Why does Conbool read each key only once?
Microsoft logs every retrieval of a key. Reading on every run would fill the log with entries in which a genuine retrieval by an attacker would get lost. A key does not change; a new one gets a new identifier and is backed up on the next run.
Does the key backup cost extra?
No. It is part of the Entra ID backup, which runs as one unit per Microsoft tenant and does not use a license seat.
What permission does Conbool need for this?
The read permission for BitLocker keys in Microsoft Graph, which you grant when giving consent. If it is missing, the run reports the keys explicitly as unreadable instead of reporting an empty backup as a success.

See your own keys backed up

We connect a test tenant and show how a key is searched for, revealed and logged.