Classify locally
Package, code, config, and runbook clues are processed in browser memory.
Azure Service Bus migration triage
Find the legacy client. Route the next test.
Paste redacted dependency or transport evidence. Get an owner-ready migration matrix without contacting Azure.
0 / 80,000
Remove real connection strings, endpoints, queue/topic names, customer data, tokens, logs, and private source before pasting.
browser memory only
Pasted-scope result
Service Bus exposure matrix
Sample mapped locally
RETIREMENT
September 30, 2026
Legacy Service Bus SDK support and SBMP protocol support retire on this date. Older libraries may still run, but without official support and updates.
Evidence boundary
Dependency clues are not runtime transport proof. Confirm current Microsoft guidance before acting.
Sensitive evidence warning
NO EVIDENCE
Add Service Bus evidence to begin.
Paste redacted package files, Maven/Gradle snippets, transport flags, runbook notes, or owner/test evidence.
| Component | Ecosystem | Evidence | Library | Transport | Exposure | Migration target | Blocker | Owner | Missing evidence | Exact next action | Boundary |
|---|
Transport and protocol review
Separate package exposure from SBMP, AMQP, WebSockets, and firewall proof.
Owner and test queue
Unknown stays unknown until a named owner attaches deployment-parity evidence.
| Scope | Environment | Owner | Firewall owner | Integration test | Rollback | Window | Next queue action |
|---|
Migration checklist
A test route, not a migration claim. Close each item with role-owned evidence.
Redacted handoffs
Neutral scope labels only. Raw pasted rows and detected identifiers are excluded.
Method boundary
A map of evidence, not a scan of Azure.
Keep gaps visible
Missing package, owner, transport, test, rollback, and parity proof remain unknown.
Route a safe handoff
Copy artifacts use neutral scope labels and omit pasted identifiers and secret-like values.