Configuration Manager Lazy Properties
In brief
The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `sdk` documentation pairing.
What Intune admins need to know
No administrator action is required; the documentation metadata is updated for this page.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Configuration Manager Lazy Properties
Some Configuration Manager object properties are relatively inefficient to retrieve. If these properties were retrieved for many instances in a class (as might be done in a query), the response would be considerably delayed. Such properties are considered lazy properties and are not usually retrieved during query operations. However, if these properties are retrieved during a query, they have null or zero values, which might not be the actual value of the property for every instance. Therefore, if you want to get the correct value for lazy properties, you must get each instance individually.
@@ -5,7 +5,7 @@ ms.date: 09/20/2016 ms.subservice: sdk ms.topic: article ms.collection: tier3-ms.service: microsoft-endpoint-configuration-manager+ms.service: configuration-manager --- # Configuration Manager Lazy Properties Some Configuration Manager object properties are relatively inefficient to retrieve. If these properties were retrieved for many instances in a class (as might be done in a query), the response would be considerably delayed. Such properties are considered lazy properties and are not usually retrieved during query operations. However, if these properties are retrieved during a query, they have `null` or zero values, which might not be the actual value of the property for every instance. Therefore, if you want to get the correct value for lazy properties, you must get each instance individually.