A canvas app can natively consume a custom connector, giving makers a low-code, interactive UI that calls any REST-based Web API in real time. The connector abstracts authentication, request, and response handling; once it is added to the canvas app, API operations are available as standard functions that run client-side with immediate results for the user. Microsoft documentation recommends this pattern whenever external services must be surfaced directly in an app’s interface.

B. Plug-ins run server-side in Dataverse; sandbox security restricts outbound HTTP requests and they cannot provide a user-interactive experience.

C. Power Automate flows can use the connector but execute asynchronously/background; requirement for direct app interaction is unmet.

D. Webhooks push Dataverse events to external endpoints; they are one-way notifications and cannot be invoked on demand by an app.

1. Microsoft Docs – “Register and use a custom connector in a canvas app”, Power Apps documentation, Section: Use the connector in a canvas app (2023-10-05).

2. Microsoft Docs – “Call an external web service from a plug-in”, Dataverse developer guide, Section: Sandbox limitations (2023-09-12).

3. Microsoft Docs – “Introduction to Power Automate flows in Power Apps”, Power Automate documentation, Section: Differences between flows and app logic (2023-08-18).

4. Microsoft Docs – “Create webhooks to Azure Functions and external services”, Dataverse Webhooks, Section: Webhook capabilities and limitations (2023-07-30).