Most common issues with Office 365 integration

Several conditions need to be met for the Office 365 integration to work properly. Below, you can find the most common issues that may arise.

Please note that Microsoft Basic authentication will be deprecated by October 1, 2022.

For this reason, our integration mechanism will be replaced by a new CASB technology that will be released in September (Safetica 10.3.)

The issues that may arise are with:



Behavior: An error is displayed right after the confirmation of O365 integration settings in Safetica Management Console.

Solution: The MSAL authentication requires .NET 6.0 Desktop Runtime (v6.0.8) installed. 

Internet Explorer

Behavior: In Internet Explorer, the authentication ends with an error.

Solution: You can either change the default browser to e.g. Chrome or run the integration from a different computer.


Time out

Behavior: An error is displayed in Safetica Management Console after you finish the authentication process in a browser.

Solution: The MSAL authentication has a shorter time limit for going through the steps in the browser. This can lead to a timeout, and thus an error is displayed in Safetica Management Console. Please try finishing this process faster.
More information: O365 integration issues




Behavior: You are unable to finish the integration, or there are no logs synced.

Solution: The following URLs have to be reachable from the Safetica server:,,,

Basic authentication (Safetica server)

Behavior: You will see this pop-up when you log in to the Safetica Management Console.

MicrosoftTeams-image (2)

Solution:  Review the prerequisites as described in our KB article:

Office 365 integration prerequisites 



Multi-factor authentication

Behavior: There are no logs synced, and there might be a warning displayed in the Office 365 integration section.

Solution: If you are using multi-factor authentication, you must make sure that Safetica Service Account is excluded from these requirements.