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.2Platform APIs and Azure Functions
Understand the Dataverse Web API, the Organization service, API limits and retries, OAuth, concurrency/transactions/bulk, and Azure Functions (long-running, triggers, managed identities).
There are multiple ways to operate Dataverse programmatically. Design which API to use and within which constraints.
4.2.1Web API and Organization service
The Dataverse Web API is an OData v4-based REST API callable over HTTP from any language/client. The Organization service uses the .NET SDK (IOrganizationService) from server-side/plug-ins. Authenticate with OAuth 2.0 (a Microsoft Entra ID app registration). APIs have request limits (throttling); handle 429 responses with retry (exponential backoff).
4.2.2Concurrency, bulk, Azure Functions
Detect update conflicts with optimistic concurrency (ETag/RowVersion) and keep integrity with transactions. Batch many operations with bulk (ExecuteMultipleRequest) for performance. Offload long-running work beyond plug-in timeouts to Azure Functions, started by scheduled/event-driven triggers. Azure Functions can authenticate to Power Platform with managed identities, removing secret management.
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.