WhatsApp channel fails with "no WhatsApp accounts associated" despite correctly linked ACS resource - same agent works fine on Teams

Adilson Capaia 0 Reputation points
2026-09-10T09:47:25.8866667+00:00

I'm trying to connect a Copilot Studio agent to WhatsApp via Azure Communication Services (ACS). The ACS side confirms the WhatsApp Business Account is correctly linked, but Copilot Studio's Channels > WhatsApp screen reports "There are no WhatsApp accounts associated with the selected Azure Communication Services resource" when selecting the subscription and ACS resource. The same agent connects successfully to the Microsoft 365 and Teams channel without any issue, which rules out a broken bot registration.

Environment details

  • Environment type: Developer
  • Region: Europe
  • Environment URL: trd-blog-deve.crm4.dynamics.com
  • Environment ID: 5907187c-555a-ee2c-a6ce-321c4307b551
  • Organization ID: c70c3aef-a55d-f111-9bb3-000d3adc9f5f
  • Tenant ID: b1578f2c-f814-4f0c-a2c6-c4a382ed34c9
  • Agent (bot) schema name: trd_AgentTRDProspection

What's already verified/configured correctly on the Azure side

  • ACS resource "ACS-For-Agent-TRD" exists in the same tenant as the Copilot Studio environment
  • WhatsApp Business Account ("The Rational Developer") is linked to the ACS resource, Channel ID and Sender ID (+33 7 59 22 11 38) are populated and visible in the Azure portal
  • Contributor role assigned to both "Power Virtual Agents" and "Microsoft Copilot Studio Service" enterprise applications, at the resource, resource group, AND subscription level (tested progressively widening scope)
  • My own account has Owner role on the subscription (not just Contributor) - Microsoft.EventGrid resource provider is Registered on the subscription
  • Same agent's Microsoft 365/Teams channel connects and works correctly (confirmed via "Added successfully" and direct chat in Teams)

Steps to reproduce

  1. Open the agent in Copilot Studio > Settings > Channels > WhatsApp
  2. Select the Azure subscription (1 of 1 available)
  3. Select the ACS resource "ACS-For-Agent-TRD"
  4. Error appears: "There are no WhatsApp accounts associated with the selected Azure Communication Services resource. Please select a different resource or subscription." This has persisted for over 24 hours, ruling out normal Azure RBAC propagation delay.

Console evidence

When the WhatsApp channel panel is open, the following request returns 404: powervamg.eu-il109.gateway.prod.island.powerapps.com/chatbotmanagement/tenants/b1578f2c-f814-4f0c-a2c6-c4a382ed34c9/environments/5907187c-555a-ee2c-a6ce-321c4307b551/bots/trd_AgentTRDProspection/api/channels/whatsapp Failed to load resource: the server responded with a status of 404 () Note the gateway hostname includes "island" (eu-il109.gateway.prod.island.powerapps.com) - flagging in case this cluster type has any relevant limitation for WhatsApp channel provisioning.

Question

Given that ACS-side configuration is confirmed correct and the same agent works fine on other channels, is this a known issue with WhatsApp channel discovery on Developer-type environments, or specific to this "island" cluster? Is there a way to confirm which cluster/backend is expected to serve this bot, or to move the agent to a different one?

Microsoft Copilot | Microsoft 365 Copilot | Development
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anusha Saraswat 0 Reputation points
    2026-09-10T10:07:45.61+00:00

    Based on your description, my main observation is that the issue does not appear to be ACS or RBAC related, since the WhatsApp Business Account is already linked to ACS, the required permissions are in place, and the same Copilot Studio agent works successfully on Teams and Microsoft 365.

    What stands out is the 404 response from the /api/channels/whatsapp endpoint. Instead of simply returning no senders, the backend itself seems unable to serve the WhatsApp channel request, which may indicate an environment or backend provisioning issue.

    Suggestions:

    1. Verify that the WhatsApp sender/display name is fully approved and active in Meta and ACS.
    2. Test the same ACS resource from a different Copilot Studio environment (Sandbox or Production, if available).
    3. Create a new test agent in the current environment to see if the behavior is agent-specific or environment-wide.
    4. Capture a HAR trace and open a Microsoft Support ticket, including the Environment ID, Tenant ID, ACS resource name, and the failing 404 request. Given the evidence, I would lean more toward an environment/backend provisioning issue (possibly related to the Developer environment) than a WhatsApp configuration problem on the Azure side.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.