📝NOTE: The availability of this feature may be limited based on the license type, region, and other criteria. To access this feature, contact support. |
This article describes how to install and configure the Druva Cloud Platform to protect Microsoft Power Platform data.
Prerequisites
License: Ensure your account has a Microsoft Power Platform license. If prompted to "Contact Support," the feature is not yet enabled.
Permissions: You must have Global Administrator credentials for Microsoft 365.
Encryption: Decide between Druva Cloud KMS (recommended) or Bring Your Own Key (BYOK).
Step 1: Install the Druva Power Platform App
Log in to the Druva Cloud Platform Console.
Navigate to the Hamburger Menu > All Services > Microsoft Power Platform.
Click Get Started on the Microsoft Power Platform dashboard card.
Click Install to add the Druva Power Platform application to your tenant.
Step 2: Authorize Microsoft Permissions
Sign In: When redirected, enter your Global Administrator credentials.
Review Permissions: Review the requested API permissions.
Accept: Click Accept. This authorization allows Druva to access your Power Platform environment.
Step 3: Configure Cloud Key Management (KMS)
After authentication, the Cloud Key Management configuration wizard appears.
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.
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.
📝NOTE: Scheduled backups and environment discovery will fail if KMS is not configured.