Conditional Access Gap Analysis - Windows Sign In should be removed from App Report #1824
Labels
Comments
|
@sabinasmith It looks like you might be the author of this template? |
|
Any update on this? Also facing the same issue, 60% of our logins not covered by MFA are from "Windows Sign In" which isn't covered by conditional access, so it makes zero sense for these to be reported on at all. |
|
Agreed, this should not be part of the report. |
Palciny
added a commit
to Palciny/Application-Insights-Workbooks
that referenced
this issue
Sep 11, 2023
conditionalAccessGapAnalyzer.workbook is including "Windows SignIn" that doesn't support MFA, so it doesn't have sense to be included in the report. There was also request for this change: microsoft#1824
11 tasks
|
@sabinasmith did you ever look in to this? |
|
@gardnerjr can you review my changes in #2418 that fix this Issue? |
|
@Palciny someone from the Azure AD Workbooks team needs to approve, they're the codeowners of that area. |
|
Same issue, can this please be fixed. 2022! this bug was logged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In reviewing the CA GAP Analysis workbook, in the Unprotected Applications section, the report of Number of Users Signing in to Applications with Conditional Access Policies Not applied, it includes the Windows Sign-In "app"
This is the sign in to the Windows device and PRT acquisition process and would not be in scope of CA. This causes lots of "noise" in the report since most users will have this event.
Can we remove the "Windows Sign-In" app from this report?
The text was updated successfully, but these errors were encountered: