AB-400 Explained: Lab: A Governed Service Request Integration

About this video

Build and test a governed service request integration in this hands-on AB-400 Explained lab. Connect parent and child cloud flows, a custom connector, an Azure Function, and Dataverse. Use a persistent receipt ledger to verify access boundaries, detect conflicting requests, and recover from injected failures without creating duplicate receipts. Topics covered: • End-to-end integration architecture and isolated lab identities • Least-privilege permissions for operators and the Function Application User • Service Request and Mock Receipt tables with Active composite Alternate Keys • Immutable receipt payloads and deterministic replay handling • Matching requests, replayed receipts, and HTTP 409 identity conflicts • Parent and child flow orchestration with structured outcomes • Separate business request identity and execution attemptId values • Before-write and after-write failure injection • Reconcile states and recovery using durable receipt confirmation • Acceptance checks for receipt counts and unauthorized access • Lab cleanup, role revocation, and Azure resource teardown For learners preparing for AB-400 and developers practicing reliable Power Platform integrations in an isolated environment. #AB400 #PowerPlatform #Dataverse