D365 PortalBeta
I already have access
Back to documentation

Step-by-step guides

Troubleshooting

What to do when data does not arrive, provisioning fails, or an action appears blocked.

No telemetry is arriving

  1. Check the destination is ReadyIn Connections → D365 connection, the status must be Ready. If it says Failed, review the error and try again.
  2. Confirm the pasted string is the current oneIf you rotated the string and did not update it in D365, your environment is still sending to the old destination, which no longer accepts data.
  3. Widen the time rangeMove from «Last hour» to «Last 7 days». A quiet environment can go hours without signals.
  4. Clear the environment filterPick «All environments». If data shows up that way, the registered environment identifier does not match the one D365 emits.
  5. Wait a few minutesRight after pasting the string, the first signals take a while. Half an hour with nothing is already a sign something is off.

Messages you might hit

MessageCauseWhat to do
Assign a plan to the organization before provisioningThe organization has no plan and there are no limits to apply.Go to Billing and pick a plan.
The region can no longer be changed: the resources already existThe destination is provisioned and the region is fixed.It can only be changed by creating a new organization.
Only an administrator can do thisYour role is viewer.Ask an administrator to run the action.
Too many attempts. Wait a few minutesThe action has been rate limited.Wait and retry. It usually happens after revealing the string several times in a row.
There is no telemetry destination for this organization yetThe destination has not been created.Go to Connections → D365 connection and create it.
That identifier is already registeredAnother environment uses the same GUID.Check you did not copy the identifier from the wrong environment.
You do not belong to any organization yetYour user exists but is not in any organization.Ask for an invitation, or create your organization from Billing.

If none of this fixes it

Write to us from Settings → Support, or send the detail through Feedback choosing the «Bug» type. During the beta we read everything that comes in.

Keep reading