Users with RBAC enabled in the new Azure portal may encounter errors in the classic portal

For those of you who are long time Service Bus fans, you may have been wondering when Service Bus will be available in the new Azure portal. Well, thanks to the feedback posted at, we now have a limited private preview in place. In the coming weeks, we will open our preview to a larger set of customers.

In the meantime, if you utilize RBAC in the new Azure portal, you may notice an error when provisioning namespaces from the classic portal, or from PowerShell.

  1. When creating a Service Bus namespace on the new Azure portal at, users will get redirected to the old portal at where they get an error message stating “None of your subscriptions are associated with this directory.” Also you will not see your subscription when creating a namespace there.
  2. When creating a Service Bus namespace via the PowerShell command “New-AzureSBNamespace” users will get an error stating "ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associate with this subscription."

Cause:  The classic portal does not support the new RBAC model and still uses the “Service Admin” and “Co-Admin” model.

Solution 1: Use ARM templates to create a SB Namespace. More information can be found here:

Solution 2: Have the 'Service Admin' or 'Co-Admin' of the subscription create the Service Bus namespaces.

Solution 3: Have 'Service Admin' or 'Co-Admin' add you as 'Co-Admin' to the subscription. Follow these steps to do so:

  1. Have 'Service Admin' or 'Co-Admin' go to
  2. On the left bottom click on “Settings” tab.
  3. Click on the “Administrators” tab at the top of the page.
  4. Click on the “Add” button on the bottom of the page
  5. Add email ID of additional administrators and select the desired subscription.

If you have any questions feel free to leave a comment, or if you would like to contact our support team you can do so here.