A company plans to implement an integration between Microsoft Dataverse and Azure Service Bus. When an Account row is updated, if the Credit Limit is set to over $25,000, information about the row…

Question

Options

• AIServiceEndpointNotificationService
• BIPluginExecutionContext
• CIWebHttpServiceEndpointPlugin
• DIServiceEndpointPlugin

• A
  7% (1)
• B
  73% (11)
• C
  7% (1)
• D
  13% (2)

Explanation

Power Platform, Power Apps, Dataverse, Azure integration The Azure Service Bus provides a secure and reliable communication channel between Dataverse runtime data and external cloud-based line-of-business (LOB) applications. This capability is especially useful in keeping disparate Dataverse systems or other Dataverse servers synchronized with business data changes. The data context contains the business data that is being processed as part of the current Dataverse operation. This processing was initiated when a request to perform a certain Dataverse operation was made by a user, workflow, or application. The data context is passed to any plug-ins or custom workflow activities that are registered with the event pipeline to execute on the specific request and table combination that is currently being processed. The data context is of type IPluginExecutionContext when when passed along the event execution pipeline and RemoteExecutionContext when posted to the Service Bus. Note: Microsoft Dataverse supports integration with Azure. Developers can register plug-ins with Dataverse that can pass runtime message data, known as the execution context, to one or more Azure solutions in the cloud. This capability is especially important because Azure is one of a few supported solutions for communicating runtime context to external line-of-business (LOB) https://learn.microsoft.com/en-us/power-apps/developer/data-platform/azure-integration

No community discussion yet for this question.