Azure Policy built-in definitions for Azure Service Bus Messaging
This page is an index of Azure Policy built-in policy definitions for Azure Service Bus Messaging. For additional Azure Policy built-ins for other services, see Azure Policy built-in definitions.
The name of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Version column to view the source on the Azure Policy GitHub repo.
Azure Service Bus Messaging
|All authorization rules except RootManageSharedAccessKey should be removed from Service Bus namespace||Service Bus clients should not use a namespace level access policy that provides access to all queues and topics in a namespace. To align with the least privilege security model, you should create access policies at the entity level for queues and topics to provide access to only the specific entity||Audit, Deny, Disabled||1.0.1|
|Azure Service Bus namespaces should have local authentication methods disabled||Disabling local authentication methods improves security by ensuring that Azure Service Bus namespaces exclusively require Azure Active Directory identities for authentication. Learn more at: https://aka.ms/disablelocalauth-sb.||Audit, Deny, Disabled||1.0.0|
|Azure Service Bus namespaces should use private link||Azure Private Link lets you connect your virtual network to Azure services without a public IP address at the source or destination. The Private Link platform handles the connectivity between the consumer and services over the Azure backbone network. By mapping private endpoints to Service Bus namespaces, data leakage risks are reduced. Learn more at: https://docs.microsoft.com/azure/service-bus-messaging/private-link-service.||AuditIfNotExists, Disabled||1.0.0|
|Configure Azure Service Bus namespaces to disable local authentication||Disable local authentication methods so that your Azure ServiceBus namespaces exclusively require Azure Active Directory identities for authentication. Learn more at: https://aka.ms/disablelocalauth-sb.||Modify, Disabled||1.0.0|
|Configure Service Bus namespaces with private endpoints||Private endpoints connect your virtual network to Azure services without a public IP address at the source or destination. By mapping private endpoints to Service Bus namespaces, you can reduce data leakage risks. Learn more at: https://docs.microsoft.com/azure/service-bus-messaging/private-link-service.||DeployIfNotExists, Disabled||1.0.0|
|Deploy Diagnostic Settings for Service Bus to Event Hub||Deploys the diagnostic settings for Service Bus to stream to a regional Event Hub when any Service Bus which is missing this diagnostic settings is created or updated.||DeployIfNotExists, Disabled||2.0.0|
|Deploy Diagnostic Settings for Service Bus to Log Analytics workspace||Deploys the diagnostic settings for Service Bus to stream to a regional Log Analytics workspace when any Service Bus which is missing this diagnostic settings is created or updated.||DeployIfNotExists, Disabled||2.0.0|
|Resource logs in Service Bus should be enabled||Audit enabling of resource logs. This enables you to recreate activity trails to use for investigation purposes; when a security incident occurs or when your network is compromised||AuditIfNotExists, Disabled||5.0.0|
|Service Bus Namespaces should disable public network access||Azure Service Bus should have public network access disabled. Disabling public network access improves security by ensuring that the resource isn't exposed on the public internet. You can limit exposure of your resources by creating private endpoints instead. Learn more at: https://docs.microsoft.com/azure/service-bus-messaging/private-link-service||Audit, Deny, Disabled||1.0.0|
|Service Bus namespaces should have double encryption enabled||Enabling double encryption helps protect and safeguard your data to meet your organizational security and compliance commitments. When double encryption has been enabled, data in the storage account is encrypted twice, once at the service level and once at the infrastructure level, using two different encryption algorithms and two different keys.||Audit, Deny, Disabled||1.0.0|
|Service Bus Premium namespaces should use a customer-managed key for encryption||Azure Service Bus supports the option of encrypting data at rest with either Microsoft-managed keys (default) or customer-managed keys. Choosing to encrypt data using customer-managed keys enables you to assign, rotate, disable, and revoke access to the keys that Service Bus will use to encrypt data in your namespace. Note that Service Bus only supports encryption with customer-managed keys for premium namespaces.||Audit, Disabled||1.0.0|
- See the built-ins on the Azure Policy GitHub repo.
- Review the Azure Policy definition structure.
- Review Understanding policy effects.
Submit and view feedback for