Forum Discussion
Windows Server Essentials 2012 integration with 365 broken
Pending moving them to a cloud-only setup, I have one customer still using Server 2012 Essentials (note: not R2) and their integration with 365 has broken. Yes, I know this was always slightly unsatisfactory, but cannot run grown-up AD sync s/w on this platform. Having removed the 365 integration and re-added it using the Dashboard, it will not accept any Global Admin credentials to re-setup the integration, saying that the userid or pw is incorrect (it isn't). Logs show an authentication issue but not clear exactly why and the message might be spurious (well it is, since user and pw are confirmed correct).
Here's the relevant log entry:
[46092] 220816.114050.2251: O365ManagementProvider(IO365Callback): Activate:4514888a-2f2c-4f32-be98-aa413b85fe1c failed due to O365ConfigurationFault = IncorrectCredential
Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Credential cannot be authenticated
at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.SetCredential(String userName, String password)
at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.verifyAdminAccount(IO365ServiceAdapter adapter, String adminUserName, String adminPassword)
at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.Activate(String adminUserName, String adminPassword)
at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.<>c__DisplayClass4.<InvokeOperation>b__3()
at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
I doubt that this Server dashboard is entirely up to date with security protocols. Does anyone know how I could go about finding out what the exact issue is and therefore whether there is a fix? It is still in extended support so I guess it ought still to work... ?
Hello, I had excatly the same problem
It's due to TLS 1.1 and 1.0 deprecation
You have to enable TLS 1.2.https://docs.microsoft.com/en-us/troubleshoot/azure/active-directory/enable-support-tls-environment?tabs=azure-monitor#enable-tls-12-on-client-or-server-operating-systems-
https://support.microsoft.com/en-au/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392I hope this will help you
3 Replies
Hello, I had excatly the same problem
It's due to TLS 1.1 and 1.0 deprecation
You have to enable TLS 1.2.https://docs.microsoft.com/en-us/troubleshoot/azure/active-directory/enable-support-tls-environment?tabs=azure-monitor#enable-tls-12-on-client-or-server-operating-systems-
https://support.microsoft.com/en-au/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392I hope this will help you
Many thanks. That was indeed my first thought, so I checked TLS enablement and it looks correct. Any other ideas?
- Initially I thought I could fix the problem by connecting to azureAD, so I tried with powershell the Connect-AzureAD command, but some installation was missing, after installing them I got the same error "IncorrectCredential" , then I found the point on the TLS.
Maybe the installations I did before are part of the solution.
Can you connect via powershell and the Connect-AzureAD command?
