Dynamics Community Forum Thread Details

Facing an issue while creating an account in Dynamics 365.

Steps to reproduce the bug: Go to Dynamics 365 → Copilot Service Admin Center → Channels → Accounts → Add Account. When I enter the App ID and Client Secret, it shows the error: “We couldn’t validate your app.”
Screenshot 2026-02-23 163023

I’ve attached screenshots where I entered the App ID and Client Secret.
User's image

User's image

Categories:

Dynamics 365 Customer Service

1. By design, the messaging services in Dynamics 365 (including Copilot Service and Omnichannel) require the App Registration to be Multi-Tenant. If you selected "Single Tenant" during creation, the validation service will reject it.

The Fix: 1. Go to the Azure Portal → App registrations. 2. Open your app and go to the Authentication tab. 3. Under Supported account types, ensure it is set to: > "Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant)" 4. Save and try the validation in Dynamics again.

2. "Value" vs. "ID" for the Client Secret
This is a very common "gotcha." When you create a Client Secret, Azure shows you two strings: a Value and a Secret ID.

The Problem: Users often copy the Secret ID (which is a GUID) instead of the Value (which is a long string of characters).
The Fix: You must use the string from the Value column.
- Note: If you didn't copy the Value immediately after creation, it is now masked (hidden). You will need to create a New Client Secret and copy the Value immediately.

3. Missing API Permissions (Dynamics CRM)
For the Admin Center to "validate" the app, the app must have permission to talk to your Dynamics environment.

The Fix:
1. In your App Registration, go to API permissions → Add a permission.
2. Select Dynamics CRM from the "Microsoft APIs" tab.
3. Choose Delegated permissions and check user_impersonation.
4. Crucial Step: Click the "Grant admin consent for [Your Org]" button after adding the permission. If you don't hit that "Grant" button, the validation will fail.

4. Summary Checklist for Success
If you've checked the above and it's still failing, verify these three final points:

Wait for Sync: Sometimes it takes 5–10 minutes for a newly created Client Secret to propagate through Azure's global systems before Dynamics can "see" it.
No Extra Spaces: Ensure no leading or trailing spaces were accidentally copied with the App ID or Secret.
Correct Tenant: Ensure the App Registration was created in the same tenant as your Dynamics 365 environment.

if this helps pls mark as verified so that it may be helpful for someone else. Thanks!

Quick Links

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides