Deploying the SysAid Browser Extension in Edge (macOS)

Use this guide to install the SysAid Browser Extension in Microsoft Edge on company-managed Macs.

You'll deploy one configuration profile that does two things:

• Force-installs the extension in Edge.

• Delivers the token so the extension can connect to SysAid.

Because the extension comes from the Chrome Web Store, the profile also turns on one Edge setting that allows installing extensions from other stores.

Before you start

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 Edge profile

To build the profile:

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. Validate: plutil -lint your-profile.mobileconfig (checks XML only. Also confirm each payload has PayloadIdentifier + PayloadVersion).

   Please note:

   Don’t nest the Token inside ExtensionSettings under a policy key — Chrome rejects that silently. Keep it in its own com.google.Chrome.extensions.<ID> payload.

3. 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.

Deploy the extension

Every MDM does the same two things: upload the .mobileconfig you just built as a custom profile, then assign it to a group of test devices. Find your tool below and follow its path. (Upload it as-is. Don't change the file.)

Please note:

If you deploy both browsers, use two separate profiles (one Chrome, one Edge). They can coexist.

Verify the setup

To verify the setup:

• On your device, go to System Settings > General > Device Management and see that the SysAid profile is installed with two payloads.

• Open edge://policy. You should see ExtensionInstallForcelist and a row for the SysAid token.

• Open edge://extensions. The extension is enabled and marked “Installed by your organization.”

• Click the extension icon. The pop-up should say Active.