Overview of the SharePoint Framework
Observed content change
May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices; check the roles and permissions you grant.
Changed article references · 9 added · 5 removed
- Removed link: Microsoft 365 Copilot
copilot/overview-copilot-apps - Removed link: Overview of SharePoint Copilot Apps
copilot/overview-copilot-apps - Removed link: full add-in model retirement announcement
https://aka.ms/retirement/addins/support - Removed link: multiple applications
office/overview - Removed link: SharePoint Framework Yeoman Generator
set-up-your-development-environment - Added link: Develop and deploy Copilot UX components
copilot/development-and-deployment - Added link: Copilot UX components
copilot/overview-copilot-apps - Added link: Overview of Copilot UX components
copilot/overview-copilot-apps - Added link: licensing and supported-client requirements
copilot/overview-copilot-apps#availability - Added link: Copilot UX component samples
https://aka.ms/spfx/copilot/samples - Added link: SPFx web part samples
https://pnp.github.io/sp-dev-fx-webparts/ - Added link: supported applications
office/overview - Added link: Publish SharePoint Framework applications to the marketplace
publish-to-marketplace-overview - Added link: SharePoint Framework development environment and generator
set-up-your-development-environment
[added: Start with the SharePoint Framework development environment and generator. Tooling extensions, such as the SharePoint Framework Toolkit, can assist with supported scenarios; check their SPFx and component-type requirements. Share UI and business logic across hosts while using the appropriate component type, host adapter, manifest, and deployment configuration.]
Before: No saved wording on this side.
After: Start with the SharePoint Framework development environment and generator. Tooling extensions, such as the SharePoint Framework Toolkit, can assist with supported scenarios; check their SPFx and component-type requirements. Share UI and business logic across hosts while using the appropriate component type, host adapter, manifest, and deployment configuration.
[added: Integrated authentication – Use the framework-provided clients for supported signed-in-user API access. Authentication doesn't grant access to data: tenant consent, user permissions, API requirements, and host behavior still apply.]
Before: No saved wording on this side.
After: Integrated authentication – Use the framework-provided clients for supported signed-in-user API access. Authentication doesn't grant access to data: tenant consent, user permissions, API requirements, and host behavior still apply.
[added: Component hosting – SharePoint can host packaged component assets. External APIs and backend services used by a solution have their own hosting, operations, licensing, and cost requirements.]
Before: No saved wording on this side.
After: Component hosting – SharePoint can host packaged component assets. External APIs and backend services used by a solution have their own hosting, operations, licensing, and cost requirements.
[added: Reuse shared code across supported applications, and validate the solution in each host it targets. The following image illustrates a reference solution.]
Before: No saved wording on this side.
After: Reuse shared code across supported applications, and validate the solution in each host it targets. The following image illustrates a reference solution.
Use SPFx to extend Microsoft 365 Copilot by building[removed: SharePoint]Copilot[removed: Apps.][added: UX components, generally available with SPFx 1.24 on October 28, 2026.] A[removed: Copilot App][added: solution] packages interactive UI components that render inside a Copilot conversation together with a declarative agent definition, and deploys through the[removed: same]SharePoint app[removed: catalog you already use. SharePoint][added: catalog. See the licensing and supported-client requirements, including the required] Copilot[removed: Apps are currently in preview.][added: add-on license and the iOS/Android exclusions at GA.]
Before: Use SPFx to extend Microsoft 365 Copilot by building SharePoint Copilot Apps. A Copilot App packages interactive UI components that render inside a Copilot conversation together with a declarative agent definition, and deploys through the same SharePoint app catalog you already use. SharePoint Copilot Apps are currently in preview.
After: Use SPFx to extend Microsoft 365 Copilot by building Copilot UX components, generally available with SPFx 1.24 on October 28, 2026. A solution packages interactive UI components that render inside a Copilot conversation together with a declarative agent definition, and deploys through the SharePoint app catalog. See the licensing and supported-client requirements, including the required Copilot add-on license and the iOS/Android exclusions at GA.
[added: Follow Develop and deploy Copilot UX components for initial agent sync and later runtime-discovered updates. Explore SPFx web part samples and Copilot UX component samples for host-specific examples.]
Before: No saved wording on this side.
After: Follow Develop and deploy Copilot UX components for initial agent sync and later runtime-discovered updates. Explore SPFx web part samples and Copilot UX component samples for host-specific examples.
[added: Copilot UX components are supported in the SharePoint Store starting with SPFx 1.24 GA. See Publish SharePoint Framework applications to the marketplace for submission, licensing, and supported-client guidance.]
Before: No saved wording on this side.
After: Copilot UX components are supported in the SharePoint Store starting with SPFx 1.24 GA. See Publish SharePoint Framework applications to the marketplace for submission, licensing, and supported-client guidance.
[added: It runs in the context of the current user and connection in the browser. SharePoint page customizations run in the page, while Copilot UX components are hosted in an iframe in the Copilot canvas.]
Before: No saved wording on this side.
After: It runs in the context of the current user and connection in the browser. SharePoint page customizations run in the page, while Copilot UX components are hosted in an iframe in the Copilot canvas.
[added: SharePoint page controls are rendered in the page DOM; Copilot UX components render in their host iframe.]
Before: No saved wording on this side.
After: SharePoint page controls are rendered in the page DOM; Copilot UX components render in their host iframe.
SPFx Copilot [added: UX] components can be used to extend Microsoft 365[removed: Copilot (currently in preview).][added: Copilot.]
Before: SPFx Copilot components can be used to extend Microsoft 365 Copilot (currently in preview).
After: SPFx Copilot UX components can be used to extend Microsoft 365 Copilot.
Overview of[removed: SharePoint]Copilot[removed: Apps][added: UX components]
Before: Overview of SharePoint Copilot Apps
After: Overview of Copilot UX components
[removed: Important The SharePoint add-in model deprecation in SharePoint Online does not impact SharePoint Framework (SPFx), which is the primary replacement technology for SharePoint add-ins. SPFx is the most widely used extensibility model in Microsoft 365 and continues to be supported also in future. See more on the SharePoint add-in model retirement from the full add-in model retirement announcement.]
Before: Important The SharePoint add-in model deprecation in SharePoint Online does not impact SharePoint Framework (SPFx), which is the primary replacement technology for SharePoint add-ins. SPFx is the most widely used extensibility model in Microsoft 365 and continues to be supported also in future. See more on the SharePoint add-in model retirement from the full add-in model retirement announcement.
After: No saved wording on this side.
[removed: You can build SharePoint Framework powered solutions by using SharePoint Framework Yeoman Generator, Microsoft Agents Toolkit, or with the SharePoint Framework Toolkit. Key advantage is the flexibility of automatic hosting with the option to use the exact same component across the different hosts without any code level changes. This is designed to maximize the value of your development investments, regardless of which primary host you are targeting.]
Before: You can build SharePoint Framework powered solutions by using SharePoint Framework Yeoman Generator, Microsoft Agents Toolkit, or with the SharePoint Framework Toolkit. Key advantage is the flexibility of automatic hosting with the option to use the exact same component across the different hosts without any code level changes. This is designed to maximize the value of your development investments, regardless of which primary host you are targeting.
After: No saved wording on this side.
[removed: Automatic Single Sign On – SharePoint Framework components have automatic and seamless SSO included for all platforms they are hosted on. No specific consents needed from Microsoft 365 end users.]
Before: Automatic Single Sign On – SharePoint Framework components have automatic and seamless SSO included for all platforms they are hosted on. No specific consents needed from Microsoft 365 end users.
After: No saved wording on this side.
[removed: Automatic hosting – SharePoint Framework components can be securely and automatically hosted in SharePoint without additional maintenance or operational costs.]
Before: Automatic hosting – SharePoint Framework components can be securely and automatically hosted in SharePoint without additional maintenance or operational costs.
After: No saved wording on this side.
[removed: Write once and surface exactly the same code across multiple applications. Below picture shows example case with a reference solution available from GitHub.]
Before: Write once and surface exactly the same code across multiple applications. Below picture shows example case with a reference solution available from GitHub.
After: No saved wording on this side.
[removed: It runs in the context of the current user and connection in the browser. There are no iframes for the customization (JavaScript is embedded directly to the page).]
Before: It runs in the context of the current user and connection in the browser. There are no iframes for the customization (JavaScript is embedded directly to the page).
After: No saved wording on this side.
[removed: The controls are rendered in the normal page DOM.]
Before: The controls are rendered in the normal page DOM.
After: No saved wording on this side.
Source: Microsoft source · © Microsoft · CC BY 4.0.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details
- Observed by ChangeIntel
- 29 Oct 00:56 UTC
- Source update metadata
- 28 Oct 10:43 UTC
- Microsoft's latest commit in that period
- SPFx 1.24 GA docs updates - with Copilot Components GA (#11075) · committed 28 Oct 10:38 UTC · View diff
- First observed on this installation
- 12 Oct 19:35 UTC
- Last successful check
- today 11:30 UTC
- Next check due
- today 17:30 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.