add entra traffic type#14052
Merged
v-atulyadav merged 5 commits intoAzure:masterfrom Apr 16, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the Global Secure Access solution workbooks to include the new entra traffic type, and bumps the solution version/release notes accordingly.
Changes:
- Updated workbook KQL queries to treat
TrafficType == 'entra'similarly tomicrosoft365. - Updated solution version to
3.0.4and added release notes entry for the workbook changes. - Normalized the solution data file’s empty “Hunting Queries” list to
[].
Reviewed changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| Solutions/Global Secure Access/Workbooks/GSANetworkTraffic.json | Expands TrafficType handling to include entra in workbook query logic. |
| Solutions/Global Secure Access/Workbooks/GSAM365EnrichedEvents.json | Updates multiple workbook queries to include entra traffic alongside microsoft365. |
| Solutions/Global Secure Access/ReleaseNotes.md | Adds a 3.0.4 entry documenting workbook update for Entra traffic type. |
| Solutions/Global Secure Access/Data/Solution_GlobalSecureAccess.json | Bumps solution version to 3.0.4 and adjusts empty Hunting Queries array representation. |
v-shukore
approved these changes
Apr 16, 2026
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.
Change(s):
Updated Global Secure Access solution (version 3.0.4):
Workbooks — Updated GSAM365EnrichedEvents.json (25 queries) and GSANetworkTraffic.json (1 iff condition) to support the new Entra traffic type: TrafficType == 'microsoft365' → TrafficType in ('microsoft365', 'entra')
Analytic Rule — Fixed regex in GSA - TI URL Entity.yaml for correct URL indicator matching: replace(@'[|]|"""', ...) → replace(@'[[]"]', ...)
Package — Regenerated mainTemplate.json and 3.0.4.zip using createSolutionV3.ps1
ReleaseNotes.md — Added version 3.0.4 entry; fixed missing 3.0.3 entry
Reason for Change(s):
Global Secure Access introduced a new entra TrafficType (split from microsoft365). Workbook queries need to include both types.
The TI URL Entity analytic rule had a broken regex that left a leading quotation mark in IndicatorType, causing URL-based TI detections to produce zero alerts.
Version Updated:
Yes — 3.0.3 → 3.0.4
Testing Completed:
Yes — Package generated using createSolutionV3.ps1. All JSON files validated.
Checked that the validations are passing and have addressed any issues that are present:
Yes