Trascritto

Python Is Dead: The AI That Killed Python for Microsoft Automation

22 nov 2025 · 26 min. 4 sec.
Python Is Dead: The AI That Killed Python for Microsoft Automation
Capitoli

01 · The Python Dilemma in Microsoft's AI Stack

0 sec.

02 · The Hidden Costs of Python in Power Automate

32 sec.

03 · The Pitfalls of Using Python as Glue

1 min. 41 sec.

04 · The Power of AI-Assisted Orchestration

3 min. 52 sec.

05 · Contained Analytics: The Right Place for Python

4 min. 29 sec.

06 · The Manual Coding Loop: A Recipe for Disaster

4 min. 48 sec.

07 · The Agent-Driven Approach to Orchestration

7 min. 10 sec.

08 · Power BI Data Flows: Python's Proper Place

12 min. 42 sec.

09 · Power Automate: Replacing Python with Office Scripts

15 min. 51 sec.

10 · Fabric Notebooks: Containing Python in Analytics

19 min. 11 sec.

Descrizione

Many teams push Python into Power Automate and Power BI as glue and then fight fragile flows, drifting dependencies and scattered logs. This episode shows Power Platform makers and architects...

mostra di più
Many teams push Python into Power Automate and Power BI as glue and then fight fragile flows, drifting dependencies and scattered logs. This episode shows Power Platform makers and architects how Copilot, Office Scripts and agents with typed contracts take over the orchestration while Python stays where it shines: analytics.

In this episode
  • 00:00 – AI writes the glue, not you
  • 00:33 – Python's friction inside Power Platform
  • 05:01 – Why manual code and static playbooks fail
  • 07:36 – Agent plus Copilot as the orchestrator
  • 12:57 – Power BI dataflows: generated, not hand-written
  • 16:06 – Power Automate: Office Scripts plus agents
  • 19:23 – Fabric notebooks: contain Python
  • 23:37 – 30-day implementation playbook

Key takeaways
  • Inside Power Platform, Python is indirect glue that adds external compute, secrets, cold starts and version drift, while Office Scripts and native connectors run where the Microsoft 365 data lives.
  • Let Copilot and agents generate scripts and Power Query steps against typed contracts and the semantic model, then review the diff and keep the prompt as a reusable asset.
  • Keep Python contained in Fabric notebooks and dataflows for analytics kernels, and let the platform and agents handle scheduling, validation, I/O and approvals.

Worth quoting

“office scripts aren't toy typescript. They are the sanctioned edge for automating Excel and related Microsoft 365 tasks without dragging in infra.” – Mirko Peters (02:38)

“Dynamic typing's freedom is fun until it's 3 p.m. on quarter close and your flow succeeds with the wrong shape. Strong typed boundaries catch stupidity before it ships.” – Mirko Peters (03:48)

Explore more on M365.FM
  • Episode page: the full episode with chapters, quotes and a 30-day migration plan
  • Power Automate – where Python glue behind custom connectors makes flows brittle; Office Scripts and native connectors replace it
  • AI agent – agents with typed tool contracts orchestrate Office Scripts, dataflows and notebooks instead of hand-written glue
  • Fabric notebooks – where Python stays contained as the analytics kernel, called by agents through typed job inputs and outputs
  • Related episode: Power Platform Copilot Integration - Simply Explained

Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
mostra meno
Informazioni
Autore Mirko Peters M365, Azure & AI
Organizzazione m365 FM
Sito www.m365.fm
Tag

Sembra che non tu non abbia alcun episodio attivo

Sfoglia il catalogo di Spreaker per scoprire nuovi contenuti

Corrente

Copertina del podcast

Sembra che non ci sia nessun episodio nella tua coda

Sfoglia il catalogo di Spreaker per scoprire nuovi contenuti

Successivo

Copertina dell'episodio Copertina dell'episodio

Che silenzio che c’è...

È tempo di scoprire nuovi episodi!

Scopri
La tua Libreria
Cerca