Microsoft Graph PowerShell SDK V2.37

[u/Unlikely_Tie1172]

For those that use the Microsoft Graph #PowerShell SDK, V2.37 is now available in the PowerShell Gallery: https://www.powershellgallery.com/packages/Microsoft.Graph/2.37.0

So far, this version of module appears stable.

[u/logicalmike]

Invoke-MgGraphRequest all of the things. Most of the other cmdlets are horrible.

[u/BlackV → u/logicalmike]

ya, i'm slowly removing everything out of native cmdlets to standard invoke-reset, so that I have 0 module dependencies (given their track record of breaking changes) makes it better "simple" users, my graph request ones I'm doing last as they are least likely to break

[u/HumbleSpend8716 → u/BlackV]

me too bro

we meet again

[u/BlackV → u/HumbleSpend8716]

:)

[u/evetsleep → u/logicalmike]

I refactored all my automations\modules to do just that a long time ago. The handling of v1.0, beta, and different dependencies between modules and updating to a new version being a complete nightmare quickly taught me it's far better to just leverage the Microsoft.Graph.Authentication module and then write my own for everything else. I've been far happier and less annoyed when I need to update the module or port scripts to new machines.

I appreciate the work Microsoft has done to create modules for this SDK, but the cmdlet naming, help files (or lack there of), and documentation really has left a lot to be desired.

[u/BlackV → u/evetsleep]

I appreciate the work Microsoft robots (literal robots) has done to create modules for this SDK, but the cmdlet naming, help files (or lack there of), and documentation really has left a lot to be desired.

its all done automatically, only the newer entra ad modules are human curated

[u/Due_Capital_3507 → u/logicalmike]

Oh so it's not just me where I find the need to just do API calls instead of using built in commands

[u/Unlikely_Tie1172 → u/logicalmike]

I can appreciate it when people say that they focus on Graph requests and ignore the SDK. That's a perfectly reasonable position for developers to take. The Graph PowerShell SDK helps people who can use PowerShell but find the Graph a real challenge with concepts like pagination and token refresh to master. The fact that there are over 1.05 million downloads of the last version of the SDK attests to the use that it gets, especially in Microsoft 365 tenants.

But everyone's free to choose their own tool. I like the Graph SDK, warts and all.

[u/AbfSailor]

Did you say.. "stable" 😉

Long live v2.25.0! 🥇

[u/AdeelAutomates → u/AbfSailor]

Long Live Graph API!

[u/Unlikely_Tie1172 → u/AbfSailor]

Yep. Stable as in I haven't found anything that is broken yet. All versions of SDKs have some imperfections, and because the PowerShell SDK is based on human-written OpenAPI specification documents, it inherits all the human-generated errors...

[u/Federal_Ad2455]

Same here. One small improvement was to use Graph Api calls batching (plus parallel processing) to make it work a lot faster.

Official sdk modules are a disaster 🙁

[u/dangermouze]

Have they fixed the WAM repeat auth issues?

[u/Unlikely_Tie1172 → u/dangermouze]

I believe so. I don't see anything on https://github.com/microsoftgraph/msgraph-sdk-powershell/issues

[u/rogueit]

I still use irm for everything!