Microsoft 365 Organisation Addition Failure
This issue may occur when the required Microsoft API permissions or environment prerequisites are not met.Common Reasons
One or more required API permissions may not have been assigned to the application.
Admin consent may not have been granted for the API permissions associated with the application.
The Global Administrator and Exchange Administrator roles may not have been assigned to the user account used to add the Microsoft 365 organization.
The system may not have a stable internet connection while adding the Microsoft 365 organization.
The system date and time may not be synchronized correctly with the local date and time, which can cause Microsoft authentication to fail.
Solution
To resolve the issue, follow these steps:
1. Verify API permissions
Sign in to the Microsoft Entra admin center using a Global Administrator account.
Navigate to Identity → Applications → App registrations.
Select the application used for adding the Microsoft 365 organization in BDRShield.
From the left pane, select API permissions.
The page displays all configured API permissions under Configured permissions.
2. Verify/Grant Admin Consent
On the same API permissions page:
Check the Status column for the configured permissions.
Verify that the required permissions show Granted for <Organization Name>.
If consent has not been granted, click Grant admin consent for <Organization Name>.
Review the confirmation prompt and click Yes.
Wait for the permission status to update.
3.Verify the required administrator roles
Global Administrator access
Ensure that you are signed in using an account with Global Administrator privileges.Assign the Exchange Administrator role
Sign in to the Microsoft Entra admin center using the Global Administrator account.
Navigate to Identity → Roles & admins.
Search for and select Exchange Administrator.
Click Add assignments.
Select the required user account and click Add to assign the role.
4. Verify internet connectivity
Ensure that the system has a stable internet connection while adding the Microsoft 365 organization. Internet connectivity must also be available while running Microsoft 365 backup jobs.
5. Verify system date and time
Ensure that the system's date, time, and time zone are correct and synchronized with the local time. Incorrect system time can cause authentication or authorization failures when communicating with Microsoft services.6. Try adding the organization again
Once all the above requirements are verified, try adding the Microsoft 365 organization again from the BDRShield Console.