Microsoft now requires Office Add-in developers to prompt users for permission to access their device capabilities. To do this, you can now implement the Device Permission API.
Announcing the public preview of Nested App Authentication (NAA) and that legacy Exchange user identity tokens and callback tokens will be turned off by default for all Exchange Online tenants in October 2024.
Script Lab is now officially owned and maintained by Microsoft, will no longer be open source, and the GitHub repository will be archived.
We're excited to continue our commitment to supporting our Office Add-ins developer community with a variety of free Microsoft Partner programs.
These APIs extend and enrich the following Word document UI experiences: annotation support, checkbox content control support, and custom XML support.
Discover initial offerings for Office Add-ins developers to mark the beginning of a comprehensive series of encouragement initiatives. Â
As part of the Microsoft Secure Future initiative, we're making improvements to the Microsoft 365 Developer Program. The blog post covers those improvements.
Take a deep dive into the strategies to design an effective Office add-in.
AppSource validation ensures your Office Add-in submission follows Microsoft’s quality standards. In this post, you’ll learn about what the affected AppSource policies are looking for so you can be confident your Office Add-in submission won’t hit these issues.
We’re announcing changes to how Office Add-ins and apps are installed, accessed, and sideloaded to Outlook for Windows and Outlook for Web.
