Turn your real-world experience into part of the show.

Glen Scales

Glen Scales Profile Photo

Developer

Glen Scales is a Microsoft MVP and senior developer based on the Sunshine Coast, Australia, specializing in Exchange, Active Directory, Office 365, and Teams. He's been blogging about mail development and Exchange since 2004 — over 20 years of hands-on, in-the-trenches technical writing that has become essential reading for anyone building on Microsoft's messaging platform.

Glen's expertise runs deep across every Exchange programming model — from the early days of CDO and WebDAV through Exchange Web Services to the Microsoft Graph API. His blog posts and code samples don't just explain how things *should* work; they map out the undocumented corners, the gray areas, and the practical workarounds that only surface when you're building real solutions. Whether it's sending MIME messages via Graph, migrating directory access code from EWS, or navigating large attachment uploads, Glen has been there first and written the guide.

He shares his tools and PowerShell libraries openly on GitHub, is a trusted voice on Stack Overflow with over one thousand answers, and now publishes his latest work on his [eMail Development Substack](https://glenscales.substack.com/). If you've ever searched for an answer to an Exchange development question, chances are Glen's work pointed you in the right direction.

May 20, 2026

Migrate Exchange Web Services to Microsoft Graph with Glen Scales [MVP]

Microsoft is ending support for Exchange Web Services (EWS) in Exchange Online, with full retirement starting October 2026. The article explains why this matters for Microsoft 365 administrators, developers, ISVs, backup vendors, and enterprises still relying on legacy integrations. EWS has been a core API for mailbox access, calendar synchronization, migrations, archiving, and third-party tools for years, but Microsoft is now pushing organizations toward Microsoft Graph as the modern replacement. The article highlights that this is not just a technical API change. Many existing applications, scripts, automation processes, monitoring tools, and enterprise workflows still depend heavily on EWS. Organizations that fail to identify these dependencies early may face outages, broken integrations, compliance risks, or unsupported applications once Microsoft disables the service. A major focus is the migration challenge. While Microsoft Graph offers a modern, secure, and unified API mo…