encryption
3 TopicsBitLocker recovery key not being uploaded into Intune when using BackupToAAD-BitLockerKeyProtector
Hello, We are having an issue with the BackupToAAD-BitLockerKeyProtector PowerShell cmdlet to upload the BitLocker recovery key of our devices into AAD/Intune. We currently use Sophos Device Encryption to encrypt our devices but want to migrate the recovery keys into Intune as we transition to Intune BitLocker policies. We created a script that attempts to upload the BitLocker recovery key into Intune but it appears theBackupToAAD-BitLockerKeyProtector cmdlet only works on devices where the user logs in with a domain account, and not a local Windows account. Is this standard behaviour? I would have assumed that since the device is enrolled into Intune it would use the Management Extension to communicate with Intune for this task - and have no reliance on the logged in user. Looking at the BitLocker PowerShell module itself, a method named " BackupRecoveryInformationToCloudDomain" is called when this cmdlet is executed. I haven't been able to find much online about what happens beyond here.It would be good to know a bit more about this cmdlet as documentation is limited online. CheersSolved35KViews0likes7CommentsDevice Configuration Policy showing false information
Hi, I noticed every client applied successfully our device policy and shows "Encrypt devices" as "Succeeded" but when I take a closer look at some clients I found out that many of them are not encrypted at all. Those clients also don't have a decrypt key in Azure. If I trigger Bitlocker manually on those clients the key is sent to Azure as configured. Anyone with similar issues? Thanks, Josch2.5KViews0likes1CommentIntune device encryption - not applicable
Hi all, We have created an Intune Device configuartion profile te enable/ enforce the encryption of the drives with Bitlocker. The deviecs all run Windows 10 1709 and encryption is enforce on all devices exept one. This device has the same image as all other devices, but gives the deployment status "not applicable" How can we troubleshoot this behavior? Thanks, Peter2.4KViews0likes0Comments