fix broken links and remove unneeded sections

Author: glorialimicrosoft

articles/communication-services/concepts/advanced-messaging/whatsapp/template-messages.md

@@ -80,10 +80,6 @@ var sampleTemplate = new MessageTemplate(templateName, templateLanguage);
 For detailed examples and template supported scenarios by Advanced Messages SDK, see:
 - [WhatsApp Template Quickstart](../../../quickstarts/advanced-messaging/whatsapp/send-template-messages.md)
 
-## Authentication templates and BSUIDs
-
-Authentication templates that use one-tap, zero-tap, or copy code flows **require a phone number** as the recipient. You can't use a business-scoped user ID (BSUID) to send these authentication template types. All other template types support both phone numbers and BSUIDs. For more information about BSUIDs, see [WhatsApp usernames and BSUIDs](./whatsapp-usernames-bsuid.md).
-
 ## Next steps
 
 -   [Get started with advanced communication messages SDK](../../../quickstarts/advanced-messaging/whatsapp/get-started.md)

articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-bsuid.md

@@ -17,8 +17,6 @@ WhatsApp is launching usernames in 2026. Usernames are an optional feature that
 
 This article explains what BSUIDs are, how they affect Azure Communication Services Advanced Messaging, and how to prepare your integration.
 
-[!INCLUDE [Survey Request](../../../includes/survey-request.md)]
-
 ## What is a BSUID?
 
 A business-scoped user ID (BSUID) is a unique, opaque identifier that Meta assigns to a WhatsApp user within a specific business portfolio. BSUIDs are:
@@ -147,7 +145,7 @@ Meta provides a Contact Book feature that automatically stores WhatsApp user con
 
 ## Limitations
 
-- **Authentication templates**: One-tap, zero-tap, and copy code [authentication templates](/azure/communication-services/concepts/advanced-messaging/whatsapp/template-messages) still require phone numbers. BSUIDs can't be used for these template types.
+- **Authentication templates**: One-tap, zero-tap, and copy code authentication templates still require phone numbers. BSUIDs can't be used for these template types.
 - **Portfolio scoping**: BSUIDs are scoped to individual business portfolios and can't be used across different portfolios.
 - **Contact Book**: Only captures interactions after launch. No retroactive data.
 

articles/event-grid/communication-services-advanced-messaging-events.md

@@ -44,7 +44,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-bsuid). |
+| 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](/articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-bsuid). |
 | 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.  |
@@ -354,7 +354,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-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](/articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-bsuid). |
 | 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). |