Extend SharePoint with SPFx

The SharePoint Framework is Microsoft's supported model for extending SharePoint Online and Teams with your own code — web parts, extensions and Adaptive Card extensions built in TypeScript and usually React. You need it when the out-of-the-box web parts genuinely cannot express what the page has to do. If a modern page, a list view or a Power App can do the job, that is the cheaper and more durable answer.

SPFx is the supported extensibility model, so it survives updates in a way that the old approaches did not. Solutions built with sandboxed code, farm solutions or script injection are the ones that break. SPFx components still need a version bump periodically as Microsoft moves the framework forward, which is ordinary maintenance rather than a rebuild.

It runs in the user's browser, in the page's own context, so it sees exactly what that user is permitted to see — an SPFx web part cannot show someone a document their permissions deny. Calls to Microsoft Graph or to your own APIs go through Azure AD with permissions an administrator approves once for the whole tenant.

Yes. An SPFx web part can be exposed as a Teams tab or a personal app from the same codebase, which is usually the reason to choose SPFx over a standalone web application: one deployment, one permission model, two places it appears.

You own it. We deliver the source, the build pipeline and the documentation, and the solution package lives in your own app catalogue. Teams with in-house front-end capability often take it from there; where that capability does not exist we keep it maintained under the same support model as our other work.