Skip to content

Conversation

xuegao112
Copy link

Updated the email subject example in the alert customization documentation to use the correct syntax for array fields in the common alert schema. Replaced ${data.essentials.alertTargetIDs} with ${data.essentials.alertTargetIDs[0]}, since alertTargetIDs is an array and must be accessed with an index.

Updated the email subject example in the alert customization documentation to use the correct syntax for array fields in the common alert schema. 
Replaced `${data.essentials.alertTargetIDs}` with `${data.essentials.alertTargetIDs[0]}`, since `alertTargetIDs` is an array and must be accessed with an index.
Copy link
Contributor

@xuegao112 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit cf25588:

✅ Validation status: passed

File Status Preview URL Details
articles/azure-monitor/alerts/alerts-customize-email-subject-how-to.md ✅Succeeded

For more details, please refer to the build report.

@ttorble ttorble requested a review from Copilot September 29, 2025 14:57
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes an incorrect email subject example in the Azure Monitor alert customization documentation by properly accessing array elements in the common alert schema.

  • Updated email subject template to use proper array indexing syntax
  • Corrected alertTargetIDs reference to access the first element with [0]

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@ttorble
Copy link
Contributor

ttorble commented Sep 29, 2025

@xuegao112 did you intend to open this PR in the private repo? It looks like you have access to the private repo, and if so, you should use that for content updates. I'll leave this PR open in case @IngridAtMicrosoft wants to review it here. If you decide to open a new PR in the private repo, please close this PR. Thanks.

@IngridAtMicrosoft

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants