Installation-Level Message Subscriptions: Migration to AMQP 1.0

Status:Effective FromFull Deprecation Date
Planned16/11/2026To be announced

What’s changing

Zaptec will continue to support installation-level subscriptions for existing subscribers. Delivery will move from Azure Service Bus to an AMQP 1.0 host. Installation-level subscriptions remain deprecated until the transition is complete. Final details and dates are to be confirmed.

User Group-level subscriptions are not affected by this change. If your integration only uses User Group-level subscriptions, you don’t need to do anything.

Requirements for installation-level subscriptions

  • Use AMQP 1.0 clients only. The current installation-level subscriptions already accept connections from standard AMQP 1.0 clients. The new AMQP 1.0 host will not support Azure Service Bus SDKs/libraries (for example Azure.Messaging.ServiceBus or azure-servicebus).
  • Don’t cache connection details. Credentials, hostname and other connection parameters may change at any time. Fetch them from GET https://api.zaptec.com/api/installation/{id}/messagingConnectionDetails before every connection attempt, including reconnects.

Both requirements work with the current service today, so you can migrate now.

Timeline

  • Now: Migrate installation-level integrations to AMQP 1.0 clients and stop caching connection details.
  • [TBC]: The AMQP 1.0 host becomes available. Azure Service Bus libraries will no longer be supported for installation-level subscriptions.

Impact

  • Installation-level integrations that use Azure Service Bus libraries will stop working once the AMQP 1.0 host replaces Service Bus.
  • Installation-level integrations that cache connection details may lose their connection without warning.
  • User Group-level subscriptions are not affected.

Action required (installation-level subscribers)

  1. Replace any Azure Service Bus SDK/library with a standard AMQP 1.0 client, such as AMQP.Net Lite (.NET), Apache Qpid Proton (Python, C, Java) or rhea (Node.js) or Any compliant AMQP 1.0 client should work.
  2. Call messagingConnectionDetails before every connection and never cache the results.
  3. Follow this page for confirmed dates and further updates.