Skip to content

SharePoint

What is SPFx?

By Suresh Girinathuni

Quick answer

SharePoint Framework (SPFx) is Microsoft’s client-side development model for extending SharePoint and related Microsoft 365 experiences. Developers build web parts and extensions with standard web tooling — TypeScript, Node.js, and frameworks such as React — and the resulting components run in the browser in the context of the current user, with no iframes.

Key takeaways

  • Client-side model: TypeScript, React, and standard web tooling — no iframes.
  • Build web parts plus Application, Field, and Command Set extensions.
  • Deploy .sppkg via the app catalog with admin-approved API permissions.

Detailed Explanation

SharePoint Framework (SPFx) is Microsoft’s client-side development model for extending SharePoint and related Microsoft 365 experiences. Developers build web parts and extensions with standard web tooling — TypeScript, Node.js, and frameworks such as React — and the resulting components run in the browser in the context of the current user, with no iframes.

How it works

You scaffold a project with the SharePoint Framework Yeoman generator, build with the standard toolchain (npm, TypeScript, gulp/webpack), and package the solution as an .sppkg file deployed to the SharePoint app catalog. Tenant administrators approve the solution and any API permissions it requests. The same component model extends SharePoint pages (web parts), list and library experiences (extensions such as Application Customizers, Field Customizers, and Command Sets), Microsoft Teams, and Viva Connections (Adaptive Card Extensions).

Limitations and considerations

SPFx is client-side only — there is no server-side code. Solutions need tenant admin approval and API permission grants before they can call Microsoft Graph or other protected APIs. Match the React and Node.js versions supported by your SPFx version, and never depend on the SharePoint page DOM structure, which Microsoft can change.

This Q&A page is the short-answer layer for “What is SPFx?” Use the related guides below when you need implementation steps, architecture trade-offs, or troubleshooting detail.

For broader context, visit the SharePoint Hub. It connects this topic to surrounding Microsoft 365, Power Platform, SharePoint, Copilot Studio, Dataverse, migration, and Dynamics 365 guidance.

When to use it

Use SPFx when you need custom web parts, branded page experiences, list/library customizations, or Teams and Viva surfaces that low-code options cannot deliver. For form-style business apps, compare with Power Apps first.

Practical example

An IT team ships an employee-directory web part: it reads profiles through Microsoft Graph, renders with React, and is deployed once to the app catalog so every intranet site owner can add it to a page.

Sources