From cf25588a6297a7de4716ce87e556501bb7a347fc Mon Sep 17 00:00:00 2001
From: CCWit <63446094+xuegao112@users.noreply.github.com>
Date: Mon, 29 Sep 2025 16:50:49 +0800
Subject: [PATCH] Update email subject example to use first alert target

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.
---
 .../alerts/alerts-customize-email-subject-how-to.md             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/azure-monitor/alerts/alerts-customize-email-subject-how-to.md b/articles/azure-monitor/alerts/alerts-customize-email-subject-how-to.md
index 85eedee490..9168ccdf7e 100644
--- a/articles/azure-monitor/alerts/alerts-customize-email-subject-how-to.md
+++ b/articles/azure-monitor/alerts/alerts-customize-email-subject-how-to.md
@@ -36,7 +36,7 @@ The format for extracting a dynamic value from the alert payload is: `${<path to
 
 This example creates an email subject containing the affected resource and whether it was fired or resolved. 
 
-- Value: "Alert ${data.essentials.monitorCondition} on ${data.essentials.alertTargetIDs}"
+- Value: "Alert ${data.essentials.monitorCondition} on ${data.essentials.alertTargetIDs[0]}"
 - Potential results:
   - Alert Fired on VM1.
   - Alert Resolved on VM1.