Azure AD PowerShell Module Migration

[@NTFAQGuy]

Looking at moving off the legacy AzureAD PowerShell module! Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc. 👂 Translate the captions to your native language via the auto-translate feature in settings! kzbin.info/www/bejne/rGbFZmZjhcx4o6s for a demo of using this feature. Thanks for watching! 🤙

[@tdannecy]

Thanks for the video explanation! I think this move to the Graph module is only better on paper. They should have kept the original module commands and rewritten the backend to interact with Graph to keep compatibility. The new REST api format in addition to new command syntax is a big lift for non-dev people.

[@jazzchamp]

Thanks John. A lot of information that I hadn't even considered as part of the rename and as someone that is just beginning to immerse myself in PowerShell, very timely.

[@NTFAQGuy]

As noted in the video, this is nothing to do with the rename at all :-). Very important point.

[@Semtx552]

great to give this issue attention :) I hope my colleagues understand me better when i ask them to rewrite their scripts, ill point them to this vid :) The standard app the graph module uses, we only allow API read permissions. All scripts that change stuff through graph get their own app registration with permissions. I dunno if I'm over cautious, but i feel being more in control over what happens :)

[@TechChefMM]

As ALWAYS very informative, timely and useful! Thanks much John! MM

[@NTFAQGuy]

Glad it was helpful!

[@steveng.42]

Thank you sir! Appreciate you always hitting the time relevant topics along with the sprinkling of all the other fun you put out there!

[@NTFAQGuy]

My pleasure!

[@Enlidev]

Great video as always. Migrating is not easy. Microsoft.Graph is still a hot mess. It works for basic operations that are not full scale, but some of the issues I've noticed are: Poorly documented with examples and limitations. They changed some command names between v1.27.0 & v.2.0.0 & v.2.1.0 As someone pointed out, sometimes the V1 graph endpoint does not work but Beta works. I had a script that ran in 17 min with AzureAD module but it's Graph counterpart finishes in 8-9 hours. I've re-written it a couple of times in different way in case the logic on how this new module functions is different. Still no improvement. API Permissions with write grants are a big concern security wise because it's enough to have 3 specific API permissions granted to an App and an attacker can become GA. Plus other concerns. ... list can go on. At this time I'm still using the v.1.28.0 for anything production and 2.1.0 in sandbox/testing.

[@BrandonBristow]

Great video, I have been trying to get used to MSGraph for a bit now.

[@FredHendrix]

Video is right on time for me. Thank you

[@bcg623]

I can appreciate the vision of the new Graph module and the benefits it brings. However, the programmatically generated documentation is very poor and most commands lack the intuitiveness of the previous MSOL and AzureAD modules. They're basically lightweight wrappers around a REST API. As folks begin to use more advanced commands, they'll quickly scratch their head trying to figure out what the documentation means in the complex hash tables most commands use. For the past few months, I've just had to find other blog posts or GitHub issues for examples on how to use a command. The module leaves a lot to be desired and I think that stems from being generated from the API rather than designed for sysadmins.

[@luiz.mesquita]

The documentation of Microsoft Graph is very poor.

[@melmixpita543]

We can't move to Graph because we always end up having to switch to the beta endpoint to get everything working and we can't use a beta endpoint for production. I've tried multiple times over the past year and every time I have to throw in the towel and restore the original scripts. Hoping stuff will be sorted before the older modules are deprecated.

[@badsector82]

The output of Get-AzureAdUser greatly differs from the output of Get-MgUser. The first gives a lot more information. So I guess that change of modules won't happen very soon.

[@reguitarded]

Thanks, John!

[@NTFAQGuy]

Welcome!

[@pauljoneseyboy9615]

Class.

[@NTFAQGuy]

thank you 🤙

[@nex7053]

Graph is pure pain an suffering. Tried and failed miserably.