-
Notifications
You must be signed in to change notification settings - Fork 116
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: MT.1038 - Conditional Access policies should not include or exclude deleted groups. | ||
description: This test checks if there are any Conditional Access policies that target deleted security groups. | ||
slug: /tests/MT.1038 | ||
sidebar_class_name: hidden | ||
--- | ||
|
||
# All excluded objects should have a fallback include in another policy | ||
|
||
## Description | ||
|
||
This test checks if there are any Conditional Access policies that target deleted security groups. | ||
|
||
This usually happens when a group is deleted but is still referenced in a Conditional Access policy. | ||
|
||
Deleted groups in your policy can lead to unexpected gaps. This may result in Conditional Access policies not being applied to the users you intended or the policy not being applied at all. | ||
|
||
To fix this issue: | ||
|
||
## How to fix | ||
|
||
* Open the impacted Conditional access policy. | ||
* If the group is no longer needed, click Save to remove the referenced group from the policy. | ||
* If the group is still needed, update the policy to target a valid group. |