AB-400: Dataverse MCP and Work IQ Access for Agents
Choose Dataverse Model Context Protocol (MCP) access when an agent needs a discoverable interface to a particular Microsoft Dataverse environment's data and operations.
AB-400: Integrating Foundry and Copilot Studio Agents
Compose Microsoft Foundry and Microsoft Copilot Studio around explicit ownership: the application owns its user session, Copilot Studio owns the conversation it orchestrates, a connected Foundry agent performs a bounded specialist task,…
AB-400: Reliable Cloud Flows and Copilot Studio Workflows
To implement reliable cloud flows and Copilot Studio workflows, define a typed input/output contract, filter irrelevant events at the trigger, validate admitted requests, and put reusable work behind an explicit child-flow boundary.
Browse the journal
All articles
208 published articles
AB-400: Dataverse MCP and Work IQ Access for Agents
Choose Dataverse Model Context Protocol (MCP) access when an agent needs a discoverable interface to a particular Microsoft Dataverse environment's data and operations.
AB-400: Integrating Foundry and Copilot Studio Agents
Compose Microsoft Foundry and Microsoft Copilot Studio around explicit ownership: the application owns its user session, Copilot Studio owns the conversation it orchestrates, a connected Foundry agent performs a bounded specialist task,…
AB-400: Reliable Cloud Flows and Copilot Studio Workflows
To implement reliable cloud flows and Copilot Studio workflows, define a typed input/output contract, filter irrelevant events at the trigger, validate admitted requests, and put reusable work behind an explicit child-flow boundary.
AB-400: Azure Functions for Power Platform Workloads
Use Azure Functions for Power Platform workloads by separating submission from execution: accept a bounded request, persist an identifiable job, and let a scheduled or event-driven worker process it independently of the caller.
AB-400: Reliable Dataverse Bulk and Background Operations
For reliable Dataverse bulk and background operations, choose the unit of correctness before increasing throughput: decide which writes must succeed together, select a supported bulk or individual-request path, bound concurrent work, and…
AB-400: Dataverse API Clients and OAuth Authentication
Choose Dataverse API clients and OAuth authentication separately: use the Dataverse Web API for portable HTTP applications and browser access, prefer the SDK for .NET with ServiceClient when a .NET application benefits from Dataverse…
AB-400: Custom APIs, Business Events and Plug-in Identity
To expose a governed Dataverse operation, define its named custom application programming interface (API) and typed contract, attach the implementing plug-in, enforce caller and record authorization, and configure Microsoft Power Platform…
AB-400: Dataverse Plug-ins and the Event Execution Pipeline
To enforce a Dataverse data invariant across clients, define the rule on the server, select the message and table that carry the write, and register synchronous plug-in steps at the stage where the necessary data exists.
AB-400: Deploying and Troubleshooting Power Apps Code Apps
Release a Power Apps code app by building the tested source, publishing it into the intended environment and solution, and validating access as an intended user.
AB-400: Building Code Apps with Dataverse and Automation
Build a Power Apps code app by initializing it for one development environment, adding its governed data sources with the Power Apps CLI, and inspecting the generated TypeScript contracts before wiring user actions.
AB-400: Building Reusable PCF Code Components
Building reusable PCF code components starts with a host contract: choose the app surface, define the data and capabilities in the manifest, implement the component lifecycle, package the component in a solution, and configure a consuming…
AB-400: Client Scripting and Commands in Model-Driven Apps
To add responsive client scripting and commands in model-driven apps, first define the interaction, register a JavaScript web resource on the appropriate form events, and obtain the form context from each event's execution context.