SharePoint Framework roadmap
The first release of the SharePoint Framework in February 2017 only contained support for client-side web parts. This was just a start on the journey to provide additional modern customization capabilities to SharePoint.
Important
The SharePoint add-in model deprecation in SharePoint Online does not impact SharePoint Framework (SPFx), which is the primary replacement technology for SharePoint add-ins. SPFx is the most widely used extensibility model in Microsoft 365 and continues to be supported also in future.
See more on the SharePoint add-in model retirement from the full add-in model retirement announcement.
The following is a list of key capabilities released after General Availability:
- Dynamic data and web part connections
- Tenant-scoped deployment support
- On-premises support for SharePoint 2016 (Feature Pack 2)
- SharePoint Framework Extensions
- Relocating preview code to isolated packages
- Tenant properties
- Support for Yarn and PNPM package managers
- Application Lifecycle Management (ALM) APIs for SPFx solutions and add-ins
- Office UI Fabric Core support
- Asset packaging and site collection app catalog
- Improved Microsoft Graph integration with additional scopes
- Call securely Azure AD secured applications from SharePoint Framework
- Single Part App Pages
- Building Microsoft Team tabs using SharePoint Framework
- Isolated web parts
- React 16 and TypeScript 3.x support
- Pre-allocate space for the extensions while rendering page in server side
- Use the SPFx API to determine & react to changes in the web part's rendered size
- Use SPFx solutions in Microsoft Teams - support multiple deployment options
- Use SPFx solutions to extend Microsoft Viva Connections
- Building meeting apps for Microsoft Teams with SPFx
Release notes
Refer to the table of contents menu for details on each of the SharePoint Framework releases.
Note
This is a list of areas that SharePoint engineering has in the backlog and is looking into. This does NOT mean that all of them will be delivered, but we are looking into getting items and topics from this list gradually released with the future releases of SharePoint Framework.
Future key focus areas
Note
The following list is subject to change.
General improvements
- Support overriding new, edit, and view experiences with SPFx in Lists and Libraries
- Improved solution metadata support in solution packages
- Service principal registration for full API package model
- Performance improvements across apps (dev and runtime)
Microsoft Teams improvements
- Store acquisition - target SPFx solutions directly to Microsoft Teams store
- Teams store support for partner SPFx solutions
Microsoft Viva Connections improvements
- New card shapes
- More flexibiliy with the Quick View
Store improvements
- Modernize Store app catalog and store UX
- Modernize end-to-end acquisition process for store solutions
Improved communications
- More transparency also on server-side improvements
- More visibility on the issue resolution
Quality improvements
Note
The current state of the SharePoint Framework is reviewed near the beginning of the bi-weekly Viva Connections & SharePoint Framework community call. Previous Viva Connections & SharePoint Framework call recordings can be found on the Microsoft 365 & Power Platform Communtiy YouTube Channel's playlist