Merge pull request #178930 from anastasia-ms/ipconfig

Update IPConfig with portal limitations

Author: PRMerger15

articles/iot-dps/iot-dps-ip-filtering.md

@@ -1,12 +1,12 @@
 ---
-title: Azure IoT DPS IP connection filters | Microsoft Docs
-description: How to use IP filtering to block connections from specific IP addresses to your Azure IoT DPS instance. You can block connections from individual or ranges of IP addresses.
-author: wesmc7777
-ms.author: wesmc
+title: Microsoft Azure IoT DPS IP connection filters
+description: How to use IP filtering to block connections from specific IP addresses to your Azure IoT DPS instance. 
+author: anastasia-ms
+ms.author: v-stharr
 ms.service: iot-dps
 services: iot-dps
 ms.topic: conceptual
-ms.date: 12/14/2020
+ms.date: 11/05/2021
 ---
 
 # Use Azure IoT DPS IP connection filters
@@ -21,6 +21,9 @@ There are two specific use-cases where it is useful to block connections to a DP
 
 * You need to reject traffic from IP addresses that have been identified as suspicious by the DPS administrator.
 
+>[!Note]
+>If IP filtering is enabled, you'll no longer be able use the Azure portal to perform service operations (i.e. managing enrollments). To perform service operations using the portal, you'll have to temporarily deactivate IP filtering, complete your work, and then re-enable the IP filtering feature. If you want to use your own clients and avoid the deactivation of the IP filter, you can choose to add your machine's IP address to the `ipFilterRules` and manage the enrollments in the DPS through CLI.
+
 ## How filter rules are applied
 
 The IP filter rules are applied at the DPS instance level. Therefore the IP filter rules apply to all connections from devices and back-end apps using any supported protocol.