Assembly Clashes Make Microsoft 365 PowerShell Frustrating

An assembly clash happens when a PowerShell module attempts to load a .NET assembly only to find that a different version is already loaded in the session. Unhappily, this kind of thing happens far too often with Microsoft 365 modules, which implies that there isn’t a great deal of coordination between different development groups. All you can do is to load modules in the right order.

https://office365itpros.com/2025/09/24/assembly-clash-microsoft-365-ps/