This policy setting allows a process to create an access token, which may provide elevated rights to access sensitive data. The recommended state for this setting is: No One. Note: This user right is considered a 'sensitive privilege' for the purposes of auditing. Rationale: A user account that is given this user right has complete control over the system and can lead to the system being compromised. It is highly recommended that you do not assign any user accounts this right. The operating system examines a user's access token to determine the level of the user's privileges. Access tokens are built when users log on to the local computer or connect to a remote computer over a network. When you revoke a privilege, the change is immediately recorded, but the change is not reflected in the user's access token until the next time the user logs on or connects. Users with the ability to create or modify tokens can change the level of access for any currently logged on account. They could escalate their own privileges or create a DoS condition. Impact: None - this is the default behavior.
To establish the recommended configuration, set the following Device Configuration Policy to No one: To access the Device Configuration Policy from the Intune Home page: Click Devices Click Configuration profiles Click Create profile Select the platform (Windows 10 and later) Select the profile (Custom) Click Create Enter a Name Click Next Configure the following Setting Name: <Enter name> Description: <Enter Description> OMA-URI: ./Device/Vendor/MSFT/Policy/Config/UserRights/CreateToken Data type: String Value: No one Note: When there is more than one value that needs to be entered (ex: Guests, Administrator), the XML value of will need to be converted to US-ASCII to separate the values in the Value field of the Custom Device Configuration Policy. This value should convert to a square with a question mark in it (). Please note that when copied from the converter to Intune a square will appear, but the value will still work. Also note that this value cannot be copied from sources like Microsoft Word. We recommend that the value be copied and used directly from the converter. Select OK Continue through the Wizard to complete the creation of the profile (profile assignments, applicability etc.) Note #2: More than one configuration setting from each of the Configuration profiles (ex: Administrative Templates, Custom etc.) can be added to each Device Configuration Policy. Note #3: The following link is an alternative way to set the 'User Rights Assignment' section. Policy CSP - UserRights - Windows Client Management | Microsoft Docs Default Value: No one.