An osprey-bluff subscriber is not an Azure service and expects CloudEvents 1.0. How should Event Grid deliver events for that interoperability need?
Select an answer to reveal the explanation.
Short Explanation
Speak CloudEvents when the other side expects the open schema. Event Grid can deliver that way—no private wiki JSON and no Graph costume party.
Full Explanation
Event Grid can deliver using the CloudEvents 1.0 schema, which is the open interoperability format non-Azure subscribers often require. For an osprey-bluff subscriber that is not an Azure service and expects CloudEvents, configure delivery in that schema rather than inventing a private shape or forcing only the Event Grid schema.
Inventing a private JSON shape documented only in a wiki page fails interoperability: each subscriber must special-case undocumented fields, which is the opposite of CloudEvents.
Wrapping every payload as a Microsoft Graph message body fails because Graph message shapes are for mail/Graph APIs, not the Event Grid delivery schema choice for arbitrary HTTPS subscribers.
Forcing Event Grid schema only and refusing non-Azure subscribers fails the stated need: Event Grid explicitly supports CloudEvents for broader interoperability; refusing non-Azure parties is not the skill.
Exam caveat: CloudEvents and Event Grid schemas differ in envelope fields—subscribers must parse the schema you configure, and changing schema is a breaking contract. Operational check: set the subscription (or topic delivery) to CloudEvents 1.0, publish a sample event, and verify the receiver sees the CloudEvents attributes it expects.