Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receiving 403 when accessing Service Bus REST API with incorrect Subscription / Resource Group #695

Open
Kaegun opened this issue Feb 6, 2024 · 2 comments

Comments

@Kaegun
Copy link

Kaegun commented Feb 6, 2024

Description

When calling the Service Bus REST API (https://learn.microsoft.com/en-us/rest/api/servicebus/) with an incorrect SubscriptionId or ResourceGroup parameter, I receive a 403 error back. I spent far too much time chasing authentication failures before realizing the misconfigured SubscriptionId/ResourceGroup.

Actual Behavior

  1. Call Service Bus REST operation - POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName}/authorizationRules/{authorizationRuleName}/ListKeys?api-version=2021-11-01
  2. Use an incorrect value for subscription or resource group.
  3. Receive 403 response.

Expected Behavior

  1. Call REST operation - POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName}/authorizationRules/{authorizationRuleName}/ListKeys?api-version=2021-11-01
  2. Use an incorrect value for subscription or resource group
  3. Receive 404 response
@EldertGrootenboer
Copy link
Contributor

Thank you for your feedback. We have opened an investigation task for this in our backlog, and will update this issue when we have more information.

@EldertGrootenboer
Copy link
Contributor

This item in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants