ACS Advanced Messaging: WhatsApp channel stuck in Disconnected state, GET /messages/channels returns 404, cannot re-register phone number

Question

Environment

• Resource: CommunicationAbanteResource (Resource Group: AbanteApplications)
• • Subscription: DataX DEV (b2c447f4-0f0b-471d-a130-0c72330f08f2)
  • • ACS Endpoint: https://communicationabanteresource.europe.communication.azure.com
    • • **immutableResourceId `5c5fd832-8038-4a87-9383-7626e72bb381**
      • • dataLocation: Europe

      • Problem

    • Our WhatsApp channel in ACS Advanced Messaging is stuck in "Disconnected" state. We are in a circular deadlock that we cannot break:
  • 1. The ACS portal shows the channel as "Disconnected" (Channel ID: 9ef28af4-b40e-4861-a899-53b6d49e6a2c, Phone: +34 695 25 71 31)
    2. 1. Attempting to re-register the phone number via Meta Embedded Signup fails with: "A communication resource is already registered to the selected phone number"
       2. 1. Attempting to DELETE the channel via API also fails (see below)
          2. 1. Copilot Studio shows: "There are no WhatsApp accounts associated with the selected Azure Communication Services resource"

          3. API Calls Attempted (all fail)

       3. GET /messages/channels — tested with Bearer token (az account get-access-token --resource https://communication.azure.com) and HMAC auth:

    3.        
              GET https://communicationabanteresource.europe.communication.azure.com/messages/channels?api-version=2024-02-01
              → HTTP 404
              
              Tested all available versions: 2024-02-01, 2024-05-01, 2024-08-01, 2024-02-01-preview, 2025-01-15-preview
              → ALL return HTTP 404
       

       DELETE /messages/channels/{channelId}:

              DELETE https://communicationabanteresource.europe.communication.azure.com/messages/channels/9ef28af4-b40e-4861-a899-53b6d49e6a2c?api-version=2024-02-01
              → HTTP 404
       

       Alternative paths tested (all return 404):
       • /messages/whatsapp/channels
       • /messages/registrations
       • /messages/whatsapp/registrations
       • /advanced-messaging/channels

       Channel Details

       • Channel ID: 9ef28af4-b40e-4861-a899-53b6d49e6a2c
       • Phone number: +34 695 25 71 31
       • WABA ID: 810430461525595
       • Meta Business Manager ID: 923609700643487
       • Status in portal: Disconnected

       Request

       Please reset or delete the internal phone number binding for channel 9ef28af4-b40e-4861-a899-53b6d49e6a2c on resource CommunicationAbanteResource, OR restore the channel status to "Connected" so we can use the channel again with Copilot Studio. The Azure Support portal shows our subscription is on the Basic plan which does not allow technical tickets — that is why we are posting here.

Answer 1

Hello @Pablo Amián Sánchez

Thank you for reaching out Microsoft Q&A.

Azure Communication Services (ACS) Advanced Messaging for WhatsApp does not expose any public API to list, delete, reset, or manage WhatsApp channels. Channel lifecycle operations are supported only through the Azure portal using Meta’s embedded signup flow. As a result, endpoints such as /messages/channels or /messages/whatsapp/* are not part of the documented API surface and correctly return HTTP 404.

Microsoft documentation also states that, to register a WhatsApp channel, the phone number must not already be associated with another WhatsApp Business Account. If a channel appears as Disconnected and re‑registration fails with “a communication resource is already registered,” the documentation does not define a self‑service recovery or reset mechanism.

In short:

• 404 responses are expected (no supported channel‑management APIs)
• WhatsApp channels can only be managed via the Azure portal
• There is no documented way to force‑delete or reset a stuck WhatsApp channel
• If portal reconnection fails despite meeting prerequisites, the issue is outside documented self‑service capabilities and requires Microsoft backend handling

References (Microsoft Learn):

• https://learn.microsoft.com/en-us/azure/communication-services/concepts/advanced-messaging/whatsapp…
• https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/advanced-messaging/whats…

If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you

Answer 2

The WhatsApp channel in Azure Communication Services with status Disconnected cannot be reused directly and requires a full re-registration flow. The documented behavior for this status is:

• Disconnected: “A WhatsApp account is disconnected from the Azure portal side.
  • If the WhatsApp Business account is no longer needed, unshare or delete it in the WhatsApp Manager portal.
  • If the WhatsApp Business account should remain connected, redo the registration process by disconnecting then reconnecting the account.”

For a Disconnected WhatsApp account, the supported recovery path is:

1. In the Azure portal, go to the Azure Communication Services resource → Advanced Messaging → Channels and use Disconnect on the affected WhatsApp account if available.
2. In the Meta/WhatsApp Manager portal:
   • Unshare the WhatsApp Business Account or delete the phone number or the WhatsApp Business Account associated with +34 695 25 71 31.
   • This clears the “phone number already shared/locked” condition on the Meta side.
3. After the number is unshared/deleted on Meta, redo the Register WhatsApp Business account flow for Advanced Messaging:
   • Select or create the WhatsApp Business profile.
   • Add and verify the phone number again (using SMS/text verification as described).
4. Once Meta completes the display name/phone number review and the status in Azure shows Active, the WhatsApp Business account can again be:
   • Used without messaging limits, and
   • Linked as a channel in Microsoft Copilot Studio or Dynamics 365 Contact Center.

If the same WhatsApp Business Account and phone number have been used multiple times, Meta may have the number in a locked state. The documented remediation is:

• “If you try to create a WhatsApp channel multiple times using the same WhatsApp Business Account and Phone Number, you might encounter errors because the Phone Number is already shared with Microsoft and locked. To fix the problem, delete the Phone Number and WhatsApp Business Account on the META portal. If you can't delete your WhatsApp Business Account, open a Support Case for manual assistance.”

Because the 404 responses on the /messages/channels APIs are not covered in the documentation and the internal binding reset is not exposed via public APIs, resolving the circular state requires:

• Cleaning up the phone number and account sharing on the Meta side as above, and
• If that still does not allow re-registration, opening a support case with Microsoft (Azure/Communication Services) or Meta as indicated, so the backend lock can be cleared manually.

Once the WhatsApp Business account is back to Active in the Azure portal, it can be linked again as a channel in Copilot Studio or Dynamics 365 Contact Center following the documented steps.

---

References:

• Prerequisites to Configure WhatsApp as a Channel in Microsoft Copilot Studio
• Register WhatsApp Business Account
• Configure a WhatsApp channel through Azure Communication Services