Specify runtime requirements in app manifest: Your key to success across Microsoft 365
Specify Runtime Requirements in App Manifest: Your Key to Success across Microsoft 365 Hosts Through extensive user research, we’ve identified what M365 users value most for boosting productivity. They want uninterrupted workflows, an all-in-one workspace, and minimal context switching. With this insight, we evolved Microsoft 365 into a unified platform across Teams, Outlook, M365 app […]
The post Specify runtime requirements in app manifest: Your key to success across Microsoft 365 appeared first on Microsoft 365 Developer Blog.
Published on:
Learn moreRelated posts
Microsoft Teams: Improved app and agent access request flows for admin‑blocked apps
Microsoft Teams will introduce a clearer, guided request flow for access to admin-blocked apps and agents, improving user notifications and ad...
Microsoft 365 Archive: File-level archiving General Availability
Microsoft 365 Archive now supports file-level archiving for SharePoint files, enabling cold storage with discoverability. Rolling out worldwid...
Converting Get-MailboxFolderStatistics ids for use with the Graph API
In this article, we discuss how to convert Exchange folderIds (as returned by the Get-MailboxFolderStatistics cmdlet) to the RestId identifier...
Microsoft Teams: Town hall chat messages now support up to 500 characters
Microsoft Teams town hall chat messages will increase from 200 to 500 characters starting early June 2026. This applies to all attendees with ...
Dynamics 365 Customer Service – Improve customer outcomes with Service Agent in Microsoft 365 Copilot
We are announcing the ability to improve customer outcomes with Service Agent for Microsoft 365 Copilot in Dynamics 365 Customer Service. This...
Microsoft Teams: Voicemail transcription service migration and new languages
Starting June 2026, Microsoft Teams voicemail transcription will migrate to Azure LLM Speech using the Fast Transcription API, improving accur...