Getting started

By the end of this guide you will have a Dynamics 365 Finance and Operations environment sending telemetry to the portal, and you will see its batch jobs, forms and errors in the dashboards. Nothing gets installed in D365: you paste a connection string into a standard screen and the telemetry starts flowing on its own.

What you need first

• Administrator access to your Dynamics 365 Finance and Operations environment.
• The environment identifier (GUID). It comes from LCS or from D365's own traces.
• Administrator or owner role in the portal organization. The viewer role can read dashboards but cannot connect environments.

Step 1: create the telemetry destination

Go to Connections → D365 connection and pick the Azure region closest to your Finance and Operations environment. That is where the resources that receive and store your telemetry get created. Press «Create destination in Azure» and wait: the status moves through Queued, Creating and Ready.

Step 2: paste the string into Dynamics 365

1. 1
   Reveal the stringOn the same screen, press «Reveal string». It requires the administrator role and the action is recorded in the Audit log with your name and the time.
2. 2
   Open System administration in D365From the main Finance and Operations menu.
3. 3
   Go to «Monitoring and Telemetry parameters»That is the literal screen name, in English, even on Spanish installations. If it does not show up, the «Monitoring and Telemetry» feature is not enabled in Feature management.
4. 4
   Paste the string and saveWithin a few minutes the first signals start showing up in the portal.

Step 3: register the environment

Go to Connections → Environments and add the environment with its name, its type (Production, UAT, Sandbox or Development) and its D365 identifier. That identifier is what separates each environment's telemetry: without it everything arrives mixed together and the filters are useless.

Mark it as favorite if it is the one you check daily. Dashboards select it by default, saving you a click every time.

Step 4: look at the data

Open the Dashboard. You will see counts of batch tasks started, finished, failed and throttled, their time series, and which classes or jobs fail most. From there, Telemetry takes you into the detail per area: batch jobs, DMF integrations, forms, SQL queries, X++ errors and sessions.

What you now have

A connected environment, its telemetry arriving continuously, and working dashboards. From here you can invite your team, register the rest of your environments and adjust the time range on each view.