As you know you can implement Conditional Access on Azure Active Directory to determine conditions of access to applications published through Azure AD.
You may also already know that Conditional Access evaluation may be delayed because authentication token obtained previously by the client is not yet expired. This means when a connection condition change it may take some time to be evaluated again by Conditional Access.
Well, this time is going to be over with the new Continuous Access Evaluation feature currently in preview.
With the Continuous Access Evaluation any connection condition changes will evaluated again almost in real time – there still could be some delay up to 15 min because of back end event propagation.
At this stage, the Continuous Access Evaluation is focusing on Exchange Online, Teams and SharePoint Online with the below list of events being evaluated:
Before continuous access evaluation, clients would always try to replay the access token from its cache as long as it was not expired. With Continuous Access Evaluation, a new case has been introduced allowing a resource provider to reject a token even when it is not expired. In order to inform clients to bypass their cache even though the cached tokens have not expired, a new mechanism called claim challenge has been introduced to indicate that the token was rejected and a new access token need to be issued by Azure AD. Continuous Access Evaluation requires a client update to understand claim challenge. The latest version of the following applications below support claim challenge:
Once in your Azure AD blade, access the Security\Continuous access evaluation blade and then turn on the feature and select to which users/groups this will apply – default is set to all users/groups