Trascritto
Your First Power App: From Idea to Working Solution
18 apr 2026 ·
1 h 18 min. 21 sec.
Scarica e ascolta ovunque
Scarica i tuoi episodi preferiti e goditi l'ascolto, ovunque tu sia! Iscriviti o accedi ora per ascoltare offline.
Your First Power App: From Idea to Working Solution
Descrizione
Many first Power Platform projects stall because teams build screens before defining the process they want to change. Using a Contoso vacation request example, this episode shows makers and IT...
mostra di più
Many first Power Platform projects stall because teams build screens before defining the process they want to change. Using a Contoso vacation request example, this episode shows makers and IT leads how to turn Dataverse tables into a working canvas front door, choose between canvas and model-driven apps, and avoid environment and licensing traps.
In this episode
Key takeaways
Worth quoting
“The first app is not a feature demo. It is a business interface. And that difference changes almost every decision that comes after it” – Mirko Peters (03:52)
“If the thinking is clean, low code helps us express it faster. If the thinking is weak, low code helps us spread that weakness faster too.” – Mirko Peters (50:13)
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 – When data stops being enough
- 03:45 – The real job of a first app
- 10:49 – Defining the problem in operating terms
- 18:20 – Canvas or model-driven
- 32:42 – Scoping release one and the employee experience
- 42:53 – What Dataverse does underneath
- 53:20 – Traps: default environment and premium cost
- 71:04 – Why the app solves only half the problem
Key takeaways
- A first Power App should be a narrow business interface that makes one repeated request, such as a vacation request, enter a governed path with a visible status.
- Choose canvas for a low-friction employee front door and model-driven apps where roles need oversight across many Dataverse records and relationships.
- Keep release one small: avoid the default environment for operational apps, avoid unnecessary custom or premium connectors, and model future complexity like delegation in Dataverse first.
Worth quoting
“The first app is not a feature demo. It is a business interface. And that difference changes almost every decision that comes after it” – Mirko Peters (03:52)
“If the thinking is clean, low code helps us express it faster. If the thinking is weak, low code helps us spread that weakness faster too.” – Mirko Peters (50:13)
Explore more on M365.FM
- Episode page: the full episode with chapters, the Contoso vacation request example and FAQ
- Dataverse – the system of record that turns each vacation request into a governed object with status
- Power Apps – the platform for Contoso's first app, framed as a business interface rather than a demo
- Canvas app – recommended for release one as the simple employee front door for submitting vacation requests
- 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