Business events
Business events enable business process integrations between finance and operations apps and external systems in a decoupled fashion.
Durable business events - No false business events should be sent to the recipient. If a purchase order confirmation business event was sent out, then the recipient must trust that the purchase order was indeed confirmed. The design choice must ensure this transactional nature.
Targeted - Business events must be designed to optimize the consumption story for the recipient. In other words, you must make it as easy as possible for the recipient to consume business events. Hence, business events must be specific and targeted to a specific consumer.
Noiseless - Little effort should go into the design that is needed to filter out noise. To make business events specific, make sure that you avoid writing filtering logic to filter out conditions that do not match the expected business event.
Different types of events exist, including Application, Workflow, and Alert events. These events can be consumed by cloud endpoints like Microsoft Power Automate, Azure Logic Apps, or Azure Data Lake Storage for many different scenarios, such as for workflows, notifications, or integrations.
For more information, see Consume business events in finance and operations apps..