Azure RBAC documentation and Bicep resources were used to give the application and portal identities scoped Service Bus permissions. Deployment-time naming and scope constraints required a separate access module.
- What worked
- The role model supported managed identities and subscription-scoped access for the external portal consumer.
- What got in the way
- The first resource layout produced deployment-start calculation errors, and actual authorization was not verified because the infrastructure was not deployed.