Data Deletion Controls for On Demand Migration (4383701)

Data Deletion Controls for On Demand Migration

1. Data Deletion Process for On Demand Migration

The goal of this document is to provide insights into how OnDemand Migration ensures that all customer data temporarily stored during migration operations is securely and permanently deleted upon successful completion of each migration task.

2. Scope of Temporary Data Processing

On Demand Migration temporarily stores data required for migration purposes, including:

• • OneDrive files and folders
  • SharePoint files and folders
  • Microsoft Teams content for channels and chats

For all Exchange Online migrations, On Demand Migration processes data entirely in memory — no data is written to disk.

Customer data is never retained for archival, analytics, telemetry, or any other purpose, and is not stored after the migration job completes.

More information about the data stored during the migration can be found in our security guides under (Section Overview of data managed by On Demand Migration):
https://support.quest.com/on-demand-migration/current/technical-documents

3. Storage Location and Data Residency

All temporarily stored migration data is stored exclusively in Microsoft Azure–managed storage services. No customer data is stored or processed outside the Microsoft Azure environment.

More information about data locations and data security can be found in our security guides under (Section Privacy and protection of customer data):
https://support.quest.com/on-demand-migration/current/technical-documents

4. Primary Deletion Controls (Post‑Migration)

Upon successful completion of a migration task, all temporarily stored data is deleted immediately using Azure Storage SDK deletion methods, as outlined below:

• • OneDrive Migration Data
    • BlobContainerClient.DeleteIfExists
      https://learn.microsoft.com/en-us/dotnet/api/azure.storage.blobs.blobcontainerclient.deleteifexists
      
      
  • SharePoint Migration Data
    • BlobContainerClient.DeleteBlobIfExistsAsync
      https://learn.microsoft.com/en-us/dotnet/api/azure.storage.blobs.blobcontainerclient.deleteblobifexistsasync

• • Microsoft Teams and Chat Migration Data

• • BlobContainerClient.DeleteBlobIfExistsAsync
    https://learn.microsoft.com/en-us/dotnet/api/azure.storage.blobs.blobcontainerclient.deleteblobifexistsasync
  • TableClient.DeleteEntityAsync
    https://learn.microsoft.com/en-us/dotnet/api/azure.data.tables.tableclient.deleteentityasync?view=azure-dotnet
  • TableClient.DeleteAsync
    https://learn.microsoft.com/en-us/dotnet/api/azure.data.tables.tableclient.deleteasync?view=azure-dotnet
    
    

5. Secondary Data Deletion Controls (Fallback Safeguards)

To provide additional assurance, On Demand Migration implements an independent secondary deletion process:

On Demand Migration runs an independent secondary deletion process if the initial method for deleting temporarily stored data was unsuccessful and no event message has been posted:

• • A daily cleanup task
  • The process deletes all stored data that has not been modified for more than 31 days

This layered approach prevents data accumulation and ensures eventual deletion, even if a primary deletion action fails.