MC1561862: Run Python code as a workflow step

Published . Last updated .

Microsoft 365 Message Center announcement MC1561862.

MS Message Center's Summary

Makers can now execute custom Python code within Copilot Studio workflows to handle complex data parsing and transformations starting December 1 2026. This capability runs inside a managed sandbox and utilises Copilot Credits. Administrators should review credit consumption policies and inform developers about this new option for logic that standard connectors cannot resolve.

Administrator impact
No direct administrator action is required.
End user impact
Makers gain the ability to build advanced workflows incorporating custom Python logic.
Importance
3/10: This is a new feature introduction for makers that operates within existing governance frameworks.
Message Center ID
MC1561862
Category
stay Informed
Severity
normal
Services
Microsoft Copilot (Power Platform)
Tags
New feature
Expires
We are announcing the ability to use the Code node to run Python as a step in a workflow for logic that expressions and connectors cannot handle in Copilot Studio. This feature will reach general availability on December 1, 2026.

How does this affect me?
Makers can add Python steps to workflows for data transforms, file parsing and conversion (e.g. PDF to text, CSV, or XML), and calls to APIs that don't have a connector. The code can be generated using natural language using AI, or Makers can write and edit the code by hand.

Code runs in a Microsoft-managed sandbox environment and consumes Copilot Credits. Code steps are unable to make outbound API calls.

What action do I need to take?
This message is for awareness, and no action is required.