SharePoint Framework roadmap

The first release of the SharePoint Framework contained only support for client-side web parts. This was, however, just a start on the journey for providing additional modern customization capabilities to SharePoint. Following is a list of key capabilities released after General Availability:


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.

General improvements

  • Easy access to Graph API to access user specific information (GraphHttpClient in preview)
  • Site level WebHooks
  • Updated 'store' story with SharePoint Framework support
  • 'Store' story for SharePoint Framework solutions with easy distribution channel for ISVs

Client-side web parts++ and add-ins

  • Support more complex scenarios and interactions with web parts

    • Part-to-part communication
    • JavaScript Framework isolation
    • "Citizen developer" model for lightweight development
  • Bring add-ins to the modern world: let’s make them play nicer with the new UX

    • Azure AD registration
    • Native responsive support
    • Build add-ins with SharePoint Framework

Application Lifecycle Management

  • Streamlined approval experience: no need to know who your tenant admin is anymore
    • Owner initiates the approval process.
    • Tenant admin gets automatically notified.
    • Settings to control the default experience around approval process.

Developer experience

  • SharePoint Framework Workbench 2.0: Development story for SharePoint Framework Extensions
  • Toolchain components
  • Additional Yeoman templates

Already shipped capabilities

The following sections list older items that have already shipped.

Asset packaging

  • Automatic CDN hosting for code. Package JavaScript bundle into app package, which is automatically deployed to a library that gets hosted on your tenant Office 365 CDN.


  • ALM REST APIs. Deploy, activate, delete, and upgrade apps and add-ins.
  • ALM REST APIs targeted to support everything in the app catalog, including add-ins.
  • CSOM and PowerShell cmdlets released as an open source community initiative.
  • The same toolchain and deployment model as client-side web parts.
  • Derive from a strongly typed base class wherever possible, rather than manipulating the page DOM directly.
  • Enable modern extension usage with modern experiences similar to Custom Actions and JSLink in classic experience.
  • Work with NoScript via tenant app catalog.

On-premises support - Sharepoint 2016 Feature Pack 2

  • Shipping as part of Feature Pack 2 for SharePoint 2016.
  • Similar feature capabilities as in SharePoint Online.
  • Target is to provide common development platform across on-premises and the cloud.
  • Leveraging modern toolchain and open source in on-premises environments.
  • Targeting SharePoint 2016 version during calendar year 2017.

See also