Connecting an environment takes about five minutes, provided you have three values ready before you start. Collecting them is the part that takes longer.

What EaseLog asks for

Figure 1. Step 1 of the Connect to Environment wizard, before anything is entered.

FieldWhat it identifiesTenant IDYour Azure tenant.Client IDAn application registration that EaseLog authenticates as.Client SecretThe secret belonging to that registration.

All three are required. The wizard cannot get past step 1 without them.

Where the three values come from

All three belong to an app registration in your organisation's Microsoft Entra tenant. Your Azure administrator creates the registration and can read all three values from it. Ask for the three values together, and ask for the secret's expiry date at the same time.

Auditing must already be on in Dynamics 365

EaseLog collects audit data. It does not create it. If auditing is not enabled for an entity, no audit records exist for it, and connecting EaseLog will not produce them retrospectively. You can enable auditing during step 2 of the wizard, but it only records from that point on. See Enabling Auditing on a Field.

Check you have room

You need a free environment slot and enough storage. Both are under Plan Details in the account menu. Step 3 of the wizard estimates how much storage the import will need, so you can check it fits before committing. See Plan Details and Usage Limits.

Note the secret's expiry date

Client secrets expire. When one lapses the sync stops, and the gap in the audit trail only becomes obvious when somebody needs that period. Write down the expiry date when the secret is created and set a reminder ahead of it. Replacing it later is straightforward. See Editing a Connection.

A common failure worth knowing about

If your credentials are accepted but the environment list comes back empty, the usual cause is the application user missing a Dataverse security role. Nothing appears broken. EaseLog authenticated successfully and simply cannot see anything.