Update Entity Analyzer: intelligent user identifier detection#13614
Open
Yaniv-Shasha wants to merge 1 commit intoAzure:masterfrom
Open
Update Entity Analyzer: intelligent user identifier detection#13614Yaniv-Shasha wants to merge 1 commit intoAzure:masterfrom
Yaniv-Shasha wants to merge 1 commit intoAzure:masterfrom
Conversation
…jectGuid, aadUserId, UPN, and Name+UPNSuffix support
Contributor
|
Hi @Yaniv-Shasha, please package this solution using V3 tool - https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.md. Thanks! |
Contributor
|
Hi @Yaniv-Shasha, any update on the above comment. Thanks! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
This PR updates the Incident-Trigger-Entity-Analyzer playbook (
azuredeploy.json) with the following improvements:What Changed
2026-02-10Yaniv Shashahidden-SentinelTemplateNameandhidden-SentinelTemplateVersion: 2.0Condition_-_Check_Valid_User_Identifierwithcoalesce()across objectGuid, aadUserId, UPN (both casings), and Name+UPNSuffixAdd_Skip_comment_to_incidentwhen no valid user identifier existsazuresentinel(lowercase)Why
Previously the playbook only used
AadUserIdto identify users. Many Sentinel incidents provide user entities with different identifier types (objectGuid, UPN, Name+UPNSuffix), causing silent failures. This update ensures robust user resolution across all common identifier formats.