CODEWITHSUNDEEP
azureservicebusacs
ALK
ALK

Reputation: 11

Restrictions on creation of ACS namespace - Jun 30

As per this blog https://azure.microsoft.com/en-us/blog/acs-access-control-service-namespace-creation-restriction/ creation of new ACS enabled Service Bus namespace is restricted from Jun 30 2017. However, I am able to create them using powershell commands. Is there a change in the effective date?

I wrote to [email protected] a week back but didn't receive any response

Upvotes: 1

Views: 262

Answers (1)

Brando Zhang
Brando Zhang

Reputation: 27997

According to this article:

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 by opening a technical support ticket for options. You will need to provide the subscription ID or IDs that you use for creating ACS namespaces to the support engineer that assists you. Going forward please think about using Shared Access Signature (SAS) keys instead.

I'm also very strange you could create new ACS, I suggest you could contact Azure support or send email([email protected]) to check the new ACS is as same as the ACS Namespaces created before June 30.

Besides, we don't suggest you use ACS, SAS is recommended over ACS, as it provides a simple, flexible, and easy-to-use authentication scheme for Service Bus. Applications can use SAS in scenarios in which they do not need to manage the notion of an authorized "user."

Upvotes: 1

Related Questions