Events
Apr 9, 3 PM - Apr 10, 12 PM
Code the Future with AI and connect with Java peers and experts at JDConf 2025.
Register NowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
With Conditional Access policies, you can specify access requirements to websites and services. For example, your access requirements can include requiring multifactor authentication (MFA) or managed devices.
When you access a site or service directly, the impact of a related policy is typically easy to assess. For example, if you have a policy that requires multifactor authentication (MFA) for SharePoint Online configured, MFA is enforced for each sign-in to the SharePoint web portal. However, it isn't always straight-forward to assess the impact of a policy because there are cloud apps with dependencies to other cloud apps. For example, Microsoft Teams can provide access to resources in SharePoint Online. So, when you access Microsoft Teams in our current scenario, you're also subject to the SharePoint MFA policy.
Tip
Using the Office 365 app will target all Office apps to avoid issues with service dependencies in the Office stack.
If you have a service dependency configured, the policy can apply using early-bound or late-bound enforcement.
The following diagram illustrates Microsoft Teams service dependencies. Solid arrows indicate early-bound enforcement the dashed arrow for Planner indicates late-bound enforcement.
As a best practice, you should set common policies across related apps and services whenever possible. Having a consistent security posture provides you with the best user experience. For example, setting a common policy across Exchange Online, SharePoint Online, and Microsoft Teams reduces prompts that might arise from different policies being applied to downstream services.
A great way to accomplish a common policy with applications in Microsoft 365 is to use the Office 365 app instead of targeting individual applications.
The below table lists some more service dependencies, where the client apps must satisfy. This list isn't exhaustive.
Client apps | Downstream service | Enforcement |
---|---|---|
Azure Data Lake | Windows Azure Service Management API (portal and API) | Early-bound |
Microsoft Classroom | Exchange | Early-bound |
SharePoint | Early-bound | |
Microsoft Teams | Exchange | Early-bound |
MS Planner | Late-bound | |
Microsoft Stream | Late-bound | |
SharePoint | Early-bound | |
Skype for Business Online | Early-bound | |
Microsoft Whiteboard | Late-bound | |
Office Portal | Exchange | Late-bound |
SharePoint | Late-bound | |
Outlook groups | Exchange | Early-bound |
SharePoint | Early-bound | |
Power Apps | Windows Azure Service Management API (portal and API) | Early-bound |
Windows Azure Active Directory | Early-bound | |
SharePoint | Early-bound | |
Exchange | Early-bound | |
Power Automate | Power Apps | Early-bound |
Project | Dynamics CRM | Early-bound |
Skype for Business | Exchange | Early-bound |
Visual Studio | Windows Azure Service Management API (portal and API) | Early-bound |
Microsoft Forms | Exchange | Early-bound |
SharePoint | Early-bound | |
Microsoft To Do | Exchange | Early-bound |
SharePoint | SharePoint Online Web Client Extensibility | Early-bound |
SharePoint Online Web Client Extensibility Isolated | Early-bound | |
SharePoint Client Extensibility web application principal (where present) | Early-bound |
The Microsoft Entra sign-in log is a valuable source of information when troubleshooting why and how a Conditional Access policy applied in your environment. For more information about troubleshooting unexpected sign-in outcomes related to Conditional Access, see the article Troubleshooting sign-in problems with Conditional Access.
To learn how to implement Conditional Access in your environment, see Plan your Conditional Access deployment in Microsoft Entra ID.
Events
Apr 9, 3 PM - Apr 10, 12 PM
Code the Future with AI and connect with Java peers and experts at JDConf 2025.
Register Now