Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 13:41 UTC Customize Public modeDiscuss ChangeIntel on Discord

Publishing InfoPath Forms in SharePoint Online will not be allowed for all tenants

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

What the notice says

Microsoft’s text, with source markup removed
Updated July 2, 2026: We are updating this post as a reminder. Thank you for your patience.  Introduction As announced earlier in MC616550 (June 2023), InfoPath Forms Service in SharePoint Online is being retired and will be removed from existing tenants after July 14, 2026. To support this transition and reduce future migration effort, Microsoft will prevent the publication of InfoPath forms in SharePoint Online for all tenants ahead of the service’s retirement. When this will happen: After May 18, 2026: Publishing new InfoPath forms or publishing updates to existing forms will be blocked July 14, 2026: InfoPath Forms Service will be fully retired How this affects your organization: Who is affected: All SharePoint Online tenants InfoPath designers, publishers, and site owners IT administrators managing SharePoint Online What will happen: After May 18, 2026, new InfoPath forms cannot be published Modifications to existing InfoPath forms cannot be published Existing published forms will remain available and usable There is no option to extend InfoPath Forms Service beyond retirement What you can do to prepare: To understand how InfoPath is used in your organization, you can run the Microsoft 365 Assessment tool to scan the tenant for InfoPath usage. Using the Power BI InfoPath Report generated by the scanner tool, you can: Identify all InfoPath Forms usage in the tenant, per site collection and site. Evaluate the recency and volume of usage of InfoPath Forms. Understand lists, libraries, and content types that use InfoPath. We recommend communicating to the impacted site owners and teams inside your organization now, so they are aware of the coming change. For scenarios where InfoPath or InfoPath Forms Services are currently being used, we recommend migrating to Power Apps, Power Automate, or Microsoft Forms. Please ensure that you allow adequate time for migration of any use of InfoPath or InfoPath Forms Services in your organization ahead of this date, as there is no migration tool provided. Additional instructions on how to migrate can be found in this blog. Note: Please plan the migration appropriately as there will not be an option to extend InfoPath Forms Services beyond the InfoPath retirement date of July 14, 2026. Compliance considerations: This update disables the ability to publish or republish InfoPath forms in SharePoint Online as part of a planned service retirement; it does not change how existing customer data is stored, processed, or governed.

What changed

Between archive captures, newest first
  1. Updated April 20,July 2, 2026: We are updating this post as a reminder. Thank you for …

  2. Updated April 20, 2026: We are updating this post as a reminder. Thank you for your patience.  Introduction As announced earlier in MC616550 (June 2023), InfoPath Forms Service in …

  3. · first version seen

Linked documentation

Microsoft pages the notice links to
Other posts named in this one

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.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 13:41 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current