add s a note clarifying sending to a BSUID is not yet available until June 2026

Author: glorialimicrosoft

articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview.md

@@ -31,7 +31,7 @@ The key features of Azure Communications Services Advanced Messaging for WhatsAp
 
 ## WhatsApp usernames and business-scoped user IDs
 
-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 can be used as recipient identifiers in send requests.
+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).

articles/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-usernames-business-scoped-user-identifier.md

@@ -32,6 +32,9 @@ A business-scoped user ID (BSUID) is a unique, opaque identifier that Meta assig
 
 ## Impact on outbound messages
 
+> [!NOTE]
+> Sending messages to BSUIDs will be available starting in June 2026, when Meta rolls out the WhatsApp username feature to end users. Until then, the `to` field only supports phone numbers.
+
 The existing `to` field in the Send Notification API now accepts either a phone number or a BSUID. The service automatically detects the format and routes accordingly. No new fields are needed.
 
 **Send to a phone number (existing behavior):**
@@ -160,16 +163,15 @@ To prepare your integration for WhatsApp usernames and BSUIDs:
 
 2. **Process `fromBSUID` and `toBSUID` fields.** Update your event handlers to read the new BSUID fields in [AdvancedMessageReceived](../../../../event-grid/communication-services-advanced-messaging-events.md#microsoftcommunicationadvancedmessagereceived-event) and [AdvancedMessageDeliveryStatusUpdated](../../../../event-grid/communication-services-advanced-messaging-events.md#microsoftcommunicationadvancedmessagedeliverystatusupdated-event) events.
 
-3. **Update outbound messaging logic.** When replying to a username-only user, use the BSUID from the `fromBSUID` field as the `to` value in your send request.
+3. **Update outbound messaging logic.** When replying to a username-only user, use the BSUID from the `fromBSUID` field as the `to` value in your send request. Sending to BSUIDs will be available starting in June 2026.
 
 ## Key timeline
 
 | Date | Milestone |
 |------|-----------|
 | March 31, 2026 | BSUIDs begin appearing in production webhook payloads |
 | Early April 2026 | Contact Book feature launches |
-| May 2026 | APIs support sending messages to BSUIDs |
-| June 2026 | WhatsApp begins rolling out usernames to end users |
+| June 2026 | Sending messages to BSUIDs available in production; WhatsApp begins rolling out usernames to end users |
 
 ## Related content
 

articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-java.md

@@ -155,4 +155,7 @@ List<String> recipientList = new ArrayList<>();
 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).

articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-javascript.md

@@ -166,4 +166,7 @@ Example using a BSUID:
 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).

articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-net.md

@@ -60,6 +60,9 @@ Example using a BSUID:
 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).
 
 ### Start sending messages between a business and a WhatsApp user

articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-python.md

@@ -157,6 +157,9 @@ Usage example with a BSUID:
     to=["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).
 
 ### Start sending messages between a business and a WhatsApp user