Skip to main content
Configure Druva to protect Exchange Online data
Updated over 8 months ago

Before you begin

Ensure you have a Microsoft 365 global administrator account with a valid Microsoft 365 license.

Configure Druva to protect Exchange Online

Log in to the inSync Management Console as an inSync Cloud administrator.

Perform the following steps to set up inSync to configure and protect Exchange Online data.

Step 1: Provide Druva permissions to access Exchange Online data

To begin with Exchange Online data backup, you need to authorize Druva with Exchange Online app data access. For more information, see Configure Druva inSync for Microsoft 365.

Once you initiate app configuration from the Druva Management Console, the application redirects you to the Microsoft 365 login page. Log in as a Global Administrator to review the requested app permissions and grant access to the app data. To know more about the requested permissions and their purpose, check the Microsoft 365 App Permissions for Druva App article.

Druva communicates with Microsoft 365 services using OAuth 2.0, an open protocol for token-based authentication and authorization. For more information, see the OAuth website.

Support for Azure Active Directory (AD) Conditional Access policies

If your organization uses Azure AD Conditional Access policies for authenticating and providing conditional access to users, the app configuration step will adhere to these policies. For more information, see Support for Azure Active_Directory (AD) Conditional Access policies.

After you complete the configuration of inSync with Microsoft 365 app, you can use the Verify Configuration option to check if inSync can access your users. For information about verifying configuration, see Configure Druva inSync for Microsoft 365.

Step 2: Configure SaaS Apps settings for Exchange Online

Define the user attribute that you want inSync to use to map user account to their Microsoft 365 app account. For information about configuring user accounts access using the inSync email ID or Active Directory(AD) attribute and configuring the user custom domain for Microsoft 365, see Configure Druva inSync for Microsoft 365.

Step 3: Get user data encryption key(ekey)

To ensure that the Microsoft 365 data that is backed up is secure, you must configure inSync to get the data encryption key (ekey). For information about configuring inSync to get the data encryption key, see Configure Druva inSync for Microsoft 365.

Step 4: Configure a profile to protect Exchange Online data

To back up Microsoft 365: Exchange Online data, you must specify the Microsoft 365 backup settings in an existing profile or in a new profile. inSync will start backing up the user data from Microsoft 365 as per the backup schedule that is defined for a profile with SaaS Apps feature enabled. For information about configuring a profile, see Configure Druva inSync for Microsoft 365.

The setting options specific to Exchange Online on the SaaS Apps screen are explained below.

Field

Description

Backup SaaS Apps

Exchange Online

Select this check box, if you want to backup only Exchange Online data. In-Place Archive for Exchange Online is also backed up if Exchange Online is selected.

Optionally, if you want inSync to backup the Exchange Online Recoverable Items folder, which keeps the deleted emails, contacts, and calendar items in the Deletions and Purges items, select the Backup Recoverable Items check box. This enables inSync Cloud administrator and inSync users to restore or download data caused by accidental or malicious deletion.

Global Exclusions

Global Exclusions for files is not applicable for emails.

For more information on how you can configure the global exclude list, see Configure the global exclude list.

Step 5: Associate and add users to Microsoft 365 enabled SaaS Apps profile

The procedure to associate and add users depends on the SaaS Apps settings configuration set in Step 2.


πŸ“ Note

Based on the license allocated for Microsoft 365 users, you get 50% complimentary licenses for shared and resource mailboxes without any extra storage.


Did this answer your question?