Fix ServiceBus Tools Issues#2680
Draft
g2vinay wants to merge 1 commit into
Draft
Conversation
…from detail commands, return readable message content, fix topic-not-found error message, fix namespace validation error type, apply retry policy to peek operations
alzimmermsft
approved these changes
May 20, 2026
github-project-automation
Bot
moved this from Untriaged
to In Progress
in Azure MCP Server
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixed multiple issues in Azure Service Bus commands:
-
--subscriptionoption was incorrectly required onqueue details,topic details, andtopic subscription detailscommands; the option has been removed since the namespace FQDN is sufficient for authentication.-
topic detailsreturned "Subscription not found" when a topic did not exist; the error message now correctly reads "Topic not found".- Malformed namespace names (containing path separators or other invalid characters) raised a
SecurityException; they now raise anArgumentExceptionto correctly signal invalid input rather than a security violation.