Manage business event endpoints

Endpoints let you manage the destinations that business events are sent to. Business events in finance and operations apps support the following endpoint types.

Endpoints can be created for these messaging and event brokers out of the box. Some scenarios might require multiple endpoints for organized distribution of business events to consumers. You can create multiple endpoints to support these scenarios.

The Microsoft Azure–based endpoints must be in the customer's Azure subscription. For example, if Event Grid is used as an endpoint, the endpoint must be in the customer's Azure subscription.

A finance and operations app doesn't provision the endpoints. The endpoints must be created separately and provided to the app. The app then sends events to the endpoints that are provided. Customers might incur additional costs if they use these endpoints in their Azure subscription.

Subscribing to finance and operations apps events from Dataverse

After the Microsoft Power Platform integration is enabled, you can subscribe to finance and operations apps business events and data events from Dataverse. Subscription enables the following capabilities:

• Consistent behavior across events from multiple applications in Dataverse
• Application Lifecycle Management (ALM) for the Dataverse solution to consistently consume events from finance and operations apps
• Registration of plug-ins and software development kit (SDK) steps on finance and operations apps events in Dataverse

When the Microsoft Power Platform integration is enabled for a finance and operations apps environment, endpoints that are created for business events are synced with the linked Microsoft Power Platform environment for endpoint types that are supported in Dataverse. The endpoints can then be used in Microsoft Power Platform. When the endpoints are synced, business events that are sent from finance and operations apps are proxied through Dataverse to the endpoint.

The following table shows the mapping between the finance and operations apps and Dataverse implementations of the endpoints.

Viewing or creating mapped endpoints in Dataverse

When a new endpoint is added in finance and operations apps, it's synced to Dataverse. It's then available for use in Dataverse in the ServiceEndpoint table. You can also create the endpoint directly in Dataverse in the ServiceEndpoint table. If the service endpoint is created by subscribing to a finance and operations apps event, it will automatically be made available to finance and operations apps and can be viewed on the Endpoints tab of the Business events page. This behavior is applicable to the following mapped endpoint types:

• Azure Service Bus Queue
• Azure Service Bus Topic
• Azure Event Grid
• Azure Event Hub

For more information about the ServiceEndpoint table, see ServiceEndpoint table/entity reference.

Microsoft Power Automate endpoints

The Microsoft Power Automate endpoint type isn't made available for setup directly in finance and operations apps. This endpoint type is used for subscriptions that are created and sent directly from a flow in Power Automate.

The endpoint is created on the Endpoints tab of the Business events page in finance and operations apps when you subscribe to a finance and operations apps business event or data event in Power Automate. For more information about how to subscribe to business events and data events in Power Automate, see Business events in Microsoft Power Automate.

Microsoft Dataverse endpoints

The Dataverse endpoint type also isn't available for manual setup in finance and operations apps. The endpoint is created when a plug-in or an SDK step is registered on a finance and operations apps business event or data event in Dataverse. When the step is registered, it becomes visible as an endpoint in the list on the Endpoints tab of the Business events page in finance and operations apps.

The business event registration itself will also be listed on either the Business event catalog tab or the Data event catalog tab of the Business events page in finance and operations apps, depending on registration. In this way, finance and operations apps users can learn which business event or data event has a plug-in or SDK step registered in Dataverse. They can also learn the reason why the event is active in finance and operations apps.

Finance and operations apps events can be subscribed to directly in Dataverse by using the tools in the Dataverse toolset, such as the Power Platform Tools extension for Visual Studio. For more information about this extension, see Install Power Platform Tools. These subscriptions will appear on the Business event catalog tab of the Business events page in finance and operations apps.

Some attributes of service endpoints in Dataverse, such as the name and description, can be updated. These updates will also be reflected in finance and operations apps. However, updates that change the service endpoint type will be prevented if the service endpoint is used with finance and operations apps events. These updates include a change from a Service Bus article to a Service Bus queue, which Dataverse usually allows. This behavior helps ensure design simplicity and consistency, because finance and operations apps don't allow these updates to endpoints after they have been created.

After service endpoints are created, Dataverse doesn't allow them to be deleted if they are being used. This limitation also applies to service endpoints that are used by finance and operations apps events. Any attempt to delete one of these endpoints will cause an error, and deletion will be prevented.

For more information about how to subscribe to finance and operations apps business events in Dataverse, see Subscribe to events in Dataverse.