The latest Microsoft Graph PowerShell SDK and Exchange Online Management module releases seem to have compatibility issues. Are you staying on older versions, separating sessions, or using another approach?
How are you handling Graph and Exchange module compatibility?
Answers
For production, Iโd pin known-good module versions and update them in a test environment first. That avoids a surprise breaking routine work, while still giving you a chance to check newer fixes and features before rolling them out.
Reply to this answer
For manual work, separate PowerShell sessions can be the least complicated workaround if loading both modules together causes trouble. Itโs clunky, but it keeps the conflicting environments apart without changing your scripts.
Reply to this answer
I wouldnโt treat staying on an old release as a permanent fix. It can preserve stability, but you may miss bug fixes or newer functionality. Iโd test upgrades deliberately and only move production after checking the tasks your team actually depends on.
Reply to this answer
It may be worth checking whether the issue is tied to authentication or a particular cmdlet rather than assuming the modules are incompatible in every use case. The discussion raises passing an access token to Exchange Online as something to investigate, but that is not confirmed as a general solution.
Reply to this answer
Add your answer
Answers are reviewed before publication.
5D__Trombone:
That seems like a sensible middle ground. Do you keep the pinned versions documented alongside the scripts?