Device identity management
Entra · Official Microsoft guidance
Observed content change
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.
Note When devices that utilize Windows Autopilot are reused, and there is a new device owner, that new device owner must contact[removed: an][added: a non-device owner] administrator to acquire the BitLocker recovery key for that[removed: device.][added: device, even if the new device owner is an admin.] Custom role or administrative unit scoped administrators will continue to have access to BitLocker recovery keys for those devices that have undergone device ownership changes, unless the new device owner belongs to a custom role or administrative unit scope. In …
Before: Note When devices that utilize Windows Autopilot are reused, and there is a new device owner, that new device owner must contact an administrator to acquire the BitLocker recovery key for that device. Custom role or administrative unit scoped administrators will continue to have access to BitLocker recovery keys for those devices that have undergone device ownership changes, unless the new device owner belongs to a custom role or administrative unit scope. In …
After: Note When devices that utilize Windows Autopilot are reused, and there is a new device owner, that new device owner must contact a non-device owner administrator to acquire the BitLocker recovery key for that device, even if the new device owner is an admin. Custom role or administrative unit scoped administrators will continue to have access to BitLocker recovery keys for those devices that have undergone device ownership changes, unless the new device owner belongs to a custom role or administrative unit scope. In …
Source: Microsoft source · © Microsoft · MIT.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details
- Observed by ChangeIntel
- today 05:48 UTC
- Source update metadata
- 12 Nov 23:46 UTC
- Microsoft's latest commit in that period
- Clarify BitLocker recovery access after Autopilot ownership changes · committed 12 Nov 22:17 UTC · View diff
- First observed on this installation
- 8 Oct 23:13 UTC
- Last successful check
- today 05:48 UTC
- Next check due
- today 11:48 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.