D365 PortalAll your environments send telemetry to the same destination. What separates them is the D365 identifier: the portal matches it against the customDimensions.environmentId field on every trace. An unregistered environment may still send data to Application Insights, but the dashboard and telemetry views ignore it: it does not count toward licensing.
Where the identifier lives
- In LCS, under the environment properties.
- In D365's own traces, in the customDimensions.environmentId field.
Add an environment
- Open Connections → EnvironmentsYou will see the environments already registered and how many your plan has left.
- Fill in name, type and identifierThe name is for you. The type can be Production, UAT, Sandbox or Development. The identifier is the D365 GUID.
- Add the platform version if you know itOptional. It helps explain behaviour differences between environments on different PUs.
- Press «Add»The environment appears in the list and can be used as a filter in Telemetry right away.
The favorite environment
Mark as favorite the environment you check daily, usually production. Dashboards and telemetry views select it by default, so you stop picking it on every screen.
Common errors
| Message | What it means |
|---|---|
| Check the name, type and identifier (GUID) | The identifier is not GUID-shaped, or a required field is missing. |
| That identifier is already registered | Another environment in your organization uses the same GUID. Check you did not copy it from the wrong environment. |
| You have reached the plan's environment limit | Starter allows 2 environments and Pro allows 10. Remove one you do not use, or change plan. |
| Only an administrator can manage environments | Your role is viewer. Ask an administrator to register it. |