AB-400 Explained: Azure Functions for Power Platform Workloads

About this video

Learn how to use Azure Functions for Power Platform background workloads in this AB-400 Explained session. Explore how to separate task submission from execution so long-running work can run independently of interactive apps and Dataverse transactions. Design recoverable jobs with clear identity boundaries, durable status tracking, and idempotent processing. Topics covered: • Intake components, dispatch mechanisms, workers, and status readers • HTTP, Timer, and Queue trigger selection • Durable job submission with HTTP 202 Accepted and a jobId • Persisted checkpoints for scheduled batch discovery • Entra ID authorization for job submission and status access • Azure Functions Managed Identity and Dataverse Application Users • Least-privilege Dataverse security roles • requestKey-based recovery and duplicate request handling • Atomic job claims, progress tracking, and idempotent writes • Saving business results before marking jobs as Succeeded • Testing lost responses, duplicate messages, worker restarts, and permission failures For learners preparing for AB-400 and developers building Azure Functions integrations with Power Platform and Dataverse. #AB400 #AzureFunctions #PowerPlatform