Protect Microsoft 365 Teams

Once you have registered your Microsoft 365 domain as a source, you're ready to use Cohesity DataProtect as a Service to protect the Teams data in your domain.

To protect your Microsoft 365 Teams:

  • If the Teams Posts option is enabled under the Teams during app registration, the Teams Posts will be backed up along with the corresponding Teams. Teams backup may fail if the Azure subscription configuration is not set appropriately.

  • This is an Early Access feature. Contact your Cohesity account team to enable the feature. After you enable the feature, ensure that you update the registered source to include backups of Team Posts. For more details, see Step 4 in Source registration.

  1. In DataProtect as a Service, under Sources, find the Microsoft 365 source and click into it.

  2. Click the Teams tab.

  3. Select the individual Team you wish to protect or:

    • Click Users > Select All Child Objects to protect all the Teams in this source.

    • Click Users > Auto Protect This to protect all the Teams in this source.

  4. Click the Protect icon above the list.

  5. Choose a policy to specify backup frequency and retention. If you don't have a policy, you can easily create one.

  6. Under Settings, edit the Start Time if necessary.

  7. Under Additional Settings, you can enable Indexing, configure a specific End Date, Alerts, and other additional settings.

    If you plan to recover individual document library items (coming soon!), in addition to whole sites, you need to enable Indexing in this step. When you do, you can include or exclude specific sites from indexing.

  8. Click Protect.

The backups start immediately after you protect the objects, regardless of the time you set for the protection run.

Next > When the first protection run completes, you will be ready to recover your protected Teams when and if you need to.

Additional Settings

Advance Settings Description
Start Time

Available only if the selected policy is set to Backup Daily. Indicates what time the protection run should start. Enter the Start Time and select AM or PM. The default time zone is the browser's time zone. You can change the time zone of the protection run by selecting a different time zone here.
SLA

The service-level agreement (SLA) defines how long the administrator expects a protection run to take. Enter:

  • Full. The number of minutes you expect a full protection run, which captures all the blocks in an object, to take.

  • Incremental. The number of minutes you expect an incremental protection run, which captures only the changed blocks in an object, to take.
Cancel Runs at Quiet Time Start

(Available only if the selected policy has at least one Quiet Time)

When enabled, all the protection runs that are currently executing will cancel when the Quiet Time period starts. By default, this setting is disabled, meaning that after a protection run starts, it continues to execute even when a Quiet Time period starts. However, new protection runs will not start during a Quiet Time.
Indexing

By default, indexing is enabled.

Indexing is mandatory for granular restore of Teams contents.