The Power Apps App in a Day Workshop delivers Microsoft's official App in a Day curriculum as a live, instructor-led day for your IT team and power users — a hands-on progression through building a canvas app, modeling data in Dataverse, an introduction to model-driven apps, and automating a process with Power Automate, closed out with an admin and governance briefing for the people who will have to live with what the makers build. Attendees leave having built a working app with their own hands. Delivery is remote or on-site at $1,450 per trainer-day. This is training only: no production deployment, no tenant redesign — the build services on this site are the follow-on when a workshop app deserves to become a production app.
App in a Day is Microsoft's own workshop format for getting a room of beginners to a working Power Platform app in a single day, and it has earned its reputation: the labs are well-built, the progression is realistic, and people who complete it genuinely go on to build things. What the packaged content cannot do by itself is run the room — pace the labs for mixed abilities, unstick the person three steps behind without stalling the person three steps ahead, and answer the this-is-great-but-what-about-our-tenant questions that decide whether anything happens after the workshop. That is what an IT Partner instructor adds. The day follows Microsoft's curriculum: attendees build a canvas app hands-on, create and relate tables in Dataverse, get a working introduction to model-driven apps, and wire up a Power Automate flow — each person building their own app, not watching a demo. We close with the module Microsoft's slide decks treat lightly and real organizations cannot: administration and governance — environments, data loss prevention policies, licensing boundaries, and who should be allowed to build what — so IT leaves with a starting position instead of a shadow-IT problem. Where the standard scenario fits, we run it as designed; where your organization has an obvious candidate process, we agree at booking how to close the day applying the pattern to your own scenario. The boundary is deliberate and priced in your favor: this is a training day, not a consulting project in disguise. Workshop apps are training artifacts; when one deserves to become a production system, that is a scoped follow-on through our custom business apps work, quoted separately and honestly.
A short call before the day: who attends, their experience levels, remote or on-site, and — the part that saves the morning — how lab environments will be provided under your tenant policy, whether developer-plan environments, trial environments, or environments your admins provision.
Attendees build a canvas app hands-on, then model the underlying data in Dataverse: tables, columns, relationships. Everyone builds; nobody just watches.
The Dataverse tables become a model-driven app, showing the second style of Power Apps development, and a Power Automate flow automates a step of the process — approvals and notifications, the patterns every real app ends up needing.
The governance briefing for IT (environments, DLP, licensing, maker permissions), plus — where agreed at booking — a working block applying the day's pattern to a scenario from your own business.
Written wrap-up with the recommended governance starting position, the licensing one-pager, parked questions, and honest next steps — including 'you don't need us for this part' where that is true.
A one-day, instructor-led delivery of Microsoft's official App in a Day training format. Attendees personally build a canvas app, model data in Dataverse, generate a model-driven app, and automate a process with Power Automate, and the day closes with an admin and governance briefing plus, where agreed, a block applying the pattern to your own scenario. It costs $1,450 per trainer-day, remote or on-site.
The sweet spot is a mix: the IT people who will govern the Power Platform and the business power users who will actually build with it — the Excel wranglers, the process owners, the person who maintains the Access database everyone fears. No coding background is needed; the curriculum is designed for beginners and the instructor paces the room.
Microsoft's real curriculum — that is the point of the format, and its lab progression is genuinely good. What you are paying for is delivery: a live instructor who paces mixed abilities, unsticks people fast, answers tenant-specific questions the slides can't, and adds the governance close-out and licensing one-pager that the packaged content treats lightly.
Yes — each attendee builds their own working app during the labs: a canvas app, Dataverse tables behind it, a model-driven app over the same data, and a flow automating part of the process. Where we agree a your-scenario closing block at booking, attendees also see the pattern applied to data shaped like their own business. It is a training build, not a production deployment — that distinction is stated up front.
Typically none purchased for the day. The labs run in no-cost training environments — Microsoft's developer plan or trial environments where your tenant policy allows them, or environments your admins provision with our guidance. The intake call settles this before the day. Production is a different story: Dataverse-backed and model-driven patterns need premium Power Apps licensing when deployed for real, and the licensing one-pager we hand out says exactly where that line is.
The curriculum is identical. Remote runs over Teams with screen-sharing for troubleshooting and suits distributed teams; on-site adds the over-the-shoulder help that some rooms genuinely benefit from, with travel and expenses quoted in writing at booking, separate from the per-day fee.
Cohort size is agreed at booking. The honest constraint is the hands-on format: every attendee builds their own app and gets personally unstuck when they stall, which puts a practical ceiling on one instructor's room. Larger groups are simply additional workshop days at the same per-day rate, often split by department.
$1,450 per trainer-day, fixed, quoted in writing before work begins, with payment after you approve delivery. There is no project overhead — additional cohorts or a follow-up day are more days at the same rate.
They are yours, in the training environments where they were built, and they are excellent references for your makers. What they are not is production-ready — no hardening, no ALM, no security review happens in a training day, and we say so rather than let a workshop artifact quietly become a business-critical system. When an app deserves promotion, that is a scoped build engagement with real requirements.
Well — that pairing is common. The workshop gives your team the literacy to co-own what a migration project delivers: makers who understand canvas apps and Dataverse maintain a migrated app instead of orbiting it. Many clients run the workshop first, then scope the Access or InfoPath migration with trained eyes on their own side of the table.
The governance close-out, mostly — and it matters. App in a Day creates enthusiasm, and enthusiasm without environments strategy, DLP policies, and licensing awareness creates shadow IT. IT attendees leave with a recommended starting position for maker governance in your tenant and a clear map of which patterns cost money in production.
No. This is a training-only engagement — the instructor never requests administrative access to your environment. Where lab environments need admin-side preparation, your administrators do it with our written guidance before the day. Configuration gaps the workshop surfaces are documented in the wrap-up and routed to the appropriate service.