Error creating channel in advanced messaging

HI @Yves Blancquaert

Thank you for contacting us about the Azure portal cannot render or retrieve Advanced Messaging Channels for your ACS issue. We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this.

HI @Yves Blancquaert

Thank you for reaching us. The error message you’re seeing (“Error while retrieving the Advanced Messaging Channels” with a renderComponentIntoRoot failure) usually indicates a portal blade rendering issue or a WhatsApp Business Account (WABA) onboarding state that is preventing channel creation. We’ll guide you through the steps to resolve this.

Could you please follow these steps:

1. Refresh and do a clean reload of the Azure portal.

• Click Refresh on the Channels blade.
• If the issue persists:
• Try using an Incognito/Private window in Edge, Chrome, or Firefox.
• Clear site data for portal.azure.com.
• Force a fresh portal extension load by opening: https://portal.azure.com/?feature.microsoftextra=stage4

1. Verify your WhatsApp Business Account (WABA) on Meta
   • Navigate to Meta Business Manager >Business Settings > WhatsApp Accounts:
   • Check that your WABA is active and verified.
   • Make sure the phone number is not already linked to another provider (such as Twilio or 360dialog). If it is, disconnect it from there first.
   • Verify that the display name is approved and there are no policy violations.
   Note: If you have previously attempted to connect the same WABA and phone number, the number might be locked on Meta’s side. In that case, remove the phone number and WABA from the Meta portal, wait a few minutes, and then try connecting to Azure again.
2. Reconnect the WhatsApp channel in Azure
   • Go to your ACS resource > Messaging >Channels > WhatsApp:
   • If you see a Disconnect option, click it first, then select Connect.
   • Complete the steps as prompted, including signing in to Meta and making any necessary selections.
   • Once connected, you’ll see a Channel Registration ID (GUID). Be sure to save this, as it’s needed for sending messages using SDKs and tools like Power Automate or Copilot Studio.
3. Conduct an end-to-end flow test by sending a basic template message through the ACS Advanced Messaging SDK quickstart to verify connectivity.

Reference :

https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/advanced-messaging/whatsapp/connect-whatsapp-business-account

https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/advanced-messaging/whatsapp/get-started?tabs=visual-studio%2Cconnection-string&pivots=programming-language-javascript

https://learn.microsoft.com/en-us/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview

https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/advanced-messaging/whatsapp/connect-whatsapp-business-account#troubleshooting

let us know if the above helps or you need further assistance on this issue.

Hi,

I've tried everything you proposed but without success. I keep getting the same error messages.

Best regards

Yves

HI @Yves Blancquaert

Thank you for providing the screenshots and letting us know which steps you’ve completed. To ensure we offer the best possible solution and prevent any delays, could you share the following details.

1. Environment Details

• Which Azure region is your ACS resource located in?
• Are you accessing it through the https://portal.azure.com or the https://preview.portal.azure.com??

2. Access & Permissions

• What is your role on the ACS resource? (Owner / Contributor / Reader)
• Are you using a service principal or a user account for this task?

3. WhatsApp Business Account (WABA) Status

• Is your WABA verified and active in Meta Business Manager?
• Has the phone number been previously linked to another provider (such as Twilio or 360dialog)?
• If so, was it disconnected before you tried connecting it in Azure?

4. Portal Behavior

• Does the error only appear in the Channels blade, or in other ACS blades too?
• Have you tried using Incognito/Private mode or clearing your browser cache and site data?

5. Network & Security

• Are you behind a corporate proxy or firewall that could block portal resources?
• Can you reproduce the issue on another network, such as from home or a mobile hotspot?

6. Diagnostics

• Please share:
• The Session ID from the error page
• Extension name and error summary content
• Any browser console logs or HAR file captured during the error

7. Additional Context

• Have you connected this WABA and phone number to Azure before?
• If yes, did you remove them from Meta before trying again?

Once we have this information, we can adjust our troubleshooting steps to help resolve the issue more effectively.

1. Environment Details

• Which Azure region is your ACS resource located in?
  • Global
• Are you accessing it through the https://portal.azure.com or the https://preview.portal.azure.com??
  • portal.azure.com

1. Access & Permissions

• What is your role on the ACS resource? (Owner / Contributor / Reader)
  • Owner
• Are you using a service principal or a user account for this task?
  • User account

1. WhatsApp Business Account (WABA) Status

• Is your WABA verified and active in Meta Business Manager?
  • Yes
• Has the phone number been previously linked to another provider (such as Twilio or 360dialog)?
  • No
• If so, was it disconnected before you tried connecting it in Azure?

1. Portal Behavior

• Does the error only appear in the Channels blade, or in other ACS blades too?
  • Also in Try Advanced Messaging, Channels and Templates (everything under Advanced Messaging)
• Have you tried using Incognito/Private mode or clearing your browser cache and site data?
  • Yes

1. Network & Security

• Are you behind a corporate proxy or firewall that could block portal resources?
  • No
• Can you reproduce the issue on another network, such as from home or a mobile hotspot?
  • Yes

1. Diagnostics

• Please share:
• The Session ID from the error page
  • 9695269784c34fbeb8a0ca98d61a2707
• Extension name and error summary content
  • Microsoft_Azure_CommunicationServices
  • { "shellProps": { "sessionId": "9695269784c34fbeb8a0ca98d61a2707", "extName": "Microsoft_Azure_CommunicationServices", "contentName": "WhatsAppSandboxOverview.ReactView" }, "error": { "message": "The renderComponentIntoRoot component encountered an error while loading.", "metadata": { "area": "renderComponentIntoRoot" }, "error": { "data": { "message": "The renderComponentIntoRoot component encountered an error while loading.", "metadata": { "area": "renderComponentIntoRoot" }, "capturedErrors": [ { "message": "Error caught in error boundary", "metadata": { "area": "renderComponentIntoRoot", "error": { "stack": "TypeError: Cannot read properties of undefined (reading 'keyword')\n at Ol.render (https://hosting.portal.azure.net/communicationservices/Content/Dynamic/a_irRP7fl22T.js:3:3983453)\n at _u (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:77366)\n at Cu (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:77165)\n at wi (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:120203)\n at vs (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:108502)\n at hs (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:108430)\n at ms (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:108293)\n at rs (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:105128)\n at ts (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:12:103683)\n at w (https://portal.azure.com/Content/Dynamic/EdO70eIAM6Rz.js:100:1374)", "message": "Cannot read properties of undefined (reading 'keyword')", "name": "TypeError" }, "errorInfo": { "componentStack": "\n at Ol (https://hosting.portal.azure.net/communicationservices/Content/Dynamic/a_irRP7fl22T.js:3:3979839)\n at s (https://portal.azure.com/Content/Dynamic/xklDvMkw_kKn.js:19:1836)\n at Ol\n at div\n at div\n at div\n at t.FocusRectsProvider (https://portal.azure.com/Content/Dynamic/5C-Pwu8-YfQb.js:292:273)\n at https://portal.azure.com/Content/Dynamic/5C-Pwu8-YfQb.js:150:477\n at https://portal.azure.com/Content/Dynamic/5C-Pwu8-YfQb.js:354:479\n at t (https://portal.azure.com/Content/Dynamic/5C-Pwu8-YfQb.js:312:430)\n at div\n at t.FocusRectsProvider (https://portal.azure.com/Content/Dynamic/5C-Pwu8-YfQb.js:292:273)\n at https://portal.azure.com/Content/Dynamic/5C-Pwu8-YfQb.js:201:437\n at t.ThemedFabric (https://portal.azure.com/Content/Dynamic/TQMpjQyEJy9V.js:9:1625)\n at o (https://portal.azure.com/Content/Dynamic/fgUGv-bLtanQ.js:51:455)" } } } ] } }, "code": null }}
• Any browser console logs or HAR file captured during the error
  • See below

1. Additional Context

• Have you connected this WABA and phone number to Azure before?
  • No
• If yes, did you remove them from Meta before trying again?