Microsoft Configuration Manager
GeneralConfiguration Manager SQL View Security
In brief
The documentation replaces `ms.service: microsoft-endpoint-configuration-manager` with `ms.service: configuration-manager`.
What Intune admins need to know
Administrators referencing this documentation should use the updated service identifier.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Configuration Manager SQL View Security
The Configuration Manager object security mechanism, implemented in the SMS Provider, facilitates instance (or row) level security on core object classes. By using the Configuration Manager schema views, an application or user is operating outside of this security mechanism. This doesn't mean that the views can't be secured from unauthorized data access; however, security must be configured separately and is less precise than standard Configuration Manager object security. You can give a user read-only permission to access only the views and deny access to any internal Configuration Manager tables. The main security functionality that is lost in the view approach is the ability to secure specific object instances (such as packages and collections) separately for members of groups.
@@ -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 SQL View Security The Configuration Manager object security mechanism, implemented in the SMS Provider, facilitates instance (or row) level security on core object classes. By using the Configuration Manager schema views, an application or user is operating outside of this security mechanism. This doesn't mean that the views can't be secured from unauthorized data access; however, security must be configured separately and is less precise than standard Configuration Manager object security. You can give a user read-only permission to access only the views and deny access to any internal Configuration Manager tables. The main security functionality that is lost in the view approach is the ability to secure specific object instances (such as packages and collections) separately for members of groups.