Merge pull request #232178 from dominicbetts/central-cloud-properties

IoT Central: update description of cloud properties

Author: prmerger-automator[bot]

articles/iot-central/core/concepts-device-templates.md

@@ -23,8 +23,7 @@ A device template includes the following sections:
   - _Root component_. Every device model has a root component. The root component's interface describes capabilities that are specific to the device model.
   - _Components_. A device model may include components in addition to the root component to describe device capabilities. Each component has an interface that describes the component's capabilities. Component interfaces may be reused in other device models. For example, several phone device models could use the same camera interface.
   - _Inherited interfaces_. A device model contains one or more interfaces that extend the capabilities of the root component.
-- _Cloud properties_. This part of the device template lets the solution developer specify any device metadata to store. Cloud properties are never synchronized with devices and only exist in the application. Cloud properties don't affect the code that a device developer writes to implement the device model.
-- _Views_. This part of the device template lets the solution developer define visualizations to view data from the device, and forms to manage and control a device. The views use the device model, cloud properties, and customizations. Views don't affect the code that a device developer writes to implement the device model.
+- _Views_. This part of the device template lets the solution developer define visualizations to view data from the device, and forms to manage and control a device. Views don't affect the code that a device developer writes to implement the device model.
 
 ## Assign a device to a device template
 
@@ -326,6 +325,30 @@ Don't use properties to send telemetry from your device. For example, a readonly
 
 For writable properties, the device application returns a desired state status code, version, and description to indicate whether it received and applied the property value.
 
+### Cloud properties
+
+You can also add cloud properties to the root component of the model. Cloud properties let you specify any device metadata to store in the IoT Central application. Cloud property values are stored in the IoT Central application and are never synchronized with a device. Cloud properties don't affect the code that a device developer writes to implement the device model.
+
+A solution developer can add cloud properties to device views and forms alongside device properties to enable an operator to manage the devices connected to the application. A solution developer can also use cloud properties as part of a rule definition to make a threshold value editable by an operator.
+
+The following DTDL snippet shows an example cloud property definition:
+
+```json
+{
+    "@id": "dtmi:azureiot:Thermostat:CustomerName",
+    "@type": [
+        "Property",
+        "Cloud",
+        "StringValue"
+    ],
+    "displayName": {
+        "en": "Customer Name"
+    },
+    "name": "CustomerName",
+    "schema": "string"
+}
+```
+
 ## Telemetry
 
 IoT Central lets you view telemetry in device views and charts, and use rules to trigger actions when thresholds are reached. IoT Central uses the information in the device model, such as data types, units and display names, to determine how to display telemetry values. You can also display telemetry values on application and personal dashboards.
@@ -347,25 +370,17 @@ Offline commands are one-way notifications to the device from your solution. Off
 > [!NOTE]
 > Offline commands are marked as `durable` if you export the model as DTDL.
 
-## Cloud properties
-
-Cloud properties are part of the device template, but aren't part of the device model. Cloud properties let the solution developer specify any device metadata to store in the IoT Central application. Cloud properties don't affect the code that a device developer writes to implement the device model.
-
-A solution developer can add cloud properties to device views and forms alongside device properties to enable an operator to manage the devices connected to the application. A solution developer can also use cloud properties as part of a rule definition to make a threshold value editable by an operator.
-
 ## Views
 
 A solution developer creates views that let operators monitor and manage connected devices. Views are part of the device template, so a view is associated with a specific device type. A view can include:
 
 - Charts to plot telemetry.
 - Tiles to display read-only device properties.
 - Tiles to let the operator edit writable device properties.
-- Tiles to let the operator edit  cloud properties.
+- Tiles to let the operator edit cloud properties.
 - Tiles to let the operator call commands, including commands that expect a payload.
 - Tiles to display labels, images, or markdown text.
 
-The telemetry, properties, and commands that you can add to a view are determined by the device model, cloud properties, and customizations in the device template.
-
 ## Next steps
 
 Now that you've learned about device templates, a suggested next steps is to read [Telemetry, property, and command payloads](./concepts-telemetry-properties-commands.md) to learn more about the data a device exchanges with IoT Central.

articles/iot-central/core/howto-manage-device-templates-with-rest-api.md

@@ -24,7 +24,7 @@ To learn how to manage device templates by using the IoT Central UI, see [How to
 
 ## Device templates
 
-A device template contains a device model, cloud property definitions, and view definitions. The REST API lets you manage the device model and cloud property definitions. Use the UI to create and manage views.
+A device template contains a device model and view definitions. The REST API lets you manage the device model including cloud property definitions. Use the UI to create and manage views.
 
 The device model section of a device template specifies the capabilities of a device you want to connect to your application. Capabilities include telemetry, properties, and commands. The model is defined using [DTDL V2](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.v2.md).
 

articles/iot-central/government/tutorial-connected-waste-management.md

@@ -137,8 +137,9 @@ Try to customize the following features:
 
 Here's how:
 
-1. From the device template menu, select **Cloud property**.
-1. Select **+ Add Cloud Property**. In Azure IoT Central, you can add a property that is relevant to the device but isn't expected to be sent by a device. For example, a cloud property might be an alerting threshold specific to installation area, asset information, or maintenance information. 
+1. Navigate to the **Connected Waste Bin** device template, and select **+ Add capability**.
+1. Add a new cloud property by selecting **Cloud Property** as **Capability type**.
+    In Azure IoT Central, you can add a property that is relevant to the device but isn't expected to be sent by a device. For example, a cloud property might be an alerting threshold specific to installation area, asset information, or maintenance information.
 1. Select **Save**.
 
 ### Views

articles/iot-central/retail/tutorial-in-store-analytics-create-app.md

@@ -144,17 +144,17 @@ In this section, you add a device template for RuuviTag sensors to your applicat
 
 You can customize the device templates in your application in three ways: 
 
-* Customize the native built-in interfaces in your devices by changing the device capabilities. 
+* Customize the native built-in interfaces in your devices by changing the device capabilities.
 
-   For example, with a temperature sensor, you can change details such as the display name of the temperature interface, the data type, the units of measurement, and the minimum and maximum operating ranges. 
+   For example, with a temperature sensor, you can change details such as the display name of the temperature interface, the data type, the units of measurement, and the minimum and maximum operating ranges.
 
-* Customize your device templates by adding cloud properties. 
+* Customize your device templates by adding cloud properties.
 
    Cloud properties aren't part of the built-in device capabilities. Cloud properties are custom data that your Azure IoT Central application creates, stores, and associates with your devices. Examples of cloud properties could be:
    * A calculated value
    * Metadata, such as a location that you want to associate with a set of devices
 
-* Customize device templates by building custom views. 
+* Customize device templates by building custom views.
 
    Views provide a way for operators to visualize telemetry and metadata for your devices, such as device metrics and health.