Infrastructure as Code in Power Platform with Terraform
Power Platform environments are usually clicked into existence - admin center, PPAC, maker portal - which means the moment you need the same setup twice, in a different region or for a different environment, you're relying on memory and screenshots. This talk treats environments, connections, DLP policies and settings as infrastructure: defined in code, reviewed in a pull request, and reproducible on demand.
Using Microsoft's official Terraform provider for Power Platform, we build an environment from nothing - provisioning, connection references, environment groups and rule-based policies - and see where Terraform's declarative model fits cleanly onto Power Platform's APIs and where it doesn't. Along the way: state management for a platform that also lets makers change things by hand, drift detection, and how this sits alongside a Dataverse solution pipeline rather than replacing it.
Less a syntax tour, more a look at what's actually happening underneath the resource blocks - and an honest account of where the provider still has gaps.
Automatic Test Generation with the Playwright CLI
Code Apps - Power Platform's code-first canvas surface - get built and rebuilt fast, often by an AI agent that has no idea it just changed behaviour it can't see. This is the hands-on companion to that problem: using the Playwright CLI to generate real, runnable UI tests directly against a Code App, without hand-writing selectors.
We go from a blank Code App to a working test suite live: pointing the CLI at the running app, generating Playwright test code from what it finds, and wiring the result into a pipeline so every Copilot-authored change has to prove it didn't break the parts that already worked.
This is deliberately the practical half of the story - less about why AI-authored code needs a different testing approach (that's a separate talk of mine), more about the exact commands, the generated code, and where the CLI still needs a human to clean up after it.
Full Stack Solutions with Code Apps: Source Control, Build System and CI/CD Pipelines
An update to the ALM talk I've given at EPPC and Update Days, built around Code Apps: live coding a complete full stack Power Platform solution from scratch. A React Code Apps frontend in TypeScript, C# Dataverse plugins for server-side validation, custom connectors, Power Automate handling background jobs, and Package Deployer shipping all of it as one unit. The coherent architecture picture that the documentation, split across a dozen separate feature pages, doesn't give you.
You'll see the real implementation: plugins enforcing transactional safety that client-side validation can't guarantee on its own, a monorepo holding frontend and backend code together, GitHub Copilot generating across the whole stack against custom instructions, and deployment automation carrying changes from development through to production.
And the developer workflow behind it: a VS Code workspace set up for a fast local inner loop, an outer loop of automated deployments, a version control strategy for the solution files everyone forgets to plan for, and what code review looks like when an agent generated part of the change, across frontend and backend at once.
Across European and Czech Power Platform events.
Validating behavior after AI changes your code
UI testing for Power Platform has always been painful - thin tooling, heavy upfront effort, and tests that break with every form change. This deep dive uses LLMs to generate stable test code from natural-language scenarios instead. Why UI-level tests beat unit tests once AI writes the code: an agent will happily adjust the code and the test together until the checkmarks go green without validating anything. An LLM with Playwright MCP explores the app, identifies scenarios and produces Gherkin plans; a Copilot agent turns those into Playwright code that runs with no inference in your pipeline. Because Gherkin describes behaviour rather than selectors, the scenarios survive UI changes and double as executable specifications that steer the coding agent.
90 min · Advanced · Makers & Developers
Low Code is Dead, Long Live Vibe Code!
In September 2025 Charles Lamanna, CVP at Microsoft, told the Power Platform Conference that "low code is dead - as we know it," with vibe coding as its successor: a faster, more flexible way to build apps over enterprise data. What vibe coding can actually do inside Power Platform, how it follows on from the low-code world we already know, and how you govern and secure the apps that come out of it so organisational data stays safe.
Setting up developer environment, repository and build system
The developer inner loop - the fast local cycle before code reaches CI/CD. Source controlling Dataverse solutions, MSBuild-based local builds, generating version numbers from Git history, early bound types, running validation locally, unit testing plugins and PCF controls, and cutting the dependency on long-lived development environments.
With Tomáš Prokop
Validating behavior after AI changes your code
Two complementary testing approaches for Power Platform: TDD with mocking frameworks for frontend and backend code, and AI-assisted BDD acceptance tests that explore the app through browser automation. With Code Apps, Generative Pages and vibe coding, UIs change more often than ever - natural-language scenarios give you a stable behavioural contract when the UI abstractions keep shifting.
With Julie Koťátková
Developer ALM Lab – Source Control, Build System and CI/CD
A hands-on lab on managing the lifecycle of Power Platform applications with the Dataverse Solution Framework - Pipelines, Catalog and Git integration, where they work and where you need more. Attendees build their own monorepo setup combining plugins, form scripts, PCFs and connectors, wire up MSBuild automation, and make source control the single source of truth so dev and test environments can be ephemeral.
With Tomáš Prokop
Source Control, Build System and CI/CD Pipelines
Going past the basics of native Git source control integration in Dataverse: managing Power Platform projects as monorepos, bringing plugins, form scripts, PCFs, connectors and solution components together, setting up an MSBuild build process, and establishing a real multi-developer workflow - branching strategy, conflict resolution, PR quality checks, release management and automated deployment of code, infrastructure and configuration data.
With Tomáš Prokop
Developer Lab – Source Control, Build System and CI/CD
A full-day workshop on improving developer productivity through continuous integration, automation and testing frameworks - building sustainable workflows that hold up over the long life of a Power Platform product.
With Scott Durow, Eric Regnier, Parvez Ghumra
Integrations with Custom Connectors, Dataflows and Virtual Tables
Building and using Custom Connectors against external APIs, low-code ETL with Dataflows to ingest and map data into Dataverse, and virtualizing external data with Virtual Tables to get access without duplication - including full CRUD through custom virtual table data providers, and where each approach breaks down.
With Jan Koštejn
Community & user group talks
Dataverse: concurrent requests without corrupting your data
Running concurrent requests against Dataverse without overwrites or inconsistent state - what row version does for you, and how to use it.
Community & user group talks
GitHub Actions for Power Platform
Automating CI/CD over Power Platform with GitHub Actions - from solution export through to environment promotion.
Community & user group talks
PCF in 15 Minutes
A rapid-fire introduction to the Power Apps Component Framework - building a PCF control live, from nothing.
Community & user group talks
Power Cards, and How to Use Them
How to use Power Cards, where their strengths and weaknesses lie, and when to reach for them over Adaptive Cards.
Community & user group talks
Introducing Power FX Plugins
Low-code plugins, and whether it is finally time to consider them for production workloads.
Community & user group talks
Power FX SDK Lessons Learned
Practical takeaways from building on the Power FX SDK - talking to Dataverse and implementing custom functions.
Community & user group talks
Official Power Platform Skills, and How to Hand Them to an Agent
Building an app using the official Power Platform skills - installing the plugin, handing the skills to a coding agent, and how the pieces work together.
