{"id":306,"date":"2017-08-09T00:00:00","date_gmt":"2017-08-09T00:00:00","guid":{"rendered":"http:\/\/officedevblogs.wpengine.com\/?p=306"},"modified":"2021-11-15T10:38:14","modified_gmt":"2021-11-15T18:38:14","slug":"engage-more-users-with-sharepoint-framework-parts-and-extensions-announcing-tenant-scoped-sharepoint-framework-package-deployment","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/engage-more-users-with-sharepoint-framework-parts-and-extensions-announcing-tenant-scoped-sharepoint-framework-package-deployment\/","title":{"rendered":"Engage more users with SharePoint Framework Parts and Extensions: Announcing Tenant-Scoped SharePoint Framework Package Deployment"},"content":{"rendered":"<div id=\"body-content\">\n<p>You can use new capabilities released today that provide more options for engaging broader audiences with your SharePoint Framework (SPFx) web parts. We are pleased to announce a new tenant-wide SPFx deployment option, which complements the existing site-collection targeted deployment option. Developers can choose to mark their solution as being ready for tenant-scoped deployment which gives tenant administrators the option to make a SPFx solution and its corresponding parts and extensions immediately available across all site collections in a tenant.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2018\/05\/todotracker.png\" alt=\"\" width=\"659\" height=\"401\"><br><em>Image: a SharePoint Framework client-side solution can be deployed to all sites, across a tenancy<\/em><\/p>\n<p>You can plan for tenant-wide deployment with newly <a href=\"https:\/\/aka.ms\/tenantdeploydocs\">available documentation<\/a>&nbsp;and <a href=\"https:\/\/aka.ms\/tenantdeployvideo\">this overview video<\/a>.<\/p>\n<p>With tenant-scoped deployment, declarative provisioning to sites via feature.xml is not available. Therefore, developers should consider whether their solution requires feature.xml-based provisioning. To mark a solution as tenant-wide deployable, developers will also need to mark their packages with the SkipFeatureDeployment flag. This then gives administrators the option of deployment scopes for their SharePoint Framework solutions.<\/p>\n<p>The tenant-scoped deployment option is now generally available across all Office 365 tenants.<\/p>\n<p>With these new tenant-wide deployment options, it&rsquo;s easier to get SharePoint Framework web parts into the hands of your users. We&rsquo;d love to hear your feedback on tenant-scoped deployment, as well as your requests for new deployment tools and options you may need. Let us know on the <a href=\"https:\/\/techcommunity.microsoft.com\/t5\/SharePoint-Developer\/bd-p\/SharePointDev\">SharePoint TechCommunity<\/a>.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>You can use new capabilities released today that provide more options for engaging broader audiences with your SharePoint Framework (SPFx) web parts. We are pleased to announce a new tenant-wide SPFx<\/p>\n","protected":false},"author":69078,"featured_media":307,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[9],"tags":[],"class_list":["post-306","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sharepoint-framework"],"acf":[],"blog_post_summary":"<p>You can use new capabilities released today that provide more options for engaging broader audiences with your SharePoint Framework (SPFx) web parts. We are pleased to announce a new tenant-wide SPFx<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/306","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\/69078"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=306"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/306\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/307"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}