This page lists exercises for AB-400: Extend Microsoft Power Platform solutions with code and AI.
Set up your lab environment
Level: 200 | Duration: 30 minutes
Create a Power Platform developer environment, turn on code apps, install the developer tools, sign in to GitHub and GitHub Copilot, and import the base solution used by every lab in this course.
Build and register an equipment-validation plug-in
Level: 300 | Duration: 35 minutes
Write, sign, and register a Microsoft Dataverse plug-in that uses a pre-image and the Organization service to enforce a replacement-eligibility rule, then catalog the rule as a Dataverse business event.
Perform resilient Dataverse API operations
Level: 300 | Duration: 30 minutes
Use the Dataverse Web API, the Organization service, and the Dataverse SDKs for .NET and Python to create, retrieve, update, and query equipment-provisioning data, then add a bounded retry for a simulated transient error.
Process an equipment request with Azure Functions
Level: 400 | Duration: 30 minutes
Deploy an Azure Functions app that uses a managed identity to authenticate to Microsoft Dataverse, then complete an HTTP-triggered function that processes an equipment request asynchronously.
Build a Dataverse equipment request code app
Level: 300 | Duration: 35 minutes
Connect a Power Apps code app to Dataverse tables, call a Dataverse custom API and an environment variable, and gate a business rule on the client.
Display profile data through a Power Platform connection in a code app
Level: 300 | Duration: 20 minutes
Configure a React and TypeScript Power Apps code app to call a Power Platform connection with the Power Apps CLI, then verify the connection locally and after publishing.
Build a model-driven app script with GitHub Copilot
Level: 300 | Duration: 30 minutes
Use GitHub Copilot to draft a model-driven app form script that calls the Dataverse Web API, shows form notifications, and runs a confirmation dialog from a custom command.
Build a device-condition Power Apps code component
Level: 300 | Duration: 40 minutes
Create, test, debug, and deploy a Power Apps component framework (PCF) control that renders and edits a bound Dataverse column.
Build a resilient equipment-approval cloud flow
Level: 300 | Duration: 35 minutes
Harden a naive Power Automate cloud flow with Dataverse trigger filtering, a Try/Catch scope with a bounded retry policy, a reusable child flow, and a Microsoft Entra service-principal connection.
Consume a Power Platform MCP server from an MCP client
Level: 300 | Duration: 30 minutes
Connect GitHub Copilot CLI to an existing Dataverse MCP server, inspect the tools a supplied allowlist exposes, and retrieve equipment-provisioning data through a read-only connection.