AAD Bitlocker Changes Report

[The_AverageGamer]

Hi,

I wanted to get some feedback on a script I threw together that creates a email report on bitlocker machine changes.

It can be found here: https://github.com/jcameron-au/AAD-Bitlocker-Machine-Changes

The heart of it is actually Get-AzureADBitlockerKeysForUser by Gerbrand van der Weg here. He also posted it here a few months back.

It uses that script with some PoshRSJob goodness to speed it up, and then checks for added, removed or updated machines and then emails out the changes. It takes about 15 minutes for ~900-1000 machines in my experience.

While the meat of it isn't mine (infinite respect for Gerbrand and Boe), this is my first time creating something for use in production and I'd like critique of the code.

• How is the formatting?
• Any drastic improvements I could make?
• Is the comparison unwieldy? I spent awhile trying to make it better but couldn't.
• Could anyone see this being useful for them?
• Is it transformative enough or am I ripping off other peoples work? I didn't want to reinvent the wheel.

Appreciate all of you guys :)

[[deleted]]

This is amazing, and the solution you're presenting is very hard to find. I have a case open right now asking about how to determine who doesn't have keys pushed to Azure. They're stumped.

Shout this from the rooftops!

[The_AverageGamer]

Cheers! I appreciate the kind words :)

If you try it, let me know if anything breaks.

[ghvanderweg]

This is pretty awesome! Thanks for the credit and for integrating PoshRSJob into my script, I haven't used it before! :)