Azure Service Bus | Operate As Docs

Connect your client's Azure Service Bus with a sign-in, and call its API through Operate As.

Website: azure.microsoft.com
Connects by: Signing in with Azure Service Bus
Category: Developer tools
Services: 1
Tools: Pass-through only

Service	Key	Base URL
Azure Service Bus	`azure-service-bus`	`https://{namespace}.servicebus.windows.net`

Your client also types their namespace (The part before .servicebus.windows.net in your namespace's address).

Connecting

Your client presses Connect on their link and approves on Azure Service Bus's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "azure-service-bus"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "azure-service-bus"    ]  }]

Permissions

What the client reads	Permission it asks for
Send and receive messages in the Service Bus namespaces you can reach	`https://servicebus.azure.net/user_impersonation`
Stay connected without signing in again	`offline_access`

Pass-through

Azure Service Bus has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.

Add the client

In Clients, add your client and select Azure Service Bus. Then send them their link.

Your client connects

They sign in with Azure Service Bus and approve.

Find the endpoint

Pick the call from Azure Service Bus's own API docs. Your path is everything after https://{namespace}.servicebus.windows.net, with the parts in braces filled in from your client's account.

Send it through Operate As

Use the client's ID, the service key azure-service-bus and that path. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../azure-service-bus/$Resources/Queues" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../azure-service-bus/$Resources/Queues" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Azure Service Bus refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Azure Service Bus access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Azure Service Bus access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "azure-service-bus",
    "services": [
      "azure-service-bus"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "azure-service-bus",    "services": [      "azure-service-bus"    ],    "reconnectUrl": "https://…"  }}