Overview:
The steps in this document describe the logical workflow and APIs required to perform this operation.
Customers can implement this workflow using any preferred automation or scripting tool, such as:
Python
PowerShell
Postman workflows
Integration platforms
Internal automation frameworks
The workflow should:
Execute the Preserved Users Datasources report.
Filter the results based on the required license states.
Extract the userID values from the report output.
Retrieve the target ProfileID using the Profile API.
Loop through the filtered users and invoke the User Management API to update the profile.
Prerequisite
Before implementing this workflow, create a dedicated inSync profile for Shared Mailboxes.
In the Druva inSync Management Console, create a new profile intended to host Shared Mailboxes only.
Configure the profile with the following settings:
Exchange Online: Enabled
OneDrive: Disabled
This ensures that only the mailbox data is protected after a user is converted to a Shared Mailbox.
Note: The API endpoints and parameters referenced in this article are based on the current Druva Public API documentation at the time of publication.
Druva continuously enhances its APIs, and API endpoints, parameters, or response fields may change in future releases. Customers should always refer to the latest documentation available on the Druva Developer Portal before implementing or maintaining their workflows.
Developer Portal: https://developer.druva.com
API Reference: https://apis.druva.com
If any discrepancies are observed between this article and the latest API documentation, the Developer Portal documentation should be considered the authoritative source.
Workflow:
Step 1: Generate API Access Token
1. Create Druva Admin API Credentials:
Log in to the Druva Cloud Platform Console.
Navigate to Menu → Integration Center → API Credentials.
Click New Credentials.
Note the following values:
ClientID
Secret
2. Generate Access Token
Use the ClientID and Secret to generate an OAuth access token.
API: POST /oauth/token
Capture the following value from the response:
access_token
3. Use Access Token in API Requests
Include the access token in the Authorization header for all subsequent API calls.
Example header format:
Authorization: Bearer <access_token>
Step 2: Retrieve Preserved Users Datasources Report
API:
GET /platform/reporting/v1/reports/m365PreservedUsersDatasourcesPurpose: Retrieve the report containing users whose Microsoft 365 datasources are in the Preserved state.
Fields to capture from report output:
userID
userName
smbLicenseState
m365LicenseState
Filter the results to include users where:
smbLicenseState = YES
m365LicenseState = Preserved
Store the userID values for the next step.
Step 3: Retrieve Available Profiles
API:
GET /insync/profilemanagement/v1/profilesPurpose: Retrieve the list of available profiles.
Fields to capture:
profileName
profileID
Identify the ProfileID to assign to the filtered users.
Step 4: Configure Workflow Input for Target Profile
Configure the workflow to accept a ProfileID input parameter.
Source: Profile list retrieved in Step 3
Purpose: Allow administrators to specify the target profile to assign to users returned in the report.
Step 5: Update Profile for Filtered Users
API:
PATCH /insync/usermanagement/v1/users/{userID}Purpose: Update the user profile.
Fields to provide:
userID (from Step 2 report output)
profileID (workflow input from Step 4)
Execute this API for each userID retrieved from the report.
Outcome
The workflow updates the profile assignment for all users who:
Have SMB license enabled, and
Have Microsoft 365 datasource in Preserved state.
Note:
If you encounter issues or output inconsistency while invoking the Druva APIs described in this article, contact Druva Support for assistance with API availability or behavior.
Druva Support can assist with API usage and troubleshooting. However, development, customization, or debugging of scripts and automation workflows created using these APIs is outside the scope of Druva Support.