Hi Adam
Thank you very much for your detailed response and explanation. Good to hear, that our goals are aligned.
We never tried minimal environments, that’s a good point, we will check that out. And we are planning to update to PSU 5.5.0 this week.
I agree with you, that the root cause of all our issues lies within Microsoft and the inability of the M365 product teams to harmonize the PowerShell module development and that they don’t stick strictly to schematic versioning. In my understanding, there should be a core module for the core workload like authentication (a Microsoft-managed successor of MSAL.PS). And all other Microsoft Cloud modules should be able to depend “the PowerShell way” with cmdlets on that core module. I hope such an improvement or something similar is planned within Microsoft (of course, the problem is much more complex, but there has to be a better solution as the current state).
And yes, it’s also a problem even outside of PSU directly in pwsh.exe - as you pointed out, it’s hard to get multiple Microsoft Cloud modules to work in the same session. We have to choose the versions carefully. And if we found a version mix of all modules and PSU, we normally keep that for months until a new feature or a change triggers us to upgrade a component.
Better testing is good, importing the modules and connecting to the services should show the major issues.
Thank you!
Bests
Claudio