From 7d8440a5ab5d7d2cd5bdcf50f1897c3a1da581e3 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 5 May 2020 17:21:02 -0700 Subject: [PATCH] Added policy timeline --- .../mdm/policy-csp-restrictedgroups.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/windows/client-management/mdm/policy-csp-restrictedgroups.md b/windows/client-management/mdm/policy-csp-restrictedgroups.md index 8053b57d73..8f1b817cf8 100644 --- a/windows/client-management/mdm/policy-csp-restrictedgroups.md +++ b/windows/client-management/mdm/policy-csp-restrictedgroups.md @@ -154,6 +154,19 @@ The member SID can be a user account or a group in AD, Azure AD, or on the local +## Policy timeline + +The behavior of this policy setting differs in different Windows 10 versions. For Windows 10, version 1809 through version 1909, you can use name in `` and SID in ``. For the latest release of Windows 10, you can use name or SID for both the elements as described in this topic. + +The following table provides the timeline of this policy setting and describes its behavior in different Windows 10 versions: + +| Windows 10 version | Policy behavior | +| ------------------ | --------------- | +|Windows 10, version 1803 | Added the RestrictedGroups policy setting in Windows 10, version 1803.
XML accepts group and member only by name.
Supports configuring the administrators group using the group name.
Expects member name to be in the account name format. | +| Windows 10, version 1809
Windows 10, version 1903
Windows 10, version 1909 | Supports configuring any local group.
`` accepts only name.
`` accepts a name or an SID.
This is useful when you want to ensure a certain local group always has a well known SID as member. | +| The latest release of Windows 10 | Behaves as described in this topic.
Accepts name or SID for group and members and translates as appropriate. | + +