Before you begin
Make sure you meet the following prerequisites:
You must have a Microsoft 365 Global Administrator account.
The account must have a valid Microsoft 365 license.
Log into the Druva Console as an Cloud administrator, then follow these steps to configure Druva cloud for Microsoft Teams protection.
📝NOTE: Some of the Teams Metadata and Private Channel APIs are in Beta state. See, Microsoft Graph API to work with Microsoft Teams.
Step 1: Grant Druva Access to Microsoft Teams
Sign in to the Druva Console as an Cloud Administrator.
Begin the app configuration process. You will be redirected to the Microsoft 365 login page.
Log in as a Global Administrator and grant the requested app permissions. To learn more about the permissions requested, refer to the Microsoft 365 App Permissions for Druva App article.
After completing the app configuration, click the three-dot menu and select Verify to confirm access to your Microsoft 365 users.
📝NOTE:
Druva uses OAuth 2.0 for secure token-based authentication. Learn more at the OAuth website.
If your organization enforces Conditional Access policies via Azure AD, these policies will apply during app configuration.
See Support for Azure Active_Directory (AD) Conditional Access policies for details.
Step 2: Get data encryption key
Scheduled backup of SaaS Apps data requires access to the data encryption key to encrypt backed-up data. This process is part of the digital envelope encryption process that Druva strictly adheres to. Druva does not store the user’s data encryption key and has no access to the data.
Select one of the following options to generate the data encryption key.
Cloud Key Management System (KMS) (recommended) - Uses AWS KMS services to encrypt and decrypt SaaS Apps data. You cannot disable this setting once saved. For more information, see Configure Key Management for SaaS Apps.
Bring Your Own Key (BYOK) - If your organizational policies require complete control over the encryption of the data backed up by Druva, Enterprise Key Management is the solution for you. For more information, see Enterprise Key Management for Microsoft 365.
Step 3: Configure Teams for Backup and Restore
To set up Teams backup and restore, use backup profiles for org apps along with auto-configuration rules.
Backup Profile for Org Apps
Predefined Backup Profile – Use a standard backup profile for Teams.
Custom Backup Profile – Create a profile tailored to your specific backup and retention settings.
Auto Configuration Rules
To streamline configuration across multiple resources, use auto-configuration rules by defining attribute-based criteria.
To learn more refer to the Backup Profiles for Org Apps and Auto Configuration Rules. Refer Manual Configuration to manually configure a Teams.