A futuristic lab depicts Python code and Linux servers connected by a glowing Rust bridge.
Azure Functions now has a public preview of Python 3.15, and the change goes beyond a new version number. Microsoft has also rebuilt the part of the Python worker that talks to the Functions host. The preview is for evaluation and testing, not production.

A futuristic lab depicts Python code and Linux servers connected by a glowing Rust bridge. What Microsoft announced​

Microsoft's engineering post says the worker's communication layer is now written in Rust, while your functions still run in Python. The Ignite 2026 Azure Functions roundup says Python 3.15 is in public preview on Flex Consumption, Elastic Premium and Dedicated plans, on Linux only. The Azure Updates listing was published on November 17, 2026. Its text, as captured, only describes Azure Updates' status labels, so the scope details come from the Ignite post.

Microsoft's language-support matrix lists Python 3.15 as Preview with an expected end-of-support date of April 2030. In Microsoft's terms, preview means "not yet supported, but expected to reach GA status in the future." The same matrix lists:

Python versionSupport levelExpected end of support
3.15PreviewApril 2030
3.14GAApril 2029
3.13GAOctober 2029
3.12GAOctober 2028
3.11GAOctober 2027

The April 2030 date is a planning reference. It is not a promise of when 3.15 will reach general availability.

The Rust worker transport​

The Ignite post says the new transport embeds CPython. It handles host-to-worker gRPC communication outside your Python environment. Microsoft says this removes grpcio and protobuf version conflicts between the worker and your application or AI SDK dependencies.

Microsoft's engineering post puts this in context:

  • Python 3.13 introduced a proxy worker that separated communication with the host from the libraries that execute functions.
  • The Rust transport builds on that separation.
  • Users continue to write Python functions using the same programming models.
  • Through PyO3, the Rust transport calls those libraries within the same worker process.

Microsoft also notes that the move to Rust helps enable Python support on Windows ARM64 in the Azure Functions CLI (v5). That matters to Windows developers, though the preview hosting scope above is still Linux.

Microsoft is also open about the costs:

  • Each conversion between Rust and Python has a cost, particularly for functions that do very little work themselves.
  • Microsoft now maintains a mixed-language worker, builds native binaries for supported platforms, and tests the Rust-to-Python boundary.

Microsoft's material, as reviewed, gives no benchmarks. I'd treat the pitch as dependency isolation, not speed.

Who should care​

Teams that add AI SDKs to Python functions are the most likely to benefit. Those SDKs often pin their own grpcio or protobuf versions. Under the old arrangement, those pins could collide with the worker's. Microsoft says the new transport removes that class of conflict. How far that holds for your own package mix is something to test, not assume.

Boundaries to keep in mind​

  • Linux only. The announcement doesn't claim Python 3.15 on Windows-hosted Functions.
  • Three plans only. These are Flex Consumption, Elastic Premium and Dedicated.
  • Not Linux Consumption. Microsoft's documentation says newer Python versions aren't added to Linux Consumption. Python 3.12 is the last version there. That plan's retirement is set for September 30, 2028, and Microsoft points users to Flex Consumption. Windows Consumption apps aren't currently affected.
  • Preview terms apply. Microsoft says preview features are for evaluation and testing, aren't recommended for production, and fall under the Supplemental Terms of Use for Azure Previews.

A sensible way to evaluate it​

This sequence is my suggestion, not a Microsoft procedure.

  1. Pick a non-production Function App on a supported Linux plan.
  2. Rebuild your dependencies against Python 3.15. Microsoft's Python guidance says changing an app's Python version does not rebuild existing artifacts for you. That matters most for compiled or native packages.
  3. Exercise every trigger and binding the app uses, plus any native extensions.
  4. Pay extra attention to packages that previously forced you to manage grpcio or protobuf versions.
  5. Keep production on a GA Python version, such as 3.13 or 3.14, until 3.15 reaches GA.

Bottom line​

Python 3.15 on Azure Functions is an early-access chance to test a new architecture. Its stated payoff is fewer dependency collisions. Microsoft's material gives no performance numbers and no guarantee that every package works unchanged, so check compatibility one workload at a time. If you are still on Linux Consumption, this preview is another reason to plan a move to Flex Consumption.

 

References

  1. (In preview) Public Preview: Azure Functions support for Python 3.15 Azure Updates 2026-11-17T20:00:32Z
  2. A Rust foundation for Python Functions: evolution of the Python worker techcommunity.microsoft.com
  3. What's new in Azure Functions and Durable Task Scheduler at Microsoft Ignite 2026 techcommunity.microsoft.com