d9d993d267
After some building, I realized that a backup is a snapshot of a resource, not the whole m365 service. Initially, I assumed that 1 backup takes the whole service per tenant (https://discord.com/channels/1022200980487557130/1022200981376745474/1231385151376719892). This doc update should help clear the confusion more. Maybe there is a better way to word it, so any other suggestions are welcome. --- #### Does this PR need a docs update or release note? - [x] ✅ Yes, it's included - [ ] 🕐 Yes, but in a later PR - [ ] ⛔ No #### Type of change - [ ] 🌻 Feature - [ ] 🐛 Bugfix - [x] 🗺️ Documentation - [ ] 🤖 Supportability/Tests - [ ] 💻 CI/Deployment - [ ] 🧹 Tech Debt/Cleanup #### Test Plan - [ ] 💪 Manual - [x] ⚡ Unit test - [ ] 💚 E2E --------- Co-authored-by: ashmrtn <3891298+ashmrtn@users.noreply.github.com>
1.4 KiB
description
| description |
|---|
| Core Corso concepts. |
Concepts
Before using Corso, it's important to familiarize yourself with some key concepts.
Microsoft 365 concepts
-
M365 Tenant is typically associated with a unique domain (for example,
contoso.com) and represents a dedicated and logically segregated instance of the Microsoft 365 services plus associated data available to your organization. -
M365 Service refer to a cloud-applications available through the Microsoft 365 platform. Corso supports backup and recovery for Exchange Online, OneDrive, SharePoint, and Teams.
-
Azure AD Application represents an Azure AD digital identity/service principal and associated configuration which define the accessible resources and permitted actions on these resources through the application. Corso uses an Azure AD application to connect to your M365 tenant and transfer data during backup and restore operations.
Corso concepts
-
Repository refers to the storage location where Corso securely and efficiently stores encrypted backups of your M365 Service's data. See Repositories for more information.
-
Backup is a copy of a resource of your M365 Service's data to be used for restores in case of deletion, loss, or corruption of the original data. Corso performs backups incrementally, and each backup only captures data that has changed between backup iterations.