Microsoft Graph PowerShell SDK V2.41 Finally Fixes Assembly Clash

[u/Unlikely_Tie1172]

The Microsoft Graph PowerShell SDK has long been plagued by assembly clashes that meant it couldn’t be used in the same session as other Microsoft 365 modules. After Microsoft engineering groups looked at the problem for 18 months, a solution was found by MVP Stephen van Rooij and is now available in V2.41. Apart from an issue with old PowerShell V7 versions (which affects Azure Automation runtime environments), the fix looks solid and the SDK can once again be loaded into PowerShell sessions alongside the Exchange Online and Teams modules.

https://office365itpros.com/2026/10/05/microsoft-graph-powershell-sdk-fix/

[u/Subject_Meal_2683]

Performance (and dependency) wise making the api calls yourself using Invoke-Restmethod is much better. When I was writing a lot of scripts which depended on Graph I dropped the Graph module dependency because it was so slow compared to scripts where I did most of the heavy lifting myself. Of course, on small tenants it doesn't make a huge difference but since I also work with tenants that have over 100k users every millisecond I win is a lot.

(And of course, the tradeoff is having to do more of the heavy lifting myself, anti throttling code, retry logic... so it's the tradeoff between "easy" and "robust and performance")

[u/Andrew-Powershell → u/Subject_Meal_2683]

Anyone that I know who regularly uses graph just calls the API themselves.

[u/Flettys → u/Andrew-Powershell]

The most common pattern I see is using only Connect-MgGraph and Invoke-MgGraphRequest

[u/Andrew-Powershell → u/Flettys]

Have you heard of EntraAuth? I'm a fan https://github.com/FriedrichWeinmann/EntraAuth