Azure Service Bus

Create a Service Bus namespace and queue through Azure Resource Manager, read the queue's settings back, then delete both.

Plan: Free70 of 83 operations implemented across 2 APIs, 2 failed in testing

Messages weren't sent or received: AMQP wasn't tested, and the HTTPS data routes tried answer HTTP 501 DataPlaneNotEmulated.

Example checked on Vera 1.2.2, 8 November 2026. Each coverage note names its own evidence and date.

Connect

Start Vera as in Get started. Then open Bash in a terminal of its own (on macOS, whose terminal starts zsh, type bash first), go to an empty scratch directory and run this; it needs curl and Python 3. It fetches the emulator's own certificate, so every request checks TLS, and defines azmsg_request, azmsg_json and azmsg_wait, which this page's commands use. The bearer token vera-local is a dummy local credential, not your license key.

export VERA_CA_CERT="$PWD/vera-ca.pem"
curl --fail --silent --show-error --noproxy '*' --insecure \
  https://localhost:8543/_vera/ca.pem --output "$VERA_CA_CERT"
curl --fail --silent --show-error --noproxy '*' \
  --cacert "$VERA_CA_CERT" https://localhost:8543/_vera/health; echo

AZURE_ENDPOINT=https://localhost:8543
SUB=00000000-0000-0000-0000-000000000001
RG=azmsg-launch
BASE="/subscriptions/$SUB/resourceGroups/$RG"

44 more lines: show the full setup
# Writes each response to last.json and its headers to last.headers.
azmsg_request() {
  local method=$1 url=$2 body=${3:-} content_type=${4:-application/json} host
  [[ "$url" == /* ]] && url="$AZURE_ENDPOINT$url"
  host=$(python3 -c 'import sys,urllib.parse; u=urllib.parse.urlparse(sys.argv[1]); assert u.scheme=="https" and (u.hostname=="localhost" or u.hostname.endswith(".localhost")) and u.port==8543; print(u.hostname)' "$url") || return 1
  local args=(--noproxy '*' --silent --show-error --fail-with-body --max-time 30
    --cacert "$VERA_CA_CERT" --resolve "$host:8543:127.0.0.1"
    -H 'Authorization: Bearer vera-local' -D last.headers -o last.json -X "$method")
  [[ -n "$body" ]] && args+=(-H "Content-Type: $content_type" --data-binary "@$body")
  curl "${args[@]}" "$url"
}
azmsg_json() { python3 -c 'import json,sys; v=json.load(open(sys.argv[1]));
for k in sys.argv[2].split("."): v=v[int(k)] if isinstance(v,list) else v[k]
print(v if isinstance(v,str) else json.dumps(v))' "$1" "$2"; }
azmsg_wait() {
  local poll state
  poll=$(python3 - <<'PY'
from pathlib import Path
h={}
for line in Path('last.headers').read_text().splitlines():
 if ':' in line:
  k,v=line.split(':',1); h[k.lower()]=v.strip()
print(h.get('azure-asyncoperation') or h.get('location') or '')
PY
) || return 1
  [[ -z "$poll" ]] && return 0
  for attempt in {1..30}; do
    azmsg_request GET "$poll" || return
    state=$(python3 - <<'PY'
import json
from pathlib import Path
body=Path('last.json').read_text()
if body.strip():
 v=json.loads(body); print(v.get('status',v.get('properties',{}).get('provisioningState','')))
else:
 status=Path('last.headers').read_text().splitlines()[0].split()[1]
 print('Succeeded' if status in ('200','204') else '')
PY
) || return 1
    case "$state" in Succeeded|Completed) return 0;; Failed|Canceled|Cancelled) cat last.json; return 1;; esac
    sleep 1
  done
  echo 'Operation did not finish within 30 polls' >&2; return 1
}

The health check answers {"cloud": "azure", "generation_status": "generated", "status": "ok"}. Requests go only to the emulator at https://localhost:8543: the helper refuses any other address, including the Azure-looking URLs some responses hold. When you've finished, close the terminal and delete the scratch directory; that removes only these local files, not what you created in the emulator.

The example uses Resource Manager’s Microsoft.ServiceBus API at version 2026-01-01, the version tested with Vera 1.2.2. Other versions can be rejected: 1900-01-01 returned 400 InvalidApiVersionParameter. It manages resources and sends no messages, so it needs no Service Bus client library or connection string.

Example

Create a namespace and a queue in it, then read back the queue’s saved settings. This example is configuration only: it doesn’t send or receive a message, which isn’t established (see Limitations).

The first lines create the resource group azmsg-launch for the example’s resources. Creating the namespace is a long-running operation: azmsg_wait follows it until the namespace is ready, since creating the queue sooner can return 409. Only the last command prints.

cat > rg.json <<'JSON'
{"location":"eastus"}
JSON
azmsg_request PUT "$BASE?api-version=2025-04-01" rg.json

BUS="$BASE/providers/Microsoft.ServiceBus/namespaces/azmsgfinal-bus"
cat > namespace.json <<'JSON'
{"location":"eastus","sku":{"name":"Standard","tier":"Standard"}}
JSON
azmsg_request PUT "$BUS?api-version=2026-01-01" namespace.json
azmsg_wait
cat > queue.json <<'JSON'
{"properties":{"maxDeliveryCount":5,"lockDuration":"PT1M"}}
JSON
azmsg_request PUT "$BUS/queues/jobs?api-version=2026-01-01" queue.json
azmsg_request GET "$BUS/queues/jobs?api-version=2026-01-01"
cp last.json bus-queue.json
python3 -m json.tool bus-queue.json

The namespace request returns 201 and an operation to follow; the queue’s create and read return 200. The queue keeps its settings and is Active. These are selected fields; the response also has the queue’s resource ID and timestamps.

{
    "name": "jobs",
    "properties": {
        "lockDuration": "PT1M",
        "maxDeliveryCount": 5,
        "status": "Active"
    }
}

To clean up, delete the queue, then the namespace, waiting for each deletion to finish. The commands print nothing when they succeed.

BUS="$BASE/providers/Microsoft.ServiceBus/namespaces/azmsgfinal-bus"
azmsg_request DELETE "$BUS/queues/jobs?api-version=2026-01-01"
azmsg_wait
azmsg_request DELETE "$BUS?api-version=2026-01-01"
azmsg_wait

This leaves the resource group azmsg-launch in place: deleting a resource group fails in Vera 1.2.2, as Resource Manager basics explains. A fresh emulator starts without it.

Supported features

Namespaces, created with a Standard SKU, read and deleted. Creating one returns 201 with an operation to follow.
Queues, created with settings such as maxDeliveryCount and lockDuration, read back with their settings and status Active, and deleted. In testing of Vera 1.2.0 preview, a queue created before its namespace had finished provisioning returned 409; the same request returned 200 once it had.
Topics and subscriptions: in a separate check on Vera 1.2.0 preview, a topic and a subscription to it were created through Resource Manager. That’s stored configuration: nothing was published to the topic.
API version checks: an unsupported api-version returned 400 InvalidApiVersionParameter.

Limitations

The main limits are below. A few more apply to every service, and the API coverage notes cover smaller differences.

No message was sent or received. AMQP, the protocol Service Bus client libraries send and receive over, wasn’t tested on Vera 1.2.0 preview or Vera 1.2.0-rc.3, and the Resource Manager operations don’t add an AMQP transport or message delivery. Sessions, locks, time to live, dead-lettering, transactions, retries and delivery guarantees aren’t established, and queue settings such as maxDeliveryCount are stored, not shown to take effect.
The HTTPS data routes are refused. Management operations work as shown, but the emulator doesn’t serve Service Bus data calls. In Vera 1.2.0-rc.3, with the example’s queue in place, reading it at https://azmsgfinal-bus.servicebus.localhost:8543/jobs?api-version=2021-05, reading the namespace at /$namespaceinfo?api-version=2021-05 on the same host, and requests to the message routes /jobs/messages and /jobs/messages/head each answered HTTP 501 DataPlaneNotEmulated, saying the resource is managed through Resource Manager. A review of the source found no implementation for any of the 13 operations of the legacy Atom/XML entity API, such as Entity_Put, Subscription_Get and listEntities. Manage queues, topics, subscriptions and rules through Resource Manager instead.
Rule filters accept a subset of SQL. A rule’s SQL filter is checked against a safe local subset of the syntax, and anything outside it is rejected. Whether a filter selects messages isn’t established, since no message was delivered.
Disaster recovery copies configuration only. A geo-disaster recovery pairing mirrors local namespace configuration, not messages, and replication isn’t established.
Not run as examples: authorization rules and keys, topic rules, network rule sets, private endpoints, disaster recovery and migration. The API coverage marks these from a review of Vera 1.2.0’s source, with their limits in the notes.

API coverage

Every operation of the APIs on this page, from their pinned public definitions, and whether Vera 1.2.0 implements it. Only the API surfaces in this release are listed, and each operation once. Implementation availability was reviewed against the Vera 1.2.0 source on 6 November 2026. Source inspection identifies a local implementation and its known limits; it doesn't mean every operation or API version was tested with a request. Each note names its evidence: a Local observation without a build or date is from Vera 1.2.0 preview, on 5 November 2026, and one from a later build, such as Vera 1.2.0-rc.3 or Vera 1.2.2, names that build and its date. No response was compared with Azure's. What the statuses mean

Service Bus management 2026-01-01Plan: Free

70 of 70 implemented

Version 2026-01-01, from the Azure REST API specifications at commit 21bbf1b.

DisasterRecoveryConfigs

10 of 10 implemented

Operation	Status	Notes
DisasterRecoveryConfigs_BreakPairing	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_CheckNameAvailability	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_CreateOrUpdate	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_Delete	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_FailOver	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_Get	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_GetAuthorizationRule	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_List	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_ListAuthorizationRules	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
DisasterRecoveryConfigs_ListKeys	Implemented	Source inspection: Geo-disaster recovery mirrors local namespace configuration, not messages. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

MigrationConfigs

6 of 6 implemented

Operation	Status	Notes
MigrationConfigs_CompleteMigration	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
MigrationConfigs_CreateAndStartMigration	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
MigrationConfigs_Delete	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
MigrationConfigs_Get	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
MigrationConfigs_List	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
MigrationConfigs_Revert	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

Namespaces

17 of 17 implemented

Operation	Status	Notes
Namespaces_CheckNameAvailability	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_CreateOrUpdate	Implemented	Local observation: Created a Standard namespace: HTTP 201, with an operation URL to poll before creating queues.
Namespaces_CreateOrUpdateAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_CreateOrUpdateNetworkRuleSet	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_Delete	Implemented	Local observation: Deleted the example's namespace in the page's cleanup.
Namespaces_DeleteAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_Failover	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_Get	Implemented	Local observation: Read the namespace: HTTP 200, and HTTP 404 after it was deleted. A request with the unsupported version `1900-01-01` returned HTTP 400 `InvalidApiVersionParameter`.
Namespaces_GetAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_GetNetworkRuleSet	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_List	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_ListAuthorizationRules	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_ListByResourceGroup	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_ListKeys	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_ListNetworkRuleSets	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_RegenerateKeys	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Namespaces_Update	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

NetworkSecurityPerimeterConfiguration

1 of 1 implemented

Operation	Status	Notes
NetworkSecurityPerimeterConfiguration_List	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

NetworkSecurityPerimeterConfigurations

2 of 2 implemented

Operation	Status	Notes
NetworkSecurityPerimeterConfigurations_GetResourceAssociationName	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
NetworkSecurityPerimeterConfigurations_Reconcile	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

Operations

1 of 1 implemented

Operation	Status	Notes
Operations_List	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

PrivateEndpointConnections

4 of 4 implemented

Operation	Status	Notes
PrivateEndpointConnections_CreateOrUpdate	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
PrivateEndpointConnections_Delete	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
PrivateEndpointConnections_Get	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
PrivateEndpointConnections_List	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

PrivateLinkResources

1 of 1 implemented

Operation	Status	Notes
PrivateLinkResources_Get	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

Queues

10 of 10 implemented

Operation	Status	Notes
Queues_CreateOrUpdate	Implemented	Local observation: Created a queue with `maxDeliveryCount` and `lockDuration`: HTTP 200. Sent before the namespace had finished provisioning, the same request returned HTTP 409.
Queues_CreateOrUpdateAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Queues_Delete	Implemented	Local observation: Deleted the example's queue in the page's cleanup.
Queues_DeleteAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Queues_Get	Implemented	Local observation: Read the queue back with its settings and `status` `Active`: HTTP 200.
Queues_GetAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Queues_ListAuthorizationRules	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Queues_ListByNamespace	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Queues_ListKeys	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Queues_RegenerateKeys	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

Rules

4 of 4 implemented

Operation	Status	Notes
Rules_CreateOrUpdate	Implemented	Source inspection: Validates a rule's SQL filter against a safe local subset of the syntax and rejects anything outside it. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Rules_Delete	Implemented	Source inspection: Validates a rule's SQL filter against a safe local subset of the syntax and rejects anything outside it. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Rules_Get	Implemented	Source inspection: Validates a rule's SQL filter against a safe local subset of the syntax and rejects anything outside it. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Rules_ListBySubscriptions	Implemented	Source inspection: Validates a rule's SQL filter against a safe local subset of the syntax and rejects anything outside it. Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

Subscriptions

4 of 4 implemented

Operation	Status	Notes
Subscriptions_CreateOrUpdate	Implemented	Local observation: Created a subscription to a topic: HTTP 200. Delivery to it wasn't tested.
Subscriptions_Delete	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Subscriptions_Get	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Subscriptions_ListByTopic	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

Topics

10 of 10 implemented

Operation	Status	Notes
Topics_CreateOrUpdate	Implemented	Local observation: Created a topic: HTTP 200. Publishing to it wasn't tested.
Topics_CreateOrUpdateAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_Delete	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_DeleteAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_Get	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_GetAuthorizationRule	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_ListAuthorizationRules	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_ListByNamespace	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_ListKeys	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.
Topics_RegenerateKeys	Implemented	Source inspection: Namespace and entity configuration and local keys; AMQP delivery, replication, capacity and RBAC enforcement aren't established.

Service Bus data 2021-05Plan: Free

0 of 13 implemented · 2 failed in testing

Version 2021-05, from the Azure REST API specifications at commit 21bbf1b.

Entity

0 of 3 implemented · 1 failed in testing

Operation	Status	Notes
Entity_Delete	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.
Entity_Get	Failed in testing	Local observation: Vera 1.2.0-rc.3, 6 November 2026 — with the example's queue in place, reading it at `https://azmsgfinal-bus.servicebus.localhost:8543/jobs?api-version=2021-05` returned HTTP 501 `DataPlaneNotEmulated`: this release doesn't serve Service Bus data calls, and the queue is managed through Resource Manager. Earlier, in Vera 1.2.0 preview, reading the queue at `/jobs` on that host returned HTTP 404 `ResourceNotFound`, "No modeled operation matches this request.", while Resource Manager returned the queue. AMQP wasn't tested.
Entity_Put	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.

Namespace

0 of 1 implemented · 1 failed in testing

Operation	Status	Notes
Namespace_Get	Failed in testing	Local observation: Vera 1.2.0-rc.3, 6 November 2026 — reading `/$namespaceinfo?api-version=2021-05` on the namespace's host, `azmsgfinal-bus.servicebus.localhost:8543`, returned HTTP 501 `DataPlaneNotEmulated`: this release doesn't serve Service Bus data calls, and the namespace is managed through Resource Manager. Earlier, in Vera 1.2.0 preview, reading `/$namespaceinfo` there returned HTTP 404 `ResourceNotFound`, "No modeled operation matches this request." AMQP wasn't tested.

Rule

0 of 3 implemented

Operation	Status	Notes
Rule_Delete	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.
Rule_Get	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.
Rule_Put	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.

Subscription

0 of 3 implemented

Operation	Status	Notes
Subscription_Delete	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.
Subscription_Get	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.
Subscription_Put	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.

servicebus_data

0 of 3 implemented

Operation	Status	Notes
listEntities	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.
listRules	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.
listSubscriptions	Not implemented	Source inspection: This release has no implementation or data-plane host for the legacy Atom/XML entity API, so the operation isn't routed, and a request can fall through to a Resource Manager API-version error or HTTP 404. Queues, topics, subscriptions and rules can be managed through Resource Manager instead.