Deploying the SysAid Browser Extension in Chrome via Microsoft Intune (macOS)

Use this guide to deploy the SysAid Browser Extension to Chrome on managed macOS devices using Microsoft Intune.

This deployment method uses the Intune Custom configuration profile template to upload and deploy the SysAid configuration profile, so IT admins can centrally apply the required Chrome extension settings.

Before you start

In SysAid

You’ll need your SysAid Browser Extension ID and Token.

To find them:

1. In SysAid, go to License Manager > Applications Discovery.

2. Click Manage Connections in the top right corner.

3. Under Browser Extension, click Setup to see the ID and Token.

Build the profile

Before uploading the configuration profile to Microsoft Intune, create the SysAid .mobileconfig file using the following instructions:

1. All five macOS MDM docs upload the same .mobileconfig. It has two payloads plus the wrapper: three UUIDs (uuidgen && uuidgen && uuidgen). Make sure to replace YOUR_EXTENSION_ID and YOUR_TOKEN_VALUE:

   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0"><dict>
     <key>PayloadContent</key>
     <array>
       <!-- Payload 1: force-install -->
       <dict>
         <key>PayloadType</key><string>com.google.Chrome</string>
         <key>PayloadUUID</key><string>UUID-ONE</string>
         <key>PayloadIdentifier</key><string>com.sysaid.chrome.forceinstall</string>
         <key>PayloadVersion</key><integer>1</integer>
         <key>ExtensionInstallForcelist</key>
         <array><string>YOUR_EXTENSION_ID;https://clients2.google.com/service/update2/crx</string></array>
         <key>ExtensionSettings</key>
         <dict><key>YOUR_EXTENSION_ID</key><dict>
           <key>installation_mode</key><string>force_installed</string>
           <key>update_url</key><string>https://clients2.google.com/service/update2/crx</string>
         </dict></dict>
       </dict>
       <!-- Payload 2: token delivery -->
       <dict>
         <key>PayloadType</key><string>com.google.Chrome.extensions.YOUR_EXTENSION_ID</string>
         <key>PayloadUUID</key><string>UUID-TWO</string>
         <key>PayloadIdentifier</key><string>com.sysaid.chrome.token</string>
         <key>PayloadVersion</key><integer>1</integer>
         <key>token</key><string>YOUR_TOKEN_VALUE</string>
       </dict>
     </array>
     <key>PayloadType</key><string>Configuration</string>
     <key>PayloadScope</key><string>System</string>
     <key>PayloadUUID</key><string>UUID-THREE</string>
     <key>PayloadIdentifier</key><string>com.sysaid.chrome.profile</string>
     <key>PayloadVersion</key><integer>1</integer>
   </dict></plist>
   

2. The .mobileconfig file must include both required payloads:

   1. Force-install payload: Installs the SysAid Browser Extension in Chrome.

   2. Token payload: Adds the required SysAid token so the extension can connect to your SysAid environment.

3. Before uploading the file to Intune, validate it in Terminal to make sure the file is properly formatted: plutil -lint SysAid.mobileconfig.This check confirms that the .mobileconfig file is valid. It does not confirm that the token is correct or that the extension was installed successfully.

4. Apply the four changes below:

   1. Change 1: Switch the two payload types from Chrome to Edge:

      1. Payload 1:  com.google.Chrome  >  com.microsoft.Edge

      2. Payload 2:  com.google.Chrome.extensions.YOUR_EXTENSION_ID  >  com.microsoft.Edge.extensions.YOUR_EXTENSION_ID

   2. Change 2: In Payload 1, add this key (Boolean, not integer), so Edge is allowed to install a Chrome Web Store extension:
      

      <key>ControlDefaultStateOfAllowExtensionFromOtherStoresSettingEnabled</key>
      
      <true/>

   3. Change 3: Keep the force-install URL pointing at the Chrome Web Store (that's where the SysAid extension lives). The force-install line stays:

      YOUR_EXTENSION_ID;https://clients2.google.com/service/update2/crx

   4. Change 4: Leave the token payload as-is. The key name is token, the same as Chrome.

Please note:

Keep the token in its own payload. Don't nest it inside the force-install payload, or Edge ignores it silently.

Deploying the extension

To deploy the extension:

1. In Intune, go to Devices > macOS > Configuration profiles > Create > Templates > Custom.

2. Upload your .mobileconfig file and set Deployment channel = Device channel.

   Please note:

   Use Custom, not “Preference file.” The Preference file template handles a single domain and can’t carry the second (token) payload.

3. Assign to the pilot group.

4. Click Create.

Verify the setup

To verify the setup:

• In Intune, go to System Settings > General > Device Management. The SysAid profile should be installed with two payloads.

• In chrome://policy: ExtensionInstallForcelist, ExtensionSettings (no policy sub-key), and a token row.

• Extension enabled in chrome://extensions; pop-up set to Active.