Skip to content

Clarify CA policy enforcement for service principals in groups #1731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify CA policy enforcement for service principals in groups #1731

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/identity/conditional-access/workload-identity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,9 @@ These differences make workload identities harder to manage and put them at high
> [!NOTE]
> Policy can be applied to single tenant service principals that are registered in your tenant. Third party SaaS and multi-tenanted apps are out of scope. Managed identities aren't covered by policy. Managed identities could be included in an [access review](../../id-governance/access-reviews-overview.md) instead.

> [!NOTE]
> While service principals can be added to groups, Conditional Access policies assigned to a group that contains a service principal are not enforced for that service principal. To enforce a Conditional Access policy for a service principal, it must be assigned directly to the policy as a workload identity.

Conditional Access for workload identities enables blocking service principals:

- From outside of known public IP ranges.
Expand Down