Bitlocker has moved from beta to v1.0 (Get-IntuneManagedDeviceBitLockerKeyPresence)

[fr3dr1x]

Line 335 in Get-IntuneManagedDeviceBitLockerKeyPresence.ps1 should look like:

$BitLockerRecoveryKeys = Invoke-MSGraphOperation -Get -APIVersion "v1.0" -Resource "informationProtection/bitlocker/recoveryKeys?`$select=id,createdDateTime,deviceId" -Headers $AuthenticationHeader -Verbose:$VerbosePreference

[phillipwp1]

Worked for me today. Thank you!

[adelamora-vtsf]

I cannot use this script, it returns errors on both getting the auth token, and retrieving data.
At first I get this error:
See https://aka.ms/msal-net-invalid-client for details. Original exception:
AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'.

When I modify the script to provide a client secret, and I change the line as mentioned above, I then get this error:

VERBOSE: GET
https://graph.microsoft.com/v1.0/informationProtection/bitlocker/recoveryKeys?$select=id,createdDateTime,deviceId
VERBOSE: Existing token found but has expired, requesting a new token
WARNING: Unhandled error occurred in function. Error message: You cannot call a method on a null-valued expression.
VERBOSE: GET https://graph.microsoft.com/v1.0/deviceManagement/managedDevices?$filter=operatingSystem eq
'Windows'&select=azureADDeviceId&$select=deviceName,id,azureADDeviceId
VERBOSE: Existing token found but has expired, requesting a new token
WARNING: Unhandled error occurred in function. Error message: You cannot call a method on a null-valued expression.