Article ID: 2537605 - View products that this article applies to.
Not sure what release of Office 365 you're using? Go to the following Microsoft website:
Am I using Office 365 after the service upgrade?
Consider the following scenario. A user uses an "email as sign in" (EASI) account or a custom domain as his or her Microsoft account to sign in to Microsoft services. For example, the user uses email@example.com. The domain in the user's Microsoft account is the same as the domain that Microsoft Office 365 uses. In this scenario, the user tries to sign in to Microsoft Messenger or Skype. However, the user can't use his or her current Microsoft account to sign in to either Messenger or Skype. Instead, the user is forced to change his or her Microsoft account so that it uses a different domain.
To resolve this issue, use one of the following methods:
This issue occurs if the following conditions are true:
This issue occurs because of the way that the session initiation protocol (SIP) services are advertised. The Office 365 and Messenger environments can coexist if PIC or External Communications is disabled for the Office 365 domain. However, if PIC or External Communications is enabled for the Office 365 domain, the Office 365 domain becomes the authoritative SIP domain and hosts the service. Therefore, when a user tries to sign in to Messenger or Skype, the Microsoft account service recognizes that Office 365 controls the domain namespace and requires the user to change his or her Microsoft account to use a different domain.
Still need help? Go to the Office 365 Community
Article ID: 2537605 - Last Review: October 16, 2013 - Revision: 27.0
Contact us for more help
Connect with Answer Desk for expert help.