Common terms
| Term | Meaning |
|---|---|
| Project | The container for tenant connections, site matches, batches, licenses, and results. |
| Source / destination | The tenant you read sharing from / the tenant receiving restored access. |
| Tenant scan | Finds the sites and OneDrives available for matching. |
| Inventory | The recorded files, folders, and sharing information for a scanned scope. |
| Batch | Matched sites or OneDrives that will be prepared, reviewed, approved, and restored together. Older technical references may call it a wave. |
| Plan / dry run | Proposed destination access changes, with readiness and review reasons. |
| Run | One scan, mapping, preparation, verification, or execution attempt. A run ID identifies its evidence. |
| Principal / identity | A user, guest, or group that can receive access. |
| Access change | A proposed permission or link operation. Several can relate to the same file. |
| Credit | The billing unit for one unique destination file or folder with a successful verified restore change. |
Which screen should I use?
- Overview: return to recent work and follow the next action.
- Projects: connect tenants, scan, match source and destination sites, and open batches.
- Inside a batch: Prepare, Review, Restore, and Results keep that batch's work together.
- Discovery, Mapping, Identity, and Restore: inspect or work with the corresponding standalone runs. Confirm the selected run belongs to your intended scope.
- Reports: review exceptions and generate evidence packages. Account and credits: review plans, balances, and purchases.
Why counts can differ
One file can have several recipients and therefore several proposed access changes. A site scan count measures sites or OneDrives, an inventory count measures content, and a permission count measures access entries. They should not be expected to match.
A credit estimate counts unique affected destination files or folders. It is an upper bound because access that is already present does not consume another credit.