[QUERY] Does Service Bus Administration Client support Service Bus Emulator

[samvaity]

Query/Question
Does Java Service Bus Administration Client support creating & managing entities using Service Bus Emulator?

Why is this not a Bug or a feature Request?
In this post, it mentions

For the Service Bus Emulator, creating and managing entities via the Service Bus Administration client is natively supported only in .NET.

I would like to know can I use it with Java SDK?

Setup (please complete the following information if applicable):

• OS: [e.g. iOS]
• IDE: [e.g. IntelliJ]
• Library/Libraries: [e.g. com.azure:azure-core:1.16.0 (groupId:artifactId:version)]

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Query Added
• Setup information Added

[github-actions]

🎯 Agentic Issue Triage

Thank you for your feedback. Tagging and routing to the team members best able to assist. cc @Azure/azure-java-sdk @EldertGrootenboer @skarri-microsoft

Summary: This is a question about whether the Java ServiceBusAdministrationClient can create and manage entities against the Azure Service Bus Emulator. The Microsoft documentation explicitly states this feature is natively supported only in .NET for now.

---

📋 Issue Analysis

Field	Detail
Type	Question
Library	com.azure:azure-messaging-servicebus
SDK directory	sdk/servicebus/azure-messaging-servicebus
Class in question	ServiceBusAdministrationClient / ServiceBusAdministrationAsyncClient
Related service	Azure Service Bus

🔍 Research Findings

Message Client (ServiceBusClientBuilder) — ✅ Emulator Supported

The AMQP-based message client (ServiceBusClientBuilder) already supports the Service Bus Emulator connection string in Java. From the CHANGELOG:

Added support for Service Bus Emulator connection string. Refer Azure Service Bus Emulator for emulator installation and supported connection strings.

Example connection string accepted by ServiceBusClientBuilder:

Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;

Administration Client (ServiceBusAdministrationClientBuilder) — ⚠️ Emulator NOT Natively Supported

The [Microsoft documentation]((learn.microsoft.com/redacted) explicitly states:

For the Service Bus Emulator, creating and managing entities via the Service Bus Administration client is natively supported only in .NET.

Reviewing ServiceBusAdministrationClientBuilder.java, there is no emulator/UseDevelopmentEmulator handling — it communicates over HTTP using the Service Bus management REST API, and the Java SDK has not implemented the emulator bypass for this path.

💡 Workaround Options

1. Pre-create entities via config file: The Service Bus Emulator supports a config.json file to pre-define queues, topics, and subscriptions at startup. This is the recommended approach for local testing without the Admin client:

   • See [emulator config documentation]((learn.microsoft.com/redacted)

2. Use the .NET Admin client for setup: If you need dynamic entity creation in tests, a small .NET helper can be used for setup, while the Java SDK handles messaging.

3. Track the feature request: If first-class Java support is needed, this should be filed as a feature request against the Java SDK team.

📚 Resources

• [Service Bus Emulator docs]((learn.microsoft.com/redacted)
• Service Bus Java README
• ServiceBusAdministrationClientBuilder source
• Emulator Installer GitHub
• [Azure SDK for Java – Service Bus API docs]((azure.github.io/redacted)

✅ Suggested Next Steps

• Team: Confirm whether adding emulator support to ServiceBusAdministrationClientBuilder is on the roadmap for Java parity with .NET
• Team: Consider updating the Java Service Bus README or troubleshooting guide to document the emulator limitation
• User: In the meantime, use the config.json approach to pre-create entities for local emulator testing

Note

🔒 Integrity filter blocked 6 items

The following items were blocked because they don't meet the GitHub integrity level.

• #48886 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below [none:samvaity/azure-sdk-for-java].
• #48134 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below [none:samvaity/azure-sdk-for-java].
• #48553 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below [none:samvaity/azure-sdk-for-java].
• #47958 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below [none:samvaity/azure-sdk-for-java].
• #47926 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below [none:samvaity/azure-sdk-for-java].
• #43060 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below [none:samvaity/azure-sdk-for-java].

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Agentic Triage for issue #9 · ● 426.8K · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@8e6d7c86bba37371d2d0eee1a23563db3e561eb5