Chrome on Mac

Upload files/com.google.Chrome.mobileconfig to your MDM as a custom configuration profile, scoped to the computers. It sets, for Chrome (com.google.Chrome):

• ExtensionInstallForcelist: bicelplgpeknobhaandbndecidlmeook;https://clients2.google.com/service/update2/crx
• ExtensionSettings: force installed, pinned to the toolbar
• IncognitoModeAvailability: 1 (Incognito off; remove that key if you would rather keep it)

• Jamf Pro: Computers > Configuration Profiles > Upload, choose the file, set the scope.
• Kandji: Library > Add new > Custom Profile, upload the file, assign to a Blueprint.
• Intune: Devices > macOS > Configuration > Create > Templates > Custom, upload the file, deployment channel Device channel.

If your MDM builds Chrome policy from a form rather than a file, add the two extension keys above under the com.google.Chrome preference domain.

The profile's identifiers are fixed values. If your MDM requires a unique PayloadUUID per profile, generate new ones with uuidgen and replace both before uploading.

Check one Mac with verify.md.