Microsoft Configuration Manager
WindowsHow to Remove an Object Association with a Security Scope
In brief
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
What Intune admins need to know
No administrator action is required; this updates the page’s service classification.
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.
How to Remove an Object Association with a Security Scope
Removing a security scope from an object instance is as simple as deleting the Windows Management Instrumentation (WMI)SMS_SecuredCategoryMembership class instance. However, object instances must have at least one security scope associated with them. The last object instance can never be removed. Every object is created with the Default security scope, and if all other security scopes are to be removed from an object instance, the Default should be added to it before removal.
@@ -5,7 +5,7 @@ ms.date: 09/20/2016 ms.subservice: sdk ms.topic: how-to ms.collection: tier3-ms.service: microsoft-endpoint-configuration-manager+ms.service: configuration-manager --- # How to Remove an Object Association with a Security Scope Removing a security scope from an object instance is as simple as deleting the Windows Management Instrumentation (WMI)`SMS_SecuredCategoryMembership` class instance. However, object instances must have at least one security scope associated with them. The last object instance can never be removed. Every object is created with the `Default` security scope, and if all other security scopes are to be removed from an object instance, the `Default` should be added to it before removal.