GoldenrozBook a call

What is SPFx? The SharePoint Framework explained for IT managers

SPFx, the SharePoint Framework, is Microsoft's recommended model for customizing and extending SharePoint. Developers write client-side components in TypeScript, most often web parts and extensions, package them into a file and deploy that file through the SharePoint app catalog after an administrator approves it. The code runs in the browser with the permissions of the signed-in user, so approval and review are the main governance tasks.

A gold sphere set into a structure of stacked navy and white cubes.

Where SPFx fits

SharePoint can be customized in two broad ways. The first is configuration: pages, built-in web parts, lists, themes, navigation and flows. No code is written and a site owner or administrator does the work. The second is development: new components that do something the built-in parts cannot.

For the second, Microsoft Learn is direct. The SharePoint Framework “is the recommended SharePoint customization and extensibility model for developers”. It is also the way to extend Microsoft Teams with SharePoint-hosted components, and Microsoft states it is the only extensibility and customization option for Viva Connections.

An IT manager does not need to write SPFx code. The useful knowledge is what it is, what a developer will ask for, what you approve when you deploy a package and what it costs to keep.

All technical statements in this post were checked against Microsoft Learn in November 2026. Version details change, so confirm them in the documentation before a project starts.

What SPFx is, in one paragraph

SPFx is a set of libraries and build tools for writing client-side components that run inside SharePoint pages. The code is TypeScript, compiled to JavaScript and executed in the user’s browser. Microsoft’s enterprise guidance says that all parts of the generated artifacts are executed in the end user’s browser, and that the build tools are needed only at build time and not to run the code. There is no server-side code in an SPFx package. If a solution needs a backend, that backend is a separate service with its own hosting and cost.

The component types

Component What it does Typical use in an intranet
Web part A block that an editor adds to a page and configures A leave balance card, a custom news layout, a list of open approvals
Application Customizer (extension) Adds scripts to the page and renders into defined placeholders A company-wide header, footer or alert banner
Command Set (extension) Adds actions to list and library command surfaces A “send for approval” button on a document library
Form Customizer (extension) Replaces the form of a list A custom request form
Field Customizer (extension) Changes how a list field is displayed A status column shown as a coloured label
Adaptive Card Extension A card for the Viva Connections dashboard A “my tasks” card in Teams

Microsoft Learn calls web parts the primary building blocks for pages and the most common SPFx component type. It lists five extension types: Application Customizers, Field Customizers, Command Sets, Form Customizers and Search Query Modifiers.

One caution on Field Customizers. A footnote in the SharePoint service description says Microsoft announced their deprecation for lists and document libraries on June 13, 2025, and that no retirement timeline is currently set. Avoid starting new work on them without checking the current status.

Microsoft’s overview also lists Copilot UX components as a newer SPFx component type, with their own licensing and client requirements. They are outside the scope of a standard intranet.

The tooling a developer will use

SPFx uses the standard web toolchain. From Microsoft’s documentation:

  • Language. TypeScript is the primary language for SPFx artifacts.
  • UI framework. The model is framework-agnostic. The current generator offers React, Minimal and No framework templates for web parts.
  • Runtime and packages. Node.js and npm.
  • Scaffolding. The Yeoman generator for SharePoint creates the project.
  • Build. Heft, starting with SPFx 1.22. Earlier versions used Gulp, which Microsoft now calls the legacy toolchain.
  • Editor. Any. Development works on Windows, macOS and Linux.
  • Testing. On real SharePoint pages in a development site. The local workbench was removed in SPFx 1.13, and Microsoft’s guidance states that the online workbench is deprecated and will be retired on December 1, 2026.

At the time of writing, Microsoft’s enterprise guidance points new SharePoint Online projects to the SPFx 1.24 setup guidance with a current Node.js LTS release and Heft, and notes that SPFx 1.24 uses React 18.3.1. Each SPFx version supports specific Node.js versions, listed in Microsoft’s compatibility reference.

Two practical consequences follow. A general front-end developer who knows TypeScript and React can become productive in SPFx, since the tools are familiar. And an SPFx solution has dependencies that age: an old project often has to be upgraded before it can be built again.

How SPFx reaches data

SharePoint data

The framework gives components the page context and an HTTP client that handles authentication to SharePoint, so a web part can read lists and libraries through the SharePoint REST services as the current user.

Microsoft Graph and other APIs

Microsoft Graph is the API for Microsoft 365 data such as users, calendars, mail and Teams. An SPFx component reaches it through a client the framework provides, MSGraphClientV3. For other APIs secured with Microsoft Entra ID, including your own, the framework provides AadHttpClient.

The permission model has three steps, as described in Microsoft’s tutorial on consuming Microsoft Graph:

  1. The developer declares the permissions the solution needs in the webApiPermissionRequests property of the package configuration, for example User.ReadBasic.All on Microsoft Graph.
  2. When the package is uploaded, the app catalog shows that it requires permission approval.
  3. An administrator approves or rejects each request on the API access page of the SharePoint admin center.

Microsoft’s guidance is to request and approve the least-privileged permission the operation needs. It also describes these grants as working at tenant level, so read the current API permission guidance before approving. A permission approved for one solution deserves the same care as any other organization-wide consent.

Microsoft adds a point that is easy to miss: integrated authentication does not grant access to data. Tenant consent, the user’s own permissions and the API’s requirements still apply.

How a solution is deployed

  1. The developer builds and packages the project. The output is a single .sppkg file.
  2. An administrator uploads the file to the app catalog. There is a tenant app catalog, and site collections can have their own.
  3. SharePoint shows a trust dialog. Microsoft’s guidance says the dialog explains that this is a full trust client-side code solution that executes under the user’s context, and shows the domain the code will load from.
  4. The administrator enables the app. Depending on how the solution was built, it is available tenant-wide or installed site by site.
  5. Editors add the web part to pages, or the extension becomes active.

Since SPFx 1.4, script files and other assets are packaged inside the .sppkg by default and hosted by SharePoint after deployment, from the Microsoft 365 CDN if it is enabled or from an app catalog URL. A solution can also load its scripts from an external CDN, which creates a dependency you should know about.

Updating means uploading a new version of the package. Removing or disabling the package in the app catalog stops the solution on all sites. Microsoft notes that removal does not delete data the solution created.

What an IT manager should govern

Microsoft’s enterprise guidance states plainly that client-side code in SPFx executes under the current user’s context and that there is no way to constrain it after approval. That makes the approval step the control.

A governance checklist:

  • A short list of people who may upload to the app catalog
  • A review before approval: what the code does, which libraries it includes, where its scripts are hosted
  • A register of approved API permissions, each with an owner and a reason
  • Least-privileged Graph permissions, checked against what the component uses
  • Source code in a repository the company owns, including for vendor-built solutions
  • A copy of every deployed .sppkg file kept outside the app catalog
  • A named maintainer and a schedule for upgrading SPFx versions
  • A test site where new versions are checked before the tenant catalog is updated
  • A rule for third-party packages: who hosts the scripts and who can change them
  • A decision on which client-side framework the organization standardizes on

This is a review and control list for administrators. It is not a security audit, and it does not replace one.

What SPFx replaces

Older SharePoint customizations used add-ins or scripts pasted into pages. Microsoft’s documentation records that SharePoint Add-ins reached end of life in SharePoint Online on April 2, 2026, and that the retirement does not affect SPFx. Script pasted into pages depended on the page’s HTML structure, which Microsoft states is not an API and can change at any time.

If your intranet still relies on either, moving those pieces to SPFx or removing them is part of any modernization. The same thinking applies when moving from a file server or an older SharePoint Server: see our Office 365 migration checklist.

When you need SPFx and when you do not

Requirement Approach
News, pages, navigation, document libraries Configuration, no code
A request form with an approval A list and Power Automate
Standard layout with company colours Theme and site settings
Data from HR, payroll or ERP shown on a page SPFx web part plus an API to that system
Company-wide header, footer or banner SPFx Application Customizer
Custom action on a list or library SPFx Command Set
A full application with its own database and complex rules A separate application, linked or embedded

The last row matters. SPFx is a user interface layer. When the requirement is a system with its own data and logic, a custom-built portal may be the better tool, and the comparison is in our post on the SharePoint intranet, its cost and its alternatives. Both routes belong to the wider category of internal systems a company can own.

What to do next

Ask for two lists: the packages in your tenant app catalog with their owners, and the API permissions approved in the SharePoint admin center. If either list has entries nobody can explain, start there.

If you are planning custom components for an intranet, a scoping call with Shai covers which requirements need SPFx and which need only configuration. That work is delivered through SharePoint intranet development, from $25,000 at a fixed price per phase. Goldenroz is independent and is not a Microsoft partner.

Questions buyers ask

What does SPFx stand for?

SPFx stands for SharePoint Framework. Microsoft describes it as a page and web part model that provides full support for client-side SharePoint development, and as the recommended SharePoint customization and extensibility model for developers.

What language is SPFx written in?

TypeScript is the primary language. The framework itself is framework-agnostic, and Microsoft's documentation lists React among the supported choices. The current project generator offers React, Minimal and No framework templates for web parts.

Is SPFx only for SharePoint Online?

No. According to Microsoft Learn it is also supported on SharePoint Server going back to SharePoint Server 2016, with older framework versions tied to each server release. Tenant-wide deployment is available only in SharePoint Online. SPFx components can also extend Microsoft Teams and Viva Connections.

Is SPFx safe to deploy?

It is the supported model, and every package must be approved by an administrator in the app catalog. The approval matters because standard SPFx web parts run in the page with the permissions of the current user. Microsoft's guidance is that administrators should review the code and dependencies before approving deployment.

Do we need SPFx to build a SharePoint intranet?

Not for a standard one. Pages, news, navigation and libraries need no code. SPFx is needed when the built-in web parts do not cover a requirement, such as showing data from an HR or ERP system, adding a custom header or footer, or adding a command to a list.

Written by

CTO and technology partner

Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.

Keep reading

Talk to the person who will do the work

One hour, no sales team. You talk to Daniel or Shai, we look at your account or your product, and you leave with a clear next step.

Or send the details

Book a 1-hour consultationWhatsApp us