Cloud Site List Management for IE mode

-
Back in August 2021, I had published a blog covering the details and the process of configuring Enterprise mode site list to support Internet Explorer dependent URLs\web apps together with the use of an Azure blob for storing the custom enterprise mode list (EML) in the cloud. With the introduction of Cloud site list management in the Microsoft 365 Admin Portal, the entire configuration has been simplified.

Cloud site list management is a great addition as organizations can now store their own site list directly in Azure cloud. Not only that, they will be able to create, publish, import, export site lists, and audit changes to site list entries all through the Microsoft 365 Admin Center itself. The site lists can then be delivered using GPO, Intune or ConfigMgr.

However, there are some prerequisites which need to be considered before one can start using the feature -

- Customers must have an Azure AD tenant.
- Admins must have Microsoft Edge version 93 or greater installed and the latest version of the policy files.
- Admins need to be an Microsoft Edge Administrator or a Global Administrator on the tenant to access the Microsoft Edge site lists experience.

Enabling & Configuring Cloud Site List Management

The feature is only available in Microsoft 365 Admin portal and is not enabled by default. Here is how you can do it:

1. Sign in to the Microsoft 365 admin center.
2. On the left navigation pane, select Settings > Org settings.
3. Click on the Microsoft Edge site lists option.


Now it is time to create you own custom list:

1. After clicking on Microsoft Edge site lists, select Create a new list.
2. Enter a Site list name and a Description, and then select Create.
3. On receiving a confirmation, select Close panel.


At this stage, the Site list will show as 'Unpublished draft'. This will change once we publish the Site list, but before that we need to populate the Site list with a list of URLs that need to be configured for relevant browser modes.

One has the option to import an existing EML to add the sites or add them individually. For demonstration purposes, I am covering the process of adding the URLs individually.

1. Click on the newly created Site list and then select Add a site.
2. Enter the site address and pick the engine that should be used to open the site. In this case, I am selecting the default Internet Explorer Mode.
3. Select the Compatibility mode or leave it to Default mode.
4. You can select to Allow redirect to redirect the URL or leave it unchecked which is the default.
5. Leave No merge unchecked.
6. Add comments as needed and then select Save.



You will notice that the status column for any entries copied to a site list will show Addition pending. This will change after the site list is published. Let's see how that is done.

1. Go back to your site list and click on Publish site list.


2. Provide the Version select Close Panel when done.



The Published status of the Site list will change to All changes published and now we will need to deploy this to the managed endpoints. I am going to use Intune as the delivery tool. 

Important: Before we go any further, make sure to make a note of the site id which will be used later in the configuration policy.


Note: You have the option to use Configure IE mode deployment guide to create a device configuration policy in Intune, but as of now it still uses Administrative Templates. I prefer using Settings Catalog due to its ease of use & also enhanced reporting capabilities.

2. Browse to Devices > Windows > Configuration Profiles
3. Click Create Profile
4. Select Platform as Windows 10 and later
5. Select Profile as Settings catalog (Preview)
6. Provide a Name and hit next.
7. Click on Add settings.
8. Search for the following settings and add them as shown below.


Notice the Site list id highlighted above? That is the same id that we captured before. This will tell the devices to access the Cloud Site List that we created earlier. 

Note: The user must be signed into Microsoft Edge with a valid work or school account otherwise Microsoft Edge will not download the site list from the cloud location. This setting is applicable only when the 'InternetExplorerIntegrationLevel' (Configure Internet Explorer integration) setting is configured. Also, this setting takes precedence over Microsoft Edge's 'InternetExplorerIntegrationSiteList' (Configure the Enterprise Mode Site List) policy and Internet Explorer's site list setting (Use the Enterprise mode IE website list).

9. Once created, deploy to a user or device based group.

End User Experience & Compliance Reporting

Once the policy applies and the end user tries to access the URL added in the site list, it will automatically open in the configured browser mode.


The settings can be verified by navigating to edge://compat/enterprise.


On the MEM admin console, if you access the Per setting status against the policy, you will be able to see the compliance status against the settings we configured.


Conclusion

It is great that Microsoft recognized the need for adding Cloud Site List management in Microsoft 365 Admin Portal as a lot of organizations still have sites dependent on IE. With support for Internet Explorer ending on June 15th, 2022, one can continue using IE mode in Microsoft Edge to run the dependent sites. However, this is not forever as Microsoft may end the support after 2029. This allows organizations a good amount of time to identify the URLs and web apps that are dependent on IE and start migrating them to the modern bowser experience that comes with Edge Chromium. A good starting point will be aka.ms/EdgeAdvisor.

Until next time..

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"){              ...
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 st...
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. $P...
Read more