Can AI agents automate Microsoft Exchange Server (on-prem)?

Microsoft Exchange Server is the self-hosted Exchange boundary; Microsoft Graph is the preferred mailbox API for Exchange Online and is not a substitute for on-premises Exchange automation. On-premises mailbox and calendar applications use Exchange Web Services, a cross-platform SOAP and XML API over HTTP or HTTPS with Autodiscover, broad item and folder access, and streaming, pull, or callback-based push notifications. EWS supports NTLM for on-premises servers and retains Basic authentication only as a discouraged compatibility path that must run over TLS. The strongest administration path is the Exchange Management Shell. Microsoft states it manages every aspect of Exchange, including all graphical-tool tasks and bulk operations, and returns structured .NET objects. It runs through the installed management tools or remote Windows PowerShell and WinRM; there is no Microsoft Exchange Server module in the PowerShell Gallery. Exchange role-based access control limits the cmdlets and parameters available to an administrator. EWS is mature but its developer documentation and managed .NET client are legacy-shaped, and schema version, server version, topology, TLS, RBAC, and mailbox impersonation must be pinned. Exchange Server Subscription Edition also requires active subscription rights or Software Assurance. An on-premises Exchange-specific first-party MCP server and a repeatable computer-use result were not established.

Best path today: cli · Overall automatability: 9/10