You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-create-organizations.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.custom: contperf-fy22q2
14
14
15
15
Organizations let you define a hierarchy that you use to manage which users can see which devices in your IoT Central application. The user's role determines their permissions over the devices they see, and the experiences they can access. Use organizations to implement a multi-tenanted application.
16
16
17
-
Organizations is an optional feature that gives you more control over the [users and roles](howto-manage-users-roles.md) in your application.
17
+
Organizations are an optional feature that gives you more control over the [users and roles](howto-manage-users-roles.md) in your application.
18
18
19
19
Organizations are hierarchical:
20
20
@@ -59,7 +59,7 @@ When you create a new device in your application, assign it to an organization i
59
59
60
60
To assign or reassign an existing device to an organization, select the device in the device list and then select **Organization**:
61
61
62
-
:::image type="content" source="media/howto-create-organization/change-device-organization.png" alt-text="Screenshot that shows how change the organization a device is associated with." lightbox="media/howto-create-organization/change-device-organization.png":::
62
+
:::image type="content" source="media/howto-create-organization/change-device-organization.png" alt-text="Screenshot that shows how to change the organization a device is associated with." lightbox="media/howto-create-organization/change-device-organization.png":::
63
63
64
64
> [!TIP]
65
65
> You can see which organization a device belongs to in the device list. Use the filter tool in the device list to show devices in a particular organization.
@@ -153,10 +153,10 @@ When you start adding organizations, all existing devices, users, and experience
153
153
The following limits apply to organizations:
154
154
155
155
- The hierarchy can be no more than five levels deep.
156
-
- The total number of organization cannot be more than 200. Each node in the hierarchy counts as an organization.
156
+
- The total number of organizations can't be more than 200. Each node in the hierarchy counts as an organization.
157
157
158
158
159
159
## Next steps
160
160
161
-
Now that you've learned how to manage Azure IoT Central organizations, the suggested next step is learn how to [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).
161
+
Now that you've learned how to manage Azure IoT Central organizations, the suggested next step is to learn how to [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).
For Webhook destinations, IoT Central exports data in near real time. The data in the message body is in the same format as for Event Hubs and Service Bus.
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-manage-data-export-with-rest-api.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ The request body has some required fields:
52
52
53
53
*`displayName`: Display name of the destination.
54
54
*`type`: Type of destination object which can be one of: `blobstorage@v1`, `dataexplorer@v1`, `eventhubs@v1`, `servicebusqueue@v1`, `servicebustopic@v1`, `webhook@v1`.
55
-
*`connectionString`:The connection string for accessing the destination resource.
55
+
*`connectionString`:The connection string for accessing the destination resource.
56
56
*`containerName`: For a blob storage destination, the name of the container where data should be written.
57
57
58
58
The response to this request looks like the following example:
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-manage-iot-central-from-cli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Manage IoT Central from Azure CLI or PowerShell | Microsoft Docs
3
-
description: This article describes how to create and manage your IoT Central application using the Azure CLI or PowerShell. You can view, modify, and remove the application using these tools. You can also configure a managed system identity that can you can use to setup secure data export.
3
+
description: This article describes how to create and manage your IoT Central application using the Azure CLI or PowerShell. You can view, modify, and remove the application using these tools. You can also configure a managed system identity that can you can use to set up secure data export.
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-manage-iot-central-from-portal.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ Access to metrics in the Azure portal is managed by [Azure role based access con
124
124
125
125
### IoT Central metrics
126
126
127
-
For a list of of the metrics that are currently available for IoT Central, see [Supported metrics with Azure Monitor](../../azure-monitor/essentials/metrics-supported.md#microsoftiotcentraliotapps).
127
+
For a list of the metrics that are currently available for IoT Central, see [Supported metrics with Azure Monitor](../../azure-monitor/essentials/metrics-supported.md#microsoftiotcentraliotapps).
0 commit comments