Skip to content

Commit 394e3df

Browse files
Update notes on network security perimeter limitations
Clarified limitations of network security perimeter regarding Azure Service Bus features.
1 parent a87a1d7 commit 394e3df

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

articles/service-bus-messaging/network-security-perimeter.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,6 @@ Azure Service Bus supports scenarios that require access to other PaaS resources
3434
- **Customer-managed keys (CMK)** require communication with Azure Key Vault. For more information, see [Configure customer-managed keys for encrypting Azure Service Bus data at rest](configure-customer-managed-key.md).
3535

3636
> [!NOTE]
37-
> - Network security perimeter doesn't support [Azure Service Bus Geo-Replication](./service-bus-geo-replication.md).
3837
> - Network security perimeter doesn't support [Azure Service Bus Geo-Disaster Recovery](./service-bus-geo-dr.md).
3938
> - Network security perimeter rules don't govern private link traffic through [private endpoints](../private-link/private-endpoint-overview.md).
4039

0 commit comments

Comments
 (0)