Final Status: Engineers identified that a newly deployed portion of code inadvertently caused the Single Sign-on feature to become degraded. Engineers reverted the problematic portion of code to resolve the issue.
User Impact: Affected users may have been unable to sign in to the Yammer service when using the Single Sign-on (SSO) feature.
Customer Impact: Analysis of incident scope indicates that a very limited number of customers appeared to have been impacted. Engineers received a few isolated customer reports of this issue.
Incident Start Time: Monday, November 30, 2015, at 9:00 AM UTC
Incident End Time: Monday, November 30, 2015, at 3:45 PM UTC
Preliminary Root Cause: A newly deployed portion of code caused the Single Sign-on feature to become degraded. The underlying root cause remains under investigation.
Next Steps: The following is a list of known action item(s) associated with this incident. As part of the Office 365 problem management process, additional engineering actions may be identified to improve the overall service.
– Action: Identify the underlying root cause and develop a solution to prevent reoccurrences.
Please consider this service notification the final update on the event.