Step 1 has two halves. First you tell EaseLog how to reach your Azure tenant. Then EaseLog shows you the environments it found, and you pick one.

Start the wizard

1. Select Environments in the left navigation.
2. Select Connect Environment.

Enter your credentials

Fill in Tenant ID, Client ID and Client Secret. All three are required. See Before You Connect: What You Need from Azure.

Figure 1. Step 1 of the Connect to Environment wizard, showing the four step progress bar and the empty Tenant ID, Client ID and Client Secret fields.

With all three entered, Get Environments becomes available.

Figure 2. Step 1 with the connection credentials entered, ready to select Get Environments.

Select Get Environments.

Choose an environment

EaseLog lists every environment it can reach with those credentials.

Figure 3. The environments discovered after Get Environments, with Environment Name, Instance ID, URL, Type and Audit Status. Environments already connected show as In System.

Column Tells you Environment Name The environment as Dynamics 365 names it. Instance ID Its unique identifier. URL Its address, useful for telling similar environments apart. Type The environment type. Audit Status Whether you can connect it.

Audit Status decides what you can select

Value Meaning Accessible Available to connect. You can select it. In System Already connected to EaseLog. It is greyed out and cannot be selected again.

If the environment you want reads In System, it is already connected. Close the wizard and look for it on the Environments page.

Select an Accessible environment, then select Next.

Figure 4. An environment with Audit Status Accessible selected, which enables Next.

If no environments appear

Work through these in order:

1. Check the three values. A single wrong character in the Tenant ID or Client ID is the most common cause.
2. Check the secret has not expired. Client secrets have an expiry date.
3. Check the app registration's permissions, and that its application user has a Dataverse security role. Without that, the credentials authenticate but see nothing.

Point 3 produces the most confusing outcome, because nothing looks broken. The credentials are accepted and the list simply comes back empty.

Note

Cancel closes the wizard without connecting anything. Nothing is saved until you select Complete at the end of step 4.