Skip to main content


 

 

How can we help you?

 

 
Druva Documentation

Verify configuration

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

After you configure the SaaS Apps to work with inSync, you can use the Verify option to check if inSync can access your tenant.

When you use the Verify option, inSync performs the following checks as a part of verification: 

For Microsoft 365:

  • App authentication: This step checks if inSync can utilize the available refresh tokens to validate the connection with the Microsoft 365 tenant.
  • User and user’s endpoints existence: This step checks if the user exists at the Microsoft 365 end.
  • Licensing & other permission-related checks (for OneDrive): This step checks for all the endpoints available for the user at the Microsoft 365 end.
  • User mailbox existence (for Exchange Online): This step verifies if a mailbox exists for that user.

For Google Workspace:

  • App authentication: This step checks if inSync can utilize the available refresh tokens to validate the connection with the application. If certain app-specific permissions are revoked, then inSync identifies the error at this step.
  • User existence: This step checks if the user exists on Google Workspace.
  • User authentication: In this step inSync tries to generate JSON Web Tokens and uses the email address to authenticate the user.

Procedure

For Microsoft 365:

To verify the configuration:

  1. On the inSync Management Console menu bar,  click the Left_Navigation_Bar_Hamburger_Icon.png icon to access the global navigation panel.
  2. Click SaaS Apps.
  3. Click Microsoft 365
  4. On the Overview page, click  and then click Verify.
  5. In the Verify Configuration dialog that appears, select the app for which you want to verify the configuration.

Based on the selection of the app, the options to verify configuration are displayed. The following image displays options when Microsoft 365 app is selected.

M365_Verify_Configuration.png

Here is the list of parameters for each sub-app to verify the configuration:

  • Exchange Online and OneDrive: Email ID of the user
  • SharePoint: Site title
  • Teams: Team Name
  • Public folder: Public folder name
  • Exchange Online and OneDrive: Provide an email address in the Select a user field. 
  • inSync recommends that you enter an organization user email address to check if the configuration works instead of an administrator user. 

 

When you select an app and provide the parameters for verification, inSync performs the following checks as a part of verification: 

  • App authentication: This step checks if inSync can utilize the available refresh tokens to validate the connection with the Microsoft 365 tenant.
  • User and user’s endpoints existence: This step checks if the user exists at the Microsoft 365 end.
  • Licensing & other permission-related checks (for OneDrive): This step checks for all the endpoints available for the user at the Microsoft 365 end.
  • User mailbox existence (for Exchange Online): This step verifies if a mailbox exists for that user.

 6. If any of the authentication steps fail for the selected app, you are prompted with an error message. Click the error message to view the error details.  

M365_Verify_Config_ESITENOTFOUND.png

For Google Workspace:

  1. On the inSync Management Console menu bar,  click the Left_Navigation_Bar_Hamburger_Icon.png icon to access the global navigation panel.
  2. Click SaaS Apps.
  3. Click Google Workspace
  4. On the Overview page click   and then click Verify.
  5. In the Verify Configuration dialog that appears, select a user. 
Note: Provide an email address in the Select a user field. User Principal Name (UPN) is not supported at the moment.

 6. When you select a user, inSync authenticates with the suite, checks if it can access users in the suite, and then checks if the user data for backup is available for the apps. 

 7. If any of the steps fail, you are prompted with an error message. Click the error message to view the error details.