Step 3, Configure Schedule, decides how far back EaseLog reaches for history and how often it collects new audit data from now on.

Figure 1. Step 3, Configure Schedule, showing the Audit Log Start Date with its live record and database size preview, First Execution, Frequency, the Initial Data Export time slots and the weekend option.

Audit Log Start Date

The date EaseLog starts fetching historical audit data from.

As you change it, EaseLog tells you what that choice costs and what it skips:

Shown Meaning Total Records How many audit records will be imported. Database Size Roughly how much storage they will occupy. The exclusion line How many historical records your chosen date leaves behind.

Read that exclusion line before moving on. It states plainly how much history you are choosing not to keep, and it is much easier to reconsider now than to discover the gap during an investigation.

Move the date earlier to capture more history, at the cost of a larger import and more storage. Check the figure against your plan allocation. See Plan Details and Usage Limits.

First Execution

The date, time and timezone of the first run. EaseLog shows the UTC equivalent underneath.

Check that UTC line. Scheduling in local time and reading results in UTC is an easy way to confuse yourself later, because the Activity Heatmap on the Operations tab is in UTC too.

Frequency

How often EaseLog checks for new audit data, for example Every 12 Hours. The Next Scheduled Time below it is calculated from your first execution and frequency, so you can confirm the schedule does what you meant.

More frequent means audit data arrives sooner, and more calls against Dynamics 365. Less frequent means larger batches and a longer wait before recent events appear. See Changing the Sync Schedule for the trade off in full.

Initial Data Export

A toggle that lets the historical backlog run in parallel time windows rather than one after another, so the catch up finishes sooner.

With it on, you define up to four time slots, each with a start and an end. Use them to confine the heavy work to hours when Dynamics 365 is quiet.

Run continuously on weekends ignores those slot hours on Saturday and Sunday and exports non stop all weekend. Narrow weekday slots plus continuous weekends is usually the best balance.

See Initial (Backlog) Data Export.

Note

Everything here can be changed afterwards on the Schedule tab of Edit Environment. Nothing chosen now is permanent, though moving Audit Log Start Date earlier later means a fresh backlog to work through.