Most engineers interact with Microsoft 365 as a set of applications: Outlook for mail, Teams for chat and meetings, SharePoint for documents, OneDrive for personal storage, Excel for spreadsheets. That is the user's view of the platform. The developer's view is different. Underneath those applications is a unified data and identity plane, exposed through a small number of APIs and governed by a common set of policies. Understanding that plane is what turns a developer who writes Office add-ins into a platform engineer who builds products on top of Microsoft 365.
Microsoft 365 Platform Engineering is the engineer's guide to that platform.
You'll go from the foundations — the tenant model, Microsoft Graph, authentication, and permissions — into building on Graph: the SDKs, change notifications, Data Connect for bulk reads, and the Graph Toolkit for rapid front-end integration. Part III covers Teams and SharePoint: the app manifest, bots, message extensions, Adaptive Cards, SPFx web parts, and Viva Connections. Part IV is production: ALM and CI/CD with the Teams Toolkit, tenant governance, Purview compliance, and three closing case studies — the regulated enterprise, the multi-tenant ISV, and the internal automation platform.