WebFeb 23, 2024 · That’s not necessarily the case anymore if they are listed as the owner on the device in Azure Active Directory. If this sounds like your situation, you can check out how to recover the key in section 1.3 below. If you are an administrator, you will likely get a number of requests for the key regardless of the Self-Service Portal’s ... WebApr 6, 2024 · Dear Amrita,in this case you can verify the bitlocker key using another PC; From any device, open your browser and go to the link: aka.ms/myrecoverykey. Log in to your Microsoft account; Your bitlocker keys should be displayed on the screen; If you still have questions, watch the video below:
Why isn
WebSep 20, 2024 · Hello, The user voice shared by Teemo Tang is right, the setting "Store Recovery information in Azure Active Directory before enabling BitLocker" appears to set the OSRequireActiveDirectoryBackup_Name OMA-URI, which causes the key to be backed up to the on-prem AD DS and does not store the key in Azure AD. So Azure AD … WebOption 1, Using the Azure Management Portal. Go to the All Users object and search for the account associated to the device. Go to the Devices object under the Manage heading. Select the appropriate listed device. If the device is registered with Bitlocker encryption, then the Bitlocker Key ID and Recovery Key will be visible. raveshia realty
Fix no BitLocker Recovery tab in Active Directory
WebAug 19, 2024 · The configuration profile is showing as successful on almost all of the devices, but most of the ones showing successful don't have the BitLocker recovery codes. We've found a manual solution which is to open Manage BitLocker and use the Save recovery code to cloud account. This pushes the recovery code to the device in … WebSep 27, 2024 · We tried deploying the Intune encryption policy to get the key backed up but no luck, same story with the script running as system. Looking in event viewer shows the following after running the script: Event 846: Failed to backup BitLocker Drive Encryption recovery information for volume C: to your Azure AD. WebJul 23, 2024 · 0x80072f76 = "The requested header was not found" My guess here would be that the traffic between the client and Azure is going through a proxy or some other type of traffic filter that is interfering with the operation. Have you reviewed the BitLocker-API event log to see if there is any additional info? Have you tried this on a different network? simple baked oatmeal