In addition, we will also cover the following improvements:<\/p>\n
- \n
- Send notifications at scale with TeamsFx SDK<\/span><\/li>\n
- Improved single sign-on experience in
React with Fluent UI<\/code> template<\/span><\/li>\n<\/ul>\nOpen your existing SharePoint Framework projects<\/h2>\n
<\/p>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/07\/SPFx-Existing-App-1.png\")
<\/a><\/p>\nCurrently, Teams Toolkit only supports developers extending Teams platform with SharePoint Framework by creating a new application and developers enjoy automation brought with the toolkit. There have been increasing requests by the community to bring existing SPFx solutions created from other tooling, such as Yeoman generator, into Teams Toolkit.<\/p>\n
We are thrilled to announce this feature is coming to the July prerelease of Teams Toolkit.<\/p>\n
<\/p>\n
Implement link unfurling in Teams and Outlook<\/h2>\n
![](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/07\/word-image-14704-2.png\")
<\/p>\nLink unfurling is a Teams platform feature that allows developers to create a web service to subscribe to receive an invoke when URLs containing a particular domain are pasted into the compose message area and “unfurl” the URL into a detailed card, providing more information than the standard website preview card.<\/p>\n
Now Teams Toolkit has crafted a new app template to get you started building link unfurling features fast. With the app template, you can:<\/p>\n
- \n
- Unfurl links into an Adaptive Card in Teams and Outlook.<\/li>\n
- Unfurl previews for your shared links even before a user discovers or installs your app in Teams with Zero Install capabilities<\/a>.<\/li>\n
- Extend the application template with rich platform capabilities such as Stage Views<\/a>.<\/li>\n<\/ul>\n
<\/p>\n
Create a Microsoft Teams bot from an OpenAPI Specification<\/h2>\n
![](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/07\/word-image-14704-4.png\")
<\/p>\nMany developers start building Teams integrations based on existing APIs. While we offer app templates and samples to help developers get started, we have still seen many of them spend a lot of time understanding the complexities of Teams platform capabilities.<\/p>\n
We are thrilled to announce the Public Preview of
api2Teams<\/code> – It is a command line tool to generate a complete conversational style command and response Teams application based on your OpenAPI specification file and represent the API response in the form of Adaptive Cards. You can open the generated Teams bot in Teams Toolkit for Visual Studio to test the app in Teams and continue your work from there.<\/p>\nWe hope this is the best way to start integrating your APIs with the Teams conversational experience.<\/p>\n
Follow the quick start<\/a> guide to try it today, open a discussion<\/a> or create an issue<\/a> in GitHub if you want to leave feedback for us.<\/p>\n
<\/p>\n
Send notifications at Scale with TeamsFx SDK<\/h2>\n
Teams Toolkit provides an easy way for developers to get started with sending notifications into Teams with a bot. However, we have got a challenging question:\u201d How do I handle sending notifications at scale\u201d? Specifically, developers are having challenges with the performance of these operations:<\/p>\n
- \n
- Listing where are all the bot apps installed. Imagine the bot app could be installed in a tenant with over 300K users.<\/li>\n
- Send notifications to a specific installation.<\/li>\n<\/ul>\n
![](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/07\/word-image-14704-3.png\")
<\/p>\nGiven this, we have made a couple of updates in TeamsFx SDK:<\/p>\n
- \n
- Rename existing internal class
ConversationReferenceStore<\/code> toDefaultConversationReferenceStore<\/code>.<\/li>\n- Deprecate existing interface
NotificationStorage<\/code>.<\/li>\n- Add new interface
ConversationReferenceStore<\/code> with pagination API support.<\/li>\n<\/ul>\nexport interface ConversationReferenceStore {\r\n\r\n\u00a0 \/**\r\n\u00a0 \u00a0* Add a conversation reference to the store. If overwrite, update existing one, otherwise add when not exist.\r\n\u00a0 \u00a0* @returns true if added or updated, false if not changed.\r\n\u00a0 \u00a0*\/\r\n\r\n\u00a0 add(\r\n\u00a0 \u00a0 key: string,\r\n\u00a0 \u00a0 reference: Partial<ConversationReference>,\r\n\u00a0 \u00a0 options: ConversationReferenceStoreAddOptions\r\n\u00a0 ): Promise<boolean>;\r\n\r\n\u00a0 \/**\r\n\u00a0 \u00a0* Remove a conversation reference from the store.\r\n\u00a0 \u00a0* @returns true if exist and removed, false if not changed.\r\n\u00a0 \u00a0*\/\r\n\r\n\u00a0 remove(\r\n\u00a0 \u00a0 key: string,\r\n\u00a0 \u00a0 reference: Partial<ConversationReference>\r\n\u00a0 ): Promise<boolean>;\r\n\r\n\u00a0 \/**\r\n\u00a0 \u00a0* List stored conversation reference by page.\r\n\u00a0 \u00a0* @returns a paged list.\r\n\u00a0 \u00a0*\/\r\n\r\n\u00a0 list(\r\n\u00a0 \u00a0 pageSize?: number,\r\n\u00a0 \u00a0 continuationToken?: string\r\n\u00a0 ): Promise<PagedData<Partial<ConversationReference>>>;\r\n}\r\n\r\nexport interface ConversationReferenceStoreAddOptions {\r\n\u00a0 overwrite?: Boolean;\r\n}<\/code><\/pre>\n- \n
- Add new options for users to set customized conversation reference store, and deprecate existing option to set customize notification target storage.<\/li>\n<\/ul>\n
export interface NotificationOptions {\r\n\r\n\u00a0 botAppId?: string;\r\n\u00a0 store?: ConversationReferenceStore;\r\n\r\n\r\n\u00a0 \/**\r\n\u00a0 \u00a0* @deprecated Please use NotificationOptions.store instead.\r\n\u00a0 \u00a0*\/\r\n\r\n\u00a0 storage?: NotificationTargetStorage;\r\n\r\n}<\/code><\/pre>\nImproved single sign-on experience in
React with Fluent UI<\/code> template<\/h2>\nThe \u201cReact with Fluent UI\u201d app template has adopted Authorization Code<\/a> Flow to implement single sign-on with the intention of making our app template as lightweight as possible.<\/p>\n
There\u2019s a known limitation to using it with mobile platforms such as iOS and a few Android versions where users have to sign in again as the state was not stored due to third-party cookies being blocked by the browser<\/a>.<\/p>\n
To help developers achieve a full SSO experience, we are now updating the app template with the on-behalf-of (OBO) flow implementation for SSO, which requires you to implement a backend service and pass your token to it.<\/p>\n
The updated app template can help you get started, and you can dive deeper into the SSO in this document<\/a>.<\/p>\n
<\/p>\n
We \ud83d\udc96 your feedback<\/h2>\n
Thank you for all your feedback that has helped make this release possible. Build with us on GitHub<\/a>, share feedback as an issue<\/a>, or email our team directly at ttkfeedback@microsoft.com<\/a>.<\/p>\n
We are excited for you to try Teams Toolkit for Visual Studio Code Prelease<\/a> and \u201capi2teams<\/a>\u201d. Please share your experience with us.<\/p>\n
More resources:<\/p>\n
- \n
- Visit our Microsoft 365 Dev Center.<\/a><\/li>\n
- Follow us on Microsoft 365 Developer (@Microsoft365Dev) \/ Twitter<\/a> for the latest news and announcements.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
In this update, we share the latest with Microsoft Teams app development using Teams Toolkit for Visual Studio Code.<\/p>\n","protected":false},"author":43243,"featured_media":14752,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[128,9],"tags":[23,44],"class_list":["post-14704","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-teams","category-sharepoint-framework","tag-teams-toolkit","tag-visual-studio-code"],"acf":[],"blog_post_summary":"
In this update, we share the latest with Microsoft Teams app development using Teams Toolkit for Visual Studio Code.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/14704","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/43243"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=14704"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/14704\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/14752"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=14704"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=14704"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=14704"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Follow us on Microsoft 365 Developer (@Microsoft365Dev) \/ Twitter<\/a> for the latest news and announcements.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
- Visit our Microsoft 365 Dev Center.<\/a><\/li>\n
- Deprecate existing interface
- Rename existing internal class
- Extend the application template with rich platform capabilities such as Stage Views<\/a>.<\/li>\n<\/ul>\n
- Improved single sign-on experience in