Removed external blog reference text from several hunting query descr…#13645
Merged
v-atulyadav merged 2 commits intomasterfrom Feb 18, 2026
Merged
Removed external blog reference text from several hunting query descr…#13645v-atulyadav merged 2 commits intomasterfrom
v-atulyadav merged 2 commits intomasterfrom
Conversation
…iptions Remove external blog reference text from several hunting query descriptions and sanitize UI text. Bump hunting query versions (e.g. 1.1.1→1.1.2, 1.0.2→1.0.3, 1.0.0→1.0.1) and propagate those version changes into solution mainTemplate.json. Update package artifacts: modify Endpoint Threat Protection Essentials package files and add Windows Security Events package 3.0.12.zip. Also normalize entityMappings ordering/formatting and adjust an alert override format in the main template.
Contributor
There was a problem hiding this comment.
Pull request overview
Removes external blog reference text from hunting query descriptions/UI text and bumps solution/hunting query versions, propagating the version changes through packaged templates.
Changes:
- Updated Windows Security Events solution/package version to 3.0.12 and bumped a hunting query version (1.0.0 → 1.0.1) with corresponding product IDs.
- Updated Endpoint Threat Protection Essentials hunting query versions (1.1.1 → 1.1.2, 1.0.2 → 1.0.3) and removed external “Ref” text from package/UI descriptions.
- Normalized JSON formatting/order for
entityMappingsand adjustedalertDetailsOverrideproperty ordering.
Reviewed changes
Copilot reviewed 7 out of 9 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| Solutions/Windows Security Events/Package/mainTemplate.json | Bumps solution/package version to 3.0.12 and propagates a hunting query version update into IDs/version fields. |
| Solutions/Windows Security Events/Hunting Queries/RemoteScheduledTaskCreationUpdateviaSchtasks.yaml | Removes external blog reference and bumps hunting query version to 1.0.1. |
| Solutions/Endpoint Threat Protection Essentials/Package/mainTemplate.json | Bumps hunting query versions, removes external “Ref” from description tags, normalizes mappings format, and reorders alert override fields. |
| Solutions/Endpoint Threat Protection Essentials/Package/createUiDefinition.json | Removes external blog reference from UI text block. |
| Solutions/Endpoint Threat Protection Essentials/Hunting Queries/ScheduledTaskCreationUpdateFromUserWritableDrectory.yaml | Removes external blog reference and bumps hunting query version to 1.0.3. |
| Solutions/Endpoint Threat Protection Essentials/Hunting Queries/RemoteScheduledTaskCreationUpdateUsingATSVCNamedPipe.yaml | Removes external blog reference and bumps hunting query version to 1.1.2. |
| Hunting Queries/SecurityEvent/RemoteScheduledTaskCreationUpdateviaSchtasks.yaml | Removes external blog reference from the non-solution hunting query description. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
...tection Essentials/Hunting Queries/RemoteScheduledTaskCreationUpdateUsingATSVCNamedPipe.yaml
Show resolved
Hide resolved
...otection Essentials/Hunting Queries/ScheduledTaskCreationUpdateFromUserWritableDrectory.yaml
Show resolved
Hide resolved
Solutions/Endpoint Threat Protection Essentials/Package/mainTemplate.json
Show resolved
Hide resolved
Modify release notes for Endpoint Threat Protection Essentials and Windows Security Events. For Endpoint Threat Protection Essentials, extend the 3.0.5 entry to note removal of a broken URL from both an Analytic Rule and a Hunting query. For Windows Security Events, add a new 3.0.12 entry (18-02-2026) documenting removal of external blog reference text from two hunting query descriptions.
v-atulyadav
approved these changes
Feb 18, 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.
…iptions
Remove external blog reference text from several hunting query descriptions and sanitize UI text. Bump hunting query versions (e.g. 1.1.1→1.1.2, 1.0.2→1.0.3, 1.0.0→1.0.1) and propagate those version changes into solution mainTemplate.json. Update package artifacts: modify Endpoint Threat Protection Essentials package files and add Windows Security Events package 3.0.12.zip. Also normalize entityMappings ordering/formatting and adjust an alert override format in the main template.
Required items, please complete
Change(s):
Reason for Change(s):
Version Updated:
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present:
Guidance <- remove section before submitting
Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.
Change(s):
Reason for Change(s):
Version updated:
Testing Completed:
Note: If updating a detection, you must update the version field.
Checked that the validations are passing and have addressed any issues that are present:
Note: Let us know if you have tried fixing the validation error and need help.