Share via

How to fix the Error (Error connecting to WhatsApp phone number. Please try again.) when I deploy Copilot Studio agent to WhatsApp Channel?

Justin van Heerden 20 Reputation points
2026-03-17T14:05:45.9133333+00:00

I’m trying to deploy a chatbot built in Copilot Studio to the WhatsApp channel via Azure Communication Services (ACS), but I keep hitting an error.

Issue: On Copilot Studio, on the channels tab, I select Whatsapp. Then I select my Azure Subscription and my Azure Communication Service resource. When I press continue I get this error message:

"Error connecting to WhatsApp phone number. Please try again."

User's image

The following prerequisites have been completed:

  • Created an Azure Communication Services resource.
  • Obtained a phone number (Microsoft-provided virtual number) which is recognized in Meta Account WhatsApp Manager.
  • Connected the WhatsApp Business Account as a channel in ACS. (Channel status is active)
  • Set up and deployed Event Grid Viewer, subscribed to SMS received events
  • Created an event subscription that sends incoming messages to the WhatsApp channel ID with Microsoft Entra app authentication.
  • Verified that the Azure Tenant ID matches Copilot Studio agent tenant ID.

The agent requires conversation handover. Therefore, the copilot agent was connected to Dynamics 365 Customer Service.

A WhatsApp account was created in Dynamics Copilot Service Admin Centre with the ACS information. The agent was connected to a workstream in Dynamics with this WhatsApp channel, which allowed WhatsApp communication between the user and the copilot bot.

However, the adaptive cards do not function correctly on the workstream connection. After reviewing this guideline, we need the WhatsApp channel to be connected to implement adaptive cards.

https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-whatsapp

We disconnected the agent from the workstream and in Copilot Studio tried to connect WhatsApp channel.

However, the WhatsApp channel in copilot studio shows the above mentioned error.

When we inspect the devtools while creating the account we get an 403 error with this response:

{

"Error": {

"RetryIn": null,

"InnerErrors": [],

"Code": "VoiceProvisioningForbidden",

"Message": "User doesn't have enough rights to assign role b24988ac-6180-42a0-ab88-20f7382dd24c to service principal <the service principal id>",

"Properties": {},

"Diagnostics": null

}

}

  • According to the docs the role id: b24988ac-6180-42a0-ab88-20f7382dd24c refers to the Contributor role
  • <the service principal id> refers to an Enterprise application called Power Virtual Agents Service

Any guidance regarding this issue would be greatly appreciated.

Microsoft Copilot | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-17T14:06:22.09+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The 403 VoiceProvisioningForbidden error with message User doesn't have enough rights to assign role b24988ac-6180-42a0-ab88-20f7382dd24c to service principal <Power Virtual Agents Service> indicates a permission issue in Azure when Copilot Studio tries to complete the WhatsApp–ACS wiring.

    To resolve the Copilot Studio error “Error connecting to WhatsApp phone number. Please try again.” in this scenario, ensure the following are in place and then retry the WhatsApp channel configuration in Copilot Studio:

    1. In Azure, assign the required role to the Power Virtual Agents Service enterprise application
      • Identify the service principal shown in the error (the enterprise application “Power Virtual Agents Service”).
      • In the Azure portal, on the subscription or resource group that contains the Azure Communication Services (ACS) resource, assign the built‑in Contributor role (ID b24988ac-6180-42a0-ab88-20f7382dd24c) to this service principal.
      • This allows Copilot Studio to perform the provisioning operations against ACS and the phone number on your behalf.
    2. Verify ACS and WhatsApp channel prerequisites are fully satisfied
      • Confirm the WhatsApp Business Account is correctly connected as a channel in the ACS resource and that the channel status is Active, as required in the WhatsApp channel prerequisites.
      • Ensure the phone number used is the same one that was provisioned in ACS and linked in Meta’s WhatsApp Business Manager. The number must be unique to this WhatsApp Business Account and not used elsewhere.
      • Make sure the Event Grid Viewer and SMS Received event subscription are still active so that verification codes and events can flow correctly while connecting WhatsApp to ACS.
    3. Reconnect the Copilot Studio agent to WhatsApp
      • In Copilot Studio, set the agent authentication to either No authentication or Authenticate manually, as required for WhatsApp.
      • Publish the agent.
      • Go to Channels → WhatsApp, select the same Azure subscription and ACS resource, then select the phone number and choose Deploy.
      • After permissions are corrected, the deployment should complete and display the QR code for testing the WhatsApp channel.
    4. If the number was previously used only via Dynamics 365 Customer Service
      • Ensure the ACS WhatsApp channel remains active and correctly configured there (channel ID, Event Grid app ID, tenant ID, connection string, and channel ID all matching the ACS resource details).
      • Disconnecting the agent from the Dynamics workstream is fine, but the underlying ACS configuration must remain valid so Copilot Studio can bind directly to the same ACS WhatsApp channel.

    Once the Contributor role is granted to the Power Virtual Agents Service service principal and all ACS/WhatsApp prerequisites are intact, the Copilot Studio WhatsApp channel deployment should succeed and allow use of adaptive cards over the WhatsApp channel as described in the publication guidance.

    References:

    1 person found this answer helpful.

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.