A partner system needs to be told when an insurance claim is approved. Approval involves several rule checks across multiple Dataverse rows, and the partner does not want to receive notifications for every field edit on the claim table. Which design best meets the requirement?

Dataverse business events let developers model meaningful occurrences as custom APIs, catalog them, and deliver them to subscribers asynchronously after the operation succeeds. Approval is a business outcome determined by several checks across multiple rows, so the logic that confirms approval should raise a specific event such as OnClaimApproved, carrying only the parameters the partner needs. Microsoft's design principles call for events with clear intent that are specific and lightweight so subscribers do not have to filter. A webhook on the Update message sends the execution context for every update to a claim, regardless of whether approval occurred, so the partner receives the noise it wants to avoid and must reconstruct the approval rules itself. A Service Bus endpoint on Create fires only when claims are created, which is not when approval happens, and pushes filtering responsibility to the partner. Filtering attributes listing every claim column make the Update step fire on any change to any column, which is functionally the same as no filter and still does not identify approvals. Exam caveat: business events are not meant for bulk data transfer; for synchronizing data, use change tracking or a dedicated integration. Operational check: approve a claim and edit a different claim's description, then confirm the partner endpoint receives exactly one OnClaimApproved notification.