We have an issue with Office 365 and SSO.
I have just taken over the IT at a company and one of my first tasks was to sort out the issue of failed Office 365 SSO sign on as the company wishes to migrate to Exchange Online eventually. ADFS 2.0 and SSO with office365 was previously attempted on another server (domain controller - Server 2008 R2). The synchronisation with Office 365 and AD worked as DirSync was installed and configured. However, when login was attempted to Office 365, it would detect the SSO and try to direct you to the internal domain controller and prompt for a password. No matter what password was attempted it was rejected.
After the failure, the previous person uninstalled everything on the domain controller to do with the Office 365 SSO (dirsync, adfs, Azure AD Connect, Azure AD Module for Powershell.
I have since installed adfs 3 on a WIndows Server with 2012 R2 on the network. Obtained the correct ssl certificate and installed it into adfs, converted successfully to federated and established the relying party trusts. However, when login is attempted on Office 365, it diverts to the server adfs 2.0 was previously installed on with the internal fqdn of the server.
Also as a result of this failed attempt at SSO previously, the login used to access azure, keeps diverting to the internal fqdn of the previouslly installed server, so as a result, I cannot configure Dirsync when it asks for the Windows Azure Active Directory Credentials as this fails wth a configuration error stating it cannot connect.
It's in a bit of a mess, and I'm wondering how this can be resolved and to get the point where internal users can login to Office 365 successfully as the issue with being unable to login to azure will be resolved if the SSO issue can be resolved.