The Connection tab of the Edit Environment panel holds the credentials EaseLog uses to reach your Dynamics 365 environment. You come here when those credentials change, or when the environment reports an error.

Open the Connection tab

1. Select Environments in the left navigation.
2. Select the edit control on the environment's card.
3. The panel opens on Connection.

Figure 1. The Connection tab of the Edit Environment panel, with the Test Connection control and the saved secret indicator.

The fields

Field Holds Tenant ID The Azure tenant EaseLog connects to. Client ID The application registration EaseLog authenticates as. Client Secret The secret for that registration.

The secret is already saved

The Client Secret field shows a saved value rather than being empty, and the note below it says so.

Leave it blank to keep the existing secret. You only type here when you are replacing the secret with a new one, for example because the old one has expired or been rotated.

Test before you save

Select Test in the Test Connection block to check the credentials work before committing them. Allow a moment for validation.

Testing first is worth the few seconds. Saving credentials that do not work puts the environment into Error and stops the sync until you come back and fix it.

Save

Select Save. Save stays unavailable until you have actually changed something, so if it looks greyed out, nothing has been edited yet.

When to come here

• The client secret has expired or been rotated. This is the common one, because secrets have an expiry date and syncs stop when they lapse.
• The environment state reads Error and you suspect the connection.
• The application registration has been replaced.

See Environment States: What Each One Means.

Other controls on this panel

Audit Logs opens the audit data for this environment. Delete removes the environment, which is covered in Removing an Environment. The Schedule tab is covered in Changing the Sync Schedule.

Note

Set a reminder before your client secret expires. A lapsed secret stops the sync silently, and the gap only becomes obvious when somebody needs the audit trail for that period.