M365 Across App scenarios - Teams apps and SPFx
As you can also use SharePoint Framework (SPFx) to create Microsoft Teams applications you can now use SPFx with 1.16 onwards across Microsoft 365 as well.
A Microsoft Teams Personal Tab
A search-based messaging extension allows you to select from a defined resultset of existing objects, such as documents or people and insert this selection into a compose message without any modification to the selected object.
Instead of the search-based messaging extension the action-based variant allows to interact with the user about selection or modification or even creation of that selection. Instead of a simple pick here you can create custom forms or at least more customized selection areas.
A Microsoft Teams application can be personal or configurable Tab, a Bot, a messaging extension or a connector. It can be a standalone app or tailored to specific scenarios such as a team, a channel or a meeting.
Outlook can either reuse a personal tab as standalone app or it can use a search-based messaging extension in mail composer, that is while a mail is created. The context of an incoming mail cannot be used, yet. Also the more flexible action based messaging extension cannot be used, yet.
Office can reuse a personal tab as standalone app. So you can show the same app experience in Office or even a slightly different on by detecting in code if Office or a different product is host of your app.
A teams native app is a web application including Teams JS SDK and can be built either by using Yeoman Generator for Teams or the Teams Toolkit for Visual Studio (code). And not to forget the PowerPlatform. The teams manifest (with JSON based notation) declares the app as a Teams application and the Teams JS SDK gives you access to the Teams-specific context. For hosting you need a separate web application, for instance an Azure app service.
SharePoint Framework (SPFx) provides full support for client-side SharePoint development. But despite the name SharePoint it’s much more than that. It can also be extended to other Microsoft 365 scenarios. SharePoint framework is self hosting. So no need to acquire additional resources for this. SharePoint framework runs client-side only and in user context. For user impersonation or well performing backend operations you might still need additional backend components. Although direct access to Microsoft Graph is available within, the security model is debatable and might also need the implementation of backend components.
|Personal app||Teams App|
|Search-based messaging extension||Teams App||Teams App||-|
|Action-based messaging extension||Teams App|
The big benefit for this approach now is that user permissions to such apps only need to be configured once and not product (Teams, Office, Outlook) individually. As a downside it’s not yet controllable if such an app (mostly a personal tab) shall be published to Teams only for instance. That is, a personal tab with Teams manifest 1.13+ published to your org’s app catalog will be visible in Outlook, too, in targeted release tenants at the moment of writing this post. A GA is awaited for first half of 2023. Meanwhile you can only control the product inside the code which would enable you at least to hide your functionality/UI in Office or Outlook wheras still showing it in Teams.
I already provided one sample illustrating (not only) that capability which you may find here. And I am currently working on another one which will come in two flavors, realized by using Yeoman Generator for Teams but also an alternative that uses SPFx.
I hope you enjoyed this post and found some helpful information. I expect a lot more to come with “development across Microsoft 365” and I am highly interested in moving and bringing this forward and adapt new capabilities.
Feel free to leave a comment here, in the referenced blog posts or directly reach out to me on Twitter