Problem Description
Some Microsoft Teams resources fail to back up and appear as Disabled in the Druva inSync console, even though the Teams still exist in Microsoft 365.
In some cases, the associated Group and SharePoint site may back up successfully, but the Teams resource remains in a failed state.
Cause:
This issue can occur due to one or more of the following reasons:
The Teams resource was previously deleted in Microsoft 365, causing its App Status to change to Disabled in Druva inSync.
Insufficient permissions for the administrator account used to configure the Druva inSync Microsoft 365 app, leading to authentication or access errors during backup.
Resolution:
To resolve the issue, follow these steps:
Verify Teams Status in Microsoft 365:
Confirm that the affected Teams resources still exist in Microsoft 365 and have not been deleted.
Check Administrator Permissions:
Ensure the administrator account used for Druva inSync Microsoft 365 app configuration has the required permissions, such as:
Team.ReadBasic.All
TeamSettings.Read.All
If permissions are missing or incorrect, reconfigure the app using a Global Administrator account.
Reconfigure Druva inSync Microsoft 365 App:
Navigate to the Microsoft 365 section in the Druva console.
On the Overview page, click Re-Configure.
From the three-dot menu, select Re-Configure next to the app type you want to update.
Confirm the reconfiguration in the pop-up window.
On the Microsoft 365 login page, sign in with a Global Administrator account and grant the required permissions.
Note: This process will stop all ongoing cloud app backups and restores. Ensure you are using the same Microsoft 365 tenant for all sub-apps.
Sync the Teams Resource:
If the issue persists for a specific Teams resource, disable the associated Group in Druva inSync and then re-enable it.
This action forces a sync of the Teams resource and typically resolves the backup failure.
Preventive Measures:
Use the Verify Configuration feature in Druva inSync to confirm that the app has the necessary permissions and access.
Always perform configuration changes using a Global Administrator account.
Regularly review Microsoft 365 permissions for the Druva inSync app to ensure compliance with required access levels.
If the issue continues after performing the above steps, contact Druva Support for further assistance.