Exchange Online PowerShell Updates to 3.10.1 to Fix CBA

This is a good reminder that a successful authentication does not necessarily mean a functional administrative session.

What makes this issue particularly concerning is that CBA is heavily used for unattended automation, Azure Automation runbooks, and other production workloads where failures may not be immediately visible.

Microsoft reacted quickly with 3.10.1, but authentication and tenant-resolution changes should probably be validated against common app-only scenarios before reaching production.

For Exchange administrators, this also reinforces an important practice: module upgrades should be treated like infrastructure changes — test first, deploy second.