YA41720 | Restored | Unable to access Yammer.com| 1/12/2016 1:52 AM

Final Status: An automated feature of the Yammer service took the necessary action to remediate impact. Engineers verified that the service is healthy.

User Impact: Affected users were unable to sign in to Yammer.

Customer Impact: Analysis of incident scope indicated that a very limited number of customers and users appeared to be impacted.  No customer reports of the issue were identified during this event.

Incident Start Time: Monday, January 11, 2016, at 11:34 PM UTC

Incident End Time: Monday, January 11, 2016, at 11:48 PM UTC

Preliminary Root Cause: The underlying root cause is 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.

Posted in Uncategorized

YA41720 | Investigating | Unable to access Yammer.com | 1/12/2016 1:17 AM UTC

Final Status: Engineers have received reports of an issue within the Yammer service and have confirmed that service is now restored. Additional information will be provided in the Closure Summary.

Posted in Uncategorized

Service Restored | YA41619 | Affected users were unable to sign in to Yammer.com.

Final Status: The investigation determined that there was a temporary issue affecting routing of requests to Yammer.com. This issue has been resolved and engineers have confirmed that the service is no longer impacted. The root cause is under investigation.

User Impact: Affected users were unable to sign in to Yammer.com.

Customer Impact: Analysis of incident scope indicated that many customers appeared to be impacted by this event. For those customers affected, this issue potentially affected any user attempting to log in to the service. Some customers reported that their organization was affected by this issue.

Incident Start Time: Wednesday, January 6, 2016, at 7:21 PM UTC

Incident End Time: Wednesday, January 6, 2016, at 7:50 PM UTC

Preliminary Root Cause: The root cause of this incident is not known but is under investigation. Based on the impact of this incident the root cause will be provided, if identified, within 30 days.

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: Review the monitoring infrastructure for improvements as this event was reported by customers before the investigation prompted a communication to be published to the Service Health Dashboard.

– Action: Identify the underlying root cause and develop a solution to prevent reoccurrences.

Please consider this service notification the final update on the event.

Posted in Uncategorized

YA41600 | Service Restored | Affected Office 365 users could not activate new user accounts. | 1/6/2016 01:02 AM UTC

Final Status: Engineers have completed the deployment of the fix to the affected environment, which has remediated impact.

User Impact: Affected Office 365 users could not activate new user accounts.

Customer Impact: Analysis of incident scope indicated that a very limited number of customers and users appeared to be impacted. No customer reports of the issue were identified during this event.

Incident Start Time: Tuesday, January 5, 2016, at 3:00 PM UTC

Incident End Time: Wednesday, January 6, 2016, at 12:30 AM UTC

Preliminary Root Cause: A code issue was found in the environment. The underlying root cause is 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.

Posted in Service Interruption

YA41600 | Restoring Service | Affected Office 365 users cannot activate new user accounts. | 1/6/2016 12:33 AM UTC

Current Status: Engineers have identified a code issue causing new user account activation to fail. A code change is being deployed, which will remediate impact.

User Impact: Affected Office 365 users cannot activate new user accounts.

Customer Impact: Analysis of incident scope indicates that a very limited number of customers and users appear to be impacted. No customer reports of the issue have been identified at this time.

Next Update by: Wednesday, January 6, 2016, at 2:00 PM UTC

Posted in Service Interruption

YA41600 | Investigating | Affected Office 365 users cannot activate new user accounts. | 1/6/2016 12:21 AM UTC

Current Status: Engineers are investigating an issue in which some users may be experiencing problems accessing or using Yammer services or features. This event is actively being investigated. More information will be provided shortly.

Posted in Service Interruption

Service Restoration | YA35860 | Users were unable to upload and play videos on yammer.com | 12/18/2015 6:41 PM UTC

Final Status: Engineers determined that a recent update prevented the Yammer service from processing video requests. Engineers corrected the code issue that was inadvertently introduced in the update to resolve the issue.

User Impact: Affected users may have received an error and were unable to upload and play videos on Yammer.com.

Customer Impact: Analysis of incident scope indicated that a very limited number of customers and users appeared to have been impacted. Engineers received a few isolated customer reports of this issue.

Incident Start Time: Thursday, December 17, 2015, at 10:00 AM UTC

Incident End Time: Friday, December 18, 2015, 3:13 AM UTC

Preliminary Root Cause: A recent update to the infrastructure that facilitates uploading of videos inadvertently introduced a code issue, which caused impact to the Yammer service.

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: Review procedures for validating service updates as this issue was not identified during the testing phase of the development process.

Please consider this service notification the final update on the event.

Posted in Service Interruption