Removing an environment disconnects it from EaseLog and frees the slot for another one.

Before you remove anything

Removing an environment removes its offloaded audit data from EaseLog. That history is the reason the product exists, so pause on these questions first:

• Do you still need the audit trail? Once removed, this environment's history is no longer in EaseLog to search.
• Are you subject to a retention obligation? Audit data is often kept for a defined period for compliance reasons. Removing it early can breach that.
• Is anybody relying on it? A compliance colleague may be using this history without your knowing.

If you only want the sync to stop for a while, pause it instead. Pausing is reversible. Removal is not. See Pausing and Resuming a Sync.

Remove an environment

1. Select Environments in the left navigation.
2. Select the delete control on the environment's card.

Figure 1. The Environments page showing one card per connected environment with its idle state, record count, queue and delete controls.

You can also remove one from the Edit Environment panel, using Delete at the bottom.

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

What is not affected

Removing an environment from EaseLog does not touch Dynamics 365. Your Dataverse audit settings, your data and your users are unchanged, and auditing carries on recording there exactly as before.

What you lose is the offloaded copy EaseLog was holding, and the analytics built on it.

Freeing a slot

Your plan limits how many environments you can connect, shown as the count next to the Environments heading and again under Plan Details. Removing one frees a slot.

If you are removing an environment only to make room, check whether your plan can be raised instead. Losing history to free a slot is an expensive trade. See Plan Details and Usage Limits.

Reconnecting later

You can connect the same environment again afterwards. EaseLog fetches its history again from the Audit Log Start Date you set, and only as far back as Dynamics 365 still holds it. Audit data that Dataverse has since aged out cannot be recovered by reconnecting.