Integration between Windows 2012 Essentials and Office 365 is a really useful feature that allows us to manage the Office 365 accounts associated with our users from the Windows 2012 Essentials dashboard.
Unfortunately a server-side update to Office 365 in October or November 2016 has broken this integration and the fix has not been made public. If you are experiencing this issue, you’ll see the following behaviour:
- When trying to set up “Office 365 Integration” from the Essentials Dashboard, the following error is displayed:
“Cannot connect to Microsoft online services”
- The log file at C:\ProgramData\Microsoft\Windows Server\Logs\OIMGettingStartedWizard.log contains the following errors:
GettingStartedWizard: Activate O365 with Error Communication returned. GettingStartedWizard: error page exception : O365ConfigurationFault = Communication Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Call Bec web service <ListUsers>b__14() failed with generic communication issue
- The log file at C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-O365ProviderServiceConfig.log contains the following errors:
ProviderFramework: Information:  : PfErrorHandler: IGNORING WCF internal exception: (CommunicationException)" BecWebServiceAdapter: BEC web service is updated, need to update proxy code." BecWebServiceAdapter: Call Bec web service <ListUsers>b__14() failed: System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (65536) has been exceeded.
This problem is discussed (although mixed up with some other issues) here. The only solucion available is a fix included in a thus-far unreleased Microsoft KB, namely KB3216737. In order to obtain this hotfix, one must open a paid-for support case with Microsoft Product Support. The cost for this is £199 in the UK and $499 in the US, however if they determine that your issue is the one described here (specifically determined by the error ” The maximum message size quota for incoming messages (65536) has been exceeded”) then this fee will be refunded.
There is no known workaround or way to fix this without the patch mentioned above, and Microsoft will not allow us to share the patch ourselves. Hope this helps anyone else encountering this issue!