Tenant announcements

Loading Power Query data to Python in Excel Web: Retirement

MC1473149

All Microsoft 365 Message Center posts · Daily summary

About this page These posts come from a tenant in West Europe and are shown as a reference. Day-by-day digest: MC Summary. Linked to the roadmap via Roadmap ID when Microsoft names one. Items are kept for 12 months. Always check Message Center in your own environment for what applies to you.
Archive This post is no longer in the Microsoft 365 Message Center (last seen on 25 sep 2026). Microsoft removes posts after a while. We keep the last version here as an archive.
MC1473149 Major change

What and why

Microsoft is retiring support for loading Power Query data into the Python runtime in Excel for the web. After this change, users will no longer be able to use Power Query as a data source for Python in Excel when working in Excel for the web. This retirement aligns investments in Python in Excel with supported experiences and does not affect Excel for Windows desktop.

Rollout schedule

  • Retirement date: October 16, 2026

Impact on your organization

Who is affected

  • Users who use Python in Excel with Power Query data sources in Excel for the web.

Platforms affected:

  • Excel for the web

What will happen

  • Beginning October 16, 2026, users will no longer be able to load Power Query data into the Python runtime in Excel for the web.
  • Workflows that depend on combining Power Query and Python in Excel for the web will no longer function as expected.
  • No changes are being made to Python in Excel experiences in Excel for Windows desktop.
  • Users can continue to import external data by using Power Query and analyze data with Python in Excel on supported desktop experiences.

Action Required / Recommendations

  • No administrative action is required.
  • Identify users and business processes that rely on Power Query data being loaded into Python in Excel for the web.
  • Notify affected users of the retirement and expected workflow impact.
  • Review affected solutions and consider transitioning those workflows to Excel for Windows desktop where this capability remains available.
  • Update internal training, documentation, and support materials as needed.