Home › Apps › SPFx Development
SharePoint Framework services
SPFx Development Services (SharePoint Framework)
We build custom web parts, extensions, cards for the SharePoint app in Teams and Copilot UX components with the SharePoint Framework, the supported way to extend SharePoint Online. Start from scratch or from our library of 24 ready-made web parts.
The short answer
What is SPFx development?
The SharePoint Framework (SPFx) is Microsoft’s development model for extending SharePoint Online, Microsoft Teams, the SharePoint app in Teams and now Microsoft 365 Copilot. SPFx development means building web parts, extensions and components in TypeScript and React that run in the user’s browser, follow your permissions and keep working through platform updates.
A good SPFx partner builds only what Microsoft supports, requests only the permissions each solution needs and deploys through your app catalog so your admin stays in control.
Custom web parts and extensions
Directories, dashboards, news layouts, branded headers, list tools and integrations built for your pages and your data.
Ready-made web parts, set up
Our 24 SPFx web parts, branded and installed in your tenant, with custom work only where you need something extra.
Add-in and script replacement
Retired SharePoint Add-ins, custom scripts and InfoPath forms rebuilt as supported SPFx or Power Platform solutions.
Our services
SPFx services, end to end.
From the first architecture call to upgrades years later, with the same team throughout.
Plan
Which building block fits: a web part, an extension, a card, a Copilot UX component, or no code at all with Power Apps.
What each retired customization did, and the supported replacement for it.
Microsoft Graph and API scopes, admin approval and app catalog rules agreed before we build.
Build
Directories, dashboards, news layouts and tools built for your pages, with a property pane editors understand.
Branded headers and footers, custom list fields, toolbar actions, list forms and search query modifiers.
Adaptive Card Extensions for the dashboard formerly known as Viva Connections, on desktop and mobile.
The same web part exposed as a Teams tab or personal app and, since SPFx 1.16, in Outlook and the Microsoft 365 app.
Microsoft Graph, SharePoint REST, Dataverse and your own APIs, called securely through Microsoft Entra ID, with Power Automate for the back-end steps.
Interactive UI for Microsoft 365 Copilot agents, generally available with SPFx 1.24, for users with the Microsoft 365 Copilot add-on license.
Run
Older SPFx projects moved to the current release, Heft and a supported Node.js LTS, step by step.
Versioned packages, test and production app catalogs, monitoring and fixes after launch. See our SharePoint consulting services.
What SPFx can build
Web parts, five extension types, cards and Copilot components.
SPFx is one framework with several building blocks. We choose the right one for each need, and one solution package can ship several of them together.
Web parts: the building blocks of a page
A web part is a self-contained component an editor drops onto a modern page. It renders in the page, runs as the signed-in user and gets its settings from a property pane. Most intranet features start here.
Extensions: customize lists, pages and search
Five extension types change the SharePoint experience around the content: Application Customizers add headers and footers, Field Customizers restyle columns, Command Sets add toolbar actions, the Form Customizer replaces list forms and the Search Query Modifier adjusts search queries.
Adaptive Card Extensions: your intranet in Teams
The SharePoint app in Teams, formerly Viva Connections, shows a dashboard of cards on desktop and mobile. SPFx is the only way to build custom cards, so leave balances, tickets, approvals and announcements can reach people who never open a SharePoint page.
Copilot UX components: interactive UI inside Copilot
Generally available with SPFx 1.24, Copilot UX components let a Microsoft 365 Copilot agent show charts, forms and approvals instead of plain text. They ship in the same package as the agent definition and deploy through your app catalog, with no separate hosting.
One component, many places: the same SPFx web part can run on a SharePoint page, as a Teams tab and in Outlook and the Microsoft 365 app without code changes. Agents that answer questions rather than show UI are Copilot Studio work.
Modernization
Replacing retired add-ins and custom scripts.
SharePoint Add-ins and Azure ACS reached end of life in SharePoint Online on April 2, 2026, and custom scripts are blocked by default. SPFx is Microsoft’s primary replacement, and we map every old customization to a supported option.
Stopped working in SharePoint Online on April 2, 2026.
SPFx web parts and extensions, with Microsoft Entra ID for any API access.
Retired on the same date, with no extension.
Microsoft Entra ID app registrations and SPFx permission requests.
Blocked by default; custom script resets to not allowed within 24 hours.
An SPFx web part with the same logic, deployed through the app catalog.
Classic list views only; no modern support.
Field Customizers or column and view formatting.
InfoPath 2013 extended support ended in July 2026.
SPFx Form Customizer or Power Apps forms, depending on the complexity.
Not available in SharePoint Online.
SPFx components plus Power Automate for the server-side steps.
On-premises SharePoint Server is not affected by the add-in retirement, and SPFx still supports SharePoint Server 2016 Feature Pack 2, 2019 and Subscription Edition at older framework versions. We plan migrations with that in mind.
Secure by design
Safe access to Microsoft Graph and your APIs.
SPFx solutions call Microsoft Graph and other APIs through Microsoft Entra ID. The permissions a solution requests are approved by an administrator and then apply across the whole tenant, so we treat every request as a governance decision.
Least privilege
Each solution declares only the scopes it needs in its package, such as reading basic profiles for a directory, never a broad permission “to be safe”.
Admin approval
Your administrator reviews each request on the API access page in the SharePoint admin center. Graph requests need a Global Administrator; your own APIs need an Application Administrator.
Tenant-wide awareness
Approved permissions are granted to the tenant’s SharePoint extensibility principal, so other components can use them too. We document every grant and review them with you.
Reviewed and cleaned up
Code review on every release, no secrets in the bundle, and unused permissions revoked when a solution is retired.
Modern toolchain
Built on the current SPFx release.
The framework moves fast and old projects fall behind quietly. We build new solutions on the current release and upgrade older ones step by step, so they stay supported and secure.
SPFx 1.24 became generally available on October 28, 2026, and Microsoft recommends 1.24.1 for new projects. We track each release and its compatibility table.
SPFx 1.24 supports Node.js 22, 24 and 26, with Node.js 26 LTS recommended for new environments. Older projects often need a Node upgrade first.
Since SPFx 1.22, new projects build with Heft instead of the gulp-based toolchain, which is not supported for 1.24. We migrate build scripts and pipelines with the upgrade.
SPFx 1.24 uses React 18.3.1 and the Fluent UI React library, formerly Office UI Fabric, so components look native in SharePoint, Teams and Copilot.
The SharePoint online workbench is deprecated. We test web parts and extensions on real SharePoint pages with the Debug Toolbar, and Copilot UX components in the Copilot Workbench.
Ready-made web parts
Start faster with our 24 premium web parts.
We build intranets faster with our own library of SPFx web parts. They’re responsive, branded to your company and ready for modern pages, so your custom budget goes into what is unique to you.
See them working together in six intranet designs in our SharePoint lookbook, or add full request apps from our ready-made SharePoint apps, like the SharePoint quiz app built with SPFx.
How we deliver
From idea to your app catalog.
You see a working web part on a real page early, and every release moves through the same path.
Scope
Needs, pages, data, hosts and permissions
Design
Layouts matched to your brand and Fluent UI
Build
TypeScript and React, code reviewed, AI-assisted
Test
Browsers, phones, Teams and real data
Deploy
Through your app catalog, versioned and documented
- Debug Toolbar on real pages
- Source in your repository, versioned
- Site collection app catalog
- Real data, phones, Teams, user sign-off
- Tenant app catalog, enabled for all sites
- Permissions approved, release notes handed over
Ways to work with us
Choose how you want to work with us.
Custom SPFx project
Web parts, extensions, cards or Copilot UX components built to your requirements, with milestones and testing.
Discuss your projectReady-made web parts
Our premium web parts, set up and branded for your intranet, customized where you need something extra.
Book a live demoDedicated SPFx developer
A developer who joins your team full time or part time, matched in one to two weeks and managed by you.
Hire an SPFx developerWhy TSinfo
Why teams choose us for SPFx.
Free consultation
Talk to an SPFx expert.
Need a custom web part, replacing old add-ins or want to see our web parts? In a free 30-minute call we review what you have and suggest the fastest supported path.
- A review of your customization needs
- Custom vs ready-made advice
- Add-in and script replacement plan
- A recommended first step
FAQ
SPFx development questions
What is SPFx used for?
SPFx is used to build custom web parts, extensions, dashboard cards for the SharePoint app in Teams and Copilot UX components for Microsoft 365 Copilot. It’s Microsoft’s recommended way to add features SharePoint Online doesn’t include out of the box, and the only extensibility option for Viva Connections.
Our SharePoint Add-ins stopped working. Can you replace them?
Yes. Add-ins and Azure ACS reached end of life in SharePoint Online on April 2, 2026. We review what each add-in did and rebuild it with SPFx, Power Apps or Power Automate. Microsoft explains the change in its add-in retirement announcement.
Can an SPFx web part run in Teams and Outlook?
Yes. The same SPFx web part can be exposed as a Teams tab or personal app and, since SPFx 1.16, inside Outlook and the Microsoft 365 app without code changes. SharePoint hosts the files, and the solution is added to Teams from the app catalog.
Which SPFx version and Node.js do you use?
New projects use SPFx 1.24.1 on Node.js 26 LTS, with React 18.3.1 and the Heft toolchain, as listed in Microsoft’s SPFx compatibility reference. For existing solutions we check your version first and plan an upgrade path.
Can we buy your web parts instead of a custom build?
Yes. Our 24 premium web parts cover news, events, people, navigation and more. We set them up, brand them and customize them where you need something extra. Book a live demo to see them on a real page.
Who owns the code?
You own all custom code we build for you, delivered to your repository, and we sign an NDA on request. Our ready-made web parts are a one-time purchase with source code and updates included, which we walk you through during the demo.
Related services
Keep exploring
Files behind the web parts? Our document management service sets up the libraries, metadata and retention.
Ready to extend SharePoint the right way?
Tell us what you need. We’ll tell you whether a ready-made web part or a custom build is the faster path.