Fix Outlook Integration Error when using Skype

Fix Outlook Integration Error when using Skype perfectly if these are the primary tools used for communication in your organization or business. However, we’re seeing reports from users that a warning stays in the lower-left corner of the desktop application which reads “Outlook integration error.” It’s possible the issue occurred but fixed itself.

Outlook Integration Error

The April 2017 update to the Skype for Business client may cause problems for users with mailboxes hosted on Exchange Server. This update deprecates the “Skype for Business Contacts” folder in Outlook. The root cause of this problem is that the client tries to create the “Skype for Business Contacts” folder in the user’s exchange mailbox and fails. There are two solutions to this.

Clear the Skype for Business cache

If you’re experiencing problems with your device, it’s often due to a cached data issue. Clearing your cache can help resolve these issues. Follow the steps below:

Press Win + R, and then type in the %localappdata%\Microsoft\Office\16.0\Lync\ folder. Press Enter.
Delete the sip profile folder in it.
Go into the Tracing folder, delete all files, but not the folders.

Repair Microsoft Office and Apps

The Office troubleshooter can repair Office if there are files missing or corrupt. It will replace them with a working copy.

Migrate to higher Exchange Server

If the issue is with an Exchange server, you can try migrating the mailboxes to a higher Exchange server.

Disable the creation of the “Skype for Business Contacts” folder

Technet suggests that you add the below-mentioned policy to test and see if it works. Assign it to a single user and see if it resolves the issue. Once the policy is applied, the user needs to wait for few minutes, sign-out from the client and Outlook, and try again.

Check if EWS and MAPI Status are ok

You need to open the Configuration Information and check if the MAPI and EWS statuses are both “OK.” If not, the configuration for both of them may have changed, or the configuration on your client could be incorrect. You will need to ask your admin for the correct configuration.