Enable Google Chrome browser extensions using Settings Catalog in Intune to support Conditional Access Policies

-

When I blogged about using settings catalog for Google Chrome browser settings back in March 2022, I knew this is only a start as Google Chrome's admx was now built into Intune. After only a couple of weeks, I now find myself using settings catalog again to configure yet another Google Chrome browser setting which I had been configuring using CSP all this while. The configuration in question is for enabling specific Google Chrome browser extensions in order to support device state based Conditional Access policies.

Enabling Google Chrome Windows Accounts or Office Online extensions

Windows Accounts or Office Online extensions are required if you want Google Chrome browser to support Conditional Access policies where device state is being used as a condition. Note: These extensions may not work with Hybrid Azure AD join scenario and may only work for Azure AD identity.

In this blog, I will configure Windows Accounts extension as an example. Follow the steps below -

2. Under Devices > Windows > Configuration profiles > Create profile.
3. Under Platform, select Windows 10 & later.
4. Under Profile types, select Templates > Settings Catalog.
5. Give a name.
6. Next step is to look for relevant Google Chrome's extension setting. Search for Google Chrome extension and configure the setting as shown below. 


This policy supersedes ExtensionInstallBlocklist policy. If a previously force-installed app or extension is removed from this list, Google Chrome automatically uninstalls it. Each list item of the policy is a string that contains an extension ID and, an "update" URL separated by a semicolon (;). By default, the Chrome Web Store's update URL is used.

Syntax is - <32 letter string value>;https://clients2.google.com/service/update2/crx

The extension ids available are -

Windows Accounts - ppnbnpeolgkicgegkbkbjmhlideopiji
Office Online - ndjpnladcallmjemlbaebfadecfhkepb

Conditional Access policy for allowing access from a Compliant Device

If you have a requirement to allow access to corporate resources over browser from compliant devices, then follow the steps below to configure the CA policy.

2. Go under Devices > Conditional access > New Policy > Create new policy
3. Provide a name.
4. Target the relevant users.


5. Under Cloud apps or actions, select All cloud apps.


6. Under Conditions > Device platforms, select Windows.


7. Under Grant > Grant Access, select Require device to be marked as compliant.


End Result

If the extension is missing from Google Chrome, then the user will not be allowed to access the corporate resource using the browser. As an example I am using office.com as the resource.


However, once the extension gets installed silently, the user will be able to access the corporate resources like office.com using organization credentials.

The presence of the extension can be checked by accessing chrome://extensions



Administrators can validate for the enforcement of the right CA policy by accessing the Azure sign-ins.

When the device state is not established because of the missing extension -


When the device state is established because of the presence of the extension -


Compliance state of the policy -

In case of the user setting, ExtensionInstallForceList will reflect under HKCU. For device setting, it will reflect under HKLM\Software\Policies\Google\Chrome

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting pr
Read more