VOCA ACS Issue

Hi @Colin

The error you’re seeing (AADSTS500113: No reply address is registered for the application) is a common Microsoft Entra ID (Azure AD) issue. It occurs because the application used for the ACS/Voca integration is missing a Redirect URI (reply address) in its App Registration. This is required for the admin consent flow to complete successfully.

Recommended Fix:

1. Go to the Azure Portal > Microsoft Entra ID > App registrations.
2. Search for the application using the Application ID (Client ID) that you’re using in the consent URL.
3. Open the app registration >Authentication blade.
4. Under Redirect URIs, add a valid reply URL.
   • For admin consent flows like this, you can safely add:https://localhost (as a placeholder) or https://login.microsoftonline.com/common/oauth2/nativeclient (for public client apps).
   1. Save the changes.
   2. Try the admin consent URL again.

After adding the redirect URI, the consent page should work properly and grant the necessary permissions.

Reference:

https://learn.microsoft.com/en-us/troubleshoot/entra/entra-id/app-integration/troubleshoot-consent-issues

https://learn.microsoft.com/en-us/entra/identity-platform/reply-url

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

Hi @Colin

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?

Hi, I am still working through, I am attempting to verify ACS access to the Audiocodes VOCA platform. The voca platform essentially is acting as WebRTC using ACS SDK.

I am trying to identify any ps commands to allow access of the Voca platform to use ACS, Is there any commands to allow this interaction?

Hi @Colin

Thanks for the update.

Just to make sure we’re aligned — has the original AADSTS500113 error (No reply address registered) been resolved after adding the Redirect URI and completing the admin consent flow?

Assuming that part is now working, the next step to allow the VOCA platform (WebRTC / ACS SDK) to access your Azure Communication Services resource is assigning the proper Azure RBAC role to the service principal.

You can run the following PowerShell commands:

Connect-AzAccount -TenantId "your-tenant-id"

New-AzRoleAssignment `
  -ApplicationId "1fd5118e-2576-4263-8130-9503064c837a" `
  -RoleDefinitionName "Contributor" `
  -Scope "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Communication/communicationServices/{acs-resource-name}"

Replace the placeholders with your actual values (you can get the full Resource ID from your ACS resource in the Azure portal).

After assigning the role, retry the validation in the VOCA platform.

Reference :

https://learn.microsoft.com/en-us/azure/communication-services/concepts/authentication

https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-powershell

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

Hi, Yes after adding redirect I can access URL.

When I run the above PowerShell commands, i receive the following:

Hi @Colin

Great news — glad the redirect URI fix worked and you can now access the consent URL!

The PowerShell error you're seeing usually happens due to a formatting or line-break issue when copying multi-line commands. PowerShell is misreading the parameters.

Here’s a cleaner, single-line version you can try:

New-AzRoleAssignment -ApplicationId "1fd5118e-2576-4263-8130-9503064c837a" -RoleDefinitionName "Contributor" -Scope "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Communication/communicationServices/{acs-resource-name}"

Important: Replace the placeholders ({subscription-id}, {resource-group}, and {acs-resource-name}) with your actual values.

Easier Alternative (Recommended):

You can assign the role directly from the Azure Portal — it's often simpler and avoids scripting issues:

1. Go to your Azure Communication Services resource.
2. In the left menu, select Access control (IAM).
3. Click + Add > Add role assignment.
4. Select Contributor (or Communication Services Contributor if available).
5. On the Members tab, choose User, group, or service principal.
6. Search for and select the service principal with App ID 1fd5118e-2576-4263-8130-9503064c837a.
7. Review + Assign.

After assigning the role (either via PowerShell or Portal), retry the connection validation in the VOCA platform.

Let me know if you get any new error messages or if the validation succeeds.

Reference :

https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal

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

Please "upvote" if the information helped you. This will help us and others in the community as well.

Thank you, I still receive a Azure connection error from Voca, In reviewing There is no Contributor (or Communication Services Contributor) available to select The single line did appear to enter as it returned entries.