ETL data cleanup and tenant lifecycle

Choose the correct operation

Deleting ETL data, extending a trial, suspending a tenant and canceling a subscription have different scopes. Preferences → Data Cleanup removes the selected tenant's ETL records while preserving the listed identity, access and commercial records. It does not delete a cloud VM or substitute for a lifecycle process with retention requirements.

Confirm the intended tenant, authorized purpose, management permissions and applicable retention process before acting. Use a synthetic laboratory workspace for practice. A managed individual tenant can reject generic ETL cleanup and require its separate lifecycle process; do not change tenant type or subscription management to evade that restriction.

Review cleanup scope

The screen lists Mappings, Sessions, Workflows, Connections, credentials, runs, Repository data and tenant ETL preferences as deletion categories. It identifies users, the tenant, roles, billing and global administrator audit as preserved records. Read the current inventory because the category list alone does not establish what data is present.

1. Open Preferences → Data Cleanup and select Tenant.
2. Choose Refresh inventory and inspect counts, scope and any blockers.
3. Obtain and verify the authorized backup required for the operation. The form is not an automatic backup of the entire tenant.
4. Choose Clean tenant ETL data and compare the dialog's tenant and summary with the inventory you reviewed.
5. Complete Type to confirm and the irreversible-data acknowledgment.
6. Select Delete ETL data once and wait for the verified response.
7. Refresh inventory, verify the affected categories and separately confirm the listed preserved records.

If the inventory changed, refresh and review the latest state. A conflict or failed response does not authorize direct deletion of storage files or modification of the inventory revision.

Extend an eligible trial

1. Open Subscription & billing, select the same tenant and use Subscription → Extend trial.
2. Review the current lifecycle, dates and eligibility.
3. Choose 7 days, Custom days or Exact date and time.
4. For a custom number of days, use the displayed allowed range. For an exact date, verify the dialog's timezone and resulting end.
5. Enter the required Reason, review the new end and choose Extend trial once.
6. Confirm the accepted expiry while checking that tenant identity, existing objects and original trial history remain intact.

The supported day extension counts from the current end for a running trial, or acceptance for an expired eligible trial. The dialog shows local time and stores the instant consistently. An extension does not recreate the workspace, reset quotas or grant unrelated entitlements.

Lifecycle acceptance and recovery

An expired or past-due tenant may retain permitted safe reading, export and billing access while new business mutations or execution remain restricted. Available reading should not be interpreted as authorization to recreate objects, enroll infrastructure or generate new work.

Use separate laboratory exercises for cleanup and trial extension. For cleanup, verify deletion scope and preserved accounts. For extension, verify expiry and identity continuity. Following a network error, inspect current state before retrying; an identical retry should not produce an unintended second extension.

Read Tenants, Subscription and billing and Worker removal for their distinct operations.