updated by Account=tolower(Account)

[v-muuppugund]

Required items, please complete

Change(s):

• "By Account" changed to "By Account=tolower(Account)"

Reason for Change(s):

• As part of github issue(invalid formatting for analytics rule "Multiple RDP connections from Single System" #9376)

Version Updated:
-1.2.6

• See guidance below

Testing Completed:

• Yes

Checked that the validations are passing and have addressed any issues that are present:

• See guidance below

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.

Details of the code changes in your submitted PR. Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process. Providing associated Issues that this resolves also easily connects the reason.

Change(s):

• Updated syntax for XYZ.yaml

Reason for Change(s):

• New schema used for XYZ.yaml
• Resolves ISSUE Add Logstash required version to Readme file #1234

Version updated:

• Yes
• Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly. If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

• Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

• Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

• Guidance for Detection checks
• General contribution guidance
• PR validation troubleshooting

---

[github-actions]

Hello how are you I am GitHub bot
😀😀
I see that you changed templates under the detections/analytic rules folder. Did you remember to update the version of the templates you changed?
If not, and if you want customers to be aware that a new version of this template is available, please update the version property of the template you changed.

[github-actions]

Hello how are you I am GitHub bot
😀😀
I see that you changed templates under the detections/analytic rules folder. Did you remember to update the version of the templates you changed?
If not, and if you want customers to be aware that a new version of this template is available, please update the version property of the template you changed.

[github-actions]

Hello how are you I am GitHub bot
😀😀
I see that you changed templates under the detections/analytic rules folder. Did you remember to update the version of the templates you changed?
If not, and if you want customers to be aware that a new version of this template is available, please update the version property of the template you changed.

[contentautomationbot]

KQL Best Practices Suggestions for: RDP_MultipleConnectionsFromSingleSystem.yaml

1. Don't use '*' for searching text. Look in a specific column.
2. Consider using the materialize() function for the 'endtime' variable if its assignment involves computation or calculation. This can improve performance.
3. Consider using the materialize() function for the 'starttime' variable if its assignment involves computation or calculation. This can improve performance.
4. Consider using Col =~ "lowercasestring" instead of tolower(Col) == "lowercasestring" for case-insensitive comparisons.
5. Avoid filtering on calculated columns like 'LogonType'. Use in the format of 'T | where predicate(columnName == value)' instead of 'T | extend _value = Expression | where predicate(_value)'.
6. Avoid filtering on calculated columns like 'LogonType'. Use in the format of 'T | where predicate(columnName == value)' instead of 'T | extend _value = Expression | where predicate(_value)'.
7. Consider using hint.shufflekey=key with the summarize operator when group by keys have high cardinality.
8. Consider using hint.strategy=broadcast when the left side is small and the right side is large.
9. Consider using the lookup operator instead of join when the right side is small and the left side is large.
10. Consider using hint.shufflekey= when both sides are too large.

Disclaimer: These suggestions are offered to enhance query efficiency and adherence to best practices. It is recommended to consider applying them for improved code quality, but their application is optional and context-dependent.

[v-sudkharat]

Verified the changes, look's good.