Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries
Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 20 Jun 2025
June 30, 2026
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, with source markup removed- https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/building-simple-field-customizer
- https://learn.microsoft.com/sharepoint/dev/declarative-customization/column-formatting
- https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api
- https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/build-a-hello-world-extension
- https://support.microsoft.com/office/0eccc64e-4512-47df-9da0-d855be22fb0a
What changed
Between archive captures, newest first- Major change
Yes→ No
Updated June 24, 2025: We will not be proceeding with this change at this time. Thank you for your patience.After a detailed internal evaluation and the feedback which we have heard from the ecosystem, we no longer have plans to retire the field customers from lists and libraries We are evaluating the retirement of the SharePoint Framework (SPFx) Field Customizers …- Major change
Updated June
20,24, 2025: We will not be proceeding with this change at this time. Thank you for your patience. Wewill be retiringare evaluating the retirement of theSharePoint Framework (SPFx) Field Customizers feature from SharePoint Lists and Document Libraries. … will continue to function as expected. We recommend transitioning to Column Formattingfor visualcustomizations.customizations where possible. For scenarios requiring third-party code execution, continue usingCommand Set Customizers or Application Customizers. What you can do to prepare: …- Act by
30 Jun 2026→ none - Tags
User impact, Admin impact, Retirement→ Updated message, User impact, Admin impact, Retirement
Updated June 20, 2025: We will not be proceeding with this change at this time. Thank you for your patience. We will be retiring the SharePoint Framework (SPFx) Field Customizers
feature from SharePoint Lists and DocumentLibraries on June 30, 2026. Moving forward, we recommendLibraries. In many cases, we recommend alternatives like using ColumnFormatting, where we will continue to invest in new capabilities and improvements.Formatters and disabling SPFx Field customizers. This would help with better performance with modern experience that is continuously updated. When this will happen:This changeWe are currently assessing the timelines and will update this post as plans progress. You can be assured that it willtake effect on June 30, 2026.be communicated well in advance, with ample time to manage transition effectively. How this affects your organization:IfThere is no impact to your organizationusesas of now. In future depending on updated timelines, SharePoint Lists or Document Libraries with SPFx FieldCustomizers, please note the following impacts after the retirement date:Customizers may get affected: Field Customizers will no longer render custom code. Column data will display … Review your current use of Field Customizers and begin planning your transition.Note: There will be no option to extend the use of Field Customizers beyond June 30, 2026.Additional information: Support update for SharePoint framework field customizers in lists and …- Act by
- · first version seen
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.