Integrating Dataverse with an external AI service
Short answer
B Create a custom connector that defines the third-party AI service's operations and authentication so Dataverse-integrated apps can send and receive custom requests.
Question
You must integrate Dataverse with a third-party AI service. The solution requires authentication and custom request handling to send and receive data.
You need to enable the integration.
What should you do?
Key Takeaways
This question tests which Power Platform artifact owns external API authentication and payload definition; the trap is picking an automation or data-movement tool instead of the connector layer.
Connecting Microsoft Dataverse to a third-party AI service that needs custom authentication and request handling requires a custom connector (B), which defines the service contract before any flow or app calls it.
Common mistake: Option A, a classic workflow, looks like the natural place to send data to an external service, but classic Dataverse workflows cannot define an external endpoint's schema or hold its credentials.
Expert Analysis
Where the requirement lands The scenario is not asking for orchestration logic inside Dataverse. It asks for a transport and contract layer: a channel that can hold credentials, define the third-party AI service's HTTP operations, and serialize custom request and response bodies. Dataverse itself has no native outbound binding to an arbitrary AI endpoint, so something must stand in between the Dataverse event and the external service.
Tracing the call path With option B, the custom connector is created in the Power Platform maker portal from the service's OpenAPI (Swagger) definition. Authentication type, headers, query parameters and the JSON payload shape are all defined at this layer. When a cloud flow, canvas app or model-driven app later invokes an action from that connector, the connector performs the authenticated call to the AI service and hands the structured result back to the calling component. That is exactly where "authentication and custom request handling" is satisfied — at connector definition time, before any business logic runs.
Why the other options fail
- A. A classic workflow is a legacy synchronous Dataverse workflow that runs against Dataverse records. It has no mechanism for defining an external service's schema or managing its auth scheme.
- C. Power Fx is an expression language for formulas inside apps and columns; it can call an existing connector but cannot define one, so it cannot supply the missing authentication contract.
- D. A dataflow moves and transforms tabular data into Dataverse or lakehouse storage. It is an ingestion path, not a request-handling channel for a live AI API.
The decisive step The correct answer is B: create a custom connector. Build it first, then consume its operations from the flow or app that triggers the Dataverse integration.
Official Reference
https://learn.microsoft.com/en-us/connectors/connectors
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question names authentication plus a custom payload for an external service, look for the option that defines the API contract itself — connectors own auth and schema, while flows, Power Fx and dataflows only consume or move data. Cross-check by asking which option could exist before any logic runs; the connector is the prerequisite layer, so it is almost always the answer in integration-shaped questions.
Frequently Asked Questions
Why can't a classic Dataverse workflow call the third-party AI service?
Can Power Fx be used instead of a custom connector for the AI service?
How does the custom connector fit with a dataflow in this scenario?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
ah2006 👍 1 Answered BB. Create a custom connector.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.