Generally Available: Network Security Perimeter for Azure Service Bus

Network Security Perimeter (NSP) support for Azure Service Bus is now generally available. [Network Security Perimeter](https://learn.microsoft.com/azure/private-link/network-security-perimeter-concepts) creates a logical network boundary around your Service Bus namespaces and other Azure PaaS resources, blocking unauthorized public access by default and enabling secure communication between services within the perimeter. This complements existing Service Bus network security options - IP firewall rules, VNet service endpoints, and [private endpoints](https://learn.microsoft.com/azure/service-bus-messaging/private-link-service)\- by providing centralized, perimeter-level control. Instead of configuring network rules on each resource individually, you create a perimeter and associate your PaaS resources with it. Resources inside the perimeter can communicate freely, while explicit inbound and outbound access rules control any traffic crossing the perimeter boundary. This is especially useful for scenarios like customer-managed key (CMK) encryption, where your Service Bus namespace needs to communicate with Azure Key Vault - both resources can be placed within the same perimeter, securing the communication without additional configuration. Network Security Perimeter provides diagnostic access logs that record every allowed or denied connection attempt, supporting audit and compliance requirements. Learn more: * [Network Security Perimeter for Azure Service Bus documentation](https://learn.microsoft.com/azure/service-bus-messaging/network-security-perimeter). * Read the [blog post](https://techcommunity.microsoft.com/blog/messagingonazureblog/announcing-general-availability-of-network-security-perimeter-for-azure-service-/4508179).