Skip to content

Commit e58377f

Browse files
committed
Draft, in progress
1 parent f424997 commit e58377f

File tree

4 files changed

+18
-24
lines changed

4 files changed

+18
-24
lines changed

articles/iot-dps/quick-create-simulated-device-symm-key.md

Lines changed: 8 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Quickstart - Provision a simulated symmetric key device to Microsoft Azur
33
description: Learn how to provision a device that authenticates with a symmetric key in the Azure IoT Hub Device Provisioning Service (DPS)
44
author: kgremban
55
ms.author: kgremban
6-
ms.date: 09/29/2021
6+
ms.date: 04/06/2023
77
ms.topic: quickstart
88
ms.service: iot-dps
99
services: iot-dps
@@ -444,18 +444,13 @@ To update and run the provisioning sample with your device information:
444444
7. You should now see something similar to the following output. A "Hello World" string is sent to the hub as a test message.
445445
446446
```output
447-
D:\azure-iot-samples-csharp\provisioning\Samples\device\SymmetricKeySample>dotnet run --s 0ne00000A0A --i symm-key-csharp-device-01 --p sbDDeEzRuEuGKag+kQKV+T1QGakRtHpsERLP0yPjwR93TrpEgEh/Y07CXstfha6dhIPWvdD1nRxK5T0KGKA+nQ==
448-
449-
Initializing the device provisioning client...
450-
Initialized for registration Id symm-key-csharp-device-01.
451-
Registering with the device provisioning service...
452-
Registration status: Assigned.
453-
Device csharp-device-01 registered to ExampleIoTHub.azure-devices.net.
454-
Creating symmetric key authentication for IoT Hub...
455-
Testing the provisioned device with IoT Hub...
456-
Sending a telemetry message...
457-
Finished.
458-
Enter any key to exit.
447+
D:\azure-iot-samples-csharp\provisioning\device\samples>node register_symkey.js
448+
registration succeeded
449+
assigned hub=ExampleIoTHub.azure-devices.net
450+
deviceId=nodejs-device-01
451+
payload=undefined
452+
Client connected
453+
send status: MessageEnqueued
459454
```
460455
461456
::: zone-end

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Quickstart - Provision an X.509 certificate simulated device to Microsoft
33
description: Learn how to provision a simulated device that authenticates with an X.509 certificate in the Azure IoT Hub Device Provisioning Service
44
author: kgremban
55
ms.author: kgremban
6-
ms.date: 11/01/2022
6+
ms.date: 04/06/2023
77
ms.topic: quickstart
88
ms.service: iot-dps
99
services: iot-dps

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ az group create --name my-sample-resource-group --location westus
4141

4242
Create an IoT hub with the [az iot hub create](/cli/azure/iot/hub#az-iot-hub-create) command.
4343

44-
The following example creates an IoT hub named *my-sample-hub* in the *westus* location. An IoT hub name must be globally unique in Azure, so you may want to add a unique prefix or suffix to the example name, or choose a new name altogether. Make sure your name follows proper naming conventions for an IoT hub: it should be 3-50 characters in length, and can contain only upper or lower case alphanumeric characters or hyphens ('-').
44+
The following example creates an IoT hub named *my-sample-hub* in the *westus* location. An IoT hub name must be globally unique in Azure, so either add a unique prefix or suffix to the example name or choose a new name altogether. Make sure your name follows proper naming conventions for an IoT hub: it should be 3-50 characters in length, and can contain only upper or lower case alphanumeric characters or hyphens ('-').
4545

4646
```azurecli-interactive
4747
az iot hub create --name my-sample-hub --resource-group my-sample-resource-group --location westus

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

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Quickstart - Create an Azure IoT Hub Device Provisioning Service (DPS) us
33
description: Azure quickstart - Learn how to create an Azure IoT Hub Device Provisioning Service (DPS) using Azure Resource Manager template (ARM template).
44
author: kgremban
55
ms.author: kgremban
6-
ms.date: 01/27/2021
6+
ms.date: 04/06/2023
77
ms.topic: quickstart
88
ms.service: iot-dps
99
services: iot-dps
@@ -37,8 +37,8 @@ The template used in this quickstart is from [Azure Quickstart Templates](https:
3737

3838
Two Azure resources are defined in the template above:
3939

40-
* [**Microsoft.Devices/iothubs**](/azure/templates/microsoft.devices/iothubs): Creates a new Azure IoT Hub.
41-
* [**Microsoft.Devices/provisioningservices**](/azure/templates/microsoft.devices/provisioningservices): Creates a new Azure IoT Hub Device Provisioning Service with the new IoT Hub already linked to it.
40+
* [**Microsoft.Devices/IotHubs**](/azure/templates/microsoft.devices/iothubs): Creates a new Azure IoT hub.
41+
* [**Microsoft.Devices/provisioningServices**](/azure/templates/microsoft.devices/provisioningservices): Creates a new Azure IoT Hub Device Provisioning Service with the new IoT hub already linked to it.
4242

4343
## Deploy the template
4444

@@ -95,10 +95,10 @@ Sign in to your Azure account and select your subscription.
9595
az account set --subscription {your subscription name or id}
9696
```
9797
98-
3. Copy and paste the following commands into your CLI prompt. Then execute the commands by pressing **ENTER**.
98+
3. Copy and paste the following commands into your CLI prompt. Then execute the commands by selecting the Enter key.
9999
100100
> [!TIP]
101-
> The commands will prompt for a resource group location.
101+
> The commands prompt for a resource group location.
102102
> You can view a list of available locations by first running the command:
103103
>
104104
> `az account list-locations -o table`
@@ -116,16 +116,16 @@ Sign in to your Azure account and select your subscription.
116116
read
117117
```
118118
119-
4. The commands will prompt you for the following information. Provide each value and press **ENTER**.
119+
4. The commands prompt you for the following information. Provide each value and select the Enter key.
120120
121121
| Parameter | Description |
122122
| :-------- | :---------- |
123-
| **Project name** | The value of this parameter will be used to create a resource group to hold all resources. The string `rg` will be added to the end of the value for your resource group name. |
123+
| **Project name** | The value of this parameter is used to create a resource group to hold all resources. The string `rg` is added to the end of the value for your resource group name. |
124124
| **location** | This value is the region where all resources will reside. |
125125
| **iotHubName** | Enter a name for the IoT Hub that must be globally unique within the *.azure-devices.net* namespace. You need the hub name in the next section when you validate the deployment. |
126126
| **provisioningServiceName** | Enter a name for the new Device Provisioning Service (DPS) resource. The name must be globally unique within the *.azure-devices-provisioning.net* namespace. You need the DPS name in the next section when you validate the deployment. |
127127
128-
The AzureCLI is used to deploy the template. In addition to the Azure CLI, you can also use the Azure PowerShell, Azure portal, and REST API. To learn other deployment methods, see [Deploy templates](../azure-resource-manager/templates/deploy-powershell.md).
128+
The Azure CLI is used to deploy the template. In addition to the Azure CLI, you can also use the Azure PowerShell, Azure portal, and REST API. To learn other deployment methods, see [Deploy templates](../azure-resource-manager/templates/deploy-powershell.md).
129129
130130
131131
## Review deployed resources
@@ -144,7 +144,6 @@ Sign in to your Azure account and select your subscription.
144144
145145
Notice the hubs that are linked on the `iotHubs` member.
146146
147-
148147
## Clean up resources
149148
150149
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 the Azure portal or Azure CLI to delete the resource group and all of its resources.

0 commit comments

Comments
 (0)