another attempt to fix the filename-incomplete suggestion

glorialimicrosoft · glorialimicrosoft · commit 3bd5106c03dd · 2026-04-03T14:35:50.000-07:00
diff --git a/articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview.md b/articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview.md
@@ -34,7 +34,7 @@ The key features of Azure Communications Services Advanced Messaging for WhatsAp
 WhatsApp is launching usernames in 2026, allowing users to display a username instead of their phone number. To support this change, Meta introduces a new identifier called the **business-scoped user ID (BSUID)**. BSUIDs begin appearing in webhook payloads and will be supported as recipient identifiers in send requests starting in June 2026.
 
 > [!WARNING]
-> **Breaking change:** The `from` and `to` fields in Advanced Messaging events may now be empty when a user hides their phone number. Update your event handlers to use the new `fromBSUID` and `toBSUID` fields. For more information, see [WhatsApp usernames and BSUIDs](./whatsapp-usernames-business-scoped-user-identifier.md).
+> **Breaking change:** The `from` and `to` fields in Advanced Messaging events may now be empty when a user hides their phone number. Update your event handlers to use the new `fromBSUID` and `toBSUID` fields. For more information, see [WhatsApp usernames and BSUIDs](./whatsapp-usernames-overview.md).
 
 ## Next steps
 
diff --git a/articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md b/articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md
diff --git a/articles/communication-services/quickstarts/advanced-messaging/whatsapp/handle-advanced-messaging-events.md b/articles/communication-services/quickstarts/advanced-messaging/whatsapp/handle-advanced-messaging-events.md
@@ -97,11 +97,11 @@ With the introduction of WhatsApp usernames, Advanced Messaging events now inclu
 - **`AdvancedMessageDeliveryStatusUpdated`** events include a `toBSUID` field with the recipient's BSUID.
 
 > [!WARNING]
-> **Breaking change:** The existing `from` and `to` fields may now be empty or null when a WhatsApp user has adopted a username and hidden their phone number. Update your event handlers accordingly. For more information, see [WhatsApp usernames and BSUIDs](../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md).
+> **Breaking change:** The existing `from` and `to` fields may now be empty or null when a WhatsApp user has adopted a username and hidden their phone number. Update your event handlers accordingly. For more information, see [WhatsApp usernames and BSUIDs](../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md).
 
 ## Next steps
 
 - [Understand Advanced Communication Messages Events](../../../../event-grid/communication-services-advanced-messaging-events.md)
-- [WhatsApp usernames and BSUIDs](../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md)
+- [WhatsApp usernames and BSUIDs](../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md)
 - [Get started With Advanced Communication Messages SDK](./get-started.md)
 
diff --git a/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-java.md b/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-java.md
@@ -158,4 +158,4 @@ recipientList.add("US.13491208655302741918");
 > [!NOTE]
 > Sending messages to BSUIDs will be available starting in June 2026. Until then, use phone numbers as recipients.
 
-For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md).
+For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md).
diff --git a/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-javascript.md b/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-javascript.md
@@ -169,4 +169,4 @@ const recipientList = ["US.13491208655302741918"];
 > [!NOTE]
 > Sending messages to BSUIDs will be available starting in June 2026. Until then, use phone numbers as recipients.
 
-For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md).
+For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md).
diff --git a/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-net.md b/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-net.md
@@ -63,7 +63,7 @@ var recipientList = new List<string> { "US.13491208655302741918" };
 > [!NOTE]
 > Sending messages to BSUIDs will be available starting in June 2026. Until then, use phone numbers as recipients.
 
-For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md).
+For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md).
 
 ### Start sending messages between a business and a WhatsApp user
 
diff --git a/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-python.md b/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-python.md
@@ -160,7 +160,7 @@ Usage example with a BSUID:
 > [!NOTE]
 > Sending messages to BSUIDs will be available starting in June 2026. Until then, use phone numbers as recipients.
 
-For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md).
+For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](../../../../concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md).
 
 ### Start sending messages between a business and a WhatsApp user
 
diff --git a/articles/communication-services/toc.yml b/articles/communication-services/toc.yml
@@ -390,7 +390,7 @@ items:
   - name: Overview
     href: concepts/advanced-messaging/whatsapp/whatsapp-overview.md
   - name: WhatsApp usernames and BSUIDs
-    href: concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md
+    href: concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview.md
   - name: Pricing
     href: concepts/advanced-messaging/whatsapp/pricing.md
   - name: Advanced messaging for WhatsApp terms of service
diff --git a/articles/event-grid/communication-services-advanced-messaging-events.md b/articles/event-grid/communication-services-advanced-messaging-events.md
@@ -37,7 +37,7 @@ Example scenario: A WhatsApp user sends a WhatsApp message to a WhatsApp Busines
 #### Attribute list
 
 > [!WARNING]
-> **Breaking change:** The `from` field may now be empty when a WhatsApp user has adopted a username and hidden their phone number. Update your event handlers to use the new `fromBSUID` field instead of relying solely on `from`. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier).
+> **Breaking change:** The `from` field may now be empty when a WhatsApp user has adopted a username and hidden their phone number. Update your event handlers to use the new `fromBSUID` field instead of relying solely on `from`. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview).
 
 Details for the attributes specific to `Microsoft.Communication.AdvancedMessageReceived` events.
 
@@ -47,7 +47,7 @@ Details for the attributes specific to `Microsoft.Communication.AdvancedMessageR
 | messageId  | `string` | ❌ | Message Id of the message receive event as GUID. |
 | messageType  | `string` | ❌ | Message Type of the message receive event. Such as: `"interactive"`, `"sticker"`, `"reaction"`. |
 | from    | `string` | ✔️ | Sender ID that sent the message. May be empty when the sender has adopted a WhatsApp username and hidden their phone number.  |
-| fromBSUID | `string` | ✔️ | The sender's business-scoped user ID (BSUID). Present for all WhatsApp messages when available, regardless of whether the user adopted a username. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier). |
+| fromBSUID | `string` | ✔️ | The sender's business-scoped user ID (BSUID). Present for all WhatsApp messages when available, regardless of whether the user adopted a username. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview). |
 | to | `string` | ❌ | The channel ID that received the message, formatted as a GUID.  |
 | receivedTimestamp | `DateTimeOffset`   | ❌ | Timestamp when the message is received.|
 | content | `string` | ✔️ | The text content in the message.  |
@@ -351,7 +351,7 @@ Example scenario: Contoso uses an active Advanced Messaging channel connected to
 #### Attribute list
 
 > [!WARNING]
-> **Breaking change:** The `to` field may now be empty when the message was sent to a BSUID. Update your event handlers to use the new `toBSUID` field instead of relying solely on `to`. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier).
+> **Breaking change:** The `to` field may now be empty when the message was sent to a BSUID. Update your event handlers to use the new `toBSUID` field instead of relying solely on `to`. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview).
 
 Details for the attributes specific to `Microsoft.Communication.AdvancedMessageReceived` events.
 
@@ -360,7 +360,7 @@ Details for the attributes specific to `Microsoft.Communication.AdvancedMessageR
 | channelType | `string` | ❌ | Channel type of the channel that the message was sent on. |
 | from | `string` | ✔️ | The channel ID that sent the message, formatted as a GUID. |
 | to   | `string` | ✔️ | Recipient ID that the message was sent to. May be empty when the message was sent to a BSUID. |
-| toBSUID | `string` | ✔️ | The recipient's business-scoped user ID (BSUID). Present when available, regardless of whether the user adopted a username. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier). |
+| toBSUID | `string` | ✔️ | The recipient's business-scoped user ID (BSUID). Present when available, regardless of whether the user adopted a username. For more information, see [WhatsApp usernames and BSUIDs](/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-overview). |
 | receivedTimestamp | `DateTimeOffset` | ❌ | Timestamp of the message. |
 | messageId | `string` | ✔️ | The ID of the message, formatted as a GUID. |
 | status    | `string` | ✔️ | Status of the message. Possible values include `Sent`, `Delivered`, `Read`, and `Failed`. For more information, see [Status](#status). |
