(165) Microsoft Intune - Allowing AuthSchemes and SSL Warnings for Edge and Google Chrome

Had a recent customer that I have been helping during our onboarding stage, there have specific local domain sites that are hosted which needs to use basic auth. As customer is using Essential 8 policies from ML1 to ML3 that has the following policies, it makes it harder, had to tweak it therefore it will allow them to use it.

Go to https://intune.microsoft.com/ then select Devices then select Configuration then select Create then select New Policy then select Platform: Windows 10 and later then select Profile Type: Settings Catalog.

For Microsoft Edge (AuthSchemes):

Supported authentication schemes (Device): ntlm,negotiate,basic

Allow Basic authentication for HTTP: Enabled

List of origins that allow all HTTP authentication: Enabled

List of origins that allow all HTTP authentication (Device): domain.local, domain.xyz.au

Supported authentication schemes: Enabled

For Google Chrome (AuthSchemes):

Supported authentication schemes (Device): ntlm,negotiate,basic

Allow Basic authentication for HTTP: Enabled Authentication server allowlist: Enabled

Authentication server allowlist (Device): domain.local, domain.xyz.au

Supported authentication schemes: Enabled

For Microsoft Edge (SSL Warning):

Allow proceeding from the SSL warning page on specific origins: Enabled

Allow proceeding from the SSL warning page on specific origins (Device): domain.local, domain.xyz.au

For Google Chrome (SSL Warning):

Allow users to proceed from the HTTPS warning page for specific origins: Enabled

Allow users to proceed from the HTTPS warning page for specific origins (Device): domain.local, domain.xyz.au

Alternatively, if you wish to allow all sites, you can enter in , generally we would like specific which URL or site. It will pose a security risk if you were to allow * (wildcard).

• List of origins that allow all HTTP authentication (Device) = Edge

• Authentication server allowlist (Device) = Chrome

• Allow proceeding from the SSL warning page on specific origins (Device) = Edge

• Allow users to proceed from the HTTPS warning page for specific origins (Device) = Chrome