Merge pull request #220676 from kgremban/dec6-dpsnextsteps

Update qs/tutorial next steps and toc

Author: v-shils

articles/iot-dps/how-to-legacy-device-symm-key.md

@@ -21,7 +21,7 @@ If you can easily install a [hardware security module (HSM)](concepts-service.md
 
 This tutorial also assumes that the device update takes place in a secure environment to prevent unauthorized access to the master group key or the derived device key.
 
-This tutorial is oriented toward a Windows-based workstation. However, you can perform the procedures on Linux. For a Linux example, see [Tutorial: Provision for geolatency](how-to-provision-multitenant.md).
+This tutorial is oriented toward a Windows-based workstation. However, you can perform the procedures on Linux. For a Linux example, see [Tutorial: Provision for geo latency](how-to-provision-multitenant.md).
 
 >[!NOTE]
 > If you've previously completed [Quickstart: Provision a simulated symmetric key device](quick-create-simulated-device-symm-key.md) and still have your Azure resources and development environment set up, you can proceed to [Create a symmetric key enrollment group](#create-a-symmetric-key-enrollment-group) in this tutorial.
@@ -211,7 +211,7 @@ In this section, you'll prepare a development environment that's used to build t
 
      :::image type="content" source="./media/how-to-legacy-device-symm-key/add-symmetric-key-enrollment-group.png" alt-text="Screenshot that shows adding a symmetric key enrollment group to DPS.":::
 
-1. Select **Save**. When you save the enrollment, IoT Hub generates the **Primary Key** and **Secondary Key** and adds them to the enrollment entry. Your symmetric key enrollment group appears as **mylegacydevices** under the *Group Name* column in the *Enrollment Groups* tab.
+1. Select **Save**. When you save the enrollment, IoT Hub generates a **Primary Key** and **Secondary Key**, then adds them to the enrollment entry. Your symmetric key enrollment group appears as **mylegacydevices** under the *Group Name* column in the *Enrollment Groups* tab.
 
 1. Open the enrollment and copy the value of the **Primary Key**. This key is your master group key.
 
@@ -846,12 +846,7 @@ If you plan to continue working on and exploring the device client sample, don't
 
 ## Next steps
 
-* To learn more about Reprovisioning, see
+In this tutorial, you provisioned multiple devices to your IoT hub using an enrollment group. Next, learn how to provision IoT devices across multiple hubs.
 
-    > [!div class="nextstepaction"]
-    > [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md)
-
-* To learn more about Deprovisioning, see
-
-    > [!div class="nextstepaction"]
-    > [How to deprovision devices that were previously auto-provisioned](how-to-unprovision-devices.md)
+> [!div class="nextstepaction"]
+> [Use custom allocation policies](tutorial-custom-allocation-policies.md)

articles/iot-dps/how-to-provision-multitenant.md

@@ -1,5 +1,5 @@
 ---
-title: Tutorial - Provision devices for geolatency in Azure IoT Hub Device Provisioning Service
+title: Tutorial - Provision devices for geo latency in Azure IoT Hub Device Provisioning Service
 description: This tutorial shows how to provision devices for geolocation/geolatency with your Device Provisioning Service (DPS) instance
 author: kgremban
 ms.author: kgremban
@@ -9,11 +9,11 @@ ms.service: iot-dps
 services: iot-dps
 ---
 
-# Tutorial: Provision for geolatency
+# Tutorial: Provision for geo latency
 
-This tutorial shows how to securely provision multiple simulated symmetric key devices to a group of IoT Hubs using an [allocation policy](concepts-service.md#allocation-policy). IoT Hub Device Provisioning Service (DPS) supports a variety of allocation scenarios through its built-in allocation policies and its support for custom allocation policies.
+This tutorial shows how to securely provision multiple simulated symmetric key devices to a group of IoT Hubs using an [allocation policy](concepts-service.md#allocation-policy). IoT Hub Device Provisioning Service (DPS) supports various allocation scenarios through its built-in allocation policies and its support for custom allocation policies.
 
-Provisioning for **Geolocation/ GeoLatency** is a common allocation scenario. As a device moves between locations, network latency is improved by having the device provisioned to the IoT hub that's closest to each location. In this scenario, a group of IoT hubs, which span across regions, are selected for enrollments. The built-in **Lowest latency** allocation policy is selected for these enrollments. This policy causes the Device Provisioning Service to evaluate device latency and determine the closet IoT hub out of the group of IoT hubs.
+Provisioning for *Geolocation/Geo latency* is a common allocation scenario. As a device moves between locations, network latency is improved by having the device provisioned to the IoT hub that's closest to each location. In this scenario, a group of IoT hubs, which span across regions, are selected for enrollments. The built-in **Lowest latency** allocation policy is selected for these enrollments. This policy causes the Device Provisioning Service to evaluate device latency and determine the closet IoT hub out of the group of IoT hubs.
 
 This tutorial uses a simulated device sample from the [Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c) to demonstrate how to provision devices across regions. You'll perform the following steps in this tutorial:
 
@@ -64,9 +64,9 @@ In this section, you'll create an Azure resource group, and two new regional IoT
 
     This command may take a few minutes to complete.
 
-## Create an enrollment for geolatency
+## Create an enrollment for geo latency
 
-In this section, you'll create a new enrollment group for the your devices.  
+In this section, you'll create a new enrollment group for your devices.  
 
 For simplicity, this tutorial uses [Symmetric key attestation](concepts-symmetric-key-attestation.md) with the enrollment. For a more secure solution, consider using [X.509 certificate attestation](concepts-x509-attestation.md) with a chain of trust.
 
@@ -252,7 +252,7 @@ For each VM:
 
 When using symmetric key attestation with group enrollments, you don't use the enrollment group keys directly. Instead, you derive a unique key from the enrollment group key for each device. For more information, see [Group Enrollments with symmetric keys](concepts-symmetric-key-attestation.md#group-enrollments).
 
-In this part of the tutorial, you'll generate a device key from the you group master key to compute an [HMAC-SHA256](https://wikipedia.org/wiki/HMAC) of the unique registration ID for the device. The result will then be converted into Base64 format.
+In this part of the tutorial, you'll generate a device key from the group master key to compute an [HMAC-SHA256](https://wikipedia.org/wiki/HMAC) of the unique registration ID for the device. The result will then be converted into Base64 format.
 
 >[!IMPORTANT]
 >Don't include your group master key in your device code.
@@ -317,7 +317,7 @@ The sample code simulates a device boot sequence that sends the provisioning req
     //prov_dev_set_symmetric_key_info("<symm_registration_id>", "<symmetric_Key>");
     ```
 
-    Uncomment the function calls, and replace the placeholder values (including the angle brackets) with the unique registration IDs and derived device keys for each device that you derived in the previous section. The keys shown below are for example purposes only. Use the keys you generated earlier.
+    Uncomment the function calls, and replace the placeholder values (including the angle brackets) with the unique registration IDs and derived device keys for each device that you derived in the previous section. The keys shown below are examples. Use the keys you generated earlier.
 
     East US:
     ```c
@@ -403,11 +403,7 @@ To delete the resource group by name:
 
 ## Next steps
 
-* To learn more about reprovisioning, see:
+To learn more about custom allocation policies, see
 
 > [!div class="nextstepaction"]
-> [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md)
-
-* To learn more about deprovisioning, see
-> [!div class="nextstepaction"]
-> [How to deprovision devices that were previously auto-provisioned](how-to-unprovision-devices.md)
+> [Understand custom allocation policies](concepts-custom-allocation.md)

articles/iot-dps/quick-create-simulated-device-tpm.md

@@ -157,7 +157,7 @@ In this section, you'll prepare a development environment used to build the [Azu
 
 ## Build and run the TPM device simulator
 
-In this section, you'll build and run the TPM simulator. This simulator listens over a socket on ports 2321 and 2322. Do not close the command window. You'll need to keep this simulator running until the end of this quickstart.
+In this section, you'll build and run the TPM simulator. This simulator listens over a socket on ports 2321 and 2322. Don't close the command window. You'll need to keep this simulator running until the end of this quickstart.
 
 ::: zone-end
 
@@ -299,7 +299,7 @@ In this section, you'll build and run the TPM simulator. This simulator listens
 
 1. Run the [TPM](/windows/device-security/tpm/trusted-platform-module-overview) simulator to be the [HSM](https://azure.microsoft.com/blog/azure-iot-supports-new-security-hardware-to-strengthen-iot-security/) for the simulated device.
 
-2. Select  **Allow Access**. The simulator listens over a socket on ports 2321 and 2322. Do not close this command window; you will need to keep this simulator running until the end of this quickstart guide.
+2. Select  **Allow Access**. The simulator listens over a socket on ports 2321 and 2322. Don't close this command window; you need to keep this simulator running until the end of this quickstart guide.
 
     ```cmd/sh
     .\azure-iot-sdk-java\provisioning\provisioning-tools\tpm-simulator\Simulator.exe
@@ -449,7 +449,7 @@ In this section, you'll build and execute a sample that reads the endorsement ke
 
    * Select **TPM** as the identity attestation *Mechanism*.
    * Enter the *Endorsement key* you retrieved earlier from your HSM.
-   * Enter a unique *Registration ID* for your device. You will also use this registration ID when registering your device, so make a note of it for later.
+   * Enter a unique *Registration ID* for your device. You'll also use this registration ID when registering your device, so make a note of it for later.
    * Select an IoT hub linked with your provisioning service.
    * Optionally, you may provide the following information:
        * Enter a unique *Device ID* (you can use the suggested **test-docs-device** or provide your own). Make sure to avoid sensitive data while naming your device. If you choose not to provide one, the registration ID will be used to identify the device instead.
@@ -481,7 +481,7 @@ In this section, you'll configure sample code to use the [Advanced Message Queui
 
 4. Near the top of the file, find the `#define` statements for each device protocol as shown below. Make sure only `SAMPLE_AMQP` is uncommented.
 
-    Currently, the [MQTT protocol is not supported for TPM Individual Enrollment](https://github.com/Azure/azure-iot-sdk-c#provisioning-client-sdk).
+    Currently, the [MQTT protocol isn't supported for TPM Individual Enrollment](https://github.com/Azure/azure-iot-sdk-c#provisioning-client-sdk).
 
     ```c
     //
@@ -544,7 +544,7 @@ In this section, you'll configure sample code to use the [Advanced Message Queui
     cd '.\azure-iot-sdk-csharp\provisioning\device\samples\How To\TpmSample\'
    ```
 
-4. Run the following command to register your device. Replace `<IdScope>` with the value for the DPS you just copied and `<RegistrationId>` with the value you used when creating the device enrollment.
+4. Run the following command to register your device. Replace `<IdScope>` with the value for the DPS you copied and `<RegistrationId>` with the value you used when creating the device enrollment.
 
     ```cmd
     dotnet run -- -s <IdScope> -r <RegistrationId>
@@ -749,7 +749,7 @@ If you plan to continue working on and exploring the device client sample, don't
 
 ## Next steps
 
-In this quickstart, you've created a TPM simulated device on your machine and provisioned it to your IoT hub using the IoT Hub Device Provisioning Service. To learn how to enroll your TPM device programmatically, continue to the quickstart for programmatic enrollment of a TPM device.
+In this quickstart, you've created a TPM simulated device on your machine and provisioned it to your IoT hub using the IoT Hub Device Provisioning Service. Next, learn how to enroll your TPM device programmatically.
 
 ::: zone-end
 ::: zone pivot="programming-language-ansi-c, programming-language-csharp"

articles/iot-dps/quick-setup-auto-provision-bicep.md

@@ -47,7 +47,7 @@ Save a copy of the Bicep file locally as **main.bicep**.
 
 Sign in to your Azure account and select your subscription.
 
-1. To log in Azure at the command prompt:
+1. Sign in to Azure at the command prompt:
 
     # [CLI](#tab/CLI)
 
@@ -167,9 +167,9 @@ Sign in to your Azure account and select your subscription.
 
 ## Clean up resources
 
-Other quickstarts in this collection build upon this quickstart. If you plan to continue on to work with subsequent quickstarts or with the tutorials, do not clean up the resources created in this quickstart. If you do not plan to continue, you can use the Azure PowerShell or Azure CLI to delete the resource group and all of its resources.
+Other quickstarts in this collection build upon this quickstart. If you plan to continue on to work with subsequent quickstarts or with the tutorials, don't clean up the resources created in this quickstart. If you don't plan to continue, you can use Azure PowerShell or Azure CLI to delete the resource group and all of its resources.
 
-To delete a resource group and all its resources from the Azure portal, just open the resource group and click **Delete resource group** and the top.
+To delete a resource group and all its resources from the Azure portal, just open the resource group and select **Delete resource group** and the top.
 
 To delete the resource group deployed:
 
@@ -186,11 +186,11 @@ Remove-AzResourceGroup -name exampleRG
 ```
 
 ---
-You can also delete resource groups and individual resources using the Azure portal, PowerShell, or REST APIs, as well as with supported platform SDKs published for Azure Resource Manager or IoT Hub Device Provisioning Service.
+You can also delete resource groups and individual resources using the Azure portal, PowerShell, or REST APIs, or with supported platform SDKs.
 
 ## Next steps
 
-In this quickstart, you've deployed an IoT hub and a Device Provisioning Service instance, and linked the two resources. To learn how to use this setup to provision a device, continue to the quickstart for creating a device.
+In this quickstart, you deployed an IoT hub and a Device Provisioning Service instance, and linked the two resources. To learn how to use this setup to provision a device, continue to the quickstart for creating a device.
 
 > [!div class="nextstepaction"]
 > [Quickstart: Provision a simulated symmetric key device](./quick-create-simulated-device-symm-key.md)