AI is changing Python-and-Excel work less by making spreadsheets autonomous and more by changing who can build deterministic automation.

In practitioner discussions from the two years ending August 6, 2026, experienced developers use assistants for boilerplate, debugging, refactoring, and unfamiliar APIs. Excel power users use them to translate an existing formula, Power Query, or VBA workflow into Python. Some non-programmers describe the business process in plain language and iterate on generated scripts until the result is reliable enough to keep as a reusable tool.

That distinction matters: the durable output is often ordinary Python or VBA that can be inspected, rerun, tested, and reconciled—not an AI answer that must be trusted every time the workbook is opened.

“Python in Excel” now describes several very different workflows. Sometimes Python executes inside an Excel workbook. Sometimes an add-in connects a browser or local Python runtime to Excel. And in many of the strongest production stories, Python runs completely outside Excel and the workbook remains the input, review, or delivery format.

To understand what users are actually doing rather than what product pages say they could do, we reviewed 30 high-relevance practitioner discussions and product issues published during the two years ending August 6, 2026. The sample is purposive rather than representative, but it gives a useful picture of the tasks that repeatedly bring Python and Excel together.

There are now several materially different ways to run Python with Excel. Comparing them only by “supports Python” hides the choices that actually determine whether a workflow will work: where Python executes, how it reaches workbook data, what packages it can load, whether it can create worksheet functions, and what another user receives when the workbook is shared.

This review compares Microsoft Python in Excel, Boardflare Python for Excel, xlwings Lite, and Anaconda Code as of July 15, 2026. Because these products are changing quickly, treat this as a dated market snapshot and verify the linked official documentation before making a deployment decision.

For a much deeper maintained comparison of the first two—including row-major calculation, source storage/export, type conversion, data limits, reusable worksheet functions, packages, networking, and security boundaries—see Boardflare Python for Excel vs. Microsoft Python in Excel.

The design goal for Boardflare's Python experience was not simply “put a code editor in Excel.” It was to give substantial Python work a coherent reactive notebook while keeping the workbook directly connected as a source-data, review, output, and delivery surface.

That led to a runtime with several deliberately separate pieces: Excel's long-lived shared runtime, a Boardflare host, a cross-origin marimo notebook, browser Python through Pyodide, Anywidget capabilities, a spreadsheet-host abstraction, workbook source persistence, and live worksheet outputs/functions.

This article explains why those pieces exist and how they fit together. The maintained specifications live in Architecture and Runtime and Security and Data Flow.

“Move this spreadsheet to Python” sounds like a technical task, but the difficult decision is architectural: which parts of the workflow should move at all?

A mature workbook can contain formulas, Power Query steps, VBA, manual procedures, external data connections, review controls, and business rules that users understand precisely because they are visible in Excel. Replacing all of that with Python can make the result less maintainable.

A better migration starts by separating the workflow into responsibilities.

AI add-ins for Excel now fall into a few practical families. The most visible category is the general-purpose Excel AI assistant: a chat or task-pane agent that can write formulas, explain workbook logic, clean data, summarize ranges, create charts, and sometimes edit the workbook directly. This is the best starting point for most end users who want a broad productivity boost without committing to a specific industry workflow.

Most Excel files are already applications in disguise. They have inputs, rules, exceptions, and repeated handoffs. What they usually do not have is an interface built for the job people are actually trying to do.

Tool Builder enables you to create standalone HTML web applications using AI (like ChatGPT, Claude, or Gemini) and run them directly within your Excel workbook. Your spreadsheet becomes both the web server and the database. You ask an AI tool to generate a small single-file web app, paste it into Tool Builder, and run it directly in the workbook. The workbook stays the source of truth, but you get a custom UI tailored to your workflow.

This comprehensive post compares Excel's newly introduced native regex functions (REGEXTEST, REGEXEXTRACT, and REGEXREPLACE) with Python's long-established re module. We explore their respective capabilities, syntax variations, supported regex constructs, and advanced features to help you understand which tool is best suited for different text manipulation scenarios. Whether you're working within a spreadsheet for interactive data exploration or building automated text processing pipelines in Python, this detailed analysis will highlight the strengths and limitations of each approach.

We are thrilled to announce the availability of Python-powered statistical functions for Excel users. This release brings the full power of Python's scipy.stats library directly into your spreadsheets with comprehensive distribution support, advanced statistical methods, and capabilities that go far beyond what native Excel functions provide. Our Python functions enable you to access full distribution support (PDF, CDF, quantiles, and more) for distributions not available in Excel, perform advanced analytics, and leverage the complete toolkit of scipy.stats directly from your spreadsheets.

We've launched a repository of Python Functions that can be used in Excel as custom functions through the Python for Excel add-in and as web apps via Gradio.