Connect Dynamics 365

The portal does not connect to your database or reach into your environment. It works the other way around: it hands you a connection string, you paste it into D365, and D365 starts sending its telemetry to the destination we prepared for your organization.

Requirements

• Administrator or owner role in the organization.
• A plan assigned to the organization. With no plan there is no ingestion cap or retention to apply, so provisioning will not start.
• System administrator access in Dynamics 365 Finance and Operations.

Create the destination

1. 1
   Open Connections → D365 connectionThe screen shows the current state of your organization's telemetry destination.
2. 2
   Pick the Azure regionThe one closest to your Finance and Operations environment. That is where the receiving resources are created. It cannot be changed later.
3. 3
   Press «Create destination in Azure»The status moves through Queued, Creating and Ready. It takes a couple of minutes.

Enable the feature in Finance and Operations

D365 does not send telemetry out of the box: the feature that produces it has to be turned on first. Until you do, the screen where the string goes does not even appear in the menu.

1. 1
   Open the «Feature management» workspaceFrom the main Finance and Operations menu. The name is in English on every installation.
2. 2
   Filter the list for «Monitoring and Telemetry»That is the exact feature name. The list holds hundreds of entries: without filtering you will not find it.
3. 3
   Select it and press «Enable»Once done, «Monitoring and Telemetry parameters» shows up under System administration. That is where the string goes.

Register the environment and the string in D365

This is where you decide which environment sends to which destination. D365 sorts every environment into a mode — development, test or production — and attaches the connection string to the mode, not to the environment. That is why there are two tabs and both have to be filled in.

1. 1
   Press «Reveal string» in the portalThe masked version is always visible. The full value requires the administrator role and is recorded in the Audit log.
2. 2
   Copy it with the «Copy» buttonAvoid selecting it by hand: one extra character and D365 sends nothing.
3. 3
   In D365, go to System administration → «Monitoring and Telemetry parameters»The screen name is in English on every installation. If you cannot see it, the feature from the previous step is not enabled.
4. 4
   On the «Environments» tab, create one record per environmentRegister all your environments, not just the one you are connecting. That way the configuration survives a database refresh and travels from one environment to another.
5. 5
   On the «Application Insights Registry» tab, create one record per modePaste the string into the record for the matching mode and save. Within a few minutes telemetry should appear in the dashboards.

Choose which telemetry is emitted

With the string saved, D365 still sends nothing. Each kind of signal — batch jobs, forms, DMF integrations, slow SQL queries, exceptions — is turned on separately on the «Configure» tab of that same screen. Switch on the ones you want to see in the portal and save.

Check that it works

Open the Dashboard and set the range to «Last hour». If there is activity in the environment you should see batch tasks or form openings. The signals card tells you at a glance whether forms, DMF, slow SQL or exceptions are arriving.