{"id":5078,"date":"2020-07-16T08:30:57","date_gmt":"2020-07-16T15:30:57","guid":{"rendered":"https:\/\/officedevblogs.wpengine.com\/?p=5078"},"modified":"2021-11-17T13:15:36","modified_gmt":"2021-11-17T21:15:36","slug":"announcing-sharepoint-framework-1-11-extend-more-of-microsoft-teams-and-publish-to-appsource","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/announcing-sharepoint-framework-1-11-extend-more-of-microsoft-teams-and-publish-to-appsource\/","title":{"rendered":"Announcing SharePoint Framework 1.11: Extend more of Microsoft Teams, and publish to AppSource"},"content":{"rendered":"

SharePoint Framework (SPFx) has emerged as one of the most popular extensibility points across Microsoft 365 – thousands of different solutions have been built using SharePoint Framework, and every day, millions of users visit sites and teams that have been customized with these solutions.\u00a0 The demand for customized experiences is clearly high \u2013 and to address this, we are taking steps to make it even easier to find and deploy the right solution for your teams and your organization, through a common commercial marketplace.<\/p>\n

We\u2019re pleased to announce the next step to make SharePoint Framework solutions widely available by supporting publishing in Microsoft AppSource, the commercial marketplace for Microsoft 365. Today, version 1.11 to SharePoint Framework is now available, which adds new marketplace description capabilities for developers.\u00a0 With this version of SharePoint Framework, software vendors can now publish SharePoint Framework solutions to the marketplace and to the SharePoint store, making it even easier for administrators to find and deploy new SharePoint customizations.<\/p>\n

With SharePoint Framework version 1.11, additional metadata around the solution<\/a>, including Teams capabilities, can be added by developers into their SPFx packages to prepare them for submission to the store.\u00a0 Once a package has been updated to the 1.11\u2019s version of the manifest and various properties are updated, that solution can then be submitted to the AppSource validation experience.\u00a0To find out more about publishing your app to the store,\u00a0read this guide for adding apps via Partner Center<\/a>, and see the release notes for SharePoint Framework version 1.11<\/a>.<\/p>\n

For developers, you can use Microsoft Partner Center to manage the process of submitting your SharePoint Framework solutions. Once validated and approved, your solution will become available in the in-product store, as well as Microsoft AppSource. As a developer, you can also take advantage of marketplace capabilities \u2013 for example, adding transactions to your core SaaS app, or participating in Marketplace Rewards.<\/p>\n

\"SharePoint<\/p>\n

SharePoint applications within AppSource<\/a><\/em><\/p>\n

For IT administrators, deployment is consistent with how an administrator would add an add-in via the Store \u2013 in the SharePoint app catalog, select add an app, show Store apps, and then choose from the newly available apps.\u00a0\u00a0 After prompts to ensure that you trust the vendor of a solution, your application will be added to the SharePoint app catalog.\u00a0 From there, you can optionally deploy Teams extensions from the package, if any.\u00a0 We expect within weeks applications from many valued partners will soon be available through the Store.<\/p>\n

Extending Microsoft Teams<\/strong><\/p>\n

SharePoint Framework continues to grow and expand as a set of tools for extending Microsoft Teams – more users are experiencing Tabs in Teams that were built with SPFx.\u00a0 With SharePoint Framework version 1.11, and alongside technologies such as the Microsoft Bot Framework, SharePoint Framework developers can create task modules and messaging extensions experiences within Microsoft Teams \u2013 enabling developers to directly extend chat conversations with the power of the web and SharePoint Framework<\/a>.<\/p>\n

To see a preview and demonstration of both new Teams capabilities and Store options, see our Build session<\/a> that covers these updates to the SharePoint Framework.\u00a0 To everyone who has built SPFx solutions, now is a great time to consider whether you want to make them more broadly available with a range of capabilities through the Microsoft commercial marketplace.\u00a0 For every administrator, stay tuned to see the broad array of new apps that will become available for SharePoint within AppSource<\/a>.\u00a0 We look forward to the many new solutions developers will offer through these marketplace experiences, and across SharePoint and Microsoft Teams.<\/p>\n","protected":false},"excerpt":{"rendered":"

We\u2019re pleased to announce the next step to make SharePoint Framework solutions widely available by supporting publishing in Microsoft AppSource, the commercial marketplace for Microsoft 365.<\/p>\n","protected":false},"author":69076,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[128,9],"tags":[64],"class_list":["post-5078","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-teams","category-sharepoint-framework","tag-appsource"],"acf":[],"blog_post_summary":"

We\u2019re pleased to announce the next step to make SharePoint Framework solutions widely available by supporting publishing in Microsoft AppSource, the commercial marketplace for Microsoft 365.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5078","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\/69076"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=5078"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5078\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=5078"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=5078"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=5078"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}