Merge pull request #226438 from kgremban/feb6-dpsfaq

Reorganize FAQs

Author: Stacyrch140

articles/iot-dps/dps-faq.yml

@@ -4,26 +4,22 @@ metadata:
   description: Find answer to common questions about Azure IoT Hub Device Provisioning Service.
   author: kgremban
   ms.author: kgremban
-  ms.date: 01/24/2023
+  ms.date: 02/06/2023
   ms.topic: faq
   ms.service: iot-dps
   services: iot-dps
 title: Azure IoT Hub Device Provisioning Service frequently asked questions (FAQ)
 summary: |
   This article answers to common questions about Azure IoT Hub Device Provisioning Service. The following topics are covered:
   
-  * DPS Management
-  * DPS Billing
-
+  * [Devices and provisioning](#devices-and-provisioning)
+  * [Management and monitoring](#management-and-monitoring)
+  * [Billing](#billing)
   
 
 sections:
-  - name: Device Provisioning Service management
+  - name: Devices and provisioning
     questions:
-      - question: |
-         What is the recommended way to update a linked hub when the primary key for the IoT Hub access policy is regenerated? 
-        answer: |
-         The primary key is embedded inside the connection string that DPS uses for authentication. Whenever the primary connection string is modified, the primary key will also be modified, and you'll need to relink the hub to your DPS.
       - question: |
          How can I disable or remove a single device within an enrollment group without affecting any other devices? 
         answer: |
@@ -32,6 +28,21 @@ sections:
          Does DPS support provisioning a parent/child topology of IoT Edge gateways and devices?
         answer: |
          No.
+      - question: |
+         Can multiple DPS instances provision devices to the same IoT hub? 
+        answer: |
+         Yes; however, built-in allocation policies apply to each DPS instance individually, so load balancing across multiple IoT hubs is not possible when using the built-in DPS policies. Instead, you can use a custom allocation policy to implement load balancing when using multiple DPS instances. To learn more about custom allocation policies, see [Understand custom allocation policies](concepts-custom-allocation.md).
+      - question: |
+         Why can't I manage enrollments in the Azure portal?
+        answer: |
+         If you created a private endpoint for DPS and disabled public network access, that removes the ability to manage enrollments in the Azure portal. You can still use the Azure CLI, PowerShell, or service APIs from machines that have access to the private endpoint. For more information, see [DPS support for virtual networks](virtual-network-support.md).
+
+  - name: Management and monitoring
+    questions:
+      - question: |
+         What is the recommended way to update a linked hub when the primary key for the IoT Hub access policy is regenerated? 
+        answer: |
+         The primary key is embedded inside the connection string that DPS uses for authentication. Whenever the primary connection string is modified, the primary key will also be modified, and you'll need to relink the hub to your DPS.
       - question: |
          Can I use a WHERE clause to filter results when querying individual enrollments or enrollment groups? 
         answer: |
@@ -44,10 +55,6 @@ sections:
          How can I recover from an accidental deletion of a DPS instance?
         answer: |
          There's no recovery mechanism. Open a support ticket and we can create a new DPS instance with the same scope ID. The provisioning data will be lost but at least with the same scope ID, devices will be able to reconnect once the enrollments are rebuilt.
-      - question: |
-         Can multiple DPS instances provision devices to the same IoT hub? 
-        answer: |
-         Yes; however, built-in allocation policies apply to each DPS instance individually, so load balancing across multiple IoT hubs is not possible when using the built-in DPS policies. Instead, you can use a custom allocation policy to implement load balancing when using multiple DPS instances. To learn more about custom allocation policies, see [Understand custom allocation policies](concepts-custom-allocation.md).
       - question: |
          How can I get an authorization token to use for REST service operations? 
         answer: |
@@ -57,7 +64,7 @@ sections:
         answer: |
          Device Provisioning Service doesn't store or process customer data outside of the geography where you deploy the service instance. For more information, see [Data residency considerations](about-iot-dps.md#data-residency-consideration).
          
-  - name: Device Provisioning Service billing
+  - name: Billing
     questions:
       - question: |
          Which Device Provisioning Service API operations are billable and what are their prices?”