WhatsApp Business number created in Meta but channel not appearing in Azure Communication Services

We are configuring WhatsApp Business with Azure Communication Services Advanced Messaging.

We are using an Azure Communication Services resource named nora-acs-whatsapp.

We completed the WhatsApp Embedded Signup process from Azure today. The process in Meta appears to have progressed successfully:

• The WhatsApp Business phone number was added successfully.
• The business/display name is NORA.
• Meta WhatsApp Manager shows the integration as Microsoft Azure.
• The phone number currently shows a Pending status in WhatsApp Manager.
• Meta Activity Log confirms that the phone number was added, display-name verification was requested, the Microsoft integration app was installed, and the required permissions were granted.

However, in Azure Portal:

Azure Communication Services → nora-acs-whatsapp → Advanced Messaging → Channels

the page still shows:

“No Channels to display.”

Therefore, Meta appears to have received and created the WhatsApp assets, but the corresponding WhatsApp channel was not created or is not visible in Azure Communication Services.

This is not a repeated registration attempt. We had previously started the setup process, but we stopped before registering the WhatsApp number because the required business website was not yet available. Today, after the website became available, we performed the actual registration process.

We have not deleted the phone number or WhatsApp Business Account and we have not attempted another registration after encountering this issue.

Could you please advise:

1. Should the WhatsApp channel already appear in Azure Communication Services while the Meta display-name/phone-number status is still Pending?
2. Is there a way to verify whether the channel registration exists in the ACS backend even though it does not appear in the Azure Portal?
3. Is this an expected provisioning delay, or does this indicate that the Embedded Signup process failed between Meta and Azure Communication Services?
4. Should we wait before retrying, or can Microsoft check/reset the incomplete channel registration without requiring us to delete the WhatsApp assets in Meta?

We would prefer not to retry or delete the existing WhatsApp assets until we know the backend state, to avoid creating a duplicate or locked registration.

Thank you.We are configuring WhatsApp Business with Azure Communication Services Advanced Messaging.

We are using an Azure Communication Services resource named nora-acs-whatsapp.

We completed the WhatsApp Embedded Signup process from Azure today. The process in Meta appears to have progressed successfully:

• The WhatsApp Business phone number was added successfully.
• The business/display name is NORA.
• Meta WhatsApp Manager shows the integration as Microsoft Azure.
• The phone number currently shows a Pending status in WhatsApp Manager.
• Meta Activity Log confirms that the phone number was added, display-name verification was requested, the Microsoft integration app was installed, and the required permissions were granted.

However, in Azure Portal:

Azure Communication Services → nora-acs-whatsapp → Advanced Messaging → Channels

the page still shows:

“No Channels to display.”

Therefore, Meta appears to have received and created the WhatsApp assets, but the corresponding WhatsApp channel was not created or is not visible in Azure Communication Services.

This is not a repeated registration attempt. We had previously started the setup process, but we stopped before registering the WhatsApp number because the required business website was not yet available. Today, after the website became available, we performed the actual registration process.

We have not deleted the phone number or WhatsApp Business Account and we have not attempted another registration after encountering this issue.

Could you please advise:

1. Should the WhatsApp channel already appear in Azure Communication Services while the Meta display-name/phone-number status is still Pending?
2. Is there a way to verify whether the channel registration exists in the ACS backend even though it does not appear in the Azure Portal?
3. Is this an expected provisioning delay, or does this indicate that the Embedded Signup process failed between Meta and Azure Communication Services?
4. Should we wait before retrying, or can Microsoft check/reset the incomplete channel registration without requiring us to delete the WhatsApp assets in Meta?

We would prefer not to retry or delete the existing WhatsApp assets until we know the backend state, to avoid creating a duplicate or locked registration.

Thank you.