An Azure service that provides cloud messaging as a service and hybrid integration.
This is commonly caused by Azure for Students policy restrictions on allowed deployment regions, not by Service Bus itself.
Try this:
- In Azure portal, open Policy > Assignments.
- Find the assignment named Allowed resource deployment regions or Allowed locations.
- Open the assignment and check the Parameter value for the list of regions allowed for that subscription.
- Create the Service Bus namespace again, but choose one of those allowed regions.
When creating the namespace in the portal:
- Go to All services > Integration > Service Bus > Create.
- On Create namespace:
- Select the correct Subscription.
- Select or create a Resource group.
- Enter a Namespace name that:
- is unique across Azure
- is 6 to 50 characters
- uses only letters, numbers, and hyphens (
-) - starts with a letter
- ends with a letter or number
- does not end with
-sbor-mgmt
- Choose an allowed Location from the policy assignment.
- Select a pricing tier.
If the namespace creation returns a message that the namespace does not exist, verify:
- the correct Azure subscription is selected
- the namespace name is spelled correctly
- the namespace actually exists in that subscription
If deployment is still blocked after selecting an allowed region, the subscription policy is preventing that resource deployment and a support request is required.
References: