A consultant is extending the Sales Qualification Agent so that, before qualifying a lead, it retrieves a real-time credit risk score from an external Azure Function that is not exposed as a Dataverse table or standard connector. (Select TWO.) Which two actions are required to let the Sales Qualification Agent call this function as part of its qualification logic?
Select all correct answers, then click Submit.
Short Explanation
When an AI agent needs to reach out to something completely outside Dynamics 365 — like a custom function nobody built a connector for yet — two things have to happen. First, something has to describe to the platform how to talk to that function: where it lives, how to authenticate, what it expects and returns. Second, the agent's own logic needs an actual step that calls that description and does something with the answer, like factoring a risk score into whether a lead qualifies. Skip either piece and nothing works — describing the endpoint without wiring it into the flow just leaves it sitting unused, and trying to wire a call without first describing the endpoint gives the flow nothing to call. Treating a raw external function like it is native CRM data you can query directly does not work without real integration plumbing behind it, and there is no magic setting that finds and connects to outside services on its own.
Full Explanation
The correct answers are A and B. Calling an external Azure Function that is not exposed through Dataverse or a standard connector requires two pieces: a custom connector that describes the function's endpoint, authentication, and request and response shape, and an action wired into the agent's flow that invokes that connector and feeds the returned score into the qualification logic. Neither step alone is sufficient — the connector defines how to reach the function, and the flow action determines when and how the result is used. Option C is incorrect because a Dataverse virtual table requires a data provider that understands the target system's query model; an arbitrary Azure Function endpoint cannot simply be pointed at as a virtual table without that provider layer, making it an unreliable and unsupported shortcut for this scenario. Option D is incorrect because Copilot Studio and the Sales Qualification Agent have no auto-discovery mechanism that scans an Azure subscription for callable functions; every external call must be explicitly registered and wired, so relying on automatic discovery would leave the integration nonfunctional.