Add the Collibra platform URL via scripts

Create a custom attribute

Start by creating a custom attribute in Intune to detect whether the extension is already preconfigured. This allows for a continuous deployment of the configuration as devices receive updated extensions from the appropriate extension provider.

To create a custom attribute, load the CheckCollibraExtension.ps1 script and set the following variables in the script:

• $extensionID: "Public Collibra Extension ID"
• $BrowserPath: "Google\Chrome" or "Microsoft\Edge", depending on the web browser you want to configure

Deploy the configuration script

For the steps on deploying the configuration script, go to the Create a script policy and assign it section in the Microsoft Intune Documentation. For the information you need to provide when following the steps, refer to the following table.

Property	Information
Name	Collibra Extension Configuration
Description	This script will preconfigure Collibra Browser Extension for mass deployment.
Script location	Browse to the location of the SetCollibraExtension.ps1 script on your device. The script must be less than 200 KB (ASCII). Set the following variables in the script: $instanceURL: "YOURDOMAIN.collibra.com" $extensionID: "Public Collibra Extension ID" $BrowserPath: "Google\Chrome" or "Microsoft\Edge", depending on the web browser you want to configure
Run this script using the logged on credentials	Yes
Enforce script signature check	No
Run script in 64-bit PowerShell host	Yes
Assignments > Select groups to include	Select the group that is created from the custom attribute whose result is Extension Not Configured.

Create a Windows sensor

Start by creating a Windows sensor in WorkspaceOne to detect whether the extension is already preconfigured. This allows for a continuous deployment of the configuration as devices receive updated extensions from the appropriate extension provider.

To create a Windows sensor, load the CheckCollibraExtension.ps1 script and set the following variables in the script:

• $instanceURL: "YOURDOMAIN.collibra.com"
• $extensionID: "Public Collibra Extension ID"
• $BrowserPath: "Google\Chrome" or "Microsoft\Edge", depending on the web browser you want to configure

Deploy the configuration script

For the steps on deploying the configuration script, go to the Create a Script for Windows Desktop Devices section in the VMware Workspace ONE UEM Product Documentation. For the information you need to provide when following the steps, refer to the following table.

Setting	Information
Name	Collibra Extension Configuration
Description	This script will preconfigure Collibra Browser Extension for mass deployment.
App Catalog Customization	Leave blank.
Language	Workspace ONE UEM supports PowerShell
Execution Context	User
Execution Architecture	x64
Timeout	Retain the default value.
Code	Upload or paste the contents of the SetCollibraExtension.ps1 script. Set the following variables in the script: $instanceURL: "YOURDOMAIN.collibra.com" $extensionID: "Public Collibra Extension ID" $BrowserPath: "Google\Chrome" or "Microsoft\Edge", depending on the web browser you want to configure
Assignment	Select the group that is created from the sensor whose result is Extension Not Configured.
Triggers	Select the trigger that starts the script. You can select multiple triggers. At a minimum, you should select a regular cadence to capture updates to the extension.

Create an extension attribute

Start by creating an extension attribute in Jamf to detect whether the extension is already preconfigured. This allows for a continuous deployment of the configuration as devices receive updated extensions from the appropriate extension provider.

To create an extension attribute, load the CheckCollibraExtension.sh script and set the following variables in the script:

• extensionID: "Public Collibra Extension ID"

You must also add the SetCollibraExtension.sh script to Jamf before deployment.

Deploy the configuration script

For the steps on deploying the configuration script, go to the Running Scripts Using a Policy section in the Jamf Pro Documentation. When following the steps, consider the following:

• After selecting the Scripts payload and clicking Configure, set the following variables in the script as specified:
  • instanceURL: "YOURDOMAIN.collibra.com"
  • extensionID: "Public Collibra Extension ID"
• Configure the settings for the script such that the script runs regularly to detect any changes on the device.
• Configure the scope of the policy such that the policy is scoped to the group that is created from the extension attribute whose result is Extension Not Configured.

Create a macOS sensor

Start by creating a macOS sensor in WorkspaceOne to detect whether the extension is already preconfigured. This allows for a continuous deployment of the configuration as devices receive updated extensions from the appropriate extension provider.

To create a macOS sensor, load the CheckCollibraExtension.sh script and set the following variables in the script:

• extensionID: "Public Collibra Extension ID"

Deploy the configuration script

For the steps on deploying the configuration script, go to the Create a Script for macOS Devices section in the VMware Workspace ONE UEM Product Documentation. For the information you need to provide when following the steps, refer to the following table.

Setting	Information
Name	Collibra Extension Configuration
Description	This script will preconfigure Collibra Browser Extension for mass deployment.
App Catalog Customization	Leave blank.
Language	Bash
Execution Context	User
Timeout	Retain the default value.
Code	Upload or paste the contents of the SetCollibraExtension.sh script. Set the following variables in the script: instanceURL: "YOURDOMAIN.collibra.com" extensionID: "Public Collibra Extension ID"
Assignment	Select the group that is created from the sensor whose result is Extension Not Configured.
Triggers	Select the trigger that starts the script. You can select multiple triggers. At a minimum, you should select a regular cadence to capture updates to the extension.