Seeking Azure-based consumers for MNS discovery work

Sharing Clinical Data Multicast Notification Service (MNS)
1

We’re currently exploring a number of potential approaches for supporting new MNS event consumption patterns on Azure and would like to validate our thinking with suppliers who are either already using Azure or planning to consume MNS events via Azure services.

As part of this work, we’re looking to speak with organisations that would be willing to spend 30–60 minutes with our engineering team to discuss:

  • Your Azure architecture and preferred integration patterns
  • Operational considerations such as resilience, monitoring and message replay
  • Any constraints or requirements we should consider when evaluating options

These discussions are purely exploratory and will help us better understand real-world consumer needs before making any decisions on a preferred approach.

If your organisation would be interested in taking part, please reply to this post or contact me directly.

Many thanks,

Paul Murphy
Product Owner, MNS

2

Thank you to everyone who reached out directly and collaborated with us on this work over the past few months.

Through discussions with internal and external partners, we completed a proof of concept (PoC) evaluating HTTP/webhook event delivery patterns into Azure environments.

Following the PoC findings, our engineering team is currently assessing webhook authentication and security options (including signed JWTs, HMAC payload signing, and RFC 9421 HTTP Message Signatures) against key criteria such as replay protection, payload integrity, and ease of implementation using Azure-native tooling.

We are updating our Key Architectural Decisions (KAD) based on this analysis and will share further architectural guidance and onboarding documentation as we progress.

If you have specific requirements or questions around Azure integration patterns in the meantime, please feel free to reach out.

Thanks