What's changed: Created PL-400 Chapter 4 (domain: Extend the platform, part 2): custom connectors (Open API definition, auth OAuth/API key/Basic, policy templates, Azure Function, data transformation), platform APIs and Azure Functions (Dataverse Web API OData, Organization service .NET SDK, throttling/retry, OAuth, optimistic concurrency/ExecuteMultiple, Azure Functions long-running/triggers/managed identity), and Power Automate cloud flows (Dataverse connector, expressions, Azure Key Vault, error handling run after, trigger filter/retry, child flows, Entra ID service principal).
4.3Power Automate cloud flows
Understand the Dataverse connector, complex expressions, Azure Key Vault, error handling, trigger filter/retry, child flows, and Entra ID service principals.
Power Automate cloud flows handle low-code automation/integration. Developers build in reliability, reuse, and secret management.
4.3.1Dataverse connector, expressions, secrets
Build flows with the Dataverse connector triggers (row created/updated) and actions (get/update rows). Compute dynamic values with expressions. Retrieve secrets from Azure Key Vault (e.g., API keys) instead of hardcoding them in the flow.
4.3.2Reliability and reuse
Add error handling (scopes and "run after" configuring failure-path actions) for failures. Harden triggers with a trigger filter (conditions to avoid unneeded runs) and a retry policy. Extract shared logic into child flows for reuse across flows. Run unattended via a Microsoft Entra ID service principal, not a personal account.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.