Merge pull request #96664 from axisc/patch-5

PRMerger14 · web-flow · commit 9ca4b9765b57 · 2019-11-20T11:34:11.000-08:00
Service Bus/Event Hubs - remove claim that Azure monitor is not supported when VNET/Firewalls are enabled
diff --git a/articles/event-hubs/event-hubs-ip-filtering.md b/articles/event-hubs/event-hubs-ip-filtering.md
@@ -43,7 +43,6 @@ IP filter rules are applied in order, and the first rule that matches the IP add
 > Trusted Microsoft services are not supported when IP Filtering (Firewalls) are implemented, and will be made available soon.
 >
 > Common Azure scenarios that don't work with IP Filtering (note that the list is **NOT** exhaustive) -
-> - Azure Monitor
 > - Azure Stream Analytics
 > - Integration with Azure Event Grid
 > - Azure IoT Hub Routes
diff --git a/articles/event-hubs/event-hubs-service-endpoints.md b/articles/event-hubs/event-hubs-service-endpoints.md
@@ -30,7 +30,6 @@ The result is a private and isolated relationship between the workloads bound to
 > Trusted Microsoft services are not supported when Virtual Networks are implemented.
 >
 > Common Azure scenarios that don't work with Virtual Networks (note that the list is **NOT** exhaustive) -
-> - Azure Monitor
 > - Azure Stream Analytics
 > - Integration with Azure Event Grid
 > - Azure IoT Hub Routes
diff --git a/articles/service-bus-messaging/service-bus-ip-filtering.md b/articles/service-bus-messaging/service-bus-ip-filtering.md
@@ -43,7 +43,6 @@ IP filter rules are applied in order and the first rule that matches the IP addr
 > Trusted Microsoft services are not supported when IP Filtering (Firewall rules) are implemented, and will be made available soon.
 >
 > Common Azure scenarios that don't work with IP Filtering (note that the list is **NOT** exhaustive) -
-> - Azure Monitor
 > - Azure Stream Analytics
 > - Integration with Azure Event Grid
 > - Azure IoT Hub Routes
diff --git a/articles/service-bus-messaging/service-bus-service-endpoints.md b/articles/service-bus-messaging/service-bus-service-endpoints.md
@@ -27,7 +27,6 @@ The result is a private and isolated relationship between the workloads bound to
 > Trusted Microsoft services are not supported when Virtual Networks are implemented.
 >
 > Common Azure scenarios that don't work with Virtual Networks (note that the list is **NOT** exhaustive) -
-> - Azure Monitor
 > - Azure Stream Analytics
 > - Integration with Azure Event Grid
 > - Azure IoT Hub Routes

Original file line number	Diff line number	Diff line change
`@@ -43,7 +43,6 @@ IP filter rules are applied in order, and the first rule that matches the IP add`
`43`	`43`	`> Trusted Microsoft services are not supported when IP Filtering (Firewalls) are implemented, and will be made available soon.`
`44`	`44`	`>`
`45`	`45`	`> Common Azure scenarios that don't work with IP Filtering (note that the list is NOT exhaustive) -`
`46`		`-> - Azure Monitor`
`47`	`46`	`> - Azure Stream Analytics`
`48`	`47`	`> - Integration with Azure Event Grid`
`49`	`48`	`> - Azure IoT Hub Routes`
Original file line number	Diff line number	Diff line change
`@@ -30,7 +30,6 @@ The result is a private and isolated relationship between the workloads bound to`
`30`	`30`	`> Trusted Microsoft services are not supported when Virtual Networks are implemented.`
`31`	`31`	`>`
`32`	`32`	`> Common Azure scenarios that don't work with Virtual Networks (note that the list is NOT exhaustive) -`
`33`		`-> - Azure Monitor`
`34`	`33`	`> - Azure Stream Analytics`
`35`	`34`	`> - Integration with Azure Event Grid`
`36`	`35`	`> - Azure IoT Hub Routes`
Original file line number	Diff line number	Diff line change
`@@ -27,7 +27,6 @@ The result is a private and isolated relationship between the workloads bound to`
`27`	`27`	`> Trusted Microsoft services are not supported when Virtual Networks are implemented.`
`28`	`28`	`>`
`29`	`29`	`> Common Azure scenarios that don't work with Virtual Networks (note that the list is NOT exhaustive) -`
`30`		`-> - Azure Monitor`
`31`	`30`	`> - Azure Stream Analytics`
`32`	`31`	`> - Integration with Azure Event Grid`
`33`	`32`	`> - Azure IoT Hub Routes`