Trascritto
Why Power Platform Is Your Real Automation Layer — Not Custom Code
12 ago 2026 ·
1 h 5 min. 10 sec.
Scarica e ascolta ovunque
Scarica i tuoi episodi preferiti e goditi l'ascolto, ovunque tu sia! Iscriviti o accedi ora per ascoltare offline.
Why Power Platform Is Your Real Automation Layer — Not Custom Code
Descrizione
In many Dynamics 365 projects, every automation request ends up as custom code in a developer backlog, and the business pays for it every time a rule changes. This episode...
mostra di più
In many Dynamics 365 projects, every automation request ends up as custom code in a developer backlog, and the business pays for it every time a rule changes. This episode shows Dynamics and Power Platform teams where plug-ins still belong, how to make automation visible and owned, and how to migrate safely to Power Platform as the real automation layer.
In this episode
Key takeaways
Worth quoting
“This isn't an argument against developers, it's an argument against using developers as the routing layer for every business process change.” – Mirko Peters (03:36)
“Then somebody asks why dynamics feels slow to change. Dynamics isn't slow, the automation model is.” – Mirko Peters (06:24)
Explore more on M365.FM
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
In this episode
- 00:00 – Automation as a development backlog
- 04:25 – The hidden cost of custom code
- 08:40 – Where custom code still belongs
- 12:14 – Reasoning between event and action
- 16:46 – Sales approval without a plug-in
- 24:06 – Ownership, solutions and environments
- 35:20 – Governance, DLP and Dataverse security
- 51:09 – Inventory, migration and a 90-day reset
Key takeaways
- Keep plug-ins narrow for transactional validation and performance-critical work, and move orchestration across people, systems and time into Power Platform.
- Business-critical flows need organizational identities, solutions with environment variables and managed deployments instead of personal ownership and production edits.
- Governance through environments, DLP policies and Dataverse security is an operating model that lets automation scale, starting with an inventory rather than a rewrite.
Worth quoting
“This isn't an argument against developers, it's an argument against using developers as the routing layer for every business process change.” – Mirko Peters (03:36)
“Then somebody asks why dynamics feels slow to change. Dynamics isn't slow, the automation model is.” – Mirko Peters (06:24)
Explore more on M365.FM
- Episode page: the full episode with chapters, quotes and FAQ on Dynamics automation
- Dynamics 365 – the application where every automation request turns into a developer backlog item and hidden custom code
- Power Platform – proposed as the visible, owned automation layer for processes crossing people, systems and time
- Dataverse – the event pipeline where transactional validation still belongs, plus security roles that bound automation
- Automation – the episode's core subject: moving it from accumulated customization to an operating model with owners
- Related episode: Power Apps - 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.
Informazioni
| Autore | Mirko Peters M365, Azure & AI |
| Organizzazione | m365 FM |
| Sito | www.m365.fm |
| Tag |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Commenti