- Encrypt email in Outlook with Microsoft 365 - Tue, Dec 6 2022
- Restricting registration to Azure AD MFA from trusted locations with Conditional Access policy - Thu, Nov 24 2022
- Azure AD MFA with number matching and temporary access passes - Tue, Nov 22 2022
For example, you can set up a policy to allow any request from a trusted location (an IP address) and block access from any other location.
Conditional Access policies can be incredibly versatile, but they can also go wrong, and locking yourself out of a tenant would not be a good idea. Thus, Microsoft offers a report-only mode in which a rule is evaluated but not enforced. You can read more about Conditional Access here.
One popular way to deploy Conditional Access is to use it in conjunction with Microsoft Intune. Intune enables you to set compliance policies on devices, whether they use BitLocker or have a specific version of Windows or antivirus enabled. You can then configure a conditional access rule to grant access only to compliant devices.
Using Conditional Access to limit access only to compliant devices
This works very well and is easy to set up and deploy—until a device is denied access and you can't see why.
This issue came up for me recently. A user was denied access to SharePoint, even though the device showed as compliant. To make things more confusing, it worked perfectly on the same device using Microsoft Edge.
After successfully passing the username and password and the MFA challenge, the following was displayed.
Conditional Access failure message
To troubleshoot this further, we head into Azure Active Directory and select Users > Sign-in logs.
Use Azure AD sign in logs to troubleshoot login failures
We can set a filter to look for only the specific user we are interested in.
Setting a filter for usernames
From the list of sign-in activities, we can find a successful sign-in, open it, and look at the device details.
This is an example from Microsoft Edge. Note that it shows the version and that the device is Hybrid Azure AD joined and compliant.
Sign in on Microsoft Edge
Contrast this with a login on the same device but using Google Chrome.
Activity Details Sign in
You can clearly see that Chrome has not passed the device state through to Azure.
The solution, luckily, is straightforward enough. Microsoft released a Chrome extension called Windows Accounts that links your logged-on user and device info, and allows it to be passed through to Microsoft services.
Once this extension is deployed to the browser, your device state is correctly passed through, and your Conditional Access policies are extended to support Chrome.
Install the Windows Accounts extension
Device information now passed to Azure AD
You may also face a similar issue using Android devices. In the company portal app, you must enable browser access.
Subscribe to 4sysops newsletter!
- Launch the Company Portal
- Go to the Settingspage from the menu.
- In the Enable Browser Accesssection, tap the ENABLE button
More information about device-based Conditional Access can be found here.
We have this extension deployed however it then bypasses MFA. Our conditional access policy requires compliant device and MFA to gain access yet when this Chrome extension is enabled, the user is not required to enter username, password or MFA to access 365 apps. We find this to be a huge security hole because it offers no protection If the device is compromised. There are literally no stops in place.
The condtional access policy will not work without this extension. Is there any way make sure a user still needs to MFA, even if no login credentials are requested?
Does it show the MFA requirement is satisfied in the sign in logs?
Do you have your CA policy set to ‘all the requirements’ or ‘any of’ ?
Also, consider reviewing this: https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime
have the same issue here, extension is also installed.