Azure Service Bus in Python: fully qualified namespace plus data role

TL;DR

For just looking, use the receiver in PEEK\LOCK mode carefully or peekmessages(). - Sessions. If the queue has sessions enabled, getqueuereceiver(..., session_id="[id]")` is required; without it every receive errors.

Steps

1. ```python

from azure.identity import DefaultAzureCredential from azure.servicebus import ServiceBusClient, ServiceBusMessage

credential [your value] client = ServiceBusClient( fullyqualifiednamespace="YOUR-NAMESPACE.servicebus.windows.net", credential [your value] ) sender = client.getqueuesender(queuename="[queue]") with sender, client: sender.sendmessages(ServiceBusMessage("hello"))

2. - **Wrong role, again.** The data role is "Azure Service Bus Data Owner" (or Receiver/Sender for narrower scope). Namespace Contributor lets you manage the namespace but not send a single message.
- **fully_qualified_namespace, not the connection string.** The param wants `[namespace].servicebus.windows.net` with no scheme, no keys. Passing a connection string here is the most common TypeError-adjacent mistake.
- **Sender/receiver lifecycle.** Senders and receivers hold AMQP links. Create them per unit of work or keep one long-lived; do not create one per message in a loop.
- **Peek vs receive.** `receive_messages()` locks the message; you must `complete_message()` or it reappears after the lock timeout. For just looking, use the receiver in PEEK_LOCK mode carefully or `peek_messages()`.
- **Sessions.** If the queue has sessions enabled, `get_queue_receiver(..., session_id="[id]")` is required; without it every receive errors.

3. Verify: send one message, receive it with a short max_wait_time, complete it, then confirm the queue's active message count is back to baseline in the portal.

## When to use

You are seeing this: The data role is "Azure Service Bus Data Owner" (or Receiver/Sender for narrower scope). Use this skill when you run into "Azure Service Bus in Python: fully qualified namespace plus data role".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Proactive skill. Client pattern and data-role requirement verified against current docs. Evidence: https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-python-how-to-use-queues