To Azure Service Bus, Event Hubs and Relay customers,

We want to make sure you are aware of upcoming changes announced in this blog post for Access Control Service (ACS) Namespaces.  On June 30, 2017 creating new Acs Namespaces will be restricted.

How will this affect my Service Bus, Event Hubs or Relay ACS namespaces?

ACS Namespaces you create before June 30, 2017 will not be affected and will be fully supported, however, attempts to create new ACS enabled Service Bus, Event Hubs, or Relay namespaces using PowerShell, ARM templates, and our APIs after June 30 will fail. If ACS support is vital for your business and you need to create ACS namespaces after this date please contact Azure Customer Support for options.  Please be aware that we highly recommend you use Shared Access Signature (SAS) keys instead.

The Future of Access and Identity Management for Azure Service Bus, Event Hubs, and Relay

If you are using ACS please switch to SAS or if you are using SAS today continue to use it. We are also actively working on Azure Active Directory (Azure AD) support.  If you would like to stay updated on Azure AD support on Service Bus, Event Hubs or Relay and be a part of a private preview in the future to test it out, please join Azure Advisors on Yammer and become a member of our group Service Bus Advisors.  Once there you can interact with other members of the community and the product team.

Happy Messaging and Data Streaming,

The Azure Service Bus, Event Hubs, and Relay team (The Azure Messaging Team)

–Relay out–