Merged
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Contributor
There was a problem hiding this comment.
Pull request overview
Refreshes the Az.SecurityInsights module’s generated/help documentation and associated metadata, aligning examples and generated artifacts with the latest autorest output for the SecurityInsights module.
Changes:
- Updated several cmdlet help examples (e.g., incident update, entity examples, alert rule creation).
- Refreshed generated module metadata/artifacts (module manifest, solution/project IDs, generate-info, assembly versions).
- Updated some sample GUIDs/identifiers in documentation outputs.
Reviewed changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| src/SecurityInsights/SecurityInsights/help/Update-AzSentinelIncident.md | Updates example command for incident update help content. |
| src/SecurityInsights/SecurityInsights/help/New-AzSentinelIncidentTeam.md | Updates Teams URL sample output (tenantId). |
| src/SecurityInsights/SecurityInsights/help/New-AzSentinelAlertRule.md | Updates Scheduled alert rule example content. |
| src/SecurityInsights/SecurityInsights/help/Get-AzSentinelEntityInsight.md | Updates sample EntityId used in example. |
| src/SecurityInsights/SecurityInsights/help/Get-AzSentinelEntityActivity.md | Adjusts example description text. |
| src/SecurityInsights/SecurityInsights/help/Get-AzSentinelEntity.md | Adjusts Example 3 variable usage in pipeline example. |
| src/SecurityInsights/SecurityInsights/Az.SecurityInsights.psd1 | Refreshes manifest generation date, Az.Accounts dependency, and formatting; bumps module version. |
| src/SecurityInsights/SecurityInsights.sln | Updates solution project GUID references for Az.SecurityInsights project. |
| src/SecurityInsights/SecurityInsights.Autorest/generate-info.json | Updates generation ID. |
| src/SecurityInsights/SecurityInsights.Autorest/examples/Update-AzSentinelIncident.md | Updates incident update example snippet. |
| src/SecurityInsights/SecurityInsights.Autorest/docs/Update-AzSentinelIncident.md | Updates incident update docs example. |
| src/SecurityInsights/SecurityInsights.Autorest/docs/Az.SecurityInsights.md | Updates module doc page GUID. |
| src/SecurityInsights/SecurityInsights.Autorest/Properties/AssemblyInfo.cs | Bumps assembly version from 3.2.0 to 3.2.1. |
Comments suppressed due to low confidence (1)
src/SecurityInsights/SecurityInsights.Autorest/docs/Update-AzSentinelIncident.md:49
- The example now updates multiple fields (Title/Status/Severity) in addition to assigning an owner, but the description sentence below the example still says it only assigns an owner. Please update the description to match the example's behavior.
Update-AzSentinelIncident -ResourceGroupName "myResourceGroupName" -WorkspaceName "myWorkspaceName" -Id "4a21e485-75ae-48b3-a7b9-e6a92bcfe434" -Title "Suspicious login activity" -Status "Active" -Severity "Medium" -OwnerAssignedTo "user@mydomain.local"
This command updates an incident by assigning an owner.
</details>
| Update-AzSentinelIncident -ResourceGroupName "myResourceGroupName" -WorkspaceName "myWorkspaceName" -Id "4a21e485-75ae-48b3-a7b9-e6a92bcfe434" -Title "Suspicious login activity" -Status "Active" -Severity "Medium" -OwnerAssignedTo "user@mydomain.local" | ||
| ``` | ||
|
|
||
| This command updates an incident by assigning an owner. |
| Update-AzSentinelIncident -ResourceGroupName "myResourceGroupName" -WorkspaceName "myWorkspaceName" -Id "4a21e485-75ae-48b3-a7b9-e6a92bcfe434" -Title "Suspicious login activity" -Status "Active" -Severity "Medium" -OwnerAssignedTo "user@mydomain.local" | ||
| ``` | ||
|
|
||
| This command updates an incident by assigning an owner. |
Comment on lines
98
to
100
| ```powershell | ||
| New-AzSentinelAlertRule -ResourceGroupName "myResourceGroup" -WorkspaceName "myWorkspaceName" -Kind Scheduled -Enabled -DisplayName "Powershell Execution Alert (Several Times per Hour)" -Severity Low -Query "SecurityEvent | where EventID == 4688" -QueryFrequency (New-TimeSpan -Hours 1) -QueryPeriod (New-TimeSpan -Hours 1) -TriggerThreshold 10 -TriggerOperator "GreaterThan" | ||
| New-AzSentinelAlertRule -ResourceGroupName "myResourceGroup" -WorkspaceName "myWorkspaceName" -Kind Scheduled -Enabled -DisplayName "Powershell Exection Alert (Several Times per Hour)" -Severity Low -Query "SecurityEvent | where EventId == 4688" -QueryFrequency (New-TimeSpan -Hours 1) -QueryPeriod (New-TimeSpan -Hours 1) -TriggerThreshold 10 | ||
| ``` |
| ### Example 5: Create a Scheduled Alert Rule | ||
| ```powershell | ||
| New-AzSentinelAlertRule -ResourceGroupName "myResourceGroup" -WorkspaceName "myWorkspaceName" -Kind Scheduled -Enabled -DisplayName "Powershell Execution Alert (Several Times per Hour)" -Severity Low -Query "SecurityEvent | where EventID == 4688" -QueryFrequency (New-TimeSpan -Hours 1) -QueryPeriod (New-TimeSpan -Hours 1) -TriggerThreshold 10 -TriggerOperator "GreaterThan" | ||
| New-AzSentinelAlertRule -ResourceGroupName "myResourceGroup" -WorkspaceName "myWorkspaceName" -Kind Scheduled -Enabled -DisplayName "Powershell Exection Alert (Several Times per Hour)" -Severity Low -Query "SecurityEvent | where EventId == 4688" -QueryFrequency (New-TimeSpan -Hours 1) -QueryPeriod (New-TimeSpan -Hours 1) -TriggerThreshold 10 |
| ``` | ||
|
|
||
| This command gets insights and activities for an Entity by object | ||
| This command gets insights and activies for an Entity by object |
Comment on lines
+70
to
+71
| $Entitys = Get-AzSentinelEntity -ResourceGroupName "myResourceGroupName" -workspaceName "myWorkspaceName" | ||
| $Entitys[0] | Get-AzSentinelEntity |
4 tasks
VeryEarly
approved these changes
Mar 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.
Description
#29247 by @Faizan-Alam-1
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.