| author | ms.service | ms.topic | ms.date | ms.author |
|---|---|---|---|---|
mattchenderson |
azure-functions |
include |
01/25/2022 |
mahender |
You'll need to create a role assignment that provides access to your topics and queues at runtime. Management roles like Owner aren't sufficient. The following table shows built-in roles that are recommended when using the Service Bus extension in normal operation. Your application may require additional permissions based on the code you write.
| Binding type | Example built-in roles |
|---|---|
| Trigger1 | Azure Service Bus Data Receiver, Azure Service Bus Data Owner |
| Output binding | Azure Service Bus Data Sender |
1 For triggering from Service Bus topics, the role assignment needs to have effective scope over the Service Bus subscription resource. If only the topic is included, an error will occur. Some clients, such as the Azure portal, don't expose the Service Bus subscription resource as a scope for role assignment. In such cases, the Azure CLI may be used instead. To learn more, see Azure built-in roles for Azure Service Bus.