Teams and Microsoft Exchange PowerShell Modules Clash Over Required DLL

After updating a bunch of PowerShell modules, I was dismayed to find a PowerShell module clash caused by a dependency on the Microsoft.Identity.Client DLL. The Exchange Online management module wanted a higher version of the DLL than the one loaded by the Teams module, so the Connect-ExchangeOnline cmdlet barfed. It's easy to understand the logic behind the problem, but it's hard to understand why Microsoft let it happen.