We set up the Diagnose dashboard (real-time analytics for Unified Routing) by following the MS Learn article step by step. The dashboard still didn’t work, and it took a few MS Support tickets to get it working.
We hit different symptoms along the way:
- The Real-time analytics for record routing option didn’t appear in the admin centre.
- The dashboard loaded but showed that real-time analytics was unavailable.
- Charts failed with an error loading chart data.
- One user received an error saying they were not a Supervisor persona.
TL;DR: On top of the MS Learn steps, we needed updated Federated Identity Credentials (FICs) with Microsoft Code Signing PCA 2024. The subject identifier must contain the correct environment GUID and encoded tenant ID. We also needed to grant admin consent, verify the app registration used by the environment, and ensure users accessing the dashboard had the Supervisor persona.
What the MS Learn article covers
At a high level, the documented setup involves:
- Create an Application Insights resource.
- Create an app registration in Microsoft Entra ID.
- Add a Federated Identity Credential (FIC) to the app registration using Microsoft Code Signing PCA 2011.
- Assign the required role to the app registration on the Application Insights resource.
- Configure the Application Insights connection for the target environment.
One important detail that wasn’t clear to us was the encoded tenant GUID and environment GUID are used in the FIC subject identifier.
The subject identifier contains an tenant-specific value after /t/ and environment-specific value after /e/. This must be the actual Power Platform Environment ID, not the Dataverse Organisation ID or the app registration ID.
The article doesn’t clearly explain how to replace or update this value when configuring another environment.
We also found that additional configuration was required beyond the documented steps.
Investigation
Microsoft Support collected browser traces and worked with the Product Group to investigate the issue.
One of the errors captured in the browser network trace was:
Request not supported msdyn_ExecuteAppInsightsQuery#2011/Organization.svc
Microsoft initially identified this as a product issue involving a telemetry query falling back to a Custom API that wasn’t registered in the environment.
However, the dashboard eventually worked after the required authentication and configuration changes were completed. Microsoft didn’t confirm that a product fix had been deployed.
Root cause
There wasn’t a single cause. We encountered several configuration and access issues.
| Symptom | Finding |
|---|---|
| Real-time analytics option missing | Microsoft Product Group corrected a backend configuration issue. |
| Real-time analytics unavailable | Microsoft advised configuring FICs for PCA 2024. |
| Authentication failure | Required API permissions and admin consent needed to be completed. |
| FIC configuration not working | The FIC subject needed the correct environment GUID and had to be configured against the app registration used by the environment. |
| User is not a Supervisor persona | The user needed the appropriate Supervisor persona to access the dashboard. |
Solution
1. Check whether the real-time analytics option is available
First, confirm that the Real-time analytics for record routing option is available in the admin centre.
If the option is missing, raise a Microsoft Support ticket. In our case, Microsoft had to correct the backend configuration before the option became available.
2. Configure two Federated Identity Credentials
Microsoft confirmed that we needed updated FIC with Microsoft Code Signing PCA 2024
The subject identifier follows this format:
/eid1/c/pub/t/{encodedTenantId}/a/qzXoWDkuqUa3l6zM5mM0Rw/n/plugin/e/{environmentId}/i/{issuer}/s/{certificateSubject}
For example, assume we have the following values:
| Property | Example value |
|---|---|
| Tenant ID | 1b6d3f2e-5a4c-4e8b-9f17-2c8d4a6b0e95 |
| Encoded Tenant ID | Lj9tG0xai06fFyyNSmsOlQ |
| Environment ID | 3f9c2a71-8d4e-4b6a-9e15-7c2d0b8a6f43 |
These are fictional GUIDs used for illustration.
FIC for Microsoft Code Signing PCA 2024:
/eid1/c/pub/t/Lj9tG0xai06fFyyNSmsOlQ/a/qzXoWDkuqUa3l6zM5mM0Rw/n/plugin/e/3f9c2a71-8d4e-4b6a-9e15-7c2d0b8a6f43/i/Microsoft Code Signing PCA 2024/s/Microsoft Corporation
Important: Replace the highlighted values with your actual encoded tenant ID and Power Platform environment GUID.
3. How the tenant ID is encoded
The tenant ID in the subject identifier isn’t the GUID shown directly in Microsoft Entra ID.
It is generated by:
- Converting the tenant GUID into its 16-byte representation using little-endian GUID byte order.
- Encoding those bytes using Base64url.
- Removing the trailing Base64 padding characters.
This is equivalent to using Guid.ToByteArray() in .NET, followed by Base64url encoding.
For example, using this fictional tenant ID:
1b6d3f2e-5a4c-4e8b-9f17-2c8d4a6b0e95
You can generate the encoded value using Python:
import uuid
import base64
tenant_id = "1b6d3f2e-5a4c-4e8b-9f17-2c8d4a6b0e95"
encoded_tenant_id = base64.urlsafe_b64encode(
uuid.UUID(tenant_id).bytes_le
).decode().rstrip("=")
print(encoded_tenant_id)
Output:
Lj9tG0xai06fFyyNSmsOlQ
This is the value to use after /t/ in the subject identifier.
4. What is the /a/ value in the subject identifier?
You may have noticed another value in the subject identifier:
/a/qzXoWDkuqUa3l6zM5mM0Rw
Unlike the encoded tenant ID and environment GUID, this value is fixed.
Microsoft uses it in the documented FIC subject identifier format for Power Platform managed identity version 1.
The value qzXoWDkuqUa3l6zM5mM0Rw is a Base64url-encoded GUID. When decoded using the same GUID byte-order convention, it produces:
58e835ab-2e39-46a9-b797-accce6633447
Microsoft’s documentation doesn’t explain what the underlying GUID represents. However, the value is provided as a constant in the documented subject identifier format.
You don’t need to generate or replace this value.
Keep the following segment unchanged:
/a/qzXoWDkuqUa3l6zM5mM0Rw
For reference, see Set up Power Platform managed identity version 1 for Dataverse plug-ins.
5. Verify the app registration used by the environment
Make sure the FICs are configured on the app registration referenced by the environment’s managed identity configuration.
This is particularly important when an app registration is shared across multiple environments.
Each environment needs the correct environment-specific subject identifiers.
6. Grant admin consent
Another configuration requirement identified during troubleshooting was granting admin consent for the app registration’s API permissions.
In Microsoft Entra ID, open the app registration and navigate to API permissions.
Check whether the required permissions have admin consent granted.
If not, select Grant admin consent. This requires an account with the appropriate Entra ID permissions.
7. Check the Supervisor persona
We also encountered the following error:
User ... is not a Supervisor persona.
Make sure the users accessing the dashboard have the required Supervisor persona.
Otherwise, you may encounter an access error even when the Application Insights integration is configured correctly.
8. Test the Application Insights connection
After completing the FIC configuration, admin consent and required permissions, configure and test the Application Insights connection in the target environment.
In our case, the dashboard eventually loaded successfully and showed routed conversations.
Lessons learnt
- The PCA 2024 FIC was an additional requirement confirmed by Microsoft Support.
- The FIC subject identifier must contain the correct Power Platform environment GUID.
- The tenant ID must be converted to the correct Base64url-encoded GUID format.
- The
/a/qzXoWDkuqUa3l6zM5mM0Rwsegment is a documented constant and shouldn’t be replaced. - Check that the FICs belong to the app registration actually used by the environment.
- Grant the required admin consent for the app registration.
- Users accessing the dashboard need the appropriate Supervisor persona.
- If you encounter the HTTP 405 error on
msdyn_ExecuteAppInsightsQuery, check the authentication and FIC configuration before assuming it’s a product issue.







