Merge pull request #231990 from dominicbetts/central-property-notes

IoT Central: Add more notes about property query deprecation

Author: prmerger-automator[bot]

articles/iot-central/core/howto-query-with-rest-api.md

@@ -29,7 +29,7 @@ Every IoT Central REST API call requires an authorization header. To learn more,
 For the reference documentation for the IoT Central REST API, see [Azure IoT Central REST API reference](/rest/api/iotcentral/).
 
 > [!IMPORTANT]
-> Support for property queries is now deprecated in the IoT Central REST API and will be removed from the existing API releases. 
+> Support for property queries is now deprecated in the IoT Central REST API and will be removed from the existing API releases.
 
 [!INCLUDE [iot-central-postman-collection](../../../includes/iot-central-postman-collection.md)]
 
@@ -102,6 +102,9 @@ The following sections describe these clauses in more detail.
 
 ## SELECT clause
 
+> [!IMPORTANT]
+> Support for property queries is now deprecated in the IoT Central REST API and will be removed from the existing API releases.
+
 The `SELECT` clause lists the data values to include in the query output and can include the following items:
 
 - Telemetry. Use the telemetry names from the device template.
@@ -220,6 +223,9 @@ The time window value uses the [ISO 8601 durations format](https://en.wikipedia.
 
 ### Value comparisons
 
+> [!IMPORTANT]
+> Support for property queries is now deprecated in the IoT Central REST API and will be removed from the existing API releases.
+
 You can get telemetry or property values based on specific values. For example, the following query returns all messages where the temperature is greater than zero, the pressure is greater than 50, and the device ID is one of **sample-002** and **sample-003**:
 
 ```json