Skip to content

Commit 609d217

Browse files
Merge pull request #233117 from MayankBargali-MSFT/patch-97
(AzureCXP) fixed link
2 parents 9a57eea + 06b6631 commit 609d217

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You can use service tags to define network access controls on [network security
3232
## IP firewall
3333
By default, Service Bus namespaces are accessible from internet as long as the request comes with valid authentication and authorization. With IP firewall, you can restrict it further to only a set of IPv4 addresses or IPv4 address ranges in [CIDR (Classless Inter-Domain Routing)](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation.
3434

35-
This feature is helpful in scenarios in which Azure Service Bus should be only accessible from certain well-known sites. Firewall rules enable you to configure rules to accept traffic originating from specific IPv4 addresses. For example, if you use Service Bus with [Azure Express Route][express-route], you can create a **firewall rule** to allow traffic from only your on-premises infrastructure IP addresses or addresses of a corporate NAT gateway.
35+
This feature is helpful in scenarios in which Azure Service Bus should be only accessible from certain well-known sites. Firewall rules enable you to configure rules to accept traffic originating from specific IPv4 addresses. For example, if you use Service Bus with [Azure Express Route](../expressroute/expressroute-introduction.md), you can create a **firewall rule** to allow traffic from only your on-premises infrastructure IP addresses or addresses of a corporate NAT gateway.
3636

3737
The IP firewall rules are applied at the Service Bus namespace level. Therefore, the rules apply to all connections from clients using any supported protocol. Any connection attempt from an IP address that does not match an allowed IP rule on the Service Bus namespace is rejected as unauthorized. The response does not mention the IP rule. IP filter rules are applied in order, and the first rule that matches the IP address determines the accept or reject action.
3838

@@ -88,4 +88,4 @@ See the following articles:
8888

8989
- [How to configure IP firewall for a Service Bus namespace](service-bus-ip-filtering.md)
9090
- [How to configure virtual network service endpoints for a Service Bus namespace](service-bus-service-endpoints.md)
91-
- [How to configure private endpoints for a Service Bus namespace](private-link-service.md)
91+
- [How to configure private endpoints for a Service Bus namespace](private-link-service.md)

0 commit comments

Comments
 (0)