Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Build SharePoint and Microsoft 365 experiences with SharePoint Framework (SPFx), declarative customization, supported APIs, and Power Platform. Choose the development model for the experience and host you need.
Introducing the SharePoint development platform
SPFx provides client-side components, tenant deployment, and integration with Microsoft 365 hosts. With SPFx 1.24, Copilot UX components add interactive UI to Microsoft 365 Copilot conversations. Web parts, extensions, and Adaptive Card Extensions address different SharePoint, Teams, and Viva Connections scenarios.
Use the supported-platform overview and compatibility reference before selecting a framework version. A component's host, permissions, licensing, and supported clients are part of its requirements, not interchangeable defaults.
What kinds of development can you do with SharePoint?
| Goal | Start here |
|---|---|
| Render interactive experiences in Microsoft 365 Copilot | Copilot UX components |
| Add client-side web parts to SharePoint pages | SPFx web parts |
| Extend page, list, or form experiences | SPFx extensions |
| Build Viva Connections cards | Viva Connections and SPFx |
| Reuse web-part functionality in Microsoft Teams | SPFx integration with Teams |
| Format list columns and views without a custom component | Column formatting and view formatting |
| Apply repeatable site configuration | Site templates and site scripts |
| Build forms and automate processes | Power Apps and Power Automate |
| Access sites and content through APIs | SharePoint in Microsoft Graph and SPFx data access |
Set up your development environment and start developing
For SPFx 1.24, follow the development environment setup with Node.js 26 LTS. Use the version-specific prerequisites for older projects and SharePoint Server.
- Build your first Copilot UX component.
- Build your first web part.
- Build your first extension.
- Debug web parts on actual SharePoint pages with the developer toolbar. Use the fully supported Copilot Workbench for Copilot UX components.
Copilot UX components require the Microsoft 365 Copilot add-on USL on top of E3, E5, or E7. Review availability and client limitations, deployment and dynamic discovery, and visible context.
Publish and distribute your solution
Copilot UX components are supported in the SharePoint Store starting with SPFx 1.24 GA. Use the Marketplace guidance and submission checklist. Store publication doesn't bypass tenant deployment, license requirements, API consent, or supported-client restrictions.
SharePoint Server development
Server solutions have version-specific APIs, deployment models, and tooling. Follow the Server support guidance and, for server-side customizations, farm solution guidance. Don't treat farm deployment or old mobile-platform walkthroughs as current SharePoint Online setup.