Services
Current Status
Historical Status
Message Center Information
Incidents
Incidents Messages
Planned Maintenance
*
Exchange Online
Microsoft Kaizala
Skype for Business
Microsoft Teams
Mobile Device Management for Office 365
Office Online
OneDrive for Business
Identity Service
Office 365 Portal
Planner
SharePoint Online
Microsoft StaffHub
Sway
Yammer Enterprise
*
ServiceFeature
Exchange OnlineSign-in
Exchange OnlineE-Mail and calendar access
Exchange OnlineE-Mail timely delivery
Exchange OnlineManagement and Provisioning
Exchange OnlineVoice mail
Microsoft KaizalaKaizala Messaging
Microsoft KaizalaKaizala Management Portal
Skype for BusinessAudio and Video
Skype for BusinessFederation
Skype for BusinessManagement and Provisioning
Skype for BusinessSign-In
Skype for BusinessAll Features
Skype for BusinessDial-In Conferencing
Skype for BusinessOnline Meetings
Skype for BusinessInstant Messaging
Skype for BusinessPresence
Skype for BusinessMobility
Skype for BusinessCloud PBX
Skype for BusinessPSTN Calling
Skype for BusinessMeeting Broadcast
Microsoft TeamsTeams Components
Mobile Device Management for Office 365Mobile Device Management
Office OnlineExcel Online
Office OnlineOneNote Online
Office OnlinePowerPoint Online
Office OnlineWord Online
Office OnlineVisio Online
OneDrive for BusinessOneDrive for Business
Identity ServiceSign-In
Identity ServiceAdministration
Office 365 PortalPortal
Office 365 PortalAdministration
Office 365 PortalPurchase and Billing
PlannerPlanner
SharePoint OnlineProvisioning
SharePoint OnlineSharePoint Features
SharePoint OnlineTenant Admin
SharePoint OnlineSearch and Delve
SharePoint OnlineCustom Solutions and Workflows
SharePoint OnlineProject Online
SharePoint OnlineOffice Web Apps
SharePoint OnlineSP Designer
SharePoint OnlineAccess Services
SharePoint OnlineInfoPath Online
Microsoft StaffHubService and web access issues
Microsoft StaffHubWeb client issues
Microsoft StaffHubAndroid client issues
Microsoft StaffHubiOS client issues
SwaySway
Yammer EnterpriseYammer Components
ServiceFeature
ServiceServiceStatusStatusTimeIncidentIds
Exchange OnlineNormal service07.05.2019 23:30:20
Microsoft KaizalaNormal service07.05.2019 23:30:20
Skype for BusinessService degradation07.05.2019 23:30:20LY177449, LY179047, LY179206
Microsoft TeamsNormal service07.05.2019 23:30:20
Mobile Device Management for Office 365Normal service07.05.2019 23:30:20
Office OnlineNormal service07.05.2019 23:30:20
OneDrive for BusinessNormal service07.05.2019 23:30:20
Identity ServiceNormal service07.05.2019 23:30:20
Office 365 PortalService restored07.05.2019 23:30:20MO179236
PlannerNormal service07.05.2019 23:30:20
SharePoint OnlineNormal service07.05.2019 23:30:20
Microsoft StaffHubNormal service07.05.2019 23:30:20
SwayNormal service07.05.2019 23:30:20
Yammer EnterpriseNormal service07.05.2019 23:30:20
ServiceServiceStatusStatusTimeIncidentIds
ServiceServiceStatusFeatureFeatureStatusIncidentIdsStatusTime
Exchange OnlineNormal serviceSign-inNormal service07.05.2019 23:30:20
Exchange OnlineNormal serviceE-Mail and calendar accessNormal service07.05.2019 23:30:20
Exchange OnlineNormal serviceE-Mail timely deliveryNormal service07.05.2019 23:30:20
Exchange OnlineNormal serviceManagement and ProvisioningNormal service07.05.2019 23:30:20
Exchange OnlineNormal serviceVoice mailNormal service07.05.2019 23:30:20
Microsoft KaizalaNormal serviceKaizala MessagingNormal service07.05.2019 23:30:20
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service07.05.2019 23:30:20
Skype for BusinessService degradationAudio and VideoNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationFederationNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationManagement and ProvisioningService degradationLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationSign-InNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationAll FeaturesService degradationLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationOnline MeetingsNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationInstant MessagingNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationPresenceNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationMobilityNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationCloud PBXNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationPSTN CallingNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Skype for BusinessService degradationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920607.05.2019 23:30:20
Microsoft TeamsNormal serviceTeams ComponentsNormal service07.05.2019 23:30:20
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service07.05.2019 23:30:20
Office OnlineNormal serviceExcel OnlineNormal service07.05.2019 23:30:20
Office OnlineNormal serviceOneNote OnlineNormal service07.05.2019 23:30:20
Office OnlineNormal servicePowerPoint OnlineNormal service07.05.2019 23:30:20
Office OnlineNormal serviceWord OnlineNormal service07.05.2019 23:30:20
Office OnlineNormal serviceVisio OnlineNormal service07.05.2019 23:30:20
OneDrive for BusinessNormal serviceOneDrive for BusinessNormal service07.05.2019 23:30:20
Identity ServiceNormal serviceSign-InNormal service07.05.2019 23:30:20
Identity ServiceNormal serviceAdministrationNormal service07.05.2019 23:30:20
Office 365 PortalService restoredPortalNormal serviceMO17923607.05.2019 23:30:20
Office 365 PortalService restoredAdministrationService restoredMO17923607.05.2019 23:30:20
Office 365 PortalService restoredPurchase and BillingNormal serviceMO17923607.05.2019 23:30:20
PlannerNormal servicePlannerNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceProvisioningNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceSharePoint FeaturesNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceTenant AdminNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceSearch and DelveNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceCustom Solutions and WorkflowsNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceProject OnlineNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceOffice Web AppsNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceSP DesignerNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceAccess ServicesNormal service07.05.2019 23:30:20
SharePoint OnlineNormal serviceInfoPath OnlineNormal service07.05.2019 23:30:20
Microsoft StaffHubNormal serviceService and web access issuesNormal service07.05.2019 23:30:20
Microsoft StaffHubNormal serviceWeb client issuesNormal service07.05.2019 23:30:20
Microsoft StaffHubNormal serviceAndroid client issuesNormal service07.05.2019 23:30:20
Microsoft StaffHubNormal serviceiOS client issuesNormal service07.05.2019 23:30:20
SwayNormal serviceSwayNormal service07.05.2019 23:30:20
Yammer EnterpriseNormal serviceYammer ComponentsNormal service07.05.2019 23:30:20
ServiceServiceStatusFeatureFeatureStatusIncidentIdsStatusTime
ServiceServiceStatusIncidentIdsStatusTimeStatusDaysAgo
Exchange OnlineNormal service08.05.2019 02:00:000
Exchange OnlineNormal service07.05.2019 02:00:001
Exchange OnlineNormal service06.05.2019 02:00:002
Exchange OnlineAdditional informationEX17905905.05.2019 02:00:003
Exchange OnlineAdditional informationEX178260, EX17905904.05.2019 02:00:004
Exchange OnlineAdditional informationEX178260, EX17905903.05.2019 02:00:005
Exchange OnlineAdditional informationEX178260, EX17905902.05.2019 02:00:006
Microsoft KaizalaNormal service08.05.2019 02:00:000
Microsoft KaizalaNormal service07.05.2019 02:00:001
Microsoft KaizalaNormal service06.05.2019 02:00:002
Microsoft KaizalaNormal service05.05.2019 02:00:003
Microsoft KaizalaNormal service04.05.2019 02:00:004
Microsoft KaizalaNormal service03.05.2019 02:00:005
Microsoft KaizalaNormal service02.05.2019 02:00:006
Skype for BusinessService degradationLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessAdditional informationLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationLY177449, LY179047, LY17920602.05.2019 02:00:006
Microsoft TeamsNormal service08.05.2019 02:00:000
Microsoft TeamsNormal service07.05.2019 02:00:001
Microsoft TeamsNormal service06.05.2019 02:00:002
Microsoft TeamsNormal service05.05.2019 02:00:003
Microsoft TeamsNormal service04.05.2019 02:00:004
Microsoft TeamsNormal service03.05.2019 02:00:005
Microsoft TeamsNormal service02.05.2019 02:00:006
Mobile Device Management for Office 365Normal service08.05.2019 02:00:000
Mobile Device Management for Office 365Normal service07.05.2019 02:00:001
Mobile Device Management for Office 365Normal service06.05.2019 02:00:002
Mobile Device Management for Office 365Normal service05.05.2019 02:00:003
Mobile Device Management for Office 365Normal service04.05.2019 02:00:004
Mobile Device Management for Office 365Normal service03.05.2019 02:00:005
Mobile Device Management for Office 365Normal service02.05.2019 02:00:006
Office OnlineNormal service08.05.2019 02:00:000
Office OnlineNormal service07.05.2019 02:00:001
Office OnlineNormal service06.05.2019 02:00:002
Office OnlineNormal service05.05.2019 02:00:003
Office OnlineNormal service04.05.2019 02:00:004
Office OnlineNormal service03.05.2019 02:00:005
Office OnlineNormal service02.05.2019 02:00:006
OneDrive for BusinessNormal service08.05.2019 02:00:000
OneDrive for BusinessNormal service07.05.2019 02:00:001
OneDrive for BusinessNormal service06.05.2019 02:00:002
OneDrive for BusinessNormal service05.05.2019 02:00:003
OneDrive for BusinessNormal service04.05.2019 02:00:004
OneDrive for BusinessNormal service03.05.2019 02:00:005
OneDrive for BusinessPost-incident report publishedOD178669, OD17897502.05.2019 02:00:006
Identity ServiceNormal service08.05.2019 02:00:000
Identity ServiceNormal service07.05.2019 02:00:001
Identity ServiceNormal service06.05.2019 02:00:002
Identity ServiceNormal service05.05.2019 02:00:003
Identity ServiceNormal service04.05.2019 02:00:004
Identity ServiceNormal service03.05.2019 02:00:005
Identity ServiceNormal service02.05.2019 02:00:006
Office 365 PortalService restoredMO17923608.05.2019 02:00:000
Office 365 PortalAdditional informationMO17923607.05.2019 02:00:001
Office 365 PortalAdditional informationMO17923606.05.2019 02:00:002
Office 365 PortalAdditional informationMO17923605.05.2019 02:00:003
Office 365 PortalAdditional informationMO17923604.05.2019 02:00:004
Office 365 PortalAdditional informationMO17923603.05.2019 02:00:005
Office 365 PortalPost-incident report publishedMO178979, MO17923602.05.2019 02:00:006
PlannerNormal service08.05.2019 02:00:000
PlannerNormal service07.05.2019 02:00:001
PlannerNormal service06.05.2019 02:00:002
PlannerNormal service05.05.2019 02:00:003
PlannerNormal service04.05.2019 02:00:004
PlannerNormal service03.05.2019 02:00:005
PlannerNormal service02.05.2019 02:00:006
SharePoint OnlineNormal service08.05.2019 02:00:000
SharePoint OnlineNormal service07.05.2019 02:00:001
SharePoint OnlineNormal service06.05.2019 02:00:002
SharePoint OnlineNormal service05.05.2019 02:00:003
SharePoint OnlineNormal service04.05.2019 02:00:004
SharePoint OnlineNormal service03.05.2019 02:00:005
SharePoint OnlinePost-incident report publishedSP178637, SP178746, SP17878902.05.2019 02:00:006
Microsoft StaffHubNormal service08.05.2019 02:00:000
Microsoft StaffHubNormal service07.05.2019 02:00:001
Microsoft StaffHubNormal service06.05.2019 02:00:002
Microsoft StaffHubNormal service05.05.2019 02:00:003
Microsoft StaffHubNormal service04.05.2019 02:00:004
Microsoft StaffHubNormal service03.05.2019 02:00:005
Microsoft StaffHubNormal service02.05.2019 02:00:006
SwayNormal service08.05.2019 02:00:000
SwayNormal service07.05.2019 02:00:001
SwayNormal service06.05.2019 02:00:002
SwayNormal service05.05.2019 02:00:003
SwayNormal service04.05.2019 02:00:004
SwayNormal service03.05.2019 02:00:005
SwayNormal service02.05.2019 02:00:006
Yammer EnterpriseNormal service08.05.2019 02:00:000
Yammer EnterpriseNormal service07.05.2019 02:00:001
Yammer EnterpriseNormal service06.05.2019 02:00:002
Yammer EnterpriseNormal service05.05.2019 02:00:003
Yammer EnterpriseNormal service04.05.2019 02:00:004
Yammer EnterpriseNormal service03.05.2019 02:00:005
Yammer EnterpriseAdditional informationYA17870702.05.2019 02:00:006
ServiceServiceStatusIncidentIdsStatusTimeStatusDaysAgo
ServiceServiceStatusFeatureFeatureStatusIncidentIdsStatusTimeStatusDaysAgo
Exchange OnlineNormal serviceSign-inNormal service08.05.2019 02:00:000
Exchange OnlineNormal serviceE-Mail and calendar accessNormal service08.05.2019 02:00:000
Exchange OnlineNormal serviceE-Mail timely deliveryNormal service08.05.2019 02:00:000
Exchange OnlineNormal serviceManagement and ProvisioningNormal service08.05.2019 02:00:000
Exchange OnlineNormal serviceVoice mailNormal service08.05.2019 02:00:000
Exchange OnlineNormal serviceSign-inNormal service07.05.2019 02:00:001
Exchange OnlineNormal serviceE-Mail and calendar accessNormal service07.05.2019 02:00:001
Exchange OnlineNormal serviceE-Mail timely deliveryNormal service07.05.2019 02:00:001
Exchange OnlineNormal serviceManagement and ProvisioningNormal service07.05.2019 02:00:001
Exchange OnlineNormal serviceVoice mailNormal service07.05.2019 02:00:001
Exchange OnlineNormal serviceSign-inNormal service06.05.2019 02:00:002
Exchange OnlineNormal serviceE-Mail and calendar accessNormal service06.05.2019 02:00:002
Exchange OnlineNormal serviceE-Mail timely deliveryNormal service06.05.2019 02:00:002
Exchange OnlineNormal serviceManagement and ProvisioningNormal service06.05.2019 02:00:002
Exchange OnlineNormal serviceVoice mailNormal service06.05.2019 02:00:002
Exchange OnlineAdditional informationSign-inNormal serviceEX17905905.05.2019 02:00:003
Exchange OnlineAdditional informationE-Mail and calendar accessAdditional informationEX17905905.05.2019 02:00:003
Exchange OnlineAdditional informationE-Mail timely deliveryNormal serviceEX17905905.05.2019 02:00:003
Exchange OnlineAdditional informationManagement and ProvisioningNormal serviceEX17905905.05.2019 02:00:003
Exchange OnlineAdditional informationVoice mailNormal serviceEX17905905.05.2019 02:00:003
Exchange OnlineAdditional informationSign-inNormal serviceEX178260, EX17905904.05.2019 02:00:004
Exchange OnlineAdditional informationE-Mail and calendar accessAdditional informationEX178260, EX17905904.05.2019 02:00:004
Exchange OnlineAdditional informationE-Mail timely deliveryNormal serviceEX178260, EX17905904.05.2019 02:00:004
Exchange OnlineAdditional informationManagement and ProvisioningAdditional informationEX178260, EX17905904.05.2019 02:00:004
Exchange OnlineAdditional informationVoice mailNormal serviceEX178260, EX17905904.05.2019 02:00:004
Exchange OnlineAdditional informationSign-inNormal serviceEX178260, EX17905903.05.2019 02:00:005
Exchange OnlineAdditional informationE-Mail and calendar accessAdditional informationEX178260, EX17905903.05.2019 02:00:005
Exchange OnlineAdditional informationE-Mail timely deliveryNormal serviceEX178260, EX17905903.05.2019 02:00:005
Exchange OnlineAdditional informationManagement and ProvisioningAdditional informationEX178260, EX17905903.05.2019 02:00:005
Exchange OnlineAdditional informationVoice mailNormal serviceEX178260, EX17905903.05.2019 02:00:005
Exchange OnlineAdditional informationSign-inNormal serviceEX178260, EX17905902.05.2019 02:00:006
Exchange OnlineAdditional informationE-Mail and calendar accessAdditional informationEX178260, EX17905902.05.2019 02:00:006
Exchange OnlineAdditional informationE-Mail timely deliveryNormal serviceEX178260, EX17905902.05.2019 02:00:006
Exchange OnlineAdditional informationManagement and ProvisioningAdditional informationEX178260, EX17905902.05.2019 02:00:006
Exchange OnlineAdditional informationVoice mailNormal serviceEX178260, EX17905902.05.2019 02:00:006
Microsoft KaizalaNormal serviceKaizala MessagingNormal service08.05.2019 02:00:000
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service08.05.2019 02:00:000
Microsoft KaizalaNormal serviceKaizala MessagingNormal service07.05.2019 02:00:001
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service07.05.2019 02:00:001
Microsoft KaizalaNormal serviceKaizala MessagingNormal service06.05.2019 02:00:002
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service06.05.2019 02:00:002
Microsoft KaizalaNormal serviceKaizala MessagingNormal service05.05.2019 02:00:003
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service05.05.2019 02:00:003
Microsoft KaizalaNormal serviceKaizala MessagingNormal service04.05.2019 02:00:004
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service04.05.2019 02:00:004
Microsoft KaizalaNormal serviceKaizala MessagingNormal service03.05.2019 02:00:005
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service03.05.2019 02:00:005
Microsoft KaizalaNormal serviceKaizala MessagingNormal service02.05.2019 02:00:006
Microsoft KaizalaNormal serviceKaizala Management PortalNormal service02.05.2019 02:00:006
Skype for BusinessService degradationAudio and VideoNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationFederationNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationManagement and ProvisioningService degradationLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationSign-InNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationAll FeaturesService degradationLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationOnline MeetingsNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationInstant MessagingNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationPresenceNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationMobilityNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationCloud PBXNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationPSTN CallingNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessService degradationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920608.05.2019 02:00:000
Skype for BusinessAdditional informationAudio and VideoNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationFederationNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationManagement and ProvisioningAdditional informationLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationSign-InNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationAll FeaturesAdditional informationLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationOnline MeetingsNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationInstant MessagingNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationPresenceNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationMobilityNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationCloud PBXNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationPSTN CallingNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920607.05.2019 02:00:001
Skype for BusinessAdditional informationAudio and VideoNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationFederationNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationManagement and ProvisioningAdditional informationLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationSign-InNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationAll FeaturesAdditional informationLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationOnline MeetingsNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationInstant MessagingNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationPresenceNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationMobilityNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationCloud PBXNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationPSTN CallingNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920606.05.2019 02:00:002
Skype for BusinessAdditional informationAudio and VideoNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationFederationNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationManagement and ProvisioningAdditional informationLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationSign-InNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationAll FeaturesAdditional informationLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationOnline MeetingsNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationInstant MessagingNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationPresenceNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationMobilityNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationCloud PBXNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationPSTN CallingNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920605.05.2019 02:00:003
Skype for BusinessAdditional informationAudio and VideoNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationFederationNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationManagement and ProvisioningAdditional informationLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationSign-InNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationAll FeaturesAdditional informationLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationOnline MeetingsNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationInstant MessagingNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationPresenceNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationMobilityNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationCloud PBXNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationPSTN CallingNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920604.05.2019 02:00:004
Skype for BusinessAdditional informationAudio and VideoNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationFederationNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationManagement and ProvisioningAdditional informationLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationSign-InNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationAll FeaturesAdditional informationLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationOnline MeetingsNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationInstant MessagingNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationPresenceNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationMobilityNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationCloud PBXNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationPSTN CallingNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920603.05.2019 02:00:005
Skype for BusinessAdditional informationAudio and VideoNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationFederationNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationManagement and ProvisioningAdditional informationLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationSign-InNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationAll FeaturesAdditional informationLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationDial-In ConferencingNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationOnline MeetingsNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationInstant MessagingNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationPresenceNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationMobilityNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationCloud PBXNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationPSTN CallingNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Skype for BusinessAdditional informationMeeting BroadcastNormal serviceLY177449, LY179047, LY17920602.05.2019 02:00:006
Microsoft TeamsNormal serviceTeams ComponentsNormal service08.05.2019 02:00:000
Microsoft TeamsNormal serviceTeams ComponentsNormal service07.05.2019 02:00:001
Microsoft TeamsNormal serviceTeams ComponentsNormal service06.05.2019 02:00:002
Microsoft TeamsNormal serviceTeams ComponentsNormal service05.05.2019 02:00:003
Microsoft TeamsNormal serviceTeams ComponentsNormal service04.05.2019 02:00:004
Microsoft TeamsNormal serviceTeams ComponentsNormal service03.05.2019 02:00:005
Microsoft TeamsNormal serviceTeams ComponentsNormal service02.05.2019 02:00:006
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service08.05.2019 02:00:000
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service07.05.2019 02:00:001
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service06.05.2019 02:00:002
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service05.05.2019 02:00:003
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service04.05.2019 02:00:004
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service03.05.2019 02:00:005
Mobile Device Management for Office 365Normal serviceMobile Device ManagementNormal service02.05.2019 02:00:006
Office OnlineNormal serviceExcel OnlineNormal service08.05.2019 02:00:000
Office OnlineNormal serviceOneNote OnlineNormal service08.05.2019 02:00:000
Office OnlineNormal servicePowerPoint OnlineNormal service08.05.2019 02:00:000
Office OnlineNormal serviceWord OnlineNormal service08.05.2019 02:00:000
Office OnlineNormal serviceVisio OnlineNormal service08.05.2019 02:00:000
Office OnlineNormal serviceExcel OnlineNormal service07.05.2019 02:00:001
Office OnlineNormal serviceOneNote OnlineNormal service07.05.2019 02:00:001
Office OnlineNormal servicePowerPoint OnlineNormal service07.05.2019 02:00:001
Office OnlineNormal serviceWord OnlineNormal service07.05.2019 02:00:001
Office OnlineNormal serviceVisio OnlineNormal service07.05.2019 02:00:001
Office OnlineNormal serviceExcel OnlineNormal service06.05.2019 02:00:002
Office OnlineNormal serviceOneNote OnlineNormal service06.05.2019 02:00:002
Office OnlineNormal servicePowerPoint OnlineNormal service06.05.2019 02:00:002
Office OnlineNormal serviceWord OnlineNormal service06.05.2019 02:00:002
Office OnlineNormal serviceVisio OnlineNormal service06.05.2019 02:00:002
Office OnlineNormal serviceExcel OnlineNormal service05.05.2019 02:00:003
Office OnlineNormal serviceOneNote OnlineNormal service05.05.2019 02:00:003
Office OnlineNormal servicePowerPoint OnlineNormal service05.05.2019 02:00:003
Office OnlineNormal serviceWord OnlineNormal service05.05.2019 02:00:003
Office OnlineNormal serviceVisio OnlineNormal service05.05.2019 02:00:003
Office OnlineNormal serviceExcel OnlineNormal service04.05.2019 02:00:004
Office OnlineNormal serviceOneNote OnlineNormal service04.05.2019 02:00:004
Office OnlineNormal servicePowerPoint OnlineNormal service04.05.2019 02:00:004
Office OnlineNormal serviceWord OnlineNormal service04.05.2019 02:00:004
Office OnlineNormal serviceVisio OnlineNormal service04.05.2019 02:00:004
Office OnlineNormal serviceExcel OnlineNormal service03.05.2019 02:00:005
Office OnlineNormal serviceOneNote OnlineNormal service03.05.2019 02:00:005
Office OnlineNormal servicePowerPoint OnlineNormal service03.05.2019 02:00:005
Office OnlineNormal serviceWord OnlineNormal service03.05.2019 02:00:005
Office OnlineNormal serviceVisio OnlineNormal service03.05.2019 02:00:005
Office OnlineNormal serviceExcel OnlineNormal service02.05.2019 02:00:006
Office OnlineNormal serviceOneNote OnlineNormal service02.05.2019 02:00:006
Office OnlineNormal servicePowerPoint OnlineNormal service02.05.2019 02:00:006
Office OnlineNormal serviceWord OnlineNormal service02.05.2019 02:00:006
Office OnlineNormal serviceVisio OnlineNormal service02.05.2019 02:00:006
OneDrive for BusinessNormal serviceOneDrive for BusinessNormal service08.05.2019 02:00:000
OneDrive for BusinessNormal serviceOneDrive for BusinessNormal service07.05.2019 02:00:001
OneDrive for BusinessNormal serviceOneDrive for BusinessNormal service06.05.2019 02:00:002
OneDrive for BusinessNormal serviceOneDrive for BusinessNormal service05.05.2019 02:00:003
OneDrive for BusinessNormal serviceOneDrive for BusinessNormal service04.05.2019 02:00:004
OneDrive for BusinessNormal serviceOneDrive for BusinessNormal service03.05.2019 02:00:005
OneDrive for BusinessPost-incident report publishedOneDrive for BusinessPost-incident report publishedOD178669, OD17897502.05.2019 02:00:006
Identity ServiceNormal serviceSign-InNormal service08.05.2019 02:00:000
Identity ServiceNormal serviceAdministrationNormal service08.05.2019 02:00:000
Identity ServiceNormal serviceSign-InNormal service07.05.2019 02:00:001
Identity ServiceNormal serviceAdministrationNormal service07.05.2019 02:00:001
Identity ServiceNormal serviceSign-InNormal service06.05.2019 02:00:002
Identity ServiceNormal serviceAdministrationNormal service06.05.2019 02:00:002
Identity ServiceNormal serviceSign-InNormal service05.05.2019 02:00:003
Identity ServiceNormal serviceAdministrationNormal service05.05.2019 02:00:003
Identity ServiceNormal serviceSign-InNormal service04.05.2019 02:00:004
Identity ServiceNormal serviceAdministrationNormal service04.05.2019 02:00:004
Identity ServiceNormal serviceSign-InNormal service03.05.2019 02:00:005
Identity ServiceNormal serviceAdministrationNormal service03.05.2019 02:00:005
Identity ServiceNormal serviceSign-InNormal service02.05.2019 02:00:006
Identity ServiceNormal serviceAdministrationNormal service02.05.2019 02:00:006
Office 365 PortalService restoredPortalNormal serviceMO17923608.05.2019 02:00:000
Office 365 PortalService restoredAdministrationService restoredMO17923608.05.2019 02:00:000
Office 365 PortalService restoredPurchase and BillingNormal serviceMO17923608.05.2019 02:00:000
Office 365 PortalAdditional informationPortalNormal serviceMO17923607.05.2019 02:00:001
Office 365 PortalAdditional informationAdministrationAdditional informationMO17923607.05.2019 02:00:001
Office 365 PortalAdditional informationPurchase and BillingNormal serviceMO17923607.05.2019 02:00:001
Office 365 PortalAdditional informationPortalNormal serviceMO17923606.05.2019 02:00:002
Office 365 PortalAdditional informationAdministrationAdditional informationMO17923606.05.2019 02:00:002
Office 365 PortalAdditional informationPurchase and BillingNormal serviceMO17923606.05.2019 02:00:002
Office 365 PortalAdditional informationPortalNormal serviceMO17923605.05.2019 02:00:003
Office 365 PortalAdditional informationAdministrationAdditional informationMO17923605.05.2019 02:00:003
Office 365 PortalAdditional informationPurchase and BillingNormal serviceMO17923605.05.2019 02:00:003
Office 365 PortalAdditional informationPortalNormal serviceMO17923604.05.2019 02:00:004
Office 365 PortalAdditional informationAdministrationAdditional informationMO17923604.05.2019 02:00:004
Office 365 PortalAdditional informationPurchase and BillingNormal serviceMO17923604.05.2019 02:00:004
Office 365 PortalAdditional informationPortalNormal serviceMO17923603.05.2019 02:00:005
Office 365 PortalAdditional informationAdministrationAdditional informationMO17923603.05.2019 02:00:005
Office 365 PortalAdditional informationPurchase and BillingNormal serviceMO17923603.05.2019 02:00:005
Office 365 PortalPost-incident report publishedPortalPost-incident report publishedMO178979, MO17923602.05.2019 02:00:006
Office 365 PortalPost-incident report publishedAdministrationAdditional informationMO178979, MO17923602.05.2019 02:00:006
Office 365 PortalPost-incident report publishedPurchase and BillingNormal serviceMO178979, MO17923602.05.2019 02:00:006
PlannerNormal servicePlannerNormal service08.05.2019 02:00:000
PlannerNormal servicePlannerNormal service07.05.2019 02:00:001
PlannerNormal servicePlannerNormal service06.05.2019 02:00:002
PlannerNormal servicePlannerNormal service05.05.2019 02:00:003
PlannerNormal servicePlannerNormal service04.05.2019 02:00:004
PlannerNormal servicePlannerNormal service03.05.2019 02:00:005
PlannerNormal servicePlannerNormal service02.05.2019 02:00:006
SharePoint OnlineNormal serviceProvisioningNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceSharePoint FeaturesNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceTenant AdminNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceSearch and DelveNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceCustom Solutions and WorkflowsNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceProject OnlineNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceOffice Web AppsNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceSP DesignerNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceAccess ServicesNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceInfoPath OnlineNormal service08.05.2019 02:00:000
SharePoint OnlineNormal serviceProvisioningNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceSharePoint FeaturesNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceTenant AdminNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceSearch and DelveNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceCustom Solutions and WorkflowsNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceProject OnlineNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceOffice Web AppsNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceSP DesignerNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceAccess ServicesNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceInfoPath OnlineNormal service07.05.2019 02:00:001
SharePoint OnlineNormal serviceProvisioningNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceSharePoint FeaturesNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceTenant AdminNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceSearch and DelveNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceCustom Solutions and WorkflowsNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceProject OnlineNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceOffice Web AppsNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceSP DesignerNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceAccess ServicesNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceInfoPath OnlineNormal service06.05.2019 02:00:002
SharePoint OnlineNormal serviceProvisioningNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceSharePoint FeaturesNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceTenant AdminNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceSearch and DelveNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceCustom Solutions and WorkflowsNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceProject OnlineNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceOffice Web AppsNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceSP DesignerNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceAccess ServicesNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceInfoPath OnlineNormal service05.05.2019 02:00:003
SharePoint OnlineNormal serviceProvisioningNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceSharePoint FeaturesNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceTenant AdminNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceSearch and DelveNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceCustom Solutions and WorkflowsNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceProject OnlineNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceOffice Web AppsNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceSP DesignerNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceAccess ServicesNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceInfoPath OnlineNormal service04.05.2019 02:00:004
SharePoint OnlineNormal serviceProvisioningNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceSharePoint FeaturesNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceTenant AdminNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceSearch and DelveNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceCustom Solutions and WorkflowsNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceProject OnlineNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceOffice Web AppsNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceSP DesignerNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceAccess ServicesNormal service03.05.2019 02:00:005
SharePoint OnlineNormal serviceInfoPath OnlineNormal service03.05.2019 02:00:005
SharePoint OnlinePost-incident report publishedProvisioningNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedSharePoint FeaturesPost-incident report publishedSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedTenant AdminNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedSearch and DelveNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedCustom Solutions and WorkflowsNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedProject OnlineNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedOffice Web AppsNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedSP DesignerNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedAccess ServicesNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
SharePoint OnlinePost-incident report publishedInfoPath OnlineNormal serviceSP178637, SP178746, SP17878902.05.2019 02:00:006
Microsoft StaffHubNormal serviceService and web access issuesNormal service08.05.2019 02:00:000
Microsoft StaffHubNormal serviceWeb client issuesNormal service08.05.2019 02:00:000
Microsoft StaffHubNormal serviceAndroid client issuesNormal service08.05.2019 02:00:000
Microsoft StaffHubNormal serviceiOS client issuesNormal service08.05.2019 02:00:000
Microsoft StaffHubNormal serviceService and web access issuesNormal service07.05.2019 02:00:001
Microsoft StaffHubNormal serviceWeb client issuesNormal service07.05.2019 02:00:001
Microsoft StaffHubNormal serviceAndroid client issuesNormal service07.05.2019 02:00:001
Microsoft StaffHubNormal serviceiOS client issuesNormal service07.05.2019 02:00:001
Microsoft StaffHubNormal serviceService and web access issuesNormal service06.05.2019 02:00:002
Microsoft StaffHubNormal serviceWeb client issuesNormal service06.05.2019 02:00:002
Microsoft StaffHubNormal serviceAndroid client issuesNormal service06.05.2019 02:00:002
Microsoft StaffHubNormal serviceiOS client issuesNormal service06.05.2019 02:00:002
Microsoft StaffHubNormal serviceService and web access issuesNormal service05.05.2019 02:00:003
Microsoft StaffHubNormal serviceWeb client issuesNormal service05.05.2019 02:00:003
Microsoft StaffHubNormal serviceAndroid client issuesNormal service05.05.2019 02:00:003
Microsoft StaffHubNormal serviceiOS client issuesNormal service05.05.2019 02:00:003
Microsoft StaffHubNormal serviceService and web access issuesNormal service04.05.2019 02:00:004
Microsoft StaffHubNormal serviceWeb client issuesNormal service04.05.2019 02:00:004
Microsoft StaffHubNormal serviceAndroid client issuesNormal service04.05.2019 02:00:004
Microsoft StaffHubNormal serviceiOS client issuesNormal service04.05.2019 02:00:004
Microsoft StaffHubNormal serviceService and web access issuesNormal service03.05.2019 02:00:005
Microsoft StaffHubNormal serviceWeb client issuesNormal service03.05.2019 02:00:005
Microsoft StaffHubNormal serviceAndroid client issuesNormal service03.05.2019 02:00:005
Microsoft StaffHubNormal serviceiOS client issuesNormal service03.05.2019 02:00:005
Microsoft StaffHubNormal serviceService and web access issuesNormal service02.05.2019 02:00:006
Microsoft StaffHubNormal serviceWeb client issuesNormal service02.05.2019 02:00:006
Microsoft StaffHubNormal serviceAndroid client issuesNormal service02.05.2019 02:00:006
Microsoft StaffHubNormal serviceiOS client issuesNormal service02.05.2019 02:00:006
SwayNormal serviceSwayNormal service08.05.2019 02:00:000
SwayNormal serviceSwayNormal service07.05.2019 02:00:001
SwayNormal serviceSwayNormal service06.05.2019 02:00:002
SwayNormal serviceSwayNormal service05.05.2019 02:00:003
SwayNormal serviceSwayNormal service04.05.2019 02:00:004
SwayNormal serviceSwayNormal service03.05.2019 02:00:005
SwayNormal serviceSwayNormal service02.05.2019 02:00:006
Yammer EnterpriseNormal serviceYammer ComponentsNormal service08.05.2019 02:00:000
Yammer EnterpriseNormal serviceYammer ComponentsNormal service07.05.2019 02:00:001
Yammer EnterpriseNormal serviceYammer ComponentsNormal service06.05.2019 02:00:002
Yammer EnterpriseNormal serviceYammer ComponentsNormal service05.05.2019 02:00:003
Yammer EnterpriseNormal serviceYammer ComponentsNormal service04.05.2019 02:00:004
Yammer EnterpriseNormal serviceYammer ComponentsNormal service03.05.2019 02:00:005
Yammer EnterpriseAdditional informationYammer ComponentsAdditional informationYA17870702.05.2019 02:00:006
ServiceServiceStatusFeatureFeatureStatusIncidentIdsStatusTimeStatusDaysAgo
IDTitleLastUpdatedTimeLastUpdatedDaysAgoSeverityStartTimeEndTimeActionTypeClassificationAffectedServiceMessageType
MC179277New Feature: Create SharePoint lists from Excel or other lists08.05.2019 00:53:000Normal08.05.2019 00:53:0001.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC179211New Feature: Enable modern communication site experience at the classic root site of your tenant07.05.2019 01:17:001Normal07.05.2019 01:17:0006.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC179202New Feature: OneDrive sync client Get Help06.05.2019 21:29:002Normal06.05.2019 21:29:0021.06.2019 09:00:00AwarenessAdvisoryOneDrive for BusinessMessageCenter
MC178681Outlook on the web (opt-in) - Share availability from email compose01.05.2019 23:30:007Normal01.05.2019 23:30:0029.08.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC178679New Feature: Shifts Multiteam Support01.05.2019 22:40:007Normal01.05.2019 22:40:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC178678New Feature: Time Clock in Shifts01.05.2019 22:39:007Normal01.05.2019 22:39:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC178667Feature update: Office 365 Account Manager is getting updated01.05.2019 20:16:007Normal01.05.2019 20:16:0015.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC178666New Feature: Manage discovery of private teams in Microsoft Teams01.05.2019 20:04:007Normal01.05.2019 20:04:0031.07.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC178638Updated Feature: Actionable Messages now support Payments in Outlook on the web01.05.2019 01:01:007Normal01.05.2019 01:01:0014.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC178636Updated Feature: Microsoft Secure Score Integrated into Microsoft 365 Security Center01.05.2019 00:44:007Normal01.05.2019 00:44:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC178633Updated Feature: Skype for Business Certified IP Phones: Microsoft Online Device Registration updates01.05.2019 00:15:007Normal01.05.2019 00:15:0030.07.2019 09:00:00ActionAdvisorySkype for BusinessMessageCenter
MC178632Updated Feature: General Availability of the updated Office 365 Advanced eDiscovery experience01.05.2019 00:09:007Normal01.05.2019 00:09:0031.05.2019 09:00:00AwarenessAdvisoryOffice 365 PortalMessageCenter
MC178631Updated Feature: Microsoft Teams PowerShell30.04.2019 23:52:007Normal30.04.2019 23:52:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC178630Feature update: Yammer simplified first-time login experience30.04.2019 22:53:008Normal30.04.2019 22:53:0015.07.2019 09:00:00AwarenessAdvisoryYammer EnterpriseMessageCenter
MC178555Updated Feature: Authentication administrator and Privileged authentication administrator roles30.04.2019 00:39:008Normal30.04.2019 00:39:0028.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC178539New Feature: New Supervision Offensive Language intelligent filter30.04.2019 00:25:008Normal30.04.2019 00:25:0028.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC178523New Feature: Groups in Outlook: 'Brownbag'-style events29.04.2019 22:09:009Normal29.04.2019 22:09:0028.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC178514Updated Feature: Refreshed Folder Icon Design29.04.2019 19:11:009Normal29.04.2019 19:11:0028.06.2019 09:00:00AwarenessAdvisorySharePoint Online,OneDrive for BusinessMessageCenter
MC178455New Feature: Outlook on the web - suggested attachments27.04.2019 01:36:0011Normal27.04.2019 01:36:0001.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC178385New feature: OneDrive - updated "manage access" pane for classic user interface26.04.2019 00:28:0012Normal26.04.2019 00:28:0001.07.2019 09:00:00AwarenessAdvisorySharePoint Online,OneDrive for BusinessMessageCenter
MC178383New Feature: new Outlook on the web (opt-in) - browse rooms26.04.2019 00:04:0012Normal26.04.2019 00:04:0031.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC178376New feature: SharePoint Online news and page authors will now receive emails with comments, replies and likes25.04.2019 20:59:0013Normal25.04.2019 20:59:0031.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC178371Updated feature: User and group based assignment in the Azure AD admin center for Microsoft and LinkedIn integration25.04.2019 19:55:0013Normal25.04.2019 19:55:0030.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC178370New feature: error resolution flow for illegal file and folder names in OneDrive25.04.2019 19:21:0013Normal25.04.2019 19:21:0001.06.2019 09:00:00AwarenessAdvisoryOneDrive,OneDrive for BusinessMessageCenter
MC178286Updated feature: Document Sets in SharePoint Online25.04.2019 00:46:0013Normal25.04.2019 00:46:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC178285New feature: SharePoint Online Column Formatting - Data Bars in Lists and Libraries25.04.2019 00:39:0013Normal25.04.2019 00:39:0021.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC178278New feature: SharePoint Online news and page authors will now receive emails with comments, replies and likes24.04.2019 23:05:0014Normal24.04.2019 23:05:0031.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC178265New feature: error resolution flow for illegal file and folder names in OneDrive24.04.2019 19:30:0014Normal24.04.2019 19:30:0001.06.2019 09:00:00AwarenessAdvisoryOneDrive,OneDrive for BusinessMessageCenter
MC178198Updated timeline: Office 365 will retire 3DES starting July 10, 201923.04.2019 22:38:0015Normal23.04.2019 22:38:0015.08.2019 09:00:00ActionAdvisoryMessageCenter
MC178008Updated Feature: Changes to definition of Files Shared Internally19.04.2019 18:22:0019Normal19.04.2019 18:22:0027.06.2019 09:00:00AwarenessAdvisorySharePoint Online,Power BI,OneDrive for BusinessMessageCenter
MC177977Office 365 Skype for Business will retire 3DES starting July 10, 201919.04.2019 00:58:0019Normal19.04.2019 00:58:0030.08.2019 09:00:00ActionAdvisorySkype for BusinessMessageCenter
MC177960Updated feature: Group-connected team site homepage19.04.2019 00:24:0019Normal19.04.2019 00:24:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC177905Updated feature: Sharing links that block downloads for Office files18.04.2019 01:59:0020Normal18.04.2019 01:59:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC177896New Feature: Office 365 Group card enhancements17.04.2019 23:16:0021Normal17.04.2019 23:16:0019.07.2019 09:00:00AwarenessAdvisoryExchange Online,SharePoint OnlineMessageCenter
MC177817New Feature: Busy on Busy in Microsoft Teams16.04.2019 19:50:0022Normal16.04.2019 19:50:0001.07.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC177815Updates are coming to the authentication behavior on Azure AD (M365) sign-in pages16.04.2019 19:43:0022Normal16.04.2019 19:43:0019.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC177812Now use larger, more flexible image types to upload your company logo in the Office 365 navigation bar16.04.2019 19:02:0022Normal16.04.2019 19:02:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC177653Dynamics 365 - Updates coming to the authentication behavior on Dynamics 365 sign-in pages12.04.2019 20:13:0026Normal12.04.2019 20:13:0031.12.2019 19:13:00AwarenessAdvisoryMessageCenter
MC177651We're making an update to Office 365 Enterprise plan names12.04.2019 19:52:0026Normal12.04.2019 19:52:0001.06.2019 09:00:00AwarenessAdvisoryOffice 365 PortalMessageCenter
MC177607Dynamics 365 - Changes are coming to your sign-in page - Branding for Sign-out and Authentication Error Screens12.04.2019 01:32:0026Normal12.04.2019 01:32:0012.05.2019 01:32:09AwarenessAdvisoryMessageCenter
MC177601New feature: New Outlook on the web - Search filters11.04.2019 23:55:0026Normal11.04.2019 23:55:0001.08.2019 09:00:00AwarenessAdvisoryExchange Online,Outlook.comMessageCenter
MC177594New Feature: Full-fidelity shared libraries in OneDrive11.04.2019 22:42:0027Normal11.04.2019 22:42:0001.07.2019 09:00:00AwarenessAdvisoryOneDrive for BusinessMessageCenter
MC177592Updated - Feature update: Structural navigation performance banner11.04.2019 22:25:0027Normal11.04.2019 22:25:0001.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC177588New feature: Sign out and authentication error screens to show company branding11.04.2019 20:23:0027Normal11.04.2019 20:23:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC177587Feature update: Focus on your active teams11.04.2019 20:17:0027Normal11.04.2019 20:17:0030.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC177579Updated release plan for Sharable links in Word and Outlook for Windows and mobile11.04.2019 18:36:0027Normal11.04.2019 18:36:0031.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC177517Updated Feature: Teams support for Meeting Migration Service11.04.2019 00:45:0027Normal11.04.2019 00:45:0028.06.2019 09:00:00AwarenessAdvisorySkype for Business,Microsoft TeamsMessageCenter
MC177503Updated Feature: Role changes: Information Protection Administrator and Privileged Role Administrator10.04.2019 21:14:0028Normal10.04.2019 21:14:0028.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC177501Updated - Updated Feature: We’re changing your default SharePoint admin center experience10.04.2019 19:52:0028Normal10.04.2019 19:52:0026.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC177427New feature: audience targeting in SharePoint Online organizational news09.04.2019 18:51:0029Normal09.04.2019 18:51:0001.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC177244Microsoft Kaizala Pro will be included as part of your Office 365 service starting late-May05.04.2019 23:19:0033Normal05.04.2019 23:19:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft KaizalaMessageCenter
MC177243Microsoft Kaizala Pro will be turned on by default starting late-May05.04.2019 23:09:0033Normal05.04.2019 23:09:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft KaizalaMessageCenter
MC177199Changes to Coming Soon in Outlook for Windows05.04.2019 05:14:0033Normal05.04.2019 05:14:0001.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC177121Updated Feature: New setting in CsTeamsMeetingPolicy to manage meetings chat04.04.2019 03:58:0034Normal04.04.2019 03:58:0030.06.2019 08:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC177122Reminder: SharePoint tenant opt-out for modern lists is retiring in 201904.04.2019 03:42:0034Normal04.04.2019 03:42:0031.05.2019 09:00:00ActionAdvisorySharePoint OnlineMessageCenter
MC177013New feature: Easily add new members to your team03.04.2019 00:44:0035Normal03.04.2019 00:44:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC176992New Feature: To-Do02.04.2019 18:36:0036Normal02.04.2019 18:36:0015.06.2019 09:00:00AwarenessAdvisoryPlanner,Microsoft To-DoMessageCenter
MC176911StaffHub to Shifts in Microsoft Teams migration update01.04.2019 19:18:0037Normal01.04.2019 19:18:0030.12.2019 09:00:00AwarenessAdvisoryMessageCenter
MC176718Voicemail is now available for all VoIP-enabled users in Microsoft Teams29.03.2019 01:39:0040Normal29.03.2019 01:39:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC176702Updated - We’re increasing access to Microsoft Search across Office 36528.03.2019 21:57:0041Normal28.03.2019 21:57:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC176696New feature: Automatic processing of small changes in meeting details28.03.2019 20:48:0041Normal28.03.2019 20:48:0031.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC176548New feature: Praise in Microsoft Teams27.03.2019 01:28:0042Normal27.03.2019 01:28:0001.06.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC176515Updated rollout of Mail Reads within Exchange Online Mailbox Audit26.03.2019 19:26:0043Normal26.03.2019 19:26:0024.05.2019 21:30:00AwarenessAdvisoryExchange OnlineMessageCenter
MC176421Updated Feature: Mail flow insights25.03.2019 21:44:0044Normal25.03.2019 21:44:0028.06.2019 09:00:00AwarenessAdvisoryExchange Online,Exchange Online ProtectionMessageCenter
MC176243Updated Feature: Microsoft Teams Commercial Cloud Trial21.03.2019 18:59:0048Normal21.03.2019 18:59:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC176028New feature: Smart time suggestions in Outlook on the web19.03.2019 01:36:0050Normal19.03.2019 01:36:0001.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC175885Updated Feature: Updates to Microsoft Whiteboard15.03.2019 17:23:0054Normal15.03.2019 17:23:0015.08.2019 09:00:00AwarenessAdvisoryMessageCenter
MC175807Updated feature: Microsoft 365 Admin Center14.03.2019 17:31:0055Normal14.03.2019 17:31:0028.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC175805Sharable links in Word and Outlook for Windows and mobile14.03.2019 17:17:0055Normal14.03.2019 17:17:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC175765New feature: Rich text formatting in Yammer13.03.2019 22:20:0056Normal13.03.2019 22:20:0015.06.2019 09:00:00AwarenessAdvisoryYammer EnterpriseMessageCenter
MC175683New feature: Share and coauthor documents with LinkedIn connections12.03.2019 19:04:0057Normal12.03.2019 19:04:0015.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC175518Updated - New feature: Connected web parts for SharePoint Online09.03.2019 05:24:0060Normal09.03.2019 05:24:0017.05.2019 10:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC175361Feature update - Enabling the Flow app endpoint within Teams06.03.2019 22:00:0063Normal06.03.2019 22:00:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC175354New feature: New Yammer tab for Microsoft Teams now available06.03.2019 19:33:0063Normal06.03.2019 19:33:0005.06.2019 09:00:00AwarenessAdvisoryYammer Enterprise,Yammer.comMessageCenter
MC175309Some Yammer IDs returned by the REST API have grown beyond 32 bits06.03.2019 01:41:0063Normal06.03.2019 01:41:0017.05.2019 10:00:00ActionAdvisoryYammer EnterpriseMessageCenter
MC175274The Lifecycle Dashboards are now available to help you ensure user access to Office 36505.03.2019 19:30:0064Normal05.03.2019 19:30:0001.11.2020 08:00:00AwarenessAdvisoryMessageCenter
MC175213Updated feature: We're simplifying channel action terminology in Teams05.03.2019 01:24:0064Normal05.03.2019 01:24:0030.06.2019 10:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC175147Outlook mobile supports Teams Meetings - updated roll out plans02.03.2019 03:54:0067Normal02.03.2019 03:54:0031.05.2019 09:00:00ActionAdvisoryMessageCenter
MC175134New feature: Site navigation reorder via Drag and Drop01.03.2019 22:49:0068Normal01.03.2019 22:49:0030.05.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC175099Updated feature: Calls app available for all VoIP enabled users in Microsoft Teams01.03.2019 04:11:0068Normal01.03.2019 04:11:0030.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC173965Updated feature: Groups in Outlook - easier membership management21.02.2019 21:33:0076Normal21.02.2019 21:33:0020.05.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC173956New feature: Open file links directly in Office desktop apps21.02.2019 20:12:0076Normal21.02.2019 20:12:0030.09.2019 09:00:00AwarenessAdvisoryMessageCenter
MC173915Feature update - Mobile admin app update, including device management21.02.2019 03:48:0076Normal21.02.2019 03:48:0019.08.2019 09:00:00AwarenessAdvisoryMessageCenter
MC173908We’re making a change to non-delivery report notifications21.02.2019 00:28:0076Normal21.02.2019 00:28:0021.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC173895Outlook mobile supports Teams Meetings20.02.2019 21:45:0077Normal20.02.2019 21:45:0028.06.2019 10:00:00AwarenessAdvisoryMessageCenter
MC173771We’re changing your default SharePoint admin center experience19.02.2019 01:22:0078Normal19.02.2019 01:22:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC173616Clutter for Outlook is being retired beginning January 31, 202015.02.2019 03:14:0082Normal15.02.2019 03:14:0001.03.2020 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC173615New feature: SharePoint Online gets Sticky Column Headers for Lists and Libraries15.02.2019 03:10:0082Normal15.02.2019 03:10:0031.05.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC173597Microsoft Teams desktop app coming to new Office 365 ProPlus installs14.02.2019 22:38:0083Normal14.02.2019 22:38:0016.08.2019 09:00:00AwarenessAdvisoryMessageCenter
MC173377Updated feature: New Tasks module in Outlook on the Web12.02.2019 00:21:0085Normal12.02.2019 00:21:0031.05.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC173034New Feature: Microsoft 365 Public Roadmap Updates06.02.2019 22:28:0091Normal06.02.2019 22:28:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC172925SharePoint tenant opt-out for modern lists is retiring in 201904.02.2019 21:16:0093Normal04.02.2019 21:16:0031.05.2019 09:00:00ActionAdvisorySharePoint OnlineMessageCenter
MC172851New feature: Changes to PowerPoint and Word to open files faster01.02.2019 19:51:0096Normal01.02.2019 19:51:0001.06.2019 10:00:00AwarenessAdvisorySharePoint Online,OneDrive for BusinessMessageCenter
MC172700Updated - The Office 365 Home Page is becoming the default start page for all Office 365 commercial users30.01.2019 01:04:0098Normal30.01.2019 01:04:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC172691Upated: Compliance Manager new experience29.01.2019 22:12:0099Normal29.01.2019 22:12:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC172548We’re making it easier for your users to save files to OneDrive Consumer, OneDrive for Business, and SharePoint Online26.01.2019 00:33:00102Normal26.01.2019 00:33:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC172285Updated feature: Planner Notifications for Teams18.01.2019 23:07:00110Normal18.01.2019 23:07:0001.08.2019 09:00:00AwarenessAdvisoryPlanner,Microsoft TeamsMessageCenter
MC171955Update - Updated feature: New "Sign-in options" link on the Microsoft 365 login page12.01.2019 00:02:00116Normal12.01.2019 00:02:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC171786Reminder: We’re retiring StaffHub and migrating your organization to Microsoft Teams08.01.2019 19:11:00120Normal08.01.2019 19:11:0015.08.2019 09:00:00ActionAdvisoryMessageCenter
MC165927Yammer group files in Office 365 connected groups will now be stored in SharePoint28.11.2018 22:59:00161Normal28.11.2018 22:59:0026.11.2019 09:00:00AwarenessAdvisoryYammer EnterpriseMessageCenter
MC151704Updated feature: The help and support pane is now available from the Office 365 navbar19.10.2018 23:42:00200Normal19.10.2018 23:42:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC149144New schedule management and Home screen features coming to Teams; StaffHub will be retired25.09.2018 22:13:00225Normal25.09.2018 22:13:0001.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC143569We’re making changes to Exchange Web Services for Office 36503.07.2018 22:15:00309Normal03.07.2018 22:15:0013.11.2020 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC143503Update on Visio Web Access from SharePoint Online02.07.2018 17:28:00310Normal02.07.2018 17:28:0030.10.2019 08:00:00ActionAdvisorySharePoint OnlineMessageCenter
MC134661Important update on Windows phone apps for Skype for Business21.04.2018 00:52:00382Normal21.04.2018 00:52:0015.01.2020 08:00:00AwarenessAdvisorySkype for BusinessMessageCenter
IDTitleLastUpdatedTimeLastUpdatedDaysAgoSeverityStartTimeEndTimeActionTypeClassificationAffectedServiceMessageType
IDPublishedTimePublishedDaysAgoTitleMessageLastUpdatedTimeLastUpdatedDaysAgoSeverityStartTimeEndTimeActionTypeClassificationAffectedServiceMessageType
MC17927708.05.2019 00:53:000New Feature: Create SharePoint lists from Excel or other lists

Create SharePoint lists from Excel or other lists is a new Office 365 feature. We'll begin rolling this feature out soon.


This enhancement is related to Microsoft 365 Roadmap ID 33603.


[How does this impact me?]

Users will be able to create SharePoint lists from existing lists within a site or from Excel.


We'll be gradually rolling this out to Targeted Release in mid-May and the roll out will be completed worldwide by the end of July.


[What should I do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

08.05.2019 00:53:000Normal08.05.2019 00:53:0001.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17921107.05.2019 01:17:001New Feature: Enable modern communication site experience at the classic root site of your tenant

We are rolling out a feature that allows admins to enable the modern communication site experience at the classic root site of their SharePoint tenant.


This message is associated with Microsoft 365 Roadmap ID 46338


[How does this affect me?]

This feature can be activated by running a simple PowerShell cmdlet. On the successful execution of the PowerShell command(s), the root site of your tenant will have a new communication site home page. Details about the PowerShell cmdlet and feature requirements are available in the Additional Information

We'll be gradually rolling this out, off by default, to Targeted Release customers in early May 2019, and the roll out will be available worldwide by the end of June 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please see Additional Information to learn about the PowerShell cmdlet to enable this change.

07.05.2019 01:17:001Normal07.05.2019 01:17:0006.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17920206.05.2019 21:29:002New Feature: OneDrive sync client Get Help

Get Help is a new OneDrive sync client feature on Windows and Mac. We'll begin rolling this feature out soon.


This message is associated with Microsoft 365 Roadmap ID 49313


[How does this affect me?]

End-users will be able to reach out to Microsoft Support from OneDrive Activity Center using “More” menu and selecting “Get Help” option.


The new entry point is located right next to “Send Feedback” and is meant to set the right expectations with the user: “Get Help” will create a support ticket and a support agent will get back to you, while with “Send Feedback” you can let us know what you like and don’t like, report bugs and send us suggestions.


This feature will be available as part of OneDrive sync client build 19.043.0304.0007


[What do I need to do to prepare for this change?]

Tenant Admins can control whether their users see “Get Help” and “Send Feedback” by running a command:

  • Set-SPOTenantSyncClientRestriction -DisableReportProblemDialog $true


The SCRIPTED_DEPLOY_DISABLE_REPORT_PROBLEM registry key controls the setting on the local machine.

06.05.2019 21:29:002Normal06.05.2019 21:29:0021.06.2019 09:00:00AwarenessAdvisoryOneDrive for BusinessMessageCenter
MC17868101.05.2019 23:30:007Outlook on the web (opt-in) - Share availability from email compose

The new Outlook on the web, currently opt-in, does not support the Share availability feature.


[How does this impact me?]

Users who opt-in to the new Outlook on the web will not be able to use the Share availability feature.


[What should I do to prepare for this change?]

If users would like to continue to use the Share availability feature direct them to not opt-in to the new Outlook on the web. If they have already opted-in to the new Outlook on the web they can opt-out, via the toggle, and retain full use of the Share availability feature.

We would also suggest the following options to share availability:

  1. Use the Outlook mobile app to send availability
  2. Use the FindTime add-in to share availability

We will send additional communication around the transition to the new Outlook on the web in the future.

Please click Additional Information to learn more about how to share availability in Outlook mobile

01.05.2019 23:30:007Normal01.05.2019 23:30:0029.08.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17867901.05.2019 22:40:007New Feature: Shifts Multiteam Support

Shifts Multiteam Support is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID 50988

[How does this affect me?]

This only affects users that are on multiple Shift teams. These users will now be able to navigate to other teams via the top header. Shift features will now allow users to select the correct Team before performing team specific actions.

We'll be gradually rolling this out to customers in early May, and the roll out will be completed worldwide by the end of May.

This change does not affect Office 365 subscriptions in GCC.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change but may want to update your training and documentation as appropriate.

Please see Additional Information for end-user documentation which will be available in the Teams Helps center.

01.05.2019 22:40:007Normal01.05.2019 22:40:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17867801.05.2019 22:39:007New Feature: Time Clock in Shifts

Time Clock in Shifts is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID 50835

[How does this affect me?]

This feature is available to be enabled on Teams Web/Desktop and will be opt-in.

We'll be gradually rolling this out to customers in early May, and the roll out will be completed worldwide by the end of May.

This change does not affect Office 365 subscriptions in GCC.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change but may want to update your training and documentation as appropriate.


Please see Additional Information for end-user documentation which will be available in the Teams Helps center.

01.05.2019 22:39:007Normal01.05.2019 22:39:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17866701.05.2019 20:16:007Feature update: Office 365 Account Manager is getting updatedThe account manager in Office 365 allows an authenticated user to access account links, sign out, and change their profile picture.
We are updating Office 365 account manager to be consistent with other account experiences across all of Microsoft. This change also allows us to provide more account-based features in the future.
This enhancement is related to Microsoft 365 Roadmap ID 50753.
This change does not apply to Office 365 subscriptions in GCC.
[How does this impact me?] Your account manager in Office 365 will have a new and refreshed look that is consistent with other Microsoft products. Like before the new design, you will still sign out, access your account page, and access your Delve profile from within the account manager.
Starting in late May, users in Targeted Release will begin to see the new account manager interface in Office 365. By June, the new account manager will be shipped worldwide.
[What should I do to prepare for this change?] You don't need to do anything but may consider updating your training and documentation as well as informing your users of the upcoming change.
01.05.2019 20:16:007Normal01.05.2019 20:16:0015.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17866601.05.2019 20:04:007New Feature: Manage discovery of private teams in Microsoft TeamsAdmins and team owners can control whether private teams can be discovered by Microsoft Teams users in your organization. When a private team is discoverable, it shows up in search results and is included in suggestions in the team gallery alongside public teams in Teams. This makes it easy for users to search for and find the private teams that they want to join. Users can request to join a private team which a team owner can then approve or deny.
We’re introducing a new per team setting that determines whether a team shows up in search results and is included in suggestions in the team gallery alongside public teams in Teams. Team owners can set the discovery setting for a private team in the team settings and through create team dialog during creation and admins can do so by using PowerShell. As an admin, you can also control which users in your organization are allowed to discover private teams (for which team discovery setting is enabled) by assigning user level policies. For a given team to be discoverable for a given user, that team’s setting would need to be set to be discoverable and discovery would need to be enabled for the user through policy.
  1. All existing teams created prior to roll out will remain non-discoverable unless the setting is explicitly changed by team owners or admins after the roll out.

  2. Team owners will get an option to review the discoverability setting for the teams they own and, if needed, update it
  3. Any team created after the roll out will have the team discovery setting set as discoverable by default. When a team owner creates a private team, they can change this setting.
  4. By default, user policy AllowPrivateTeamDiscovery will be set to true for all users in an organization.

This message is associated with Microsoft 365 Roadmap ID 44370.
This feature is scheduled to roll out in early June, 2019.
[How does this affect me?] Today private teams are non discoverable in the team gallery across Microsoft Team's web, desktop, and mobile clients. With this change, existing private teams will remain non-discoverable and team owners will get an option to specify if they should be discoverable in the team gallery. They can choose to make their existing private teams discoverable from team settings. Newly created private teams will be discoverable by default unless a team owner changes this setting.
Note - Setting a team to be not discoverable will only remove it from suggestions and search results in team gallery within Microsoft Teams client. The behavior of this team in any other O365 clients will remain unchanged.
[What do I need to do to prepare for this change?]
For existing private teams which are not sensitive and highly confidential in nature, we recommend following the instructions in the "Additional Information" link to set existing private teams as discoverable in the team gallery. This will help reduce the number of duplicate private teams you see in your organization, and open up private teams to join requests from non-members. Refer to the Additional Information on when the PowerShell cmdlet will be available.
Admins will also be able to control, via policy, which users in your organization are allowed to discover private teams in search results and suggestions in Teams. This is useful if you have groups of users or vendors in your organization whom you would like to only have visibility into public teams in your organization.
To learn more about how to set this policy or apply team specific discoverable settings, please click Additional Information.
01.05.2019 20:04:007Normal01.05.2019 20:04:0031.07.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17863801.05.2019 01:01:007Updated Feature: Actionable Messages now support Payments in Outlook on the web

We’re updating Actionable Messages to now support Payments in Outlook on the web. We'll begin rolling this feature out soon.


This enhancement is related to Microsoft 365 Roadmap ID 31061.


[How does this impact me?]

Actionable Messages now supports Payments in Outlook on the web, which allows users to pay invoices without leaving their inbox.


We'll be gradually rolling this out to Standard Release customers in late May 2019, and the roll out will be completed worldwide by the end of August 2019.


[What should I do to prepare for this change?]

There is nothing you need to do to prepare for this change but may wish to update your training and documentation as appropriate.

Please click Additional Information to learn more.

01.05.2019 01:01:007Normal01.05.2019 01:01:0014.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17863601.05.2019 00:44:007Updated Feature: Microsoft Secure Score Integrated into Microsoft 365 Security Center

In response to frequent customer feedback, Microsoft Secure Score has been integrated into the new Microsoft 365 Security Center console which reached general availability on March 28th. By integrating this Microsoft Secure Score into this new console we have consolidated the experiences for many security administrators into a single location making discoverability and access to Microsoft Secure Score and other features easier for all of our customers.


This change does not apply to Office 365 subscriptions in GCC.


[How does this impact me?]

In late-May users of the existing Microsoft Secure Score site (http://securescore.microsoft.com) will automatically be redirected to Microsoft 365 Security Center.


[What should I do to prepare for this change?]

You don't need to do anything but may want to update any bookmarks to the new location within Microsoft 365 Security Center.

Please click Additional information to learn more about the Microsoft 365 Security Center and Microsoft Secure Score.

01.05.2019 00:44:007Normal01.05.2019 00:44:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17863301.05.2019 00:15:007Updated Feature: Skype for Business Certified IP Phones: Microsoft Online Device Registration updates

To provide our customers with best-in-class security across our services, Microsoft is implementing the use of Microsoft Identity Platform 2.0 (an evolution of the Azure Active Directory identity service) which uses the OAuth 2.0 authorization protocol. OAuth 2.0 is a method through which a third-party app can access web-hosted resources on behalf of a user, through a third-party application ID.


[How does this impact me?]

As result of this change, Skype for Business IP Phone partners have made a code change to use partner specific application ID. When deployed, the customer tenant admin will be required to confirm consent to allow the third-party phone application to be granted the necessary permissions (the same permissions currently being used by Skype for Business IP Phones).


[What should I do to prepare for this change?]

All certified Skype for Business IP phones must be updated by July 1st, 2019. Without the update, successful authentication to Microsoft services on IP Phones will fail. Customers are encouraged to work with their certified Skype for Business IP Phone provider to make the update before the deadline.


Please see Additional Information for more detail.

01.05.2019 00:15:007Normal01.05.2019 00:15:0030.07.2019 09:00:00ActionAdvisorySkype for BusinessMessageCenter
MC17863201.05.2019 00:09:007Updated Feature: General Availability of the updated Office 365 Advanced eDiscovery experience

We’re pleased to announce that we are releasing the updated Office 365 Advanced eDiscovery (preview announced in February 2019 - MC175132) into General Availability.


This enhancement is related to Microsoft 365 Roadmap ID 43691.


This change does not apply to Office 365 subscriptions in GCC

[How does this impact me?]

The new experience for Advanced eDiscovery in Office 365 and additional capabilities including additional custodian intelligence and communications, working sets to improve working with content within a case, and native review and annotation capabilities.


[What should I do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.

Please click Additional information to learn more.

01.05.2019 00:09:007Normal01.05.2019 00:09:0031.05.2019 09:00:00AwarenessAdvisoryOffice 365 PortalMessageCenter
MC17863130.04.2019 23:52:007Updated Feature: Microsoft Teams PowerShell

We have updated the Microsoft Teams PowerShell module to release a generally available version. This PowerShell module, first released in Beta last year, allows you to manage the lifecycle of teams within your organization. This new version of our module leverages 1.0 Graph APIs.

This change is associate with Microsoft 365 Roadmap ID: 50994

[How does this impact me?]

The new Teams Cmdlet module is available in the Powershell Gallery

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change but may want to update your documentation as appropriate.

Please click Additional Information to learn more.

30.04.2019 23:52:007Normal30.04.2019 23:52:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17863030.04.2019 22:53:008Feature update: Yammer simplified first-time login experience

We are making changes to simplify the new user login experience for Yammer.


[How does this impact me?]

The new user login experience is being updated based on customer feedback:

  • New users will not be prompted to switch their language to English
  • New users will not be prompted to Invite New Members
  • New users will not be sent a Welcome email


[What should I do to prepare for this change?]

There is nothing you need to do to prepare for this change but may wish to update your training and documentation as appropriate.


Please see Additional Information for Yammer Quick Start training for users.

30.04.2019 22:53:008Normal30.04.2019 22:53:0015.07.2019 09:00:00AwarenessAdvisoryYammer EnterpriseMessageCenter
MC17855530.04.2019 00:39:008Updated Feature: Authentication administrator and Privileged authentication administrator roles

Updated feature: Authentication administrator and Privileged authentication administrator roles


We are updating permissions for the Authentication administrator and Privileged authentication administrator roles in Azure Active Directory. These roles will be given permission to reset passwords for users. We will deploy the change to these roles in mid-May 2019.


[How does this affect me?]


When the roles are updated, existing and new users assigned to these roles will have permission to reset user passwords. Privileged authentication administrators will be able to reset passwords for all users; authentication administrators will be able to reset passwords for users in the same set of roles they can currently act on.


[What do I need to do to prepare for this change?]


You should review the list of users who are assigned to these roles. If any of these users should not have permission to reset passwords for other users, you should remove them from the role.


Please see the Additional Information for more information on roles and permissions.

30.04.2019 00:39:008Normal30.04.2019 00:39:0028.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17853930.04.2019 00:25:008New Feature: New Supervision Offensive Language intelligent filter

Monitor sent or received email messages in your organization for offensive language. The model leverages machine learning and artificial intelligence to identify inappropriate email messages as part of anti-harassment and cyber bullying monitoring requirements. We'll begin rolling this feature out soon.


This enhancement is related to Microsoft 365 Roadmap ID 43257.


[How does this impact me?]

The Offensive Language intelligent filter can be used when you create a Supervision policy.


We'll be gradually rolling this out to all customers at the end of April, and the roll out will be completed worldwide by the end of May.


[What should I do to prepare for this change?]

There is nothing you need to do to prepare for this change, but you may want to update your training and documentation as appropriate.

Please click Additional Information to learn more.

30.04.2019 00:25:008Normal30.04.2019 00:25:0028.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17852329.04.2019 22:09:009New Feature: Groups in Outlook: 'Brownbag'-style events

New feature:

'Brownbag'-style events is a new Office 365 feature for groups in Outlook. We'll begin rolling this feature out soon.


This message is associated with Microsoft 365 Roadmap ID 46257.


[How does this affect me?]

Being able to invite select attendees without inviting the group is extremely useful for group collaboration. You can now invite external speakers to "brownbag meetings" on the calendar where attendees can selectively add to their calendars, or even have meeting rooms for a group appointment.


Before this change, in Outlook for Windows, when a user creates a group meeting on a group's calendar and removes that group from the To: line, group members would still receive meeting invitations in their inbox. With this change, Outlook will now only send invitations to those in the To: line. If the group is removed from the To: line, then group members will not receive the meeting invitation. The meeting will continue to appear on the group calendar, where users can add it to their respective calendars.

Similarly, before this change in the new Outlook on the web, when a user creates a group event on a group's calendar and adds others to the event, group members would receive meeting invitations in their inbox. With this change, Outlook will now only send invitations to those that are explicitly invited. If the group is removed from the To: line, then group members will not receive the meeting invitation. The meeting will continue to appear on the group calendar, where users can add it to their respective calendars.

However, when individuals who do not have the feature accept, respond, or decline the 'brownbag-style’ event, Outlook will add and send invitations to the group as it previously did before the change.

We'll be gradually rolling this out to Targeted customers in late April, and then to Standard Release customers in early May.


[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk. Please click Additional information to learn more.

29.04.2019 22:09:009Normal29.04.2019 22:09:0028.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17851429.04.2019 19:11:009Updated Feature: Refreshed Folder Icon Design

Updated feature: Refreshed Folder Icon Design


This message is associated with Office 365 Roadmap ID 50597.


[How does this affect me?]

Microsoft is constantly pushing the bar on design, to deliver to customers a seamless experience that is not just beautiful, but actively functional. As we continue rolling out the Fluent design language and the refreshed Office brand icons, we are refreshing the representation of one of the most commonly used objects across the suite: The file folder.

This season, we are introducing golden folders. Inspired by the strong heritage of Windows but brought forth to a mobile-first age, these are the most functional and fresh folder designs we have ever shipped. Subtle yet noticeable clues emblazoned on the icon remind you of the contents and sharing status of each folder. Lastly, the color palette has been handcrafted to connect your content across the suite, and individually tested and fine-tuned for all the devices you care about.

We are rolling out the design over the coming weeks across mobile and web in OneDrive for Business, SharePoint Online and connected experiences in other apps, with no disruption in the functionality you rely on. We are always iterating, listening, and learning new ways to help you achieve more.

We'll be gradually rolling this out to all customers in late April 2019, and the roll out will be completed worldwide by the end of May 2019.

29.04.2019 19:11:009Normal29.04.2019 19:11:0028.06.2019 09:00:00AwarenessAdvisorySharePoint Online,OneDrive for BusinessMessageCenter
MC17845527.04.2019 01:36:0011New Feature: Outlook on the web - suggested attachments

New feature: Outlook on the web - suggested attachments

Suggested attachments in the new Outlook on the web is a new Office 365 feature. We'll begin rolling this feature out soon.


This message is associated with Microsoft 365 Roadmap ID 46145


[How does this affect me?]

It will soon be easier to find and attach a file in the new Outlook on the web. When you go to attach a file, Outlook will use intelligent technology to find the files that are most relevant to the ongoing conversation and the files that you most recently used, providing quick access to them. To see "suggested attachments," just respond to an email and select the "Attach" paper clip drop down icon. Suggested attachments only supports files stored in OneDrive for Business & SharePoint Online for now.


We'll be gradually rolling this out to Targeted Release organizations in late April, and the rollout will be completed worldwide by the end of August 2019. This roll out is excluded from Office 365 subscriptions in GCC.


[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

27.04.2019 01:36:0011Normal27.04.2019 01:36:0001.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17838526.04.2019 00:28:0012New feature: OneDrive - updated "manage access" pane for classic user interface

Updated file access management in advanced permissions if you are using the classic OneDrive user interface is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 50730.

[How does this affect me?]

We are making it easier for people to manage access permissions, remove individual recipients from shared links or stop sharing overall - all when working within the OneDrive classic user interface. When you go to a file or folder's information pane and click "Manage access," you're taken to a more modern interface to review, add, adjust and remove access to a file - inline with where the file lives - OneDrive or SharePoint. you can also see and manage any and all sharing links that have created on the file or folder.

We'll be gradually rolling this feature out in early May, 2019, and the roll out will be completed worldwide by the end of the month.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk, especially if you are still using Classic views in OneDrive for Business and SharePoint Online. Please click Additional information to learn more about file sharing and permissions in OneDrive for Business and SharePoint Online.

26.04.2019 00:28:0012Normal26.04.2019 00:28:0001.07.2019 09:00:00AwarenessAdvisorySharePoint Online,OneDrive for BusinessMessageCenter
MC17838326.04.2019 00:04:0012New Feature: new Outlook on the web (opt-in) - browse rooms

Browse rooms in the new Outlook on the web (opt-in) is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID 50722

[How does this affect me?]

Now when creating a meeting from your calendar, you can search for available meeting rooms in your organization by clicking on the location bar and then on "Browse more places". You can search by city or room list.

We'll be gradually rolling this out to all customers in late April, and the roll out will be completed worldwide by the end of June.

This roll out is excluded from Office 365 subscriptions in GCC.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

26.04.2019 00:04:0012Normal26.04.2019 00:04:0031.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17837625.04.2019 20:59:0013New feature: SharePoint Online news and page authors will now receive emails with comments, replies and likes

We're adding new SharePoint Online emails to keep you informed about likes and comments on pages/news posts. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 49603.

[How does this affect me?]

After this change takes place, when someone comments on a page or a news post, the author of the post will receive an email. If this comment is a reply to a top-level comment, the top-level commenter will also receive an email. Comment emails will be batched so that your users will receive a single email when several comments have been made on the page or news post within a short duration of time. Additionally, the same functionality will apply when users leave a like on a page or news post.

We’ll begin rolling this out in early June, and the rollout will be completed worldwide by the end of June 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but you may consider updating your user training and notifying your helpdesk.

End-users can unsubscribe from notification scenarios by clicking on the unsubscribe link in the footer of the email. Please click Additional Information to learn more.

25.04.2019 20:59:0013Normal25.04.2019 20:59:0031.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17837125.04.2019 19:55:0013Updated feature: User and group based assignment in the Azure AD admin center for Microsoft and LinkedIn integration

We’ve made a change to the LinkedIn account connections setting in Azure Active Directory (Azure AD) admin center. Azure AD admins can now enable the ability to connect LinkedIn and Microsoft accounts for a specific group instead of selecting individual users.


Note: LinkedIn integration is not fully enabled for your users until they consent to connect their accounts. No data is shared when you enable account connections for your users.

This message is related to Roadmap ID: 16667


[How does this affect me?]

We have replaced the ‘Selected’ option with ‘Selected group’ so that you can enable the ability to connect LinkedIn and Microsoft accounts for one group instead of individual users.


These changes do not apply to Office 365 subscriptions in GCC.


[What do I need to do to prepare for this change?]

If you don’t have LinkedIn account connections enabled for selected, individual users, you don’t need to do anything.

If you have previously enabled LinkedIn account connections for selected, individual users, you should:

  1. Get the current list of individual users
  2. Move the currently enabled individual users to a group
  3. Use the group from step 2 as the selected group in the LinkedIn account connections setting in the Azure AD admin center

Note: Even if you don’t move your currently selected, individual users to a group, they can still see LinkedIn information in Microsoft apps.


Step-by-step instructions:



$groupId = “[GUID of the target group]”

$users = Get-Content [Path to the CSV file]

$i = 1

foreach($user in $users} { Add-AzureADGroupMember -ObjectId $groupId -RefObjectId $user ; Write-Host $i Added $user ; $i++ ; Start-Sleep -Milliseconds 10 }

  • Use the group from step 2 as the selected group in the LinkedIn account connections setting in the Azure AD admin center:
  • See Integrate LinkedIn with Azure AD and follow the steps under ‘Use the Azure portal to enable LinkedIn account connections’.



See Additional Information to learn more about LinkedIn account connections data sharing and consent.

25.04.2019 19:55:0013Normal25.04.2019 19:55:0030.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17837025.04.2019 19:21:0013New feature: error resolution flow for illegal file and folder names in OneDrive

Error resolution flow for illegal file and folder names is a new OneDrive feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 49314.

[How does this affect me?]

Sometimes files are not able to sync to OneDrive because they have illegal characters in the name of the file, or in the name of the folder the file is in. OneDrive is rolling our an automated fix suggestion that will help users rename the problematic files on Windows and Mac, and thus resolve the sync issue around them.

We began gradually rolling this out to all customers in mid-April, and we anticipate roll out completion worldwide by the end of April 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk. Please click Additional information to learn more.

25.04.2019 19:21:0013Normal25.04.2019 19:21:0001.06.2019 09:00:00AwarenessAdvisoryOneDrive,OneDrive for BusinessMessageCenter
MC17828625.04.2019 00:46:0013Updated feature: Document Sets in SharePoint OnlineWe’re updating Document Sets. We'll begin rolling this feature out in May to Targeted Release tenants.
This message is associated with Microsoft 365 Roadmap ID: 33761.
[How does this affect me?] Navigating to a Document Set will show a modern experience inside document libraries configured to use the modern experience. Document Sets in libraries configured to use the classic experience, and document sets with customized welcome pages are not affected by this change.
This feature will begin rolling out in early May, and the rollout will be completed by the end of May 2019.
[What do I need to do to prepare for this change?] There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
25.04.2019 00:46:0013Normal25.04.2019 00:46:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17828525.04.2019 00:39:0013New feature: SharePoint Online Column Formatting - Data Bars in Lists and LibrariesSharePoint Online Column Formatting - Data Bars in Lists and Libraries is a new Office 365 feature. We'll begin rolling this feature out soon.
This message is associated with Microsoft 365 Roadmap ID: 45026.
[How does this affect me?] After this change takes place, SharePoint Online List and Library users will be able to format Number Columns with Data Bars.
We'll be gradually rolling this out to customers towards the end of April, and the roll out will be completed worldwide by mid-May 2019.
[What do I need to do to prepare for this change?] There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
25.04.2019 00:39:0013Normal25.04.2019 00:39:0021.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17827824.04.2019 23:05:0014New feature: SharePoint Online news and page authors will now receive emails with comments, replies and likes

We're adding new SharePoint Online emails to keep you informed about likes and comments on pages/news posts. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 49603.

[How does this affect me?]

After this change takes place, when someone comments on a page or a news post, the author of the post will receive an email. If this comment is a reply to a top-level comment, the top-level commenter will also receive an email. Comment emails will be batched so that your users will receive a single email when several comments have been made on the page or news post within a short duration of time. Additionally, the same functionality will apply when users leave a like on a page or news post.

We’ll begin rolling this out in early June, and the rollout will be completed worldwide by the end of June 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but you may consider updating your user training and notifying your helpdesk.

End-users can unsubscribe from notification scenarios by clicking on the unsubscribe link in the footer of the email. Please click Additional Information to learn more.

24.04.2019 23:05:0014Normal24.04.2019 23:05:0031.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17826524.04.2019 19:30:0014New feature: error resolution flow for illegal file and folder names in OneDrive

Error resolution flow for illegal file and folder names is a new OneDrive feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 49314.

[How does this affect me?]

Sometimes files are not able to sync to OneDrive because they have illegal characters in the name of the file, or in the name of the folder the file is in. OneDrive is rolling our an automated fix suggestion that will help users rename the problematic files on Windows and Mac, and thus resolve the sync issue around them.

We began gradually rolling this out to all customers in mid-April, and we anticipate roll out completion worldwide by the end of April 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk. Please click Additional information to learn more.

24.04.2019 19:30:0014Normal24.04.2019 19:30:0001.06.2019 09:00:00AwarenessAdvisoryOneDrive,OneDrive for BusinessMessageCenter
MC17819823.04.2019 22:38:0015Updated timeline: Office 365 will retire 3DES starting July 10, 2019The start date of the retirement of the 3DES cipher has been moved from the previously announced date of February 28th, 2019 to a new start date of July 10, 2019. Based on customer feedback we have updated the timeline to allow additional time for organizations to update older client software and devices that rely on the 3DES cipher.
As previously communicated in MC171089 in Dec 2018 and MC172798 in Jan 2019, retirement of the 3DES cipher is part of the migration of all our online services to Transport Layer Security (TLS) 1.2+ to provide best-in-class encryption, and to ensure our service is more secure by default.
[How does this impact me?] Starting July 10, 2019, Office 365 will begin retiring the 3DES cipher. This means that all connections to Office 365 using the cipher 3DES will not work. TLS 1.0/1.1 connections without the 3DES cipher will not be affected.
[What should I do to prepare for this change?] Update or replace client software and devices that rely on the 3DES cipher to connect to Office 365 prior to July 10, 2019.
By going to http://securescore.microsoft.com , you can find the overview of your TLS 1.0/1.1 and 3DES usage for Exchange. Click on ‘Score Analyzer’ and scroll to the - Remove TLS dependencies tab.
Here you will see a summary of your TLS 1.0/1.1 and 3DES usage.
If you want more details on which devices or clients are connecting using these weaker ciphers and protocols – click on the ‘Get Details’ button that will launch a flyout where you can click on ‘Launch now’. This will take you to the Secure Trust Portal (http://servicetrust.microsoft.com) where you can download your user and agent information.
Encryption in Office 365 Preparing for 3DES Retirement in Office 365 Skype for Business
Please review the Additional Information for more guidance details.
23.04.2019 22:38:0015Normal23.04.2019 22:38:0015.08.2019 09:00:00ActionAdvisoryMessageCenter
MC17800819.04.2019 18:22:0019Updated Feature: Changes to definition of Files Shared Internally

We have identified telemetry issues with the Sharing Report that resulted in inaccurate counts for files shared internally and files shared externally. We are making updates that will address these issues and improve report accuracy. We'll begin rolling this feature out soon.

After the update, “Files shared internally” is the number of files that have been shared with users within the organization, or with users within groups (that might include external users).

Also, “Files shared externally” might see an increase in the numbers as there are additional events that are being tracked and categorized within external sharing.

Please note that we are working on changes to further improve clarity over time.

[How does this affect me?]

In some cases, files shared internally or externally were being improperly counted. Specifically, events where files were being shared with security groups or Office 365 groups. Moving forward these will now be counted as Files Shared Internally. This update will address these issues going forward, additionally we will backfill the last 180 days to ensure continuity.

We will be rolling out this change starting May 15th, 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more about the Microsoft 365 analytics data model.


Information on SharePoint activity reports.

Information on OneDrive for Business activity reports.

19.04.2019 18:22:0019Normal19.04.2019 18:22:0027.06.2019 09:00:00AwarenessAdvisorySharePoint Online,Power BI,OneDrive for BusinessMessageCenter
MC17797719.04.2019 00:58:0019Office 365 Skype for Business will retire 3DES starting July 10, 2019

As previously communicated (MC171089) Office 365 Skype for Business is planning to move all of our online services to Transport Layer Security (TLS) 1.2+ to provide best-in-class encryption, and to ensure our service is more secure by default.


As part of this plan, we’ll be retiring 3DES beginning July 10, 2019.


[How does this impact me?]

Starting July 10, 2019, Office 365 Skype for Business will begin retiring 3DES. This means that all connections to Office 365 Skype for Business using the cipher 3DES will not work. Clients that still require 3DES such as Lync Phone Edition, Lync Mac 2011 and Lync 2010 will not be able to login to Office 365 Skype for Business.

Expect issues connecting to Office 365 Skype for Business services if you are using 3DES from this date onwards. TLS 1.0/1.1 connections without the 3DES cipher will not be affected.

[What should I do to prepare for this change?]

Update or replace clients and devices that rely on 3DES to connect to Office 365 Skype for Business prior to July 10, 2019.

Please review the Additional Information for more guidance details.

19.04.2019 00:58:0019Normal19.04.2019 00:58:0030.08.2019 09:00:00ActionAdvisorySkype for BusinessMessageCenter
MC17796019.04.2019 00:24:0019Updated feature: Group-connected team site homepageWe’re updating group-connected team site homepages. We'll begin rolling this feature out soon.

[How does this affect me?]
Many group-connected team sites that were created in 2016, 2017, or the first half of 2018 were created with just two web parts on the homepage: News and Activity. In early 2018, we released an update where all new sites started getting four web parts on the homepage: News, Activity, Quick Links, and Documents. We’re now upgrading all existing two web part homepages to show four web parts. This only affects homepages that have not been edited and saved by a user. Homepages that have been edited and saved will not be affected.

We'll be rolling this out in mid-May 2019 to all SharePoint Online organizations.

[What do I need to do to prepare for this change?]
There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
19.04.2019 00:24:0019Normal19.04.2019 00:24:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17790518.04.2019 01:59:0020Updated feature: Sharing links that block downloads for Office files

We’re updating Sharing links that block download for Office files. We'll begin rolling this feature out soon.

This message is associated with Office 365 Roadmap ID: 27499.

[How does this affect me?]

We are updating the feature that lets users create sharing links which block download for Office files. First, we will expand support for "specific people" links. Second, we will allow users to create "block download" links from File Explorer, Office apps, and the rest of the apps which use the common Office 365 file sharing experience.

We'll be gradually rolling this out to Standard Release organizations over the course of this week, and the roll out will be completed worldwide by mid-May 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

18.04.2019 01:59:0020Normal18.04.2019 01:59:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17789617.04.2019 23:16:0021New Feature: Office 365 Group card enhancements

New feature: Office 365 Group card enhancements: search members, renew groups, approve pending members

End users will soon be able to search members in the Office 365 Groups hover card that is available on Outlook on the web and SharePoint Online. As well, group owners will also be able to renew groups and approve pending members from the expanded view of the hover card.

No net new functionality is being introduced--the functionalities already exist in other parts of Outlook on the web or SharePoint Online.


This message is associated with Microsoft 365 Roadmap ID 49175


[How does this affect me?]

Users will no longer need to leave the page that they were working in to do these tasks.

We'll be gradually rolling this out, beginning with Targeted release users, then with Standard release customers in April, and the roll out will be completed worldwide by the end of June.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change.

17.04.2019 23:16:0021Normal17.04.2019 23:16:0019.07.2019 09:00:00AwarenessAdvisoryExchange Online,SharePoint OnlineMessageCenter
MC17781716.04.2019 19:50:0022New Feature: Busy on Busy in Microsoft Teams

Busy on Busy in Microsoft Teams is a new Office 365 feature. We’ll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 49990.

[How does this affect me?]

Busy on Busy is a feature that allows callers to know if a user is already on another call or meeting when contacting them. When a call comes in to a user who is already engaged in a call or meeting, this setting alerts the calling party that the user is busy by playing a busy signal or an appropriate message.

This feature can be enabled using the enable Busy on Busy setting in the Teams Calling Policy. It is off by default and requires administrator action to enable.

We'll be gradually rolling this out to all Teams organizations towards the end of April, and the roll out will be completed worldwide by the end of May 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

16.04.2019 19:50:0022Normal16.04.2019 19:50:0001.07.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17781516.04.2019 19:43:0022Updates are coming to the authentication behavior on Azure AD (M365) sign-in pages

There are updates coming to the authentication behavior on Azure AD (M365) sign-in pages. We'll begin rolling these changes out soon.

This message is associated with Microsoft 365 Roadmap ID: 33845.

[How does this affect me?]

Azure AD sign-in uses a process, called Home Realm Discovery, to determine where to send a user to authenticate after they enter their username on the sign-in screen. This process will be updated with an upgraded user lookup behavior. The new behavior will make intelligent decisions by reading tenant and user level settings based on the username entered on the sign-in page. This functionality will pave the path towards a passwordless future by enabling alternative credentials like FIDO 2.0.

After this change takes place, we'll check to see if the username that is entered on the sign-in page exists in their respective domain before deciding where to redirect the user to provide their credentials. Additionally, this behavior will introduce new and improved error messaging on the sign-in pages if the username the user entered doesn't match an account in the respective domain.

We'll begin gradually rolling this out in early May, and the roll out will be completed worldwide by mid-May, 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything to prepare for this change. Please click Additional information to learn more.

16.04.2019 19:43:0022Normal16.04.2019 19:43:0019.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17781216.04.2019 19:02:0022Now use larger, more flexible image types to upload your company logo in the Office 365 navigation barWe are modernizing our navigation bar customization to help you represent your brand across Office 365.
This message is associated with Microsoft 365 Roadmap ID: 46636.
Now, you’ll be able to upload your custom logo of any file size and of any format via a URL in order to improve the clarity of the logo image that your users see in their Office 365 navigation bar across their Office applications, like SharePoint Online and Office.com.
After setting your custom logo you can configure it to point to your company or intranet portal, enabling easy access to your users.
Starting in late April, we’ll begin rolling this out to Targeted Release organizations. Worldwide availability is expected by the end of May 2019.
You don't need to do anything and can start taking advantage of the updated features, once available. Please click Additional Information to learn more.
16.04.2019 19:02:0022Normal16.04.2019 19:02:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17765312.04.2019 20:13:0026Dynamics 365 - Updates coming to the authentication behavior on Dynamics 365 sign-in pagesDynamics 365 sign-in uses a process to determine where to send a user to authenticate after they enter their username on the sign-in screen. This process will be updated with an upgraded user lookup behavior. The new behavior will make intelligent decisions by reading tenant and user level settings based on the username entered on the sign-in page. This will pave the path towards a password-less future by enabling alternative credentials like FIDO (Fast Identity Online) 2.0.
[How does this affect me?] After this change takes place, Microsoft will check to see if the username that is entered on the sign-in page exists in their respective domain before deciding where to redirect the user to provide their credentials. Additionally, this behavior will introduce new and improved error messaging on the sign-in pages if the username the user entered does not match an account in the respective domain.
[What do I need to do to prepare for this change?] This feature will begin rolling out for managed domains (cloud-only) in May 2019 and for federated domains by the end of 2019. If you or your organization have practices that depend on the old domain level HRD (Home Realm Discovery), it is important that you update the employee authentication documentation, train employees to use their actual username to sign in, and notify your helpdesk of this change. The exact roll out date for federated domains will be dependent on customer feedback.
Learn more about this update at https://aka.ms/user-level-HRD/
12.04.2019 20:13:0026Normal12.04.2019 20:13:0031.12.2019 19:13:00AwarenessAdvisoryMessageCenter
MC17765112.04.2019 19:52:0026We're making an update to Office 365 Enterprise plan names

We’re updating Office 365 Enterprise plan names. This change will be made in late April, 2019.

[How does this affect me?]

The license display names of the Office 365 Enterprise plans will be updated to remove the word "Enterprise" (e.g. "Office 365 Enterprise E3" will be updated to "Office 365 E3").

This name change will go into effect on April 30, 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.

12.04.2019 19:52:0026Normal12.04.2019 19:52:0001.06.2019 09:00:00AwarenessAdvisoryOffice 365 PortalMessageCenter
MC17760712.04.2019 01:32:0026Dynamics 365 - Changes are coming to your sign-in page - Branding for Sign-out and Authentication Error Screens[Summary] We’re updating the sign out and authentication error pages to show company branding. We'll begin rolling this feature out soon.
[Details] Company branding on the Dynamics 365 sign-in page allows tenants to customize the login experience for their users. At the moment, this customization only applies to the username, password and Multi-Factor Authentication screens. This change is going to extend customization to the sign out and error screens as well.
If customers have configured company branding for the Dynamics 365 sign-in screens on their tenants, their users will start to see these customizations on the sign out and authentication error screens as well. We'll be gradually rolling this out to all customers in early-May 2019, and the roll out will be completed worldwide by the end of May.
[Action Required] Customers do not need to do anything, but may want to consider updating their user training, and notifying their helpdesk.
[Target Date] 5/9/2019
12.04.2019 01:32:0026Normal12.04.2019 01:32:0012.05.2019 01:32:09AwarenessAdvisoryMessageCenter
MC17760111.04.2019 23:55:0026New feature: New Outlook on the web - Search filters

New Outlook on the web - Search filters is a new Office 365 feature. We'll begin rolling this feature out soon.


This message is associated with Microsoft 365 Roadmap ID: 50409.


[How does this affect me?]

The new Search filters will allow you to search with more specific terms such as folders, From, To, Subject, keywords, date range, and attachment. To use Search filters, go to the Search box and then click on Filters on the right side of the box.

We'll be gradually rolling this out to Targeted Release organizations beginning in mid-April, and the roll out will be completed worldwide by the end of June 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

11.04.2019 23:55:0026Normal11.04.2019 23:55:0001.08.2019 09:00:00AwarenessAdvisoryExchange Online,Outlook.comMessageCenter
MC17759411.04.2019 22:42:0027New Feature: Full-fidelity shared libraries in OneDrive

Full-fidelity shared libraries in OneDrive for Business is a new Office 365 feature. We'll begin rolling this feature out soon.


This message is associated with Microsoft 365 Roadmap ID: 49093.


[How does this affect me?]

Not only can you sync shared libraries from SharePoint Online and Microsoft Teams to your PC or Mac using OneDrive, you can now view shared libraries in OneDrive on the web with support for viewing file metadata. Initial capabilities include viewing ,sorting and grouping by custom metadata and changing your file view to any previously saved file view.


We'll be gradually rolling this out to Targeted Release organizations in mid-April, and the roll out will be completed worldwide by the end of May 2019.


There is nothing you need to do to prepare for this change. The Additional Information will be updated shortly with additional details.

11.04.2019 22:42:0027Normal11.04.2019 22:42:0001.07.2019 09:00:00AwarenessAdvisoryOneDrive for BusinessMessageCenter
MC17759211.04.2019 22:25:0027Updated - Feature update: Structural navigation performance banner

Updated to reflect a change in scheduled roll out. We’re updating the banner for classic sites using structural navigation.

Based on feedback provided and to align to complementary features we have decided to postpone rolling out at this time.

This message is associated with Microsoft 365 Roadmap ID 50442.

[How does this affect me?]

If SharePoint Online detects that structural navigation is causing the page to render slowly, site owners will see the following banner and have the opportunity to learn more:

“Slow performance detected. Your site is using structural navigation, which decreases page performance. Learn how to improve performance by using a different navigation method.”

We'll provide additional updates, via Message Center, once the new schedule has been determined.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

11.04.2019 22:25:0027Normal11.04.2019 22:25:0001.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17758811.04.2019 20:23:0027New feature: Sign out and authentication error screens to show company brandingWe’re updating the sign out and authentication error pages to show company branding. We'll begin rolling this feature out soon.
This enhancement is related to Microsoft 365 Roadmap ID 50476.
[How does this impact me?] If you have configured company branding for the Microsoft 365 sign-in screens on your tenant, your users will start to see these customizations on the sign out and authentication error screens as well.
We'll be gradually rolling this out to all customers in early-May 2019, and the roll out will be completed worldwide by the end of May.
[What should I do to prepare for this change?] You don't need to do anything, but may consider updating your user training, and notifying your helpdesk. Please click Additional information to learn more.
11.04.2019 20:23:0027Normal11.04.2019 20:23:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17758711.04.2019 20:17:0027Feature update: Focus on your active teamsAre too many teams cluttering up your left rail? Over the next few weeks, teams you haven't visited in more than 45 days will be automatically reordered and moved to the bottom "More" category so you can focus on teams you're more active in.
This message is associated with Microsoft 365 Roadmap ID 48621.
This change will does not apply to Office 365 subscriptions for Education.
We'll be gradually rolling this out to all customers in early May, and the roll out will be completed worldwide by the end of June.
[How does this affect me?] Teams you haven't visited in more than 45 days will be automatically reordered and moved to the bottom "More" category. Users will see a dialog that will allow them to view the teams that were moved and choose to accept or undo the move.
Teams Left Nav
[What do I need to do to prepare for this change?] There is nothing you need to do to prepare for this change, but you may want to update your user and helpdesk documentation.
Please click Additional Information to learn more.
11.04.2019 20:17:0027Normal11.04.2019 20:17:0030.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17757911.04.2019 18:36:0027Updated release plan for Sharable links in Word and Outlook for Windows and mobileRecently we announced, via MC175805, updates to Office 365 apps to ensure that document sharing by inserting links in Word, Outlook for Windows and Outlook for iOS uses the permission you’ve set at the organization level for OneDrive and SharePoint.
We received feedback that our plan for when the organization sets the default permission to “Direct: Specific people” did not meet the expectations and needs of some customers. As a result, we are updating our release plans.
This enhancement is related to Microsoft 365 Roadmap IDs 33156 and 33870
[How does this impact me?] In April, the permissions for the links in Outlook for Windows and iOS and Microsoft Word will default to the organization’s Sharing settings in the OneDrive Admin center, either “Shareable: Anyone with the link” or “Internal: Only people in your organization with the link”. If your organization has set sharing to “Direct: Specific people”, there will be no changes to the current experience, only those who already have access to the document will be able to access it.
See Additional Information for more information about setting organization level permissions in OneDrive and SharePoint.
In addition, when you chose to insert a link in Outlook for Windows or a Word document you will see a new dialogue box indicating that a shareable link is being retrieved.
There is no change to cloud attachments.
[What do I need to do to prepare for this change?]
There is nothing you need to do to prepare for this change however you may wish to review the external sharing setting in the OneDrive Admin settings to ensure it complies with your company policies.
11.04.2019 18:36:0027Normal11.04.2019 18:36:0031.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17751711.04.2019 00:45:0027Updated Feature: Teams support for Meeting Migration Service

We’re updating Teams support for Meeting Migration Service. We'll begin rolling this feature out soon.

[How does this affect me?]

Currently, the Meeting Migration Service (MMS) updates existing Skype for Business meetings when either users move from on-premises to the cloud or when a user's audio-conferencing settings change. Up till now, the updated meetings have remained Skype for Business meetings.

With this new support, MMS can now convert existing Skype for Business meetings to Teams, and it can also update existing Teams meetings to reflect audio conferencing changes. MMS will be triggered to update a user’s existing meetings in the following scenarios:

  • When a user is migrated from on-premises to the cloud (whether to Skype for Business Online or to TeamsOnly).
  • When an admin makes a change to the user’s audio-conferencing settings
  • When an online user is upgraded to Teams only, or when a user's mode in TeamsUpgradePolicy is set to SfBwithTeamsCollabAndMeetings
  • When you use a PowerShell cmdlet.

We'll be rolling this out to customers starting May 8, 2019, and the roll out will be completed worldwide by the end of May.

[What do I need to do to prepare for this change?]

If you have PowerShell scripts that grant TeamsUpgradePolicy AND you do not want meetings to be migrated to Teams, update these scripts to also pass the new parameter MigrateMeetingsToTeams $false. For details, see: Grant-CsTeamsUpgradePolicy

Otherwise, you don't need to do anything but may consider updating your training and documentation. Please click Additional information to learn more.

11.04.2019 00:45:0027Normal11.04.2019 00:45:0028.06.2019 09:00:00AwarenessAdvisorySkype for Business,Microsoft TeamsMessageCenter
MC17750310.04.2019 21:14:0028Updated Feature: Role changes: Information Protection Administrator and Privileged Role Administrator

We are making some changes to the Information Protection Administrator and Privileged Role Administrator roles.

This enhancement is related to Microsoft 365 Roadmap IDs 50422 and 50424.

[How does this impact me?]

  1. Information Protection Administrator: We are updating the name of this role to “Azure Information Protection Administrator” in the Azure portal and Microsoft 365 admin center.
  2. Privileged Role Administrator: A Privileged Role Administrator can manage only role assignments today. To reduce dependency on the Global administrator we are enabling the additional abilities:
    • ability to consent/revoke any delegated or app permissions (including permissions to Microsoft or Azure Active Directory Graph)
    • ability to create, update, delete Administrative Units, including membership management

We will begin rolling out these changes in May and will be completed in June.

[What should I do to prepare for this change?]

There is nothing you need to do to prepare for this change. We would suggest updating your training and process documentation as appropriate.

Please see additional information to learn more.

10.04.2019 21:14:0028Normal10.04.2019 21:14:0028.06.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17750110.04.2019 19:52:0028Updated - Updated Feature: We’re changing your default SharePoint admin center experience

The new SharePoint admin center will be the default experience for organizations. We have completed rolling out to Office 365 organizations of 50 or fewer licenses, as communicated in MC173771, and are now rolling out more broadly.

This message is associated with Microsoft 365 Roadmap ID 46375.

[How does this affect me?]

The SharePoint admin center experience will default to the new admin center experience. You can switch back to the classic experience as necessary.

We'll be gradually rolling this out in early May and will be complete by the end of June.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.

To switch to the classic experience temporarily, select “Classic SharePoint admin center” in the left pane of the new SharePoint admin center.

To control the default experience for all global and SharePoint admins in your organization:

In the new SharePoint admin center, select Settings in the left pane, and then select Default admin center experience. Turning the setting to Off will set the classic admin center as default and On will set the new admin center as default. This control is available now.

This change will be skipped for customers that have modified the setting of their default admin center experience.

Please click Additional information to learn more.

10.04.2019 19:52:0028Normal10.04.2019 19:52:0026.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17742709.04.2019 18:51:0029New feature: audience targeting in SharePoint Online organizational news

SharePoint Online organizational news: audience targeting is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 30695.

[How does this affect me?]

Audience targeting for news and highlighted allows page authors and site owners to tag pages and news posts with Azure Active Directory groups, and filter content within these web parts to people within those groups.

We'll be gradually rolling this out to Targeted Release “entire org” customers in mid-April, and we anticipate rollout completion by the end of June 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk. Please click Additional information to learn more.

09.04.2019 18:51:0029Normal09.04.2019 18:51:0001.07.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
MC17724405.04.2019 23:19:0033Microsoft Kaizala Pro will be included as part of your Office 365 service starting late-May

Microsoft Kaizala Pro will be available as part of your Office 365 plan beginning in late-May 2019.


Microsoft Kaizala Pro is a simple and secure work management and messaging app that brings unique capabilities to Microsoft 365 with its ability to have very large, flexible group types and the ability to connect and engage with people outside of an organization’s directory – including contract workers, vendors, partners, suppliers, customers and citizens. Kaizala enables phone number-based identity for easy onboarding, and a simple user experience for messaging and work management through the open directory. With Kaizala Pro, organizations own the data within their Office 365 connected Kaizala groups.


[How does this impact me?]


Kaizala Pro will be visible in the Office 365 app launcher and will be on-by-default for your organization.

Users will start seeing a Microsoft Kaizala icon in late-May 2019. Additionally, they will be able to start using the Kaizala Management Portal and link their Office 365 account on the Kaizala mobile app.

[What should I do to prepare for this change?]


If you would like to allow users to access Microsoft Kaizala, no action is needed. If you would like to disable Kaizala for your organization, you can follow the instructions for the tenant-level admin control.

Please click Additional Information to learn more about Kaizala.


05.04.2019 23:19:0033Normal05.04.2019 23:19:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft KaizalaMessageCenter
MC17724305.04.2019 23:09:0033Microsoft Kaizala Pro will be turned on by default starting late-May

Microsoft Kaizala Pro will be turned on for your tenant by default starting late-May 2019.

Microsoft Kaizala Pro is a simple and secure work management and messaging app that brings unique capabilities to Microsoft 365 with its ability to have very large, flexible group types and the ability to connect and engage with people outside of an organization’s directory – including contract workers, vendors, partners, suppliers, customers and citizens. Kaizala enables phone number-based identity for easy onboarding, and a simple user experience for messaging and work management through the open directory. With Kaizala Pro, organizations own the data within their Office 365 connected Kaizala groups.


[How does this affect me?]

As previously communicated, Kaizala Pro will be visible in the Office 365 app launcher. The change you will experience is Kaizala Pro will now be on-by-default for your organization.

Users will start seeing a Microsoft Kaizala icon in late-May 2019. Additionally, they will be able to start using the Kaizala Management Portal and link their Office 365 account on the Kaizala mobile app.

[What do I need to do to prepare for this change?]

If you would like to allow users to access Microsoft Kaizala, no action is needed. If you would like to disable Kaizala for your organization, you can follow tenant-level admin control instructions.

Please click Additional Information to learn more about Kaizala.


05.04.2019 23:09:0033Normal05.04.2019 23:09:0028.06.2019 09:00:00AwarenessAdvisoryMicrosoft KaizalaMessageCenter
MC17719905.04.2019 05:14:0033Changes to Coming Soon in Outlook for WindowsAs announced in MC147799 in September 2018, we introduced a new “Coming Soon” feature that offers a preview of new user experience updates in Outlook for Windows and provides you and your users an opportunity to try the experience and to provide feedback. This month, we’re rolling out a new density setting to control the amount of space between emails in the message list, as well as spacing around some of the elements visible when composing a message. This setting will show up for customers who have Coming Soon turned on.
All of the experience updates that are now behind Coming Soon will be rolling out as the default experience to all Monthly Channel customers in May 2019. These feature updates are not yet available for GCC organizations.
This message is associated with Microsoft 365 Roadmap IDs: 26542 and 46976.
[How does this affect me?] Since we introduced Coming Soon, we gained a lot of valuable feedback about the user experience updates. The majority of feedback on these improvements is positive, but we’ve also heard from some users that they prefer tighter spacing in emails over the looser spacing that was designed to make the message list easier to scan visually.
Now when you toggle Coming Soon to “On” you’ll have access to the new density setting option that’s located in the View tab in your Outlook ribbon. Similar to switching between the simplified and classic Ribbon, you can switch between standard and tighter spacing from the View tab in the ribbon. We appreciate your engagement with Coming Soon features and your feedback, and we hope to continue receiving your suggestions on features in preview.
In May, the other user experience updates previously introduced in the Coming Soon pane will become the default experience and the on/off toggle and the Coming Soon pane will no longer be available. The Coming Soon preview pane and toggle may re-appear when we are ready to roll out additional capabilities in preview. To review the features that are now part of Outlook for Windows, please reference the Outlook blog post that covers them here.
[What do I need to do to prepare for this change?] There’s nothing that you need to do to prepare for this change, but we suggest that your users explore the Coming Soon pane and learn about the density setting option, as this feature will soon be on-by-default.
Please click Additional Information to learn more.
05.04.2019 05:14:0033Normal05.04.2019 05:14:0001.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17712104.04.2019 03:58:0034Updated Feature: New setting in CsTeamsMeetingPolicy to manage meetings chat

We’re updating the way meetings chat is controlled by creating a new, separate setting in CsTeamsMeetingPolicy to manage meetings chat, as a change from previous practice where meetings chat followed CsTeamsMessagingPolicy. We'll begin rolling this feature out soon, but will do it in stages to provide time for customers to make any changes.


[How does this affect me?]

At customers' request, we are making some changes to the way meetings chat is controlled. Prior to the change, it was controlled by the AllowUserChat setting of the CsTeamsMessagingPolicy. After this change, it will be controlled by a new setting, MeetingChatEnabledType, of the CsTeamsMeetingPolicy.

The change will be rolled out selectively on the basis of users’ upgrade mode:

  • Users with effective upgrade mode of SfBOnly, SfBWithTeamsCollab, or SfBWithTeamsCollabAndMeetings do not have access to the Chat tab and hence do not conduct private or group chat in Teams. However virtually all such customers want to and should be permitted to chat in meetings, and many have requested this capability. Prior to this change they were not able to do so. For these users, this change will take effect on or after April 9.

  • On the other hand, users with effective upgrade mode of Islands or TeamsOnly do have access to the Chat tab unless chat has been explicitly disabled in CsTeamsMessaging policy. When that happens, they also do not have access to meetings chat today. An example is EDU tenants, who frequently ban the use of all sorts of chat (both private chat, group chat and meetings chat) for students. For these users, this change will take effect on or after May 15. Prior to the change, tenant admins should review users for whom they want meetings chat to remain off, and make sure these users are granted the new setting.

The roll out will be completed worldwide for all tenants by 5/31/2019.


[What do I need to do to prepare for this change?]

Review your requirements and policies with respect to meetings chat. If you do not require meetings chat to be off for any user, you do not need to do anything. If you require meetings chat to be off for specific users, we recommend you apply CsTeamsMeetingPolicy's MeetingChatEnabledType setting with the Enum value of Disabled to these users.


The Additional Information will be updated shortly to reflect these changes.

04.04.2019 03:58:0034Normal04.04.2019 03:58:0030.06.2019 08:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17712204.04.2019 03:42:0034Reminder: SharePoint tenant opt-out for modern lists is retiring in 2019As previously communicated in MC172925 in February 2019, we're making some changes to how environments can opt out of modern lists in SharePoint.
Starting April 24, 2019, it will no longer be possible to restrict an entire organization (tenant) to classic mode for lists and libraries.
[How does this impact me?] In 2016, we introduced a new “modern” experience for SharePoint, bringing extensibility, accessibility, and responsive design to a complete overhaul of the user experience. Since then, modern has been the center of innovation in SharePoint and OneDrive, although classic mode remains supported and available. We’re making it easier for users to get to our latest feature updates.  Users will benefit from enhancements and new features such as attention views, PowerApps integration, Flow, column formatting, and the filters pane.
Starting April 24th, 2019, it will no longer be possible to restrict an entire organization (tenant) to classic mode for lists and libraries. The setting that previously allowed this opt-out will no longer appear in the UI, and tenants that were previously using the setting to opt out of modern will be switched to using the modern experience by default.  This change will roll out between April 24th and May 31st. After the change affects your environment, lists and libraries that are in classic mode as a result of tenant opt-out will automatically be shifted to modern.
There are no plans to remove classic mode and we’ll maintain the current feature set for classic lists and library experiences. Lists and libraries may still use classic mode using the granular opt-out switches that we provide at the site collection, site, list, and library levels.  Additionally, lists that use certain features and customizations that are not supported by modern will still be automatically switched to classic mode.
Please note that we cannot predict exactly what day this change will affect your environment during this rollout.  However, you are welcome to control this change yourself by configuring your tenant to use modern lists before the change makes that mandatory.
[What should I do to prepare for this change?] The SharePoint Modernization scanner identifies sites and lists that have customizations that are not supported by modern UI.  Although many of these lists will automatically remain in classic mode even after this change, you may wish to keep some sites running entirely in classic to avoid users switching between different experience modes within a single site.
Administrators can use a PowerShell script to enable or disable the modern experience for a single site collection or for a list of site collections as provided by the SharePoint Modernization scanner.  Alternately, users can still use the “return to classic” option on modern views of lists or libraries to temporary return to classic, list owners can use List Settings to configure that list to use the classic experience for all users, and site collection owners can use Site Collection
04.04.2019 03:42:0034Normal04.04.2019 03:42:0031.05.2019 09:00:00ActionAdvisorySharePoint OnlineMessageCenter
MC17701303.04.2019 00:44:0035New feature: Easily add new members to your teamThe ability for team members to request member additions in Teams is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 48396.

[How does this affect me?]
With this feature enabled, team members can request for other users to be added to their team. Simply click on ‘Add member’ and select the users you want to add to your team. This sends a team join request on behalf of the user you’re trying to add. The team owner(s) will get a notification to accept or deny the request.

We're also adding support for in-app notifications for self-join requests.

We'll be gradually rolling this out to all customers in early April, and the roll out will be completed by mid-April, 2019.

[What do I need to do to prepare for this change?]
There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
03.04.2019 00:44:0035Normal03.04.2019 00:44:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17699202.04.2019 18:36:0036New Feature: To-Do

We are excited to announce the To-Do & Planner Integration is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID 48624

[How does this affect me?]

Users who opt-in to the Planner integration will be able to see and edit tasks they have been assigned to in Planner within To-Do. These tasks will surface in the "Assigned to me" list, but will also appear in To-Do search results, My Day suggestions, and the Planned smart list (all tasks with a due date). Users may turn off this integration at any time via the To-Do Settings menu.

In order to use this integration in the Outlook Web task module, you must have the New Tasks module enabled. We previously announced this feature in February via MC173377

We'll be gradually rolling this out to customers in April, 2019, and the roll out will be completed worldwide by the end of May 2019.

This roll out is excluded from Office 365 subscriptions in GCC.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change.

02.04.2019 18:36:0036Normal02.04.2019 18:36:0015.06.2019 09:00:00AwarenessAdvisoryPlanner,Microsoft To-DoMessageCenter
MC17691101.04.2019 19:18:0037StaffHub to Shifts in Microsoft Teams migration update

As previously communicated in MC149144 on September 24, 2018, Microsoft Teams is evolving to include a new set of capabilities that will simplify schedule management and help deliver the tools for every worker to get the job done. As a result, we will be retiring Microsoft StaffHub on October 1, 2019 and we will be focusing our investments on Microsoft Teams. After October 1, 2019 users that attempt to log in to StaffHub will be greeted with a message directing them to download Microsoft Teams.


To help you in your transition to Microsoft Teams, we ask that you review the details below for pre-requisites related to user and data migration across Microsoft Teams and StaffHub.

[How does this affect me?]

If you’re receiving this notice, you have one or more people in your organization who currently use Microsoft StaffHub. Please communicate these details to the right stakeholders in your organization.


[What do I need to do to prepare for this change?]

If you would like to move your StaffHub teams to Shifts in Microsoft Teams the following pre-requisites are needed:

  • Microsoft Teams must be enabled for the tenant.
  • Note: Organizations who are still using Skype for Business can enable Teams to run alongside Skype for Business if they aren’t yet ready to upgrade to Teams.
  • StaffHub users must be licensed to use Teams. Teams licenses are available in Office 365 F1, E1, E3 and E5, Microsoft 365 F1, E1, E3 E5, Office 365 Business Premium, and EDU.
  • Office 365 Groups must be enabled for the tenant.
  • Each StaffHub team requires an Office 365 group. If there is no Office 365 group associated with the StaffHub team, a new O365 group will be created at the time you move the StaffHub team.
  • All StaffHub team members must be provisioned AAD users and members of the Office 365 group.
  • StaffHub team owners/managers can convert an inactive accounts and link them with a provisioned account in StaffHub by going to the team settings page and updating the e-mail address to a valid UPN.

OR

Please click Additional Information to learn more.

01.04.2019 19:18:0037Normal01.04.2019 19:18:0030.12.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17671829.03.2019 01:39:0040Voicemail is now available for all VoIP-enabled users in Microsoft TeamsWe’re excited to announce that we’re now providing voicemail capabilities for all VoIP-enabled users in Microsoft Teams. VoIP-enabled users will now be able to receive and hear voicemails in the Teams desktop and web clients. This feature is on-by-default and requires administrator action to disable.
If transcription is enabled for your tenant via Voicemail Policy, your users can also see voicemail transcriptions in their desktop clients, web clients, and in outlook clients.
This message is associated with Microsoft 365 Roadmap ID: 33579.
[How does this affect me?] After this change takes place, VoIP users that do not have voicemail functionality disabled will see the voicemail tab in their calls app in the app bar. Desktop and web clients already show the voicemail tab in the Calls App for Cloud Voice Users.
Voicemail capabilities will not be available for users who have been previously configured with voicemail disabled.
Transcription will also not be available to users and tenants who have transcription disabled. You can enable transcription and voicemail, and this feature will be available for your users.
This change will take place for your organization in late April, 2019.
[What do I need to do to prepare for this change?] Voicemail can be enabled/disabled via the AllowVoicemail setting in TeamsCallingPolicy. Please verify that your users have the appropriate setting to ensure they are configured for your organization’s desired voicemail experience. If you disable voicemail for your users between now and late April, your settings will be honored when the feature becomes available.
For reference materials, please refer to the following topics:
-https://docs.microsoft.com/powershell/module/skype/Set-CsOnlineVoicemailPolicy?view=skype-ps -https://docs.microsoft.com/powershell/module/skype/set-csteamscallingpolicy?view=skype-ps -https://support.office.com/article/check-your-voicemail-in-teams-f8d568ce-7329-4fe2-a6a2-325ec2e2b419
29.03.2019 01:39:0040Normal29.03.2019 01:39:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17670228.03.2019 21:57:0041Updated - We’re increasing access to Microsoft Search across Office 365We’re updating Microsoft Search. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 34273.

[How does this affect me?]
Microsoft Search is a new enterprise search experience that increases productivity and saves time by delivering more relevant search results. As part of this rollout we'll bring Microsoft Search to SharePoint, Office.com, and Bing.com with a unified search experience for People, Bookmarks, Groups, Locations and more. Search will also become more prominent across Microsoft 365 experiences with the search box moving to a consistent location at the top of Office apps like Word, PowerPoint and Excel as well as productivity apps such as OneDrive and Outlook. Once this update is complete, you will see a new service plan called “Microsoft Search” in the list of plans included with your subscription.

We'll be gradually rolling this out to Targeted Release organizations in late April, and the roll out will be completed worldwide by the end of June 2019.

[What do I need to do to prepare for this change?]
There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
28.03.2019 21:57:0041Normal28.03.2019 21:57:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17669628.03.2019 20:48:0041New feature: Automatic processing of small changes in meeting detailsAutomatic processing of small changes in meeting details is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 30674.

As announced at Microsoft Ignite 2018, we are rolling out an improvement to reduce the number of unnecessary meeting message updates seen by attendees. You can see the initial announcement here.

[How does this affect me?]
When an organizer changes non-critical properties of a meeting to which an attendee has already responded, the incoming meeting message update will be automatically processed without the attendee receiving an email in their inbox or having to take additional action. This means that the changes will be applied to the attendee’s calendar event while preserving their existing response, and the incoming meeting message update will be delivered to their Deleted Items folder instead of being delivered to their Inbox.

When the organizer changes critical meeting properties, there will not be any changes to the current meeting experience. Attendees will continue to receive the meeting messages in their Inbox.

The default list of critical properties is:

• Start date or start time
• End date or end time
• Recurrence pattern
• Location

There are a few scenarios in which meeting messages will always be delivered to the invitees' inbox regardless of what was changed about the meeting. By default, meeting messages will always be delivered to the inbox if:

• The attendee is @mentioned in the meeting body.
• The meeting starts within 15 minutes. In cases of recurring series, the next instance of the series is used to determine if the change occurs within 15 minutes.
• The receiving user is a delegate. Whenever a meeting message is received by a calendar delegate, the message will be delivered to the delegate’s Inbox and will never be automatically processed.

[What I do to need to do to prepare for this change?]
If the default settings work for your organization, then there is nothing you need to do.
If you would like to change what is considered critical or non-critical (for example: you want changes to meeting Location to be considered non-critical), you can change the default settings by using the Set-OrganizationConfig cmdlet and the -VisibleMeetingUpdateProperties parameter.

If you want to turn off this behavior entirely, you can specify a value of ‘AllProperties’, which will make all meeting message updates visible (this is the current behavior).

We'll be gradually rolling this out in early April, and the roll out will be completed worldwide by the end of June 2019.

Please reference the Additional Information link to learn more on how to configure this update.
28.03.2019 20:48:0041Normal28.03.2019 20:48:0031.07.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17654827.03.2019 01:28:0042New feature: Praise in Microsoft TeamsPraise is a new Microsoft Teams feature that gives users the option to send Praise badges to their colleagues, and we are beginning the rollout starting today. This feature is on-by-default and requires administrator action to disable.
This message is associated with Microsoft 365 Roadmap ID: 49172.
[How does this affect me?] With Praise, your users will be able to recognize their colleague’s contributions by sending various badges their way. “Leadership,” “team player,” and “problem solver” are just a few options.
We’ve begun rolling this out to all Teams organizations and we’ll complete the rollout in late April 2019. This feature is not currently available for GCC organizations.
[What do I need to do to prepare for this change?] If you would like to disable this feature, you’ll need to make the change by accessing your Microsoft 365 admin center. Please click here for supporting content regarding Teams management.
Otherwise, there is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
27.03.2019 01:28:0042Normal27.03.2019 01:28:0001.06.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17651526.03.2019 19:26:0043Updated rollout of Mail Reads within Exchange Online Mailbox Audit

In MC171679 we introduced audit of mail reads/accessed by default for owners, admins and delegates under the MailItemsAccessed action, with automatic availability of the action for users on default audit configuration.

We have rolled back the feature, at this time, and so the MailItemsAccessed action will no longer be available.

This enhancement is related to Microsoft 365 Roadmap ID 32224.

[How does this impact me?]

Since the audit action has been rolled back, records for MailItemsAccessed will not be available for both Exchange Auditing and Unified Audit logs. You can continue to use MessageBind to have visibility to Mailread actions. This change does not impact the remaining set of verbs, or the process of enabling mailbox auditing by default.

[What should I do to prepare for this change?]

There is no action for you at this time. We plan to reinitiate the rollout of the MailItemsAccessed audit action soon and will send additional communication to inform you of the new timeline.

26.03.2019 19:26:0043Normal26.03.2019 19:26:0024.05.2019 21:30:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17642125.03.2019 21:44:0044Updated Feature: Mail flow insights

We’re releasing new Mail flow insights. There will be 6 new insights/reports added on the Mail flow dashboard in Security & Compliance Center. We'll begin rolling this feature out soon.


This message is associated with Office 365 Roadmap ID 49361.


[How does this affect me?]

You will be able to see more insights for your organization's mail flow.


We'll be gradually rolling this out to Targeted Release ("entire org") customers in early April, and the roll out to all customers is planned in May and will be completed worldwide by early June.


[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.


Please click Additional information to learn more.

25.03.2019 21:44:0044Normal25.03.2019 21:44:0028.06.2019 09:00:00AwarenessAdvisoryExchange Online,Exchange Online ProtectionMessageCenter
MC17624321.03.2019 18:59:0048Updated Feature: Microsoft Teams Commercial Cloud Trial

We’re updating the Microsoft Teams Commercial Cloud Trial. We'll begin rolling this feature out soon.

This message is associated with Office 365 Roadmap ID 49456.

[How does this affect me?]

With the updated Microsoft Teams Commercial Cloud Trial offering, we are making it easier to manage all end-user initiated Teams trials. This will now be owned and controlled by the billing admin of the tenant, making this consistent with all other Microsoft 365 offers.

Starting in late April, all new Teams Trial users will begin leveraging this new offering. We will begin rolling out support for the migration of existing Teams Trial users to this new offering in late April and complete by early June. Once support is rolled out, users will be automatically migrated to the new offering next time they log into Teams.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

21.03.2019 18:59:0048Normal21.03.2019 18:59:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
MC17602819.03.2019 01:36:0050New feature: Smart time suggestions in Outlook on the webSmart time suggestions in Outlook on the web is a new Microsoft 365 feature. We'll begin rolling this feature out soon.
This message is associated with Microsoft 365 Roadmap ID: 48581.
[How does this affect me?] With smart time suggestions, when you schedule a meeting in Outlook on the web, it will recommend days and times when your attendees are available to meet so you can easily find a time that works for everyone. Smart time suggestions will work only if free/busy information is available.
We'll be gradually rolling this out to Targeted Release organizations this week, and the roll out will be completed worldwide by the end of April. This feature is not currently available for GCC organizations.
[What do I need to do to prepare for this change?] There is nothing you need to do to prepare for this change. To learn more about this feature, please read the "Create a meeting request or appointment" in the Additional Information link.
19.03.2019 01:36:0050Normal19.03.2019 01:36:0001.06.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
MC17588515.03.2019 17:23:0054Updated Feature: Updates to Microsoft Whiteboard

We're making several changes to Microsoft Whiteboard that will roll out over the next 3-4 months.


  1. For all organizations with Whiteboard - Microsoft Whiteboard will appear as an available product in Office 365 and the service principal will be added to appropriate tenants that have Whiteboard enabled.
  2. For all Office 365 tenants with Whiteboard located in Europe - Microsoft Whiteboard will automatically store whiteboard content in datacenters in that region.
  3. For all organizations with Surface Hubs – If you manage Surface Hubs, the legacy 2016 application of Whiteboard will be upgraded to the latest version and the legacy version will no longer receive updates.


[How does this impact me?]

You are receiving this message because our reporting indicates that Microsoft Whiteboard is available for your tenant.


[What should I do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.


Please click Additional information to learn more.

15.03.2019 17:23:0054Normal15.03.2019 17:23:0015.08.2019 09:00:00AwarenessAdvisoryMessageCenter
MC17580714.03.2019 17:31:0055Updated feature: Microsoft 365 Admin CenterThe Microsoft 365 admin center, available at admin.microsoft.com, is the common entry point for managing all your Microsoft 365 services. We’ll begin rolling out the new Microsoft 365 admin center with enhanced features and functionality in April.
This enhancement is related to Microsoft 365 Roadmap ID 48639.
[How does this impact me?] All IT admin tasks that can be completed in the admin center today will continue to be supported. There is no loss of functionality. With the change, there is a simplified admin experience with enhancements made in the following areas:
  • Improved user, device, and settings management to make common, everyday tasks more efficient
  • Targeted, intelligent recommendations and actionable insights to help your org get the most out of your Microsoft 365
  • Tailored admin center experiences for your organization and admin role to provide a focused environment

  • [What should I do to prepare for this change?] You don’t need to do anything. If you’d like to experience it today, it’s currently available in preview to all admins. Click on the toggle in the upper right corner of the admin center dashboard to access the preview. After the rollout of the new Microsoft 365 admin center, you will still have access to the old version of the admin center via the toggle in the upper right corner.
    For more details about the Microsoft 365 admin center, please review the Additional Information.
    14.03.2019 17:31:0055Normal14.03.2019 17:31:0028.06.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17580514.03.2019 17:17:0055Sharable links in Word and Outlook for Windows and mobileWe are making updates to key Office 365 apps to ensure that document sharing by inserting links in Word, Outlook for Windows and Outlook for iOS uses the permission you’ve set at the organization level for OneDrive and SharePoint. This change aligns with the expected permission level for email recipients and collaboration partners when inserting sharable links into Outlook messages and Word.

    This enhancement is related to Microsoft 365 Roadmap IDs 33156 and 33870.

    [How does this impact me?]
    In April, Monthly Channel subscribers of Outlook for Windows and Word will start to see a new dialogue box when they chose to insert a link in an email or a Word document that lets them know that a sharable link is being retrieved.

    Inserting a link for a shared document in email (including Outlook for iOS) and Word will continue to show clear, actionable text reflecting the file name as it exists in OneDrive and SharePoint.

    The permissions for the links in email and Word will default to the organization’s Sharing settings in the OneDrive Admin center, either “Shareable: Anyone with the link” or “Internal: Only people in your organization with the link”. The setting “Direct: Specific people” is not yet supported and the permission will default to the most permissive available link, if available. With this change, links will now almost always work for your email recipients. See Additional Information for more information about setting organization level permissions in OneDrive and SharePoint.

    [What should I do to prepare for this change?]
    There is nothing you need to do to prepare for this change however you may wish to review the external sharing setting in the OneDrive Admin settings to ensure it complies with your company policies.

    Please see the Additional Information for details on managing sharing in OneDrive and SharePoint.
    14.03.2019 17:17:0055Normal14.03.2019 17:17:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17576513.03.2019 22:20:0056New feature: Rich text formatting in YammerWe’re excited to announce that we’re adding rich text formatting to Yammer. We’ll begin rolling this change out soon.
    This message is associated with Microsoft 365 Roadmap ID: 18223.
    [How does this affect me?] All Yammer users will now be able to write posts using bold, italics, links, bullet points and numbered lists.
    Composing of messages with rich text formatting will only be available on the web client. However, the web client, as well as the mobile clients, will support rendering of styled messages. Messages created using rich text formatting can be edited on the web client but not on mobile clients.
    We’ll begin rolling this change out over the next week, and we anticipate rollout completion by mid-May 2019.
    [What do I need to do to prepare for this change?] There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
    13.03.2019 22:20:0056Normal13.03.2019 22:20:0015.06.2019 09:00:00AwarenessAdvisoryYammer EnterpriseMessageCenter
    MC17568312.03.2019 19:04:0057New feature: Share and coauthor documents with LinkedIn connectionsThe ability to share and coauthor documents with LinkedIn connections directly from OneDrive, SharePoint, Word, Excel, and PowerPoint Online is a new Office 365 feature. We'll begin rolling this feature out soon.
    This enhancement is related to Microsoft 365 Roadmap IDs 48534.
    We are rolling out a new feature to OneDrive, SharePoint, Word, PowerPoint, and Excel Online powered by LinkedIn to enhance the way users connect and collaborate with people outside their organization. This is one of the new experiences powered by LinkedIn that enhances the way users collaborate and build relationships by providing contextual insights and contact information for the people they work with, inside and outside their organization.
    This rollout is excluded from Microsoft 365 subscriptions in GCC at this time.
    This will roll out to Targeted Release starting at the end of March and is expected to complete worldwide by the end of April.
    [How does this impact me?] With this update, users will be able to find many of their first-degree LinkedIn connections as people suggestions when sharing files or folders from OneDrive, SharePoint, Word, Excel, and PowerPoint Online. This makes it easier for employees in your organization to collaborate with people outside your organization without needing to know their email addresses.
    This update respects all the existing external sharing policies and settings that you have configured in your organization. For example, this update will not suddenly enable external sharing with LinkedIn contacts for files which are not allowed to be shared externally. The OneDrive common sharing experience also implements safeguards to limit accidental external sharing by informing users when they have selected someone outside their organization.
    [What should I do to prepare for this change?] Both administrators and end users have control over this experience. Information for administrators is here: LinkedIn integration, including how to disable. End users with enabled accounts must opt-in by securely connecting their LinkedIn and Microsoft accounts before they can use this feature. Connect your LinkedIn and Microsoft accounts has information for end users about how to connect, what is shared, what’s not shared, and an FAQ.
    Please review your existing sharing policies to verify your experience with this new feature.
    Data is shared between the accounts to enable enhanced experiences in both Microsoft 365 and LinkedIn. We respect their privacy and honor settings across both services. For example, the feature will not work if a first-degree connection is not sharing their email with their network. The feature also will not use data from Office 365 to send automatic LinkedIn invites.
    To learn more about the features powered by LinkedIn in Microsoft 365, please read our Tech Community post: Achieve more through people with LinkedIn and Microsoft 365.
    12.03.2019 19:04:0057Normal12.03.2019 19:04:0015.05.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17551809.03.2019 05:24:0060Updated - New feature: Connected web parts for SharePoint OnlineUpdate - we have updated the roll out completion date of this feature.
    Connected web parts for SharePoint Online is a new Office 365 feature. We'll begin rolling this feature out soon.
    This message is associated with Microsoft 365 Roadmap ID: 33133.
    We’re releasing 3 new Connected Web Parts for SharePoint Online that allow you to display data from list and library web parts. With the List Properties, File Viewer and Embed web parts you can now connect to a data source and interact with lists and libraries in new ways.
    We'll be gradually rolling this out to Targeted Release organizations starting on March 11, and the roll out will be completed worldwide by the end of April 2019.
    There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
    09.03.2019 05:24:0060Normal09.03.2019 05:24:0017.05.2019 10:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
    MC17536106.03.2019 22:00:0063Feature update - Enabling the Flow app endpoint within TeamsWe are enabling the Flow app endpoint within Teams to allow the creation of a flow with the resulting action of “messaging someone in my tenant with Teams”.

    This enhancement is related to Microsoft 365 Roadmap ID Microsoft 365 Roadmap IDs 49149.

    This change does not impact Office 365 subscriptions in GCC.

    We will begin rolling this out at the beginning of April and expect to be complete by the end of April.

    [How does this impact me?]
    We are enabling the Flow endpoint on Teams to be on by default. After this update has rolled out a user that has access to Flow can create a flow with the resulting action of "messaging someone in my tenant in Teams". The message will be sent through the flow app to that target user within the tenant with proper attributes. Before this feature, you were not able to do so.

    [What should I do to prepare for this change?]
    There is nothing you need to do to prepare for this change. If you would like to disable the Flow app within Teams you can do so through the Teams admin portal.

    Please click Additional Information to learn more.
    06.03.2019 22:00:0063Normal06.03.2019 22:00:0031.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
    MC17535406.03.2019 19:33:0063New feature: New Yammer tab for Microsoft Teams now available

    Yammer tabs for Microsoft Teams is a new Office 365 feature. We'll begin rolling this feature out soon.


    This message is associated with Microsoft 365 Roadmap ID: 31502


    [How does this affect me?]

    Starting today, Microsoft Teams users will be able to add a Yammer tab to their Teams channel that loads a specified group or topic feed from Yammer. This new feature will allow members to follow and share conversations in Yammer without having to leave Teams.


    Your team members can participate in the Yammer conversation, right from Teams, or discuss a Yammer conversation in Teams before posting a reply to the wider Yammer group. When a Teams member goes to the Yammer tab, they are authenticated again by Yammer, so that they only see Yammer content that they have access to.


    Members can only add tabs to a team if team members are enabled to do so.


    [What do I need to do to prepare for this change?]

    There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

    06.03.2019 19:33:0063Normal06.03.2019 19:33:0005.06.2019 09:00:00AwarenessAdvisoryYammer Enterprise,Yammer.comMessageCenter
    MC17530906.03.2019 01:41:0063Some Yammer IDs returned by the REST API have grown beyond 32 bitsWe're making some changes to Yammer IDs that are exposed in our Yammer APIs.
    On April 4, 2019 some of our Yammer IDs may grow beyond 32 bits in size.
    This change does not impact Office 365 subscriptions in GCC.
    [How does this impact me?] You are receiving this message because it is possible that you have custom Yammer applications that consume Yammer IDs and you should know that if they are storing them as 32-bit integers they could start to fail. If your custom apps are built by third-party app developers, you should contact them to make sure they update their apps accordingly.
    If you do not have custom Yammer applications you can disregard this message.
    [What should I do to prepare for this change?] When this change takes effect, you will need to have modified your custom Yammer applications to not restrict Yammer ID variables to 32 bits.
    Please click Additional Information to learn more.
    06.03.2019 01:41:0063Normal06.03.2019 01:41:0017.05.2019 10:00:00ActionAdvisoryYammer EnterpriseMessageCenter
    MC17527405.03.2019 19:30:0064The Lifecycle Dashboards are now available to help you ensure user access to Office 365In February of last year, we announced that starting on October 13, 2020, your organization would need Office 365 ProPlus or Office 2019 apps to connect to Office 365 services. On September 6 of last year, we announced that we would continue supporting Office 2016 connections with Office 365 services through October of 2023. In order for you to better understand if and how your organization is affected by this change, and where you need to take action to migrate users, we’re providing you with two System Center Configuration Manager (SCCM) dashboards to help you begin your user migration.
    For larger organizations, we recommend starting this work in the near future in order to meet the October 13, 2020 deadline.
    [How does this affect me?] Office versions will now be visible in the SCCM Product Lifecycle Dashboard, and a new dashboard will display desktops in your organization that are ready to upgrade to Office 365 ProPlus with high confidence. These two features will be available with SCCM 1902.
    These dashboards will help ensure that your users will continue to be supported after October 13, 2020. The Product Lifecycle dashboard will display Office perpetual products, easily distinguishing the desktops that need their Office apps updated from those that do not. The ProPlus Readiness dashboard will identify the desktops that are ready to be upgraded to Office 365 ProPlus.
    [What do I need to do to prepare for this change?] There’s nothing you need to do to prepare for this change. Please click Additional information to learn more about the SCCM Product Lifecycle Dashboards.
    05.03.2019 19:30:0064Normal05.03.2019 19:30:0001.11.2020 08:00:00AwarenessAdvisoryMessageCenter
    MC17521305.03.2019 01:24:0064Updated feature: We're simplifying channel action terminology in TeamsWe’re making some changes to the names of channel action terminology in an effort to simplify the experience for your users. Currently, the two left rail actions - “Favorite” and “follow” are too close in name. We plan to simplify these concepts by renaming 'Favorite' to 'Show' and 'Remove favorite' to 'Hide'.
    Additionally, the current actions of “Follow” and “Unfollow” will be changed to “Notifications” for all shown channels. The channel notifications will provide additional notification preferences. All channels that your users have historically followed/unfollowed will be respected with this change.
    [How does this affect me?]
    After this change takes place, the action to 'Favorite' a channel will be renamed 'Show' a channel. Similarly, the action to 'Remove Favorite' a channel is renamed 'Hide' a channel. Actions to ‘Follow’ or ‘Unfollow’ a channel will be available through ‘Notifications’.
    We'll be gradually rolling this out to selected users in mid-March, and the roll out will be completed worldwide by the end of May 2019.
    [What do I need to do to prepare for this change?]
    There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
    05.03.2019 01:24:0064Normal05.03.2019 01:24:0030.06.2019 10:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
    MC17514702.03.2019 03:54:0067Outlook mobile supports Teams Meetings - updated roll out plansWe recently announced that we will be rolling out native support for creating and joining Microsoft Teams in Outlook for iOS and Android (MC173895). GCC High and Department of Defense organizations did not receive the original announcement. Based on your feedback, we’re providing more clarity, additional flexibility to the roll out plans and expanding the audience.
    This enhancement is related to Microsoft 365 Roadmap ID 32955 and 32956
    The roll out of Teams in Outlook mobile will take into consideration your organization’s plans to upgrade to Teams. The experience in Outlook mobile will be based on how you have set your coexistence mode between Teams and Skype for Business in the Microsoft Teams admin center or in PowerShell (Grant-CsTeamsUpgradePolicy), at the tenant level and/or for the user.
    We will start to roll out these changes at the beginning of April 2019 and will support Office 365 Monthly Channel customers world-wide as well as US Government Community Cloud (GCC) customers including GCC High and Department of Defense.
    [How does this impact me?] The experience for Teams Meetings in Outlook mobile will be based on how you set the organization’s or individual users’ Teams and Skype coexistence mode based on the following:
    Coexistence mode in Teams Admin Center Meetings solution in Outlook mobile
    Teams Only Teams
    Skype for Business with Teams Collaboration and Meetings* Teams
    Skype for Business with Teams Collaboration* Skype for Business
    Skype for Business Only Skype for Business
    Islands Skype for Business
    The experience in Outlook mobile will be based on this coexistence mode setting at the tenant and the user level. The user level setting, if present, will take precedence over the tenant level setting. For example, regardless of the tenant level setting, if a user’s coexistence mode is “Teams Only” or “Skype for Business with Teams Collaboration and Meetings”, then they will be able to add Teams meetings instead of Skype for Business when creating Outlook mobile events.
    Similarly, if a user’s coexistence mode is “Skype for Business Only”, “Skype for Business with Teams collaboration”, or “Islands”, then nothing changes. They will continue to have the option to add Skype for Business meetings in Outlook mobile.
    In addition, for customers who have also started to use the Microsoft sync technology for Outlook mobile (MC165218), we’re introducing a new Teams Join button in calendar events. This makes it easy to Join a Teams meeting and will be available for all coexistence modes as users could be invited to Teams Meetings even if they are not enabled to create Teams meetings themselves. Customers who are not using the Outlook mobile sync technology yet will continue to be able to join Teams Meetings using the weblink in the meeting description.
    Note that the addition of the Teams Join button does not replace the Skype Join button. The Skype Join button will continue to be offered for Skype Meetings, and the Teams Join button will be offered for Teams Meetings.
    [What should I do to prepare for this change?] There is nothing you need to do to prepare for this change however you may want to check your organization’s settings for Teams coexistence by April 1st, 2019 to be sure it is set to fit your organizational needs when we roll out these changes or if you wish to set preferences for certain groups of users within your organization.
    For information about how to set the Coexistence mode for your organization, see Additional Information. For more information about setting user level permissions, go here: Manage user access to Microsoft Teams
    02.03.2019 03:54:0067Normal02.03.2019 03:54:0031.05.2019 09:00:00ActionAdvisoryMessageCenter
    MC17513401.03.2019 22:49:0068New feature: Site navigation reorder via Drag and DropSite navigation reorder via Drag and Drop is a new Office 365 feature. We'll begin rolling this feature out soon.

    This message is associated with Microsoft 365 Roadmap ID: 48551.

    [How does this affect me?]
    For Site navigation links now users will be able to reorder via simply Dragging and Dropping.

    We've begun gradually rolling this out to Targeted release organizations, and the roll out will be completed worldwide by the end of April.

    [What do I need to do to prepare for this change?]
    There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
    01.03.2019 22:49:0068Normal01.03.2019 22:49:0030.05.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
    MC17509901.03.2019 04:11:0068Updated feature: Calls app available for all VoIP enabled users in Microsoft TeamsTo make calling more discoverable in Microsoft Teams, users that have Voice over IP enabled will now see the Calls App in the App bar on Desktop and Web Clients. There is no change in available functionality for existing users or their calling policy configurations.
    This feature has been previously discussed in MC149373 and MC171414.
    This message is associated with Microsoft 365 Roadmap ID: 33579.
    [How does this affect me?] After this change takes place, users that have calling enabled will see the Calls App in the App bar. Desktop and web clients already show the Calls App for Cloud Voice Users. Additionally, Mobile Microsoft Teams clients already show the Calls App for all calling enabled users.
    The Calls App will not show for existing users who have been configured with Voice over IP calling disabled.
    We’ll begin rolling this feature out soon and we anticipate rollout completion to take place by the end of March 2019.
    [What do I need to do to prepare for this change?] There’s nothing you need to do to prepare for this change, but you may want to verify that your users have the correct calling policy enabled to ensure they are configured for your organization’s desired calling experience. Please click Additional Information to learn more.
    01.03.2019 04:11:0068Normal01.03.2019 04:11:0030.05.2019 09:00:00AwarenessAdvisoryMicrosoft TeamsMessageCenter
    MC17396521.02.2019 21:33:0076Updated feature: Groups in Outlook - easier membership management

    We’re updating how owners of groups in Outlook can manage membership requests. We'll begin rolling this feature out soon.

    This message is associated with Office 365 Roadmap ID: 46436.

    [How does this affect me?]

    Powered by actionable messages, group owners will now have the capability to approve or decline membership requests right inside an email in Outlook on the web and in Outlook for Windows, without the need to navigate to other pages. Approved or declined requests will be visible to all the group owners. Owners can select one or multiple requests to approve or decline.

    We’re gradually rolling this feature out over the next few weeks, and the roll out will be completed worldwide by the end of March 2019. Organizations in GCC, GCC High, DoD and BlackForest environments will receive this feature update in mid-April.

    [What do I need to do to prepare for this change?]

    There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

    21.02.2019 21:33:0076Normal21.02.2019 21:33:0020.05.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
    MC17395621.02.2019 20:12:0076New feature: Open file links directly in Office desktop appsWe’re excited to announce a new feature that will allow your users to open files saved in the Microsoft cloud directly in their existing Office 365 desktop apps.

    This message is associated with Microsoft 365 Roadmap ID: 46330.

    [How does this affect me?]
    After this change takes place, when users open links to Word, Excel, or PowerPoint files, users can choose to have the file open directly in the appropriate Office app instead of it opening in the browser. For Office file links opened from the browser, the file will still open in the Office web apps.

    We'll be gradually rolling this out beginning in April 2019, and we anticipate rollout completion to take place over the following months.

    [What do I need to do to prepare for this change?]
    There’s nothing you need to do to prepare for this change, but you may consider updating your user training and notifying your helpdesk. If you have feedback on this feature, please don’t hesitate to leave a like, dislike, or comment.

    Please click Additional Information to learn more.
    21.02.2019 20:12:0076Normal21.02.2019 20:12:0030.09.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17391521.02.2019 03:48:0076Feature update - Mobile admin app update, including device managementThe Microsoft 365 Admin mobile app allows you to receive notifications, add users, reset passwords, manage devices, create support requests, and more- all while you’re on the go.
    This enhancement is related to Microsoft 365 Roadmap ID 47918.
    This rollout does not impact Office 365 subscriptions in GCC.
    [How does this impact me?] A new version of the Microsoft 365 Admin mobile app will be released with the following updates:
  • Rename the app from Office 365 Admin to Microsoft 365 Admin
  • Ability to restore corporate devices to factory state
  • Ability to remove corporate data from personal devices

  • [What should I do to prepare for this change?] You do not need to do anything to prepare for this change. There is no requirement to use the mobile app.
    The mobile app will be available in the iTunes App Store and Google Play store in late first quarter of calendar year 2019.
    The Additional Information and Microsoft 365 Tech Community will be updated with additional details.
    21.02.2019 03:48:0076Normal21.02.2019 03:48:0019.08.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17390821.02.2019 00:28:0076We’re making a change to non-delivery report notificationsBeginning on March 20, 2019, if after multiple attempts we’re unable to send or deliver a message sent by one of your users, we’ll send them a bounce message about it within 24 hours instead of 48 hours.
    [How does this affect me?]
    Currently, when a temporary routing error occurs, we repeatedly attempt to send the message for 48 hours before the system returns a bounce message (or non-delivery report (NDR)) to the sender.
    This change reduces the Office 365 message expiration timeout interval from 48 hours to 24 hours. By reducing the message expiration timeout interval to 24 hours, senders will know sooner if we were unable to deliver their message, and can respond to the error in a more timely fashion.
    Note that this will only affect messages queued on Office 365 servers. The message expiration times for messages queued on servers outside of Office 365 are not affected by this change.
    We will begin rolling this change out on March 20, 2019, and we anticipate worldwide rollout completion by the end of April.
    [What do I need to do to prepare for this change?] There is nothing you need to do to prepare for this change. Please click Additional Information to learn more about non-delivery reports in Office 365.
    21.02.2019 00:28:0076Normal21.02.2019 00:28:0021.06.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17389520.02.2019 21:45:0077Outlook mobile supports Teams MeetingsAs announced at Microsoft Ignite, we will be rolling out native support for creating and joining Microsoft Teams meeting in Outlook for iOS and Android in late March.
    This enhancement is related to Microsoft 365 Roadmap ID 32955 and 32956
    The ability to create Teams meetings will be available to all Outlook mobile customers. For customers who have migrated to the updated architecture using the Microsoft sync technology, as communicated in message center post MC165218, we’re also making it easier and faster to join a Teams meeting by introducing a new Join button in calendar events.
    This does not impact Office 365 subscriptions within GCC.
    [How does this impact me?] If your organization has enabled Teams only, then your users will start to see the option to add Teams when creating or editing calendar events in Outlook mobile. If your organization is enabled for both Skype for Business and Teams, the option to create Teams meetings will replace the option to create Skype meetings for your users in Outlook mobile. If some of the people in your organization still need to create Skype meetings, they can continue to do so from Outlook for Windows, Outlook for Mac and Outlook on the web.
    Customers who are not using the Outlook mobile sync technology yet will continue to be able to join Teams meeting using the weblink in the meeting description.
    If users in your organization receive invitations to Skype meetings, there is no change to the current experience, they will continue to see the Join button in those calendar events.
    [What should I do to prepare for this change?] There is nothing you need to do to prepare for this change if your organization has already enabled Teams for your users.
    If you do NOT want Teams as an option when creating meetings in Outlook mobile, even if select users are enabled for Teams, then you must disable Teams for the entire organization. Please see Additional Information for details on managing user access.
    20.02.2019 21:45:0077Normal20.02.2019 21:45:0028.06.2019 10:00:00AwarenessAdvisoryMessageCenter
    MC17377119.02.2019 01:22:0078We’re changing your default SharePoint admin center experienceThe new SharePoint admin center will be the default experience for some organizations. We'll begin rolling out this change soon.
    This message is associated with Microsoft 365 Roadmap ID 46375.
    [How does this affect me?] The SharePoint admin center experience, for Office 365 organizations of 50 or fewer licenses, will default to the new admin center experience.  You can switch back to the classic experience as necessary.
    We'll be gradually rolling this out to Standard Release customers that have 50 or fewer licenses in late March, and we will expand to larger organizations in the coming months. We will provide further notifications when we make the change for additional organizations.
    [What do I need to do to prepare for this change?] You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.
    To switch to the classic experience temporarily, select “Classic SharePoint admin center” in the left pane of the new SharePoint admin center.
    To control the default experience for all global and SharePoint admins in your organization:
    In the new SharePoint admin center, select Settings in the left pane, and then select Default admin center experience. Turning the setting to Off will set the classic admin center as default and On will set the new admin center as default. This control is available now.
    This change will be skipped for customers that have modified the setting of their default admin center experience.
    Please click Additional information to learn more.
    19.02.2019 01:22:0078Normal19.02.2019 01:22:0015.06.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
    MC17361615.02.2019 03:14:0082Clutter for Outlook is being retired beginning January 31, 2020As we previously announced in December 2017, on the Outlook blog, we will be retiring the Clutter feature from Outlook beginning January 31, 2020. To help our users manage their mail and be productive, we are leading with the Focused Inbox experience which provides a similar benefit as Clutter by showing less important and urgent mail in Other.
    [How does this impact me?] We’ll continue to make Clutter available to Office 365 customers until January 31, 2020. To prepare for Clutter’s eventual retirement, we’ve turned the feature off by default for new users. It’s also deactivated for those with extremely low usage (less than 12 emails per month being moved to the Clutter folder), however they can re-enable Clutter at any time, if desired.
    [What should I do to prepare for this change?] If your organization is using Clutter today, the process for transitioning to Focused Inbox depends on what version of Outlook you are using.
    Please review the Additional Information for additional details and guidance for transitioning to Focused Inbox.
    15.02.2019 03:14:0082Normal15.02.2019 03:14:0001.03.2020 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
    MC17361515.02.2019 03:10:0082New feature: SharePoint Online gets Sticky Column Headers for Lists and LibrariesSticky Column Headers is a new SharePoint Online feature. We'll begin rolling this feature out soon.
    This enhancement is related to Microsoft 365 Roadmap ID 46103.
    We'll be gradually rolling this out to Targeted release Organizations in mid-February 2019, and the roll out will be completed worldwide by the end of April.
    [How does this impact me?] For large lists and libraries, the column headers will remain visible as you scroll vertically or horizontally in larger lists and libraries.
    [What should I do to prepare for this change?] There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.
    15.02.2019 03:10:0082Normal15.02.2019 03:10:0031.05.2019 09:00:00AwarenessAdvisorySharePoint OnlineMessageCenter
    MC17359714.02.2019 22:38:0083Microsoft Teams desktop app coming to new Office 365 ProPlus installs

    In an effort to improve and streamline user’s initial experience with Teams, we’re making an enhancement so that the desktop Teams app will now be downloaded automatically when new users with Office 365 ProPlus licenses first download the Office Pro Plus apps. We'll begin rolling this feature out soon.

    This message is associated with Office 365 Roadmap ID: 46444.

    [How does this affect me?]

    After this change takes place for your organization, Microsoft Teams will be included in the initial user download with other apps like Word, PowerPoint and Excel in their Office 365 ProPlus subscription. You or your users will no longer need to separately download and install Teams. This change does not affect any existing users who are already licensed and using the service.

    We began gradually rolling this change out to Targeted Release organizations in mid-January. On February 25, 2019 the rollout will continue to Monthly Channel, and to Semi-Annual Channel Targeted (SAC-T) subscribers on March 12. Semi-Annual Channel (SAC) subscribers will see this change in July 2019.

    [What do I need to do to prepare for this change?]

    If you want your new users to have access to Microsoft Teams by default, then there’s nothing you need to do to prepare for this change. If you would like to restrict access to Teams, or delay the rollout for your organization, please click Additional Information below.

    14.02.2019 22:38:0083Normal14.02.2019 22:38:0016.08.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17337712.02.2019 00:21:0085Updated feature: New Tasks module in Outlook on the WebWe are excited to announce the new Tasks module in Outlook on the web as an updated Office 365 feature. We'll begin rolling this feature out in mid-March.
    This enhancement is related to Microsoft 365 Roadmap ID 34338.
    [How does this impact me?] Customers who opt-in to the early version of the new Outlook on the web will see a newly redesigned Tasks experience, powered by Microsoft To-Do. We'll be gradually rolling this out to Targeted Release customers in March, and the rollout will follow the general release timeline of the new Outlook on the web.
    This rollout is excluded from Office 365 subscriptions in GCC.
    [What should I do to prepare for this change?] If you white-list or block domains that can be accessed by your users - Please note that the new Tasks experience powered by To-Do uses the “to-do.office.com” domain, so you might wish to whitelist domains accordingly for your users to be able to use the new Tasks experience.
    If you don't white-list/block any domains, you don't need to do anything, but may consider updating your user training, and notifying your helpdesk.
    12.02.2019 00:21:0085Normal12.02.2019 00:21:0031.05.2019 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
    MC17303406.02.2019 22:28:0091New Feature: Microsoft 365 Public Roadmap Updates

    New feature: Last Modified Date, Enhances RSS and Feedback features coming to the Microsoft 365 Public Roadmap


    We'll be gradually rolling this out to all customers in early March 2019, and the roll out will be completed worldwide by the end of April 2019.


    [How does this impact me?]

    Starting in March, we will begin rolling out the following enhancements and features to the Microsoft 365 Public Roadmap:

    • Last Modified Date: When this update is rolled out, the Last Modified Date will reflect the date information is updated for an individual feature item. This will allow better tracking when information changes for features that are important to you and your organization.
    • Enhanced RSS Feeds: Currently, when a ‘More Information’ link is not provided for a feature, the M365 Roadmap RSS feed defaults to provide a link back to the roadmap. The RSS feed will be updated to include both a ‘View Roadmap Item’ link, directing users to the feature in the M365 Public Roadmap and a ‘More Information’ link that will direct users to more information when available. Not all features will have a ‘More Information’ link, as upcoming feature information is provided as early as possible and this information is not always available. ‘More Information’ links will continue to be provided in Message Center posts for specific features.
    • Microsoft 365 Feedback Feature: We will be adding a feature to the M365 Public Roadmap which will allow users to share ideas and suggestions on how we can improve the M365 Public Roadmap experience. We look forward to hearing feedback on how we can continue to improve the M365 Public Roadmap experience.


    [What do I need to do to prepare for this change?]

    There is nothing you need to do to prepare for this change.


    Please click the Additional Information link to access the Microsoft 365 Roadmap.

    06.02.2019 22:28:0091Normal06.02.2019 22:28:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17292504.02.2019 21:16:0093SharePoint tenant opt-out for modern lists is retiring in 2019We're making some changes to how environments can opt out of modern lists in SharePoint. Starting April 1, 2019, we're going to begin retiring the ability to opt out of modern lists at the tenant level.
    [How does this impact me?] In 2016, we introduced a new “modern” experience for SharePoint, bringing extensibility, accessibility, and responsive design to a complete overhaul of the user experience. Since then, modern has been the center of innovation in SharePoint and OneDrive, although classic mode remains supported and available.
    We’re making it easier for users to get to our latest feature updates. Starting April 1, 2019, it will no longer be possible to restrict an entire organization (tenant) to classic mode for lists and libraries. Lists and libraries may still use classic mode using the granular opt-out switches that we provide at the site collection, site, list, and library levels. Additionally, lists that use certain features and customizations that are not supported by modern will still be automatically switched to classic mode.
    After April 1, lists and libraries that are in classic mode as a result of tenant opt-out will automatically be shifted to modern. Users will benefit from enhancements and new features such as attention views, PowerApps integration, Flow, column formatting, and the filters pane.
    [What should I do to prepare for this change?] The SharePoint Modernization scanner identifies sites and lists that have customizations that are not supported by modern UI. Although many of these lists will automatically remain in classic mode even after this change, you may wish to keep some sites running entirely in classic to avoid users switching between different experience modes within a single site.
    Administrators can use a PowerShell script to enable or disable the modern experience for a single site collection or for a list of site collections as provided by the SharePoint Modernization scanner. Alternately, users can still use the “return to classic” option on modern views of lists or libraries to temporary return to classic, and list owners can use List Settings to configure that list to use the classic experience for all users.
    Please click Additional Information to learn more.
    04.02.2019 21:16:0093Normal04.02.2019 21:16:0031.05.2019 09:00:00ActionAdvisorySharePoint OnlineMessageCenter
    MC17285101.02.2019 19:51:0096New feature: Changes to PowerPoint and Word to open files fasterWe’re excited to release a new change to make documents saved to OneDrive and SharePoint open faster. We’ll be rolling this change out soon.
    Rather than always checking for updates for cloud files prior to opening, Word and PowerPoint will open any existing version on the user’s device and then sync updates immediately afterwards. This is already the behavior today for files saved to local OneDrive and SharePoint sync folders. This change introduces this behavior for files that are stored on the cloud but not synced to your device in a sync folder.
    This message is associated with Microsoft 365 Roadmap ID: 45426.
    [How does this affect me?] After this change takes place, while Word or PowerPoint checks for the latest version of a non-synced file, users will see the previous version of a document stored in the Office Document Cache.
    Users will be able to see the sync status of their files in the Status Bar (along the bottom of the window) and will be notified accordingly if we are unable to get the latest version. For example, for files that were deleted or moved on the server, the user will receive a message after opening the cached copy. If the user has AutoSave turned on for the file, they will automatically see the latest changes. Otherwise, they will see it the next time they Save or click on "Updates Available" in the Status Bar.
    Users and automated scripts or add-ins should avoid acting (especially creating copies, printing, presenting) on files that are modified on multiple machines until the file is up to date.
    This change updates the behavior for non-synced files to match the behavior of files stored within a user’s sync folders, which already open the version stored on their machine while changes are downloaded. This will apply to files opened directly from OneDrive, SharePoint (both Online as well as On-Premises) or Microsoft Teams that are not in a local sync folder.
    By default, files are kept in the Office Document Cache for 14 days. Users can delete specific files from the Office Document Cache via the Upload Center. If files are deleted or if a user has chosen to automatically delete files from the Office Document Cache when they are closed, users will not be able to view files as quickly.
    We will begin rolling these changes out to Monthly Channel organizations at the end of February, beginning with PowerPoint, and we anticipate rollout completion to all Monthly Channel organizations for both Word and PowerPoint to take place over the next few months. We anticipate that organizations using our Semi-Annual Channels will also receive the change as a part of the September 2019 Semi-Annual (Targeted) release.
    [What do I need to do to prepare for this change?] Performance is very important to us and the goal of this change is for users to have a faster experience when opening cloud documents. In most cases, we do not expect an impact to existing workflows. However, we are sensitive to potential unexpected impacts. While existing APIs remain unchanged, it’s possible that add-ins or automated processes that assume Word or PowerPoint files are up to date with the cloud immediately upon document open may need to be updated.
    If you have any concerns or you’d like additional details on how to validate your scenarios, please leave feedback for this post via Message Center, and we will work with you to address your needs. Please make sure you provide your contact email address so we are able to get in touch.
    You can learn more about cache settings by clicking Additional Information below.
    01.02.2019 19:51:0096Normal01.02.2019 19:51:0001.06.2019 10:00:00AwarenessAdvisorySharePoint Online,OneDrive for BusinessMessageCenter
    MC17270030.01.2019 01:04:0098Updated - The Office 365 Home Page is becoming the default start page for all Office 365 commercial usersCurrently in Office 365, there is a setting that allows users to personalize what page they land on when they log into Office 365. The Office 365 Home Page has evolved to pull a user's most relevant apps, documents and places where they are working —all in one place--and consequently will be the default page a user lands on when signing into Office 365.

    This enhancement is related to Microsoft 365 Roadmap ID 45971.

    [How does this impact me?]
    We initially designed the start page setting to bring users to a preferred app faster. Now that the Office 365 Home Page has evolved to provide quick access not only to default and recently used apps but also recent and recommended files and places, we are retiring the setting for users to select a different default start page.

    Of course, users can continue to leverage browser bookmarks and direct URL navigation to apps like Outlook to get straight to the app of their choice.

    In March, users who have set a start page other than the Office 365 Home Page will be directed to the Office 365 Home Page when they log-in.

    [What should I do to prepare for this change?]
    You don't need to do anything but may consider informing your users of the upcoming change and encouraging them to bookmark, in the browser, the page they've set their start page to. Consider also updating your user training and notifying your help desk.

    The Additional Information will be updated closer to the rollout.
    30.01.2019 01:04:0098Normal30.01.2019 01:04:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17269129.01.2019 22:12:0099Upated: Compliance Manager new experienceWe’re updating Compliance Manager to help you assess your compliance risks more effectively with the integration with Secure Score and the ability to customize your assessments for Microsoft and non-Microsoft applications.

    This message is associated with Microsoft 365 Roadmap ID 31757.

    [How does this affect me?]
    Integration with Secure Score means that you will now get credit for both Compliance Score and Secure Score when you implement security-oriented controls. The new experience can monitor your tenant’s configuration settings and update your scores automatically when a security setting is configured in according with the Secure Score or Compliance Manager guidance. Additionally, you can now import your own assessments in Compliance Manager, including assessments for non-Microsoft applications and for standard and regulations that are not included in Compliance Manager by default.

    GCC customers can also access Compliance Manager, however GCC users should evaluate whether to use the document upload feature, as the storage is currently compliant with Office 365 Tier C.

    The new experience is only for Microsoft 365 at this time, but Azure and Dynamics will onboard in the future. If you would like to continue to use the old experience until all applications have been onboarded, you are able to do so.

    We'll be gradually rolling out the new experience to customers by the end of April, and the rollout is expected to be completed worldwide by the end of May. When your tenant gets the new experience, you’ll still have access to all existing assessment data via the new experience for at least 6 months. After that, you’ll have the option to export your data or migrate it to the new experience.

    [What do I need to do to prepare for this change?]
    The monitoring of configuration settings is disabled by default. When the new experience is rolled out, tenant administrators must configure Role Based Access Control (RBAC) under Admin > Settings on the Service Trust Portal (https://servicetrust.microsoft.com) before enabling automatic detection. Click here to learn more about how to set up RBAC.

    The Additional Information link will be updated with information about the new experience when the new experience begins rolling out.
    29.01.2019 22:12:0099Normal29.01.2019 22:12:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17254826.01.2019 00:33:00102We’re making it easier for your users to save files to OneDrive Consumer, OneDrive for Business, and SharePoint OnlineWe’re making it easier for your users to save their files to Microsoft 365 cloud storage locations. We'll begin rolling this feature out soon.

    This message is associated with Microsoft 365 Roadmap ID: 45063.

    [How does this affect me?]
    This new experience allows users of Word, Excel & PowerPoint on Windows and macOS to save documents to the cloud more easily.

    When using Ctrl-S (Windows), Cmd-S (macOS), or the Save button in the QAT (Quick Access Toolbar), a new dialog will allow users to quickly set the file name and save to OneDrive Consumer, OneDrive for Business or SharePoint Online. When closing an unsaved document, users will also see a new save experience that defaults to automatic saving to a user’s preferred Microsoft 365 cloud storage solution.

    We'll begin gradually rolling this out starting in early February 2019, and we anticipate rollout completion by mid-2019.

    This feature is not yet available for GCC organizations.

    [What do I need to do to prepare for this change?]
    You don't need to do anything to prepare for this change, but you may consider updating your user training, and notifying your helpdesk. Please click Additional Information to learn more.
    26.01.2019 00:33:00102Normal26.01.2019 00:33:0001.07.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17228518.01.2019 23:07:00110Updated feature: Planner Notifications for TeamsWe’re updating the Planner app for Teams to add notifications. We'll begin rolling this feature out soon.

    This message is associated with Microsoft 365 Roadmap ID: 45878.

    [How does this affect me?]
    After this update takes place, team members who are members of a team with Planner installed will receive a Teams notification when a task is assigned to them by another person. This notification will appear in the Teams Activity Feed and Chat.

    This update adds a Planner bot to teams where Planner is installed, and audit logs will show the bot as being added by “Microsoft Teams Services” on behalf of the team owner. The only purpose of the bot is to send a notification to a specific user when a task is assigned to him or her by another person, users cannot interact with this bot in any other way.

    We’ll be gradually rolling this feature starting on February 18, 2019 and we anticipate rollout completion by July 2019.

    [What do I need to do to prepare for this change?]
    You don't need to do anything, but may consider updating your user training and notifying your helpdesk. Please click Additional Information to learn more.
    18.01.2019 23:07:00110Normal18.01.2019 23:07:0001.08.2019 09:00:00AwarenessAdvisoryPlanner,Microsoft TeamsMessageCenter
    MC17195512.01.2019 00:02:00116Update - Updated feature: New "Sign-in options" link on the Microsoft 365 login pageUpdate: We are pleased to announce that we are ready to move forward with this roll out. We will be begin rolling this change out in early May and expect to be completed by the end of May.

    We're updating the Microsoft 365 login page to add a new link for more sign-in options. The functionality this link provides only applies to personal accounts.

    This message is associated with Microsoft 365 Roadmap ID: 45516.

    [How does this affect me?]
    Your organization may have configured the login experience to only accept organization accounts, if so, this change does not impact you.

    After this change takes place, when signing into Office, your users will see a new link that says "Sign-in options" on the Microsoft 365 login page. Clicking on this link will bring the user to a new screen that will show additional login options that only work for personal Microsoft account users. These sign in options will have no impact for commercial users. i.e. A user that uses the new sign in options, will not login to the commercial Microsoft 365 service.

    [What do I need to do to prepare for this change?]
    You don't need to do anything, but may consider updating your user training, and notifying your helpdesk. Please click Additional Information to learn more.
    12.01.2019 00:02:00116Normal12.01.2019 00:02:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC17178608.01.2019 19:11:00120Reminder: We’re retiring StaffHub and migrating your organization to Microsoft TeamsAs previously communicated in MC149144 on September 24, 2018, Microsoft Teams is evolving to include a new set of capabilities that will simplify schedule management and help deliver the tools for every worker to get the job done. As a result, we will be retiring Microsoft StaffHub on October 1, 2019 and we will be focusing our investments on Microsoft Teams.
    After October 1, 2019 users that attempt to log in to StaffHub will be greeted with a message directing them to download Microsoft Teams.
    To help you in your transition to Microsoft Teams, we ask that you review the details below for pre-requisites related to user and data migration across Microsoft Teams and StaffHub.
    If you’re receiving this notice, you have one or more people in your organization who currently use Microsoft StaffHub. Please communicate these details to the right stakeholders in your organization.
    [How does this affect me?] To help transition users, we plan to migrate data chat history in Microsoft StaffHub to Microsoft Teams. The amount of chat history that will be available in Microsoft Teams will depend on how soon you configure your organization for the transition. We recommend taking action no later than June 30, 2019 to provide enough time to transition 90 days of data by October 1, 2019. Please ensure that Microsoft Teams and Office 365 Group Creation are enabled in your Microsoft 365 admin center before the transition begins, as these setting selections are essential to us being able to move your StaffHub data into Teams. Failure to turn these services on by June 30, 2019, will result in a later migration date or less chat data being copied over.
    Please note, by enabling Microsoft Teams and Office 365 Group Creation, we will create a corresponding Microsoft Teams team and Office 365 Group if those do not already exist for each of your StaffHub teams as part of the migration effort. We will also begin copying Microsoft StaffHub chat messages into the corresponding Teams team chat history. We recommend that you enable Office 365 Group Creation and Microsoft Teams no later than June 30, 2019, and that you do not delete these teams or groups as they are required to successfully migrate data into Microsoft Teams.
    [What do I need to do to prepare for this change?] We encourage you to activate Microsoft Teams, ensure group creation is enabled and that all impacted users are properly covered with an active license that includes Microsoft Teams. This is just the first step as we help you transition towards Microsoft Teams. As more information becomes available we will be providing additional documentation and guidance on user and team migration over the next few months.
    Please click Additional Information to learn more about Microsoft Teams and how you can enable it for your organization.
    If you plan to terminate your use of Microsoft StaffHub before October 1, 2019, and you do not wish to have your organization’s data transferred to Microsoft Teams, please contact us at [email protected]
    08.01.2019 19:11:00120Normal08.01.2019 19:11:0015.08.2019 09:00:00ActionAdvisoryMessageCenter
    MC16592728.11.2018 22:59:00161Yammer group files in Office 365 connected groups will now be stored in SharePointWe'll be gradually releasing a new feature where all new files posted in Yammer groups that are Office 365 connected will be stored in SharePoint.
    This message is associated with Microsoft 365 Roadmap ID: 26821.
    [How does this affect me?]
    With this functionality all new files posted in Office 365 connected Yammer groups will now be stored in the SharePoint account that is associated with the Office 365 Group. Keep in mind that existing files, files in unconnected groups, and files in private messages will not be impacted by this change and will continue to be stored in the legacy location.
    This change will begin rolling out towards the end of December and is expected to be completed worldwide by end of March 2019.
    [What do I need to do to prepare for this change?]
    You don’t need to do anything to prepare for this change, but you may consider updating user training, and notifying your helpdesk. Please click Additional information to learn more.
    28.11.2018 22:59:00161Normal28.11.2018 22:59:0026.11.2019 09:00:00AwarenessAdvisoryYammer EnterpriseMessageCenter
    MC15170419.10.2018 23:42:00200Updated feature: The help and support pane is now available from the Office 365 navbarWe’re excited to announce that your Office 365 navbar will now include a help and support pane. We’ll begin rolling this feature out soon.

    This message is associated with Microsoft 365 Roadmap ID: 42268.

    [How does this affect me?]
    The new and improved help and support pane provides contextual help on top issues, access to the latest support information, and the ability for admins to customize the pane with their company’s helpdesk information. The same services that power help and support in Office desktop clients, are now extended to the web.

    You can see this today in the new Outlook in the web that is available to Targeted Release organizations. It will be coming to more Office 365 web apps over the next six months, starting with Office.com.

    [What do I need to do to prepare for this change?]
    You don't need to do anything, but you may consider configuring the helpdesk contact card in the Admin Portal, and notifying your helpdesk. Please click Additional information to learn more.
    19.10.2018 23:42:00200Normal19.10.2018 23:42:0031.05.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC14914425.09.2018 22:13:00225New schedule management and Home screen features coming to Teams; StaffHub will be retiredWe are pleased to announce that Microsoft Teams is evolving to include a new set of capabilities that will simplify schedule management and help deliver the tools for every worker to get the job done.

    Because our investments in schedule management have been developed with Firstline Workers in mind, we’ve decided to retire Microsoft StaffHub and bring this capability in addition to a new Home screen experience, into Teams, making it the platform for all workers.

    Customers using Microsoft StaffHub, today, have been notified via MC149091. If you did not receive this notification, and you were planning to utilize StaffHub, we encourage you to explore Microsoft Teams, the ultimate hub for teamwork for employees.

    [How does this affect me?]
    Starting in September 2018, we will be rolling out new features in Microsoft Teams designed to simplify schedule management, and deliver the tools and information every worker needs.

    Starting on April 1, 2019, Microsoft StaffHub will no longer be available for new tenants and will be removed from the Apple App Store, Google Play Store, and all other points of access. Microsoft StaffHub will then stop functioning for all users on October 1, 2019. Anyone who attempts to open it will be greeted with a message directing them to download Microsoft Teams.

    All users will require an active license that includes Microsoft Teams.

    These changes are part of our continued efforts to refine Microsoft 365 as the universal toolkit for teamwork and the investments we’re making in Microsoft Teams.

    [What do I need to do to prepare for this change?]
    There is nothing you need to do to prepare for this change. We encourage you to explore Microsoft Teams.

    If you are receiving this message and had future plans to explore Microsoft StaffHub, please click Additional Information to learn more.
    25.09.2018 22:13:00225Normal25.09.2018 22:13:0001.06.2019 09:00:00AwarenessAdvisoryMessageCenter
    MC14356903.07.2018 22:15:00309We’re making changes to Exchange Web Services for Office 365Over the last few years, we have been investing in services to help developers access information in Office 365 in a simple and intuitive way. As we make progress on this journey, we have continued to evaluate the role of Exchange Web Services (EWS) and how to best interact with Office 365 data and authenticate with Exchange Online.

    We are making the following announcements today:
  • Basic Authentication for Exchange Web Services (EWS) will be retired, beginning October 13, 2020, as we focus our efforts on OAuth 2.0.

  • We are investing our development resources in Microsoft Graph as the future mechanism for accessing Exchange Online data.


  • [How does this affect me?]
    With this change, we are focusing our investments in OAuth 2.0 for authentication and authorization as the preferred method to access Exchange Online. Starting October 13, 2020, we will completely remove Basic Authentication for EWS as a way to access Exchange Online.

    Additionally, EWS will continue to receive security updates and certain performance updates, but product design and features will remain unchanged.

    [What do I need to do to prepare for this change?]
    If you have been using Basic Authentication for EWS in your applications, you should plan to use OAuth 2.0 for authentication and authorization, before October 13, 2020. In addition, we strongly suggest that you plan on transitioning to Microsoft Graph based Outlook APIs to continue accessing Exchange Online data.

    Please click Additional Information to learn more.
    03.07.2018 22:15:00309Normal03.07.2018 22:15:0013.11.2020 09:00:00AwarenessAdvisoryExchange OnlineMessageCenter
    MC14350302.07.2018 17:28:00310Update on Visio Web Access from SharePoint OnlineLast September, we announced that we would be removing Visio Web access from SharePoint Online (MC120728). Since then we have listened to your feedback and are extending the timeline to September 2019 to allow more time for the migration of your existing Visio content to the newer platforms.

    Beginning September 30, 2019, Visio Web Access (Visio Service) and its Web Part for SharePoint Online will no longer be available. Instead of Visio Web Access you can now use Visio Online and migrate your organization’s web parts to a newer experience with the new Javascript (JS) APIs for Visio Online. Visio Online enables high fidelity viewing, sharing, and collaboration in your favorite browser, without installing the client for all Office 365 licenses. It supports embedding Visio diagrams in SharePoint Online using a modern file viewer web part and with IFrame along with JS API programmability.

    [How does this affect me?]
    Beginning September 30, 2019, users in your organization will only be able to view Visio diagrams in their browser, but not create or edit. Visio Online viewing is available to most Office 365 subscriptions.

    [What do I need to do to prepare for this change?]
    Before September 30, 2019 you should migrate any of your existing Visio content to the newer platforms.

    Please click Additional Information for more detail about how to migrate your existing content.
    02.07.2018 17:28:00310Normal02.07.2018 17:28:0030.10.2019 08:00:00ActionAdvisorySharePoint OnlineMessageCenter
    MC13466121.04.2018 00:52:00382Important update on Windows phone apps for Skype for BusinessThe Windows Phone app for Skype for Business is being retired. After this change takes effect, new users will no longer be able to download the app from the Microsoft Store, and the app will no longer be supported.

    While Microsoft continues to support Windows 10 Mobile, we aren't focused on building new features for it. We continue to invest in the Skype for Business mobile apps for iOS and Android, as well as desktop applications for Windows and Mac.

    [How does this affect me?]
    You are receiving this message because your organization has access to Skype for Business as part of your subscription.

    Existing users of the Windows Phone app for Skype for Business will continue to be able to use the app. Moreover, they will continue to be able to re-download the app from the Windows Store.

    New users who need to install the app from the Windows Store, will have the following experience:
  • Beginning in August 2018, Skype for Business on Windows Phone 8.1 will no longer be available for download.
  • Beginning in December 2019, Skype for Business on Windows 10 Mobile, will no longer be available for download.

  • The Skype for Business app may continue to work after these dates, but this is not guaranteed. This app will no longer receive updates or support.

    [What do I need to do to prepare for this change?]
    If you need to continue using Skype for Business on Windows Phone, we recommend that you install the app before the dates that are cited above. Please click Additional Information to learn more.
    21.04.2018 00:52:00382Normal21.04.2018 00:52:0015.01.2020 08:00:00AwarenessAdvisorySkype for BusinessMessageCenter
    IDPublishedTimePublishedDaysAgoTitleMessageLastUpdatedTimeLastUpdatedDaysAgoSeverityStartTimeEndTimeActionTypeClassificationAffectedServiceMessageType
    ServiceFeatureIDTitleImpactDescriptionLastUpdatedTimeLastUpdatedDaysAgoUserFunctionalImpactPostIncidentDocumentUrlSeverityStartTimeEndTimeClassificationAffectedTenantCountAffectedUserCountMessageType
    Office 365 PortalAdministrationMO179236Can't launch appsWindows 7 users may have been unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.08.05.2019 21:28:100Sev229.03.2019 23:00:0008.05.2019 21:00:00Advisory21543325Incident
    Skype for BusinessManagement and ProvisioningLY179047Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.08.05.2019 20:32:480Sev215.03.2019 11:00:00Advisory8507806Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    OneDrive for BusinessOneDrive for BusinessOD178669Can’t sync changes to Office documentsUsers may have been unable to sync recent Office document changes to OneDrive for Business.07.05.2019 14:28:501https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178669')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident6647323Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    Skype for BusinessManagement and ProvisioningLY179206Inaccurate Skype for Business conferencing metrics in Admin Usage ReportsAdmins may notice that usage reports contain inaccurate data for Skype for Business conferencing scenarios.06.05.2019 23:48:261Sev225.04.2019 14:00:00Advisory8605029Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Exchange OnlineE-Mail and calendar accessEX179059My Templates add in missingUsers may have been unable to see the My Templates add in for Outlook on the web or the desktop client.06.05.2019 06:59:422Sev230.04.2019 01:00:0005.05.2019 15:30:00Advisory18322638Incident
    Office 365 PortalPortalMO178979Unable to access Microsoft 365 services or featuresUsers may have been unable to access Microsoft 365 services or features.04.05.2019 04:10:584https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='MO178979')Sev002.05.2019 22:34:0002.05.2019 23:10:00Incident21543325Incident
    OneDrive for BusinessOneDrive for BusinessOD178975Delays or problems loading OneDrive contentUsers may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.04.05.2019 04:10:324https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178975')Sev002.05.2019 22:04:3902.05.2019 23:10:00Incident6748785Incident
    SharePoint OnlineSharePoint FeaturesSP178746Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.04.05.2019 04:09:564https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178746')Sev002.05.2019 21:41:5102.05.2019 23:10:00Incident13019533Incident
    SharePoint OnlineSharePoint FeaturesSP178789Delays or problems loading SharePoint Online sites or OneDrive for BusinessUsers may experience intermittent delays or navigation errors when accessing SharePoint sites or OneDrive content.02.05.2019 22:24:176Sev202.05.2019 21:46:5802.05.2019 22:24:15Advisory79704Incident
    Yammer EnterpriseYammer ComponentsYA178707Can't load feedsUsers may have experienced intermittent failures when attempting to load feeds in the Yammer service.02.05.2019 07:10:436Sev202.05.2019 05:05:0002.05.2019 06:15:00Advisory4074204Incident
    Skype for BusinessAudio and VideoLY178266Can't add Skype contactsUsers were unable to add federated Skype contacts.26.04.2019 18:13:4812Sev218.03.2019 13:25:0025.04.2019 21:05:00Advisory8507806Incident
    Office 365 PortalAdministrationMO178227Usage report content delaysAdmins may have noticed that some usage reports were only showing data prior to April 17, 2019.26.04.2019 05:35:5612Sev221.04.2019 00:00:0026.04.2019 01:56:00Advisory21537464Incident
    Office 365 PortalAdministrationMO178238Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.26.04.2019 03:46:1812Sev222.04.2019 04:57:0026.04.2019 01:40:00Advisory21506665Incident
    Exchange OnlineE-Mail timely deliveryEX178295Can't access emailN/A25.04.2019 09:13:1113Sev225.04.2019 01:34:2925.04.2019 09:12:58Advisory17982048Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineE-Mail timely deliveryEX177852Unable to send email due to SPFUsers may have been intermittently unable to send email to some domains.17.04.2019 18:17:0521Sev216.04.2019 22:00:0017.04.2019 01:25:00Incident18083178Incident
    Office OnlineWord OnlineOO177786Can't save Word documentsUsers may have experienced errors when attempting to save their Word documents using Office Online.16.04.2019 23:22:4122Sev216.04.2019 04:55:5316.04.2019 12:00:00Advisory7021578Incident
    Skype for BusinessAudio and VideoLY177821Not receiving push notificationsUsers may have been intermittently not receiving Skype for Business app push notifications on Android and iOS devices.16.04.2019 21:35:1822Sev212.04.2019 14:00:0016.04.2019 20:10:00Advisory8637660Incident
    Skype for BusinessAudio and VideoLY177299Audio/video calling problemsUsers may have been unable to initiate and accept Skype for Business audio and video calls..15.04.2019 13:22:3023https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='LY177299')Sev208.04.2019 08:55:0008.04.2019 10:45:00Incident3350523Incident
    Yammer EnterpriseYammer ComponentsYA177663Can't view live events on mobile appsUsers may have been unable to view live events via iOS and Android clients.13.04.2019 01:09:2325Sev112.04.2019 20:14:0013.04.2019 01:02:00Advisory4012188Incident
    Skype for BusinessAudio and VideoLY177655Can't join or delays joining conferences via Public Switched Telephone Network (PSTN)Users may have been unable to join or experience delays of up to 12 seconds when joining conference calls via PSTN.12.04.2019 21:54:4126Sev212.04.2019 18:37:0012.04.2019 21:00:00Incident2902160Incident
    Yammer EnterpriseYammer ComponentsYA177625Can't use Search function.Users were unable to use the Search function within Yammer.12.04.2019 14:53:0826Sev212.04.2019 08:55:0012.04.2019 13:43:00Advisory4012188Incident
    Skype for BusinessAudio and VideoLY177631Unable to join PSTN conference callsUsers were unable to join Public Switched Telephone Network (PSTN) conference calls.12.04.2019 13:50:3026Sev212.04.2019 10:55:0012.04.2019 13:50:14Incident6587744Incident
    Yammer EnterpriseYammer ComponentsYA177605Can't load feedsUsers may have been unable to load their feeds on Yammer.com.12.04.2019 02:18:1826Sev212.04.2019 00:20:0012.04.2019 01:13:00Advisory4012188Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    SharePoint OnlineTenant AdminSP177484SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.11.04.2019 01:54:1727Sev208.04.2019 14:00:0011.04.2019 01:42:00Advisory6319693Incident
    Yammer EnterpriseYammer ComponentsYA177504Sign in errorsUsers may experience sign in errors when attempting to access Yammer.10.04.2019 23:35:1027Sev210.04.2019 21:18:2210.04.2019 22:25:00Advisory4012188Incident
    Office OnlineWord OnlineOO177408Word documents online issueUsers may have been unable to open Word documents online using the Web Application Client.10.04.2019 00:06:2328Sev209.04.2019 12:36:4309.04.2019 13:41:51Advisory6970822Incident
    Skype for BusinessAudio and VideoLY177351Can't dial in or out of audio conferences intermittentlyUsers may have been unable to dial in or out of audio conferences intermittently.09.04.2019 00:34:5429Sev208.04.2019 18:56:0009.04.2019 00:21:07Incident2902160Incident
    ServiceFeatureIDTitleImpactDescriptionLastUpdatedTimeLastUpdatedDaysAgoUserFunctionalImpactPostIncidentDocumentUrlSeverityStartTimeEndTimeClassificationAffectedTenantCountAffectedUserCountMessageType
    ServiceFeatureIDTitleImpactDescriptionPublishedTimePublishedDaysAgoMessageLastUpdatedTimeLastUpdatedDaysAgoUserFunctionalImpactPostIncidentDocumentUrlSeverityStartTimeEndTimeClassificationAffectedTenantCountAffectedUserCountMessageType
    Office 365 PortalAdministrationMO179236Can't launch appsWindows 7 users may have been unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.08.05.2019 18:43:280Title: Can't launch apps
    User Impact: Windows 7 users may be unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.
    More info: When users launch the desktop app, they may see the template page, and then the app closes.
    Affected users may work around the problem by completely exiting and reopening the Office app, or by opening the files from their saved location, rather than through the specific Office app.
    Current status: We've initiated deployment of the fix to the service environment. Users who are able to do so may download and install the fix now via standard Windows update; though, we expect that the deployment will fully complete within the next few hours.
    Scope of impact: This issue affects any enterprise user attempting to launch Office apps on Windows 7.
    Start time: Friday, March 29, 2019, at 10:00 PM UTC
    Preliminary root cause: A faulty feature update within the March 2019 Office update, is causing Office apps on Windows 7 to crash.
    Next update by: Thursday, May 9, 2019, at 7:00 PM UTC
    08.05.2019 21:28:100Sev229.03.2019 23:00:0008.05.2019 21:00:00Advisory21543325Incident
    Office 365 PortalAdministrationMO179236Can't launch appsWindows 7 users may have been unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.07.05.2019 07:19:301Title: Can't launch apps
    User Impact: Windows 7 users may be unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.
    More info: When users launch the desktop app, the user may see the template page, and then the app closes.
    As we work to restore service, users can update to the latest version of Internet Explorer 11 to mitigate impact. If the issue persists following the update, users may need to manually install Cumulative Update (CU) KB3008923.
    This issue only affects Windows 7 users running build version 16.0.11601.20144.
    Current status: We've determined that a code regression was introduced through a feature update contained within the March Office update. We're performing validation on a potential fix to ensure that it will resolve the issue prior to deployment. In the interim, users may be able to further avoid the issue by opening the files directly and not through the specific Office app.
    Scope of impact: This issue affects any enterprise user attempting to launch Office apps on Windows 7.
    Preliminary root cause: A code regression was introduced through a feature update within the March 2019 Office update, which is impacting access to Office apps on Windows 7.
    Next update by: Tuesday, May 7, 2019, at 7:00 PM UTC
    08.05.2019 21:28:100Sev229.03.2019 23:00:0008.05.2019 21:00:00Advisory21543325Incident
    Office 365 PortalAdministrationMO179236Can't launch appsWindows 7 users may have been unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.07.05.2019 18:46:261Title: Can't launch apps
    User Impact: Windows 7 users may be unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.
    More info: When users launch the desktop app, the user may see the template page, and then the app closes.
    While we work to deploy the long-term solution for this issue, affected users may work around the problem by completely exiting and reopening the Office app.
    Additionally, users may avoid further impact by opening the files from their saved location, rather than through the specific Office app.
    Current status: We’ve disabled the feature update responsible for the app crashes and confirmed that this has mitigated impact for most affected users. Additionally, we’ve completed validation of the long-term fix and are preparing to deploy it to the affected environment within the next 24 hours.
    Scope of impact: This issue affects any enterprise user attempting to launch Office apps on Windows 7.
    Preliminary root cause: A code regression was introduced through a feature update within the March 2019 Office update, which is impacting access to Office apps on Windows 7.
    Next update by: Wednesday, May 8, 2019, at 7:00 PM UTC
    08.05.2019 21:28:100Sev229.03.2019 23:00:0008.05.2019 21:00:00Advisory21543325Incident
    Office 365 PortalAdministrationMO179236Can't launch appsWindows 7 users may have been unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.08.05.2019 21:28:100Title: Can't launch apps
    User Impact: Windows 7 users may have been unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.
    More info: Affected Windows 7 users would have been shown the template page upon opening an Office app, and then the app would close.
    The problem could have been circumvented by completely exiting and reopening the Office app, or by opening the files from their saved location, rather than through the specific Office app.
    Final status: We've confirmed that the fix has fully deployed to the service environment and the problem is resolved.
    Scope of impact: This issue affected any enterprise user attempting to launch Office apps on Windows 7.
    Start time: Friday, March 29, 2019, at 10:00 PM UTC
    End time: Wednesday, May 8, 2019, at 7:00 PM UTC
    Preliminary root cause: A faulty feature update within the March 2019 Office update caused Office apps on Windows 7 to crash.
    Next steps: - We're examining our pre-deployment update validation procedures to help prevent further impact from future updates.
    We'll publish a post-incident report within five business days.
    08.05.2019 21:28:100Sev229.03.2019 23:00:0008.05.2019 21:00:00Advisory21543325Incident
    Skype for BusinessManagement and ProvisioningLY179047Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.03.05.2019 21:55:045Title: Incomplete call records
    User Impact: Admins may see incomplete results when viewing call records in Call Analytics.
    More info: Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected. 
    Current status: We've determined that a recent change intended to adjust an Application Programming Interface (API) used in the records process resulted in impact. We've developed a code fix that is being tested and validated before deployment.
    Scope of impact: This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.
    Start time: Friday, March 15, 2019, at 10:00 AM UTC
    Root cause: A recent change intended to adjust an Application Programming Interface (API) used in the records process resulted in impact.
    Next update by: Saturday, May 4, 2019, at 9:00 PM UTC
    08.05.2019 20:32:480Sev215.03.2019 11:00:00Advisory8507806Incident
    Skype for BusinessManagement and ProvisioningLY179047Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.08.05.2019 20:32:480Title: Incomplete call records
    User Impact: Admins may see incomplete results when viewing call records in Call Analytics.
    More info: Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected.
    Current status: The deployment of the fix has achieved 96 percent completion. Admins hosted on infrastructure that has received the fix may already see impact mitigation.
    Scope of impact: This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.
    Start time: Friday, March 15, 2019, at 10:00 AM UTC
    Estimated time to resolve: Based on the current progress of the fix, we anticipate the remainder of the deployment completing by end of day Friday, May 10, 2019.
    Preliminary root cause: A recent change intended to adjust an API used in the records process resulted in incomplete results.
    Next update by: Friday, May 10, 2019, at 9:00 PM UTC
    08.05.2019 20:32:480Sev215.03.2019 11:00:00Advisory8507806Incident
    Skype for BusinessManagement and ProvisioningLY179047Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.06.05.2019 21:52:432Title: Incomplete call records
    User Impact: Admins may see incomplete results when viewing call records in Call Analytics.
    More info: This is an incremental update to provide the latest status on the issue.
    Current status: The fix has been deployed to 83 percent of the affected environment. Some admins may begin to see impact mitigation as the fix reaches their environment. The fix is expected to complete deployment by the end of the week. For complete details on this event, please reference the post from 7:21 PM UTC on May 4, 2019.
    Next update by: Wednesday, May 8, 2019, at 9:00 PM UTC
    08.05.2019 20:32:480Sev215.03.2019 11:00:00Advisory8507806Incident
    Skype for BusinessManagement and ProvisioningLY179047Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.04.05.2019 21:21:074Title: Incomplete call records
    User Impact: Admins may see incomplete results when viewing call records in Call Analytics.
    More info: Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected.
    Current status: We've successfully validated the code fix and have begun deployment to the affected infrastructure. We expect deployment of the fix to complete in approximately two weeks.
    Scope of impact: This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.
    Start time: Friday, March 15, 2019, at 10:00 AM UTC
    Estimated time to resolve: Based on current progress, we expect the issue to be fully resolved in approximately two weeks.
    Root cause: A recent change intended to adjust an API used in the records process resulted in incomplete results.
    Next update by: Monday, May 6, 2019, at 9:00 PM UTC
    08.05.2019 20:32:480Sev215.03.2019 11:00:00Advisory8507806Incident
    Skype for BusinessManagement and ProvisioningLY179047Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.03.05.2019 21:32:265Title: Incomplete call records
    User Impact: Admins may see incomplete results when viewing call records in Call Analytics.
    More info: Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected. 
    Current status: We're investigating a potential issue with the Skype for Business service. We'll provide an update within 30 minutes.
    Scope of impact: This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.
    08.05.2019 20:32:480Sev215.03.2019 11:00:00Advisory8507806Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.30.04.2019 20:36:528Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We're adding additional capacity to help process trace requests more efficiently. In parallel, we're continuing to apply traffic routing optimizations and run a clean-up script for previously-logged message trace results to provide more immediate relief.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Wednesday, May 1, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.06.05.2019 20:47:142Title: Message trace functionality issues
    User Impact: Admins may have experienced issues with message trace reports and services utilizing message trace functionality.
    More info: Affected admins would have experienced this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins could work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and was not impacted by this incident.
    Final status: We've confirmed that the backlog has fully drained, and subsequent service monitoring shows that the problem is fixed.
    Scope of impact: Impact was specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    End time: Saturday, May 4, 2019, at 6:00 AM UTC
    Root cause: A resource configuration issue allowed a large influx of Exchange Online log requests to overwhelm the traffic routing service, resulting in a backlog of these requests.
    Next steps: - We're closely monitoring the previously affected service environment for an additional period to ensure no further impact occurs.
    We'll publish a post-incident report within five business days.
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.01.05.2019 21:35:417Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident. Instructions for extended message trace can be found here: https://docs.microsoft.com/en-us/powershell/module/exchange/mail-flow/start-historicalsearch?view=exchange-ps
    Current status: We've deployed additional capacity within the environment and the provisioning for these machines is 90 percent complete. In parallel, we're investigating a potential performance issue that could be contributing to this problem and are evaluating our mitigation options.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Thursday, May 2, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.25.04.2019 20:55:2813Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident. Current status: We're continuing to implement additional monitoring tools to aid our investigation of the underlying problem. Additionally, we've made infrastructural improvements that should improve the end-user experience and limit impact associated with the event. We're monitoring the rate in which message trace requests are processing to confirm the improvements have helped.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Friday, April 26, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.24.04.2019 21:17:5214Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: Our monitoring of system logs indicates that the additional optimizations implemented to reduce impact did not yield the anticipated relief, as some users may continue to experience results latency up to six hours. We're implementing additional monitoring tools to the affected infrastructure to enhance the process of isolating the cause of the spike in traffic load and develop our next troubleshooting steps.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Thursday, April 25, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.02.05.2019 20:50:046Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident. Instructions for extended message trace can be found here: https://docs.microsoft.com/en-us/powershell/module/exchange/mail-flow/start-historicalsearch?view=exchange-ps
    Current status: Our work to deploy and provision additional capacity to the environment is complete and we've observed that the backlog of requests is decreasing. In parallel, we've initiated deployment of a fix that will address a performance issue that is contributing to impact, and we expect that fix to be fully deployed by tomorrow.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Friday, May 3, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.26.04.2019 20:17:2612Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We're continuing to make improvements on the impacted infrastructure to restore the service. In parallel, we've confirmed that the additional improvements have begun draining the affected queues.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Monday, April 29, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.29.04.2019 21:22:359Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We're continuing our efforts to install additional monitoring functionality within the affected environment to identify the potential cause. Concurrently, we're working to implement additional traffic routing optimizations within the environment to alleviate the message trace latency and reporting issues. We're also preparing to run a script to clean up previously-logged message trace results as a secondary mitigation effort.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Tuesday, April 30, 2019, at 2:00 AM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.30.04.2019 03:00:398Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We're preparing to implement a series of traffic routing optimizations within the affected environment. Additionally, we're running the script to clean up previously-logged message trace results in an effort to provide additional relief.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Tuesday, April 30, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.04.05.2019 02:40:044Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: The deployment of the fix has completed. We're monitoring the environment to ensure that the backlog of requests processes as expected, which we anticipate will complete by Monday, May 6, 2019.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Monday, May 6, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.03.05.2019 20:28:175Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: The deployment of the fix is in progress and we anticipate that this process will complete within the next three hours. The backlog of requests will require more time to process and we'll be monitoring the environment to ensure it completes as expected.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Saturday, May 4, 2019, at 2:00 AM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    Exchange OnlineManagement and ProvisioningEX178260Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.24.04.2019 17:59:4414Title: Message trace functionality issues
    User Impact: Admins may experience issues with message trace reports and services that utilize message trace functionality.
    More info: Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).
    Admins can work around the problem by using the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We've confirmed that our initial efforts to mitigate latency caused by the additional traffic spike did not successfully resolve the issue. We've implemented additional optimizations to further reduce impact while working to identify the cause of the traffic spike, and we’re monitoring system logs to determine if this configuration change will help alleviate the latency issue. If our testing proves to be successful, we’ll be implementing the configuration change to the remaining impacted infrastructure. In addition, we're continuing to identify the cause of the traffic spikes.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Next update by: Wednesday, April 24, 2019, at 8:00 PM UTC
    08.05.2019 04:19:560Sev215.04.2019 19:00:0004.05.2019 08:00:00Advisory18218053Incident
    OneDrive for BusinessOneDrive for BusinessOD178669Can’t sync changes to Office documentsUsers may have been unable to sync recent Office document changes to OneDrive for Business.07.05.2019 14:28:501A post-incident report has been published.07.05.2019 14:28:501https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178669')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident6647323Incident
    OneDrive for BusinessOneDrive for BusinessOD178669Can’t sync changes to Office documentsUsers may have been unable to sync recent Office document changes to OneDrive for Business.01.05.2019 23:28:047Title: Can’t sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to OneDrive for Business.
    More info: Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within OneDrive for Business.
    Users experiencing these issues may be able to successfully edit existing Office documents by saving a copy to a local machine before making edits, then re-uploading the document as a copy to OneDrive for Business. Users may edit newly created Office documents first by creating the document with a save location on their local machine and then saving the document to OneDrive for Business once edits are completed.
    Current status: We’re continuing to monitor the service while the fix completes deployment and anticipate that it will finish within 24 hours.
    Scope of impact: Any of your users that are using Office 2013 client or earlier versions may experience this problem.
    Start time: Sunday, April 28, 2019 at 7:00 PM UTC
    Root cause: A recent update introduced a code issue that prevents Office document changes from properly syncing to OneDrive for Business via Office 2013 clients or earlier versions.
    Next update by: Thursday, May 2, 2019, at 1:00 AM UTC
    07.05.2019 14:28:501https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178669')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident6647323Incident
    OneDrive for BusinessOneDrive for BusinessOD178669Can’t sync changes to Office documentsUsers may have been unable to sync recent Office document changes to OneDrive for Business.02.05.2019 03:02:076Title: Can’t sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to OneDrive for Business.
    More info: Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within OneDrive for Business.
    Users experiencing these issues may be able to successfully edit existing Office documents by saving a copy to a local machine before making edits, then re-uploading the document as a copy to OneDrive for Business. Users may edit newly created Office documents first by creating the document with a save location on their local machine and then saving the document to OneDrive for Business once edits are completed.
    Current status: The fix is progressing as expected and has been deployed to approximately 60 percent of the affected environment. We anticipate that it will finish within the next 16 hours. We've confirmed with users that the fix does resolve the issue so users will experience service restoration as the fix reaches their environment.
    Scope of impact: Any of your users that are using Office 2013 client or earlier versions may experience this problem.
    Start time: Sunday, April 28, 2019 at 7:00 PM UTC
    Root cause: A recent update introduced a code issue that prevents Office document changes from properly syncing to SharePoint Online sites via Office 2013 clients or earlier versions.
    Next update by: Thursday, May 2, 2019, at 5:00 PM UTC
    07.05.2019 14:28:501https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178669')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident6647323Incident
    OneDrive for BusinessOneDrive for BusinessOD178669Can’t sync changes to Office documentsUsers may have been unable to sync recent Office document changes to OneDrive for Business.02.05.2019 18:48:076Title: Can’t sync changes to Office documents
    User Impact: Users may have been unable to sync recent Office document changes to OneDrive for Business.
    More info: Users operating Office 2013 or earlier clients may have encountered this issue when editing existing or newly created Office documents with a target save location within OneDrive for Business.
    Users experiencing these issues could have successfully worked around the problem by saving a copy of an existing Office document to a local machine before making edits, then re-uploading the document as a copy to OneDrive for Business. Additionally, users could edit new Office documents first by creating the document with a save location on their local machine and then saving the document to OneDrive for Business once edits were completed.
    Final status: We’ve confirmed that the fix has saturated across all of the affected environments and the problem is fixed.
    Scope of impact: Any of your users that were using Office 2013 client or earlier versions may have experienced this problem.
    Start time: Sunday, April 28, 2019, at 7:00 PM UTC
    End time: Thursday, May 2, 2019, at 10:00 AM UTC
    Root cause: A service update contained code that interfered with Office document sync to OneDrive for Business.
    Next steps: - We're working to identify additional compatibility checks to ensure issues of this nature do not arise in future updates.
    We'll publish a post-incident report within five business days.
    07.05.2019 14:28:501https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178669')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident6647323Incident
    OneDrive for BusinessOneDrive for BusinessOD178669Can’t sync changes to Office documentsUsers may have been unable to sync recent Office document changes to OneDrive for Business.01.05.2019 20:33:307Title: Can’t sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to OneDrive for Business.
    More info: This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions.
    Current status: We’ve identified that a recent service update is inadvertently causing issues syncing Office document changes to OneDrive for Business. We’ve developed and have begun deploying a fix for this issue to the affected environment. We expect this process may require 24 – 48 hours to complete.
    Scope of impact: Your organization is affected by this event, and impact is reportedly limited to a few users.
    Root cause: A recent update is inadvertently causing Office document sync changes to OneDrive for Business via Office 2013 client or earlier.
    Next update by: Thursday, May 2, 2019, at 7:00 PM UTC
    07.05.2019 14:28:501https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178669')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident6647323Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.01.05.2019 20:28:507Title: Can't sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to SharePoint Online sites.
    More info: This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions.
    Current status: We’ve completed developing the fix and have begun deploying it to the affected environment. We expect this process may require 24 – 48 hours to complete.
    Scope of impact: Your organization is affected by this event, and impact is reportedly limited to a few users.
    Root cause: A recent update is inadvertently causing Office document sync changes to SharePoint Online sites via Office 2013 client or earlier.
    Next update by: Thursday, May 2, 2019, at 7:00 PM UTC
    07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.02.05.2019 18:40:246Title: Can't sync changes to Office documents
    User Impact: Users may have been unable to sync recent Office document changes to SharePoint Online sites.
    More info: Users operating Office 2013 or earlier clients may have encountered this issue when editing existing or newly created Office documents with a target save location within SharePoint Online.
    Users experiencing these issues could have successfully worked around the problem by saving a copy of an existing Office document to a local machine before making edits, then re-uploading the document as a copy to SharePoint Online. Additionally, users could edit new Office documents first by creating the document with a save location on their local machine and then saving the document to SharePoint Online once edits were completed.
    Final status: We’ve confirmed that the fix has saturated across all of the affected environments and the problem is fixed.
    Scope of impact: Any of your users that were using Office 2013 client or earlier versions may have experienced this problem.
    Start time: Sunday, April 28, 2019, at 7:00 PM UTC
    End time: Thursday, May 2, 2019, at 10:00 AM UTC
    Root cause: A service update contained code that interfered with Office document sync to SharePoint Online.
    Next steps: - We're working to identify additional compatibility checks to ensure issues of this nature do not arise in future updates.
    We'll publish a post-incident report within five business days.
    07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.01.05.2019 23:27:307Title: Can't sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to SharePoint Online sites.
    More info: Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within SharePoint Online.
    Users experiencing these issues may be able to successfully edit existing Office documents by saving a copy to a local machine before making edits, then re-uploading the document as a copy to SharePoint Online. Users may edit newly created documents first by creating the document with a save location on their local machine and then saving the document to SharePoint Online once edits are completed.
    Current status: We’re continuing to monitor the service while the fix completes deployment and anticipate that it will finish within 24 hours.
    Scope of impact: Any of your users that are using Office 2013 client or earlier versions may experience this problem.
    Start time: Sunday, April 28, 2019 at 7:00 PM UTC
    Root cause: A recent update introduced a code issue that prevents Office document changes from properly syncing to SharePoint Online sites via Office 2013 clients or earlier versions.
    Next update by: Thursday, May 2, 2019, at 1:00 AM UTC
    07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.07.05.2019 14:28:151A post-incident report has been published.07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.01.05.2019 04:26:357Title: Can't sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to SharePoint Online sites.
    More info: This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions.
    Current status: We've confirmed that the issue is the result of a recent update. We're developing a fix which will be applied throughout the affected infrastructure upon completing all required validation checks.
    Scope of impact: Your organization is affected by this event, and impact is reportedly limited to a few users.
    Root cause: A recent update is inadvertently causing Office document sync changes to SharePoint Online sites via Office 2013 client or earlier.
    Next update by: Wednesday, May 1, 2019, at 7:00 PM UTC
    07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.02.05.2019 02:59:356Title: Can't sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to SharePoint Online sites.
    More info: Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within SharePoint Online.
    Users experiencing these issues may be able to successfully edit existing Office documents by saving a copy to a local machine before making edits, then re-uploading the document as a copy to SharePoint Online. Users may edit newly created documents first by creating the document with a save location on their local machine and then saving the document to SharePoint Online once edits are completed.
    Current status: The fix is progressing as expected and has been deployed to approximately 60 percent of the affected environment. We anticipate that it will finish within the next 16 hours. We've confirmed with users that the fix does resolve the issue so users will experience service restoration as the fix reaches their environment.
    Scope of impact: Any of your users that are using Office 2013 client or earlier versions may experience this problem.
    Start time: Sunday, April 28, 2019, at 7:00 PM UTC
    Estimated time to resolve: Based on current progress, we expect the fix to complete deployment by 5:00 PM UTC on Thursday, May 2, 2019.
    Root cause: A recent update introduced a code issue that prevents Office document changes from properly syncing to SharePoint Online sites via Office 2013 clients or earlier versions.
    Next update by: Thursday, May 2, 2019, at 5:00 PM UTC
    07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.01.05.2019 00:58:337Title: Can't sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to SharePoint Online sites.
    More info: This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    Scope of impact: Your organization is affected by this event, and impact is reportedly limited to a few users.
    07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    SharePoint OnlineSharePoint FeaturesSP178637Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.01.05.2019 01:29:477Title: Can't sync changes to Office documents
    User Impact: Users may be unable to sync recent Office document changes to SharePoint Online sites.
    More info: This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions.
    Current status: We've tentatively confirmed that a recent update has inadvertently degraded the service. We're working to confirm the exact cause and to develop and test a fix to address this issue.
    Scope of impact: Your organization is affected by this event, and impact is reportedly limited to a few users.
    Root cause: A recent update is inadvertently causing Office document sync changes to SharePoint Online sites via Office 2013 client or earlier.
    Next update by: Wednesday, May 1, 2019, at 6:30 AM UTC
    07.05.2019 14:28:151https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178637')Sev228.04.2019 21:00:0002.05.2019 12:00:00Incident12764190Incident
    Skype for BusinessManagement and ProvisioningLY179206Inaccurate Skype for Business conferencing metrics in Admin Usage ReportsAdmins may notice that usage reports contain inaccurate data for Skype for Business conferencing scenarios.06.05.2019 23:48:261Title: Inaccurate Skype for Business conferencing metrics in Admin Usage Reports
    User Impact: Admins may notice that usage reports contain inaccurate data for Skype for Business conferencing scenarios.
    Current status: We identified an issue in which Skype for Business usage reports contain inaccurate data for conferencing scenarios. Our investigation determined that a routine service update introduced a code issue which resulted in impact. We've developed and deployed a fix to the affected environment and will be monitoring the deployment as it progresses.
    Scope of impact: Impact is specific to the Conference Organizer Activity and Conference Participant Activity reports.
    Start time: Thursday, April 25, 2019, at 12:00 PM UTC
    Preliminary root cause: A routine service update contained a code issue that caused Skype for Business usage reports to contain inaccurate data for specific conferencing scenarios.
    Next update by: Friday, May 10, 2019, at 9:00 PM UTC
    06.05.2019 23:48:261Sev225.04.2019 14:00:00Advisory8605029Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.29.04.2019 22:53:419Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Specifically, users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web, the Outlook client for Mac, or the iOS mobile app.
    Current status: We've developed a long-term fix for this issue and we're working to validate this internally before initiating a deployment to the affected environment.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Start time: Monday, March 25, 2019, at 2:25 PM UTC
    Estimated time to resolve: We believe that the fix will be completely deployed by Friday, May 10, 2019, at 12:00 PM UTC.
    Root cause: A network configuration change intended to improve service performance inadvertently mislabeled a subset of Skype for Business infrastructure. As a result, a communication problem with the affected Skype for Business infrastructure and a subset of Exchange Online infrastructure was introduced that resulted in impact.
    Next update by: Monday, May 6, 2019, at 9:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.06.05.2019 23:08:092Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Specifically, users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web, the Outlook client for Mac, or the iOS mobile app.
    Current status: We've completed initial validation of the fix and are performing additional testing to ensure it effectively resolves the issue. We'll provide an updated timeline for full deployment to affected users when available; however, we expect this may take two to three weeks to complete.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Start time: Monday, March 25, 2019, at 2:25 PM UTC
    Estimated time to resolve: We expect this issue to be completely resolved for all affected users within the next three weeks as the fix is safely implemented through our change management process.
    Root cause: A network configuration change intended to improve service performance inadvertently mislabeled a subset of Skype for Business infrastructure. As a result, a communication problem with the affected Skype for Business infrastructure and a subset of Exchange Online infrastructure was introduced that resulted in impact.
    Next update by: Monday, May 13, 2019, at 9:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.10.04.2019 23:57:0027Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We've determined that a network misconfiguration occurred on a portion of infrastructure that facilitates communication between the Skype for Business and Exchange Online services, which caused impact to Skype for Business meeting creation functionality via Outlook on the web. We're implementing a fix to correct the configuration issue on the affected infrastructure, and we’re assessing how long the fix will take to fully resolve the event.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Root cause: A network misconfiguration occurred on a portion of infrastructure that facilitates communication between the Skype for Business and Exchange Online services, which resulted in impact to Skype for Business meeting creation for Outlook events via Outlook on the web.
    Next update by: Thursday, April 11, 2019, at 11:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.11.04.2019 23:34:5426Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We're continuing to work on implementing the fix to correct the configuration issue on the affected infrastructure. In parallel, we're still attempting to establish an estimated time to resolution as we progress closer to the deployment throughout the affected environments.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Root cause: A network misconfiguration occurred on a portion of infrastructure that facilitates communication between the Skype for Business and Exchange Online services, which caused impact to Skype for Business meeting creation functionality via Outlook on the web.
    Next update by: Friday, April 12, 2019, at 10:30 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.13.04.2019 00:15:3125Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We're actively working to ensure the best course of action of implementing the fix to the entirety of the affected infrastructures. We're also actively working to establish an optimal resolution time for deployment.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Root cause: A network misconfiguration occurred on a portion of infrastructure that facilitates communication between the Skype for Business and Exchange Online services, which caused impact to Skype for Business meeting creation functionality via Outlook on the web.
    Next update by: Monday, April 15, 2019, at 9:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.10.04.2019 07:43:1528Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, affected users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We've developed a configuration fix and have deployed it to a small subset of the network infrastructure. Testing has confirmed that this change fixes the issue. We're deploying the change to the remaining infrastructure, which may take up to 12 hours to complete.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Estimated time to resolve: We expect this issue to be completely resolved for all affected users within the next 12 hours as the fix is safely implemented through our change management process.
    Root cause: A potential misconfiguration on a subset of the network infrastructure may be incorrectly routing traffic, causing Skype for Business meeting creation request to not add the meeting details to the meeting invitation.
    Next update by: Wednesday, April 10, 2019, at 10:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.10.04.2019 00:35:3128Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, affected users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.10.04.2019 01:10:5328Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, affected users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We're investigating network diagnostic logs to determine the underlying cause of the issue.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Next update by: Wednesday, April 10, 2019, at 1:00 AM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.10.04.2019 02:51:3528Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, affected users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We're continuing to investigate network diagnostic logs to determine the underlying cause of the issue.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Next update by: Wednesday, April 10, 2019, at 3:00 AM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.10.04.2019 06:56:2528Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, affected users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We've determined that a potential misconfiguration on a subset of the network infrastructure may be incorrectly routing traffic. We're working to develop the necessary configuration changes to fix the issue.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Root cause: A potential misconfiguration on a subset of the network infrastructure may be incorrectly routing traffic, causing Skype for Business meeting creation request to not add the meeting details to the meeting invitation.
    Next update by: Wednesday, April 10, 2019, at 7:00 AM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.10.04.2019 04:52:2828Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, affected users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: We're gathering Transport Control Protocol (TCP) trace information to further isolate the source of the problem.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Next update by: Wednesday, April 10, 2019, at 5:00 AM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.15.04.2019 22:51:3823Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status:  We're continuing to validate a fix for this issue and are working on a deployment schedule. We suspect that the fix will be fully deployed sometime in May, and aim to provide a more solidified estimate next week.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Next update by: Monday, April 22, 2019, at 9:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.22.04.2019 22:43:2416Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through various Outlook services.
    More info: Specifically, users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web, the Outlook client for Mac, or the iOS mobile app.
    Current status: We're continuing to develop and validate a long-term fix for this issue, which is expected to be completely deployed by Friday, May 10, 2019, at 12:00 PM UTC. If users are experiencing issues when utilizing the provided workaround, please contact support and discuss the issues with the workaround and provide available network trace data so a short-term fix may be implemented manually.
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Start time: Monday, March 25, 2019, at 2:25 PM UTC
    Estimated time to resolve: We believe that the fix will be completely deployed by Friday, May 10, 2019, at 12:00 PM UTC.
    Root cause: A network configuration change intended to improve service performance inadvertently mislabeled a subset of Skype for Business infrastructure. As a result, a communication problem with the affected Skype for Business infrastructure and a subset of Exchange Online infrastructure was introduced that resulted in impact.
    Next update by: Monday, April 29, 2019, at 9:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Skype for BusinessAll FeaturesLY177449Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.18.04.2019 16:47:3520Title: Can't create Skype for Business meetings for Outlook events
    User Impact: Users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.
    More info: Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.
    As a workaround, users can use the Skype for Business Outlook client add-in to create invites with meetings.
    Current status: Whilst we're continuing to validate a fix for this issue we believe that the fix will be completely deployed by Friday, May 10, 2019, at 12:00 PM UTC
    Scope of impact: This issue could potentially affect any of your users if they are routed through the affected infrastructure.
    Start time: Monday, March 25, 2019, at 2:25 PM UTC
    Estimated time to resolve: We believe that the fix will be completely deployed by Friday, May 10, 2019, at 12:00 PM UTC.
    Next update by: Monday, April 22, 2019, at 9:00 PM UTC
    06.05.2019 23:10:002Sev225.03.2019 15:25:00Advisory8507806Incident
    Exchange OnlineE-Mail and calendar accessEX179059My Templates add in missingUsers may have been unable to see the My Templates add in for Outlook on the web or the desktop client.04.05.2019 02:41:024Title: My Templates add in missing
    User Impact: Users may be unable to see the My Templates add in for Outlook on the web or the desktop client.
    Current status: We've successfully refreshed the data in your environment and will be checking in with your representatives early next week to ensure that the remediation steps we've provided have resolved the problem.
    Scope of impact: Your organization is affected by this event, and any user using Outlook on the web or the desktop client may be impacted by this.
    Start time: Monday, April 29, 2019, at 11:00 PM UTC
    Root cause: A recent service update inadvertently caused impact to the My Templates feature.
    Next update by: Monday, May 6, 2019, at 8:00 PM UTC
    06.05.2019 06:59:422Sev230.04.2019 01:00:0005.05.2019 15:30:00Advisory18322638Incident
    Exchange OnlineE-Mail and calendar accessEX179059My Templates add in missingUsers may have been unable to see the My Templates add in for Outlook on the web or the desktop client.06.05.2019 06:57:042Title: My Templates add in missing
    User Impact: Users may have been unable to see the My Templates add in for Outlook on the web or the desktop client.
    Final status: We've verified that disabling the offending update and refreshing the data in all affected environments has resolved the underlying issue. We've determined that the following manual mitigation steps will be required from tenant admins to completely mitigate impact: 1) A tenant admin will need to navigate to the add-in management page in the Exchange admin center (EAC). Disabling and then re-enabling My Templates will bypass an 8-day cache expiration. 2) At this point, it will take up to 3 hours for the add-in to be available to end-users. During this time, some users will see the add-in before others. 3) After 3 hours, a user can restart the Outlook desktop client or refresh Outlook on the web to see My Templates. If a user doesn't restart the Outlook desktop client, they will see the add-in within 4 additional hours.
    Scope of impact: This issue may have potentially affected any of your users attempting to use the My Templates add in for Outlook on the web or the desktop client.
    Start time: Monday, April 29, 2019, at 11:00 PM UTC
    End time: Sunday, May 5, 2019, at 1:30 PM UTC
    Preliminary root cause: A recent service update inadvertently caused impact to the My Templates feature.
    Next steps: - We're reviewing our update procedures to better recognize similar issues during our development and testing cycles.
    This is the final update for the event.
    06.05.2019 06:59:422Sev230.04.2019 01:00:0005.05.2019 15:30:00Advisory18322638Incident
    Exchange OnlineE-Mail and calendar accessEX179059My Templates add in missingUsers may have been unable to see the My Templates add in for Outlook on the web or the desktop client.04.05.2019 00:59:104Title: My Templates add in missing
    User Impact: Users may be unable to see the My Templates add in for Outlook on the web or the desktop client.
    Current status: Our investigation shows that a recent service update inadvertently caused impact to the My Templates feature. We've disabled the recent service update and we're working to refresh the data in your environment. Once completed, we'll inform your organization and will require the following steps to propagate these changes more quickly in your environment: 1) Admins may need to force a server-side cache refresh by making a change to the organization-wide "My Templates" add-in configuration. Disabling and then re-enabling the add-in is a potential action to complete this process. 2) Affected users may need to refresh their web browser if using Outlook on the web or restart their Outlook client for the mitigation to take effect.
    Scope of impact: Your organization is affected by this event, and any user using Outlook on the web or the desktop client may be impacted by this.
    Start time: Monday, April 29, 2019, at 11:00 PM UTC
    Root cause: A code issue introduced in a recent service update resulted in users being unable to access or use the "My Templates" add-in.
    Next update by: Saturday, May 4, 2019, at 1:00 AM UTC
    06.05.2019 06:59:422Sev230.04.2019 01:00:0005.05.2019 15:30:00Advisory18322638Incident
    Office 365 PortalPortalMO178979Unable to access Microsoft 365 services or featuresUsers may have been unable to access Microsoft 365 services or features.04.05.2019 04:10:584A post-incident report has been published.04.05.2019 04:10:584https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='MO178979')Sev002.05.2019 22:34:0002.05.2019 23:10:00Incident21543325Incident
    Office 365 PortalPortalMO178979Unable to access Microsoft 365 services or featuresUsers may have been unable to access Microsoft 365 services or features.03.05.2019 00:17:015Title: Unable to access Microsoft 365 services or features
    User Impact: Users may have been unable to access Microsoft 365 services or features.
    More info: Affected services included SharePoint Online, OneDrive for Business, Microsoft Teams, Stream, Power BI, Planner, Forms, PowerApps, Dynamics 365, Intune, Azure Active Directory (AAD) and Office Licensing.
    Final status: We've monitored the environment and have confirmed that service has been restored.
    Scope of impact: This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 7:20 PM UTC
    End time: Thursday, May 2, 2019, at 9:10 PM UTC
    Preliminary root cause: A DNS configuration issue was preventing users from accessing multiple Microsoft 365 services.
    Next steps: - We're reviewing our DNS configuration update policies and procedures to better understand why this issue occurred and to prevent it from happening again.
    We'll publish a post-incident report within five business days.
    04.05.2019 04:10:584https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='MO178979')Sev002.05.2019 22:34:0002.05.2019 23:10:00Incident21543325Incident
    Office 365 PortalPortalMO178979Unable to access Microsoft 365 services or featuresUsers may have been unable to access Microsoft 365 services or features.02.05.2019 23:05:366Title: Unable to access Microsoft 365 services or features
    User Impact: Users may be unable to access Microsoft 365 services or features.
    More info: Affected services include SharePoint Online, OneDrive for Business, Microsoft Teams, Stream, Power BI, Planner, Forms, PowerApps, Dynamics 365, Intune, Skype for Business and Office Licensing.
    Current status: We've identified a potential Domain Name System (DNS) issue that could be contributing to the problem. We're working to develop an action plan to mitigate impact.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Next update by: Thursday, May 2, 2019, at 10:00 PM UTC
    04.05.2019 04:10:584https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='MO178979')Sev002.05.2019 22:34:0002.05.2019 23:10:00Incident21543325Incident
    Office 365 PortalPortalMO178979Unable to access Microsoft 365 services or featuresUsers may have been unable to access Microsoft 365 services or features.02.05.2019 23:27:476Title: Unable to access Microsoft 365 services or features
    User Impact: Users may be unable to access Microsoft 365 services or features.
    More info: Affected services include SharePoint Online, OneDrive for Business, Microsoft Teams, Stream, Power BI, Planner, Forms, PowerApps, Dynamics 365, Intune, Skype for Business and Office Licensing.
    Current status: We've identified and corrected a DNS configuration issue that prevented users from accessing Microsoft 365 services and features. We've observed an increase in successful connections and our telemetry indicates that all services are recovering. We're continuing to monitor the environment to validate that service has been restored.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 7:41 PM UTC
    Preliminary root cause: A DNS configuration issue is preventing users from accessing Microsoft 365 services and features. 
    Next update by: Thursday, May 2, 2019, at 10:30 PM UTC
    04.05.2019 04:10:584https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='MO178979')Sev002.05.2019 22:34:0002.05.2019 23:10:00Incident21543325Incident
    Office 365 PortalPortalMO178979Unable to access Microsoft 365 services or featuresUsers may have been unable to access Microsoft 365 services or features.02.05.2019 22:35:406Title: Unable to access Microsoft 365 services or features
    User Impact: Users may be unable to access Microsoft 365 services or features.
    Current status: We're investigating an issue in which users may be unable to access multiple Microsoft 365 services or features. We're analyzing system logs in an effort to understand the problem and determine the next troubleshooting steps.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Next update by: Thursday, May 2, 2019, at 9:30 PM UTC
    04.05.2019 04:10:584https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='MO178979')Sev002.05.2019 22:34:0002.05.2019 23:10:00Incident21543325Incident
    OneDrive for BusinessOneDrive for BusinessOD178975Delays or problems loading OneDrive contentUsers may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.04.05.2019 04:10:324A post-incident report has been published.04.05.2019 04:10:324https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178975')Sev002.05.2019 22:04:3902.05.2019 23:10:00Incident6748785Incident
    OneDrive for BusinessOneDrive for BusinessOD178975Delays or problems loading OneDrive contentUsers may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.02.05.2019 23:31:465Title: Delays or problems loading OneDrive content
    User Impact: Users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
    Current status: We've identified and corrected a DNS configuration issue that prevented users from accessing OneDrive for Business content. We've observed an increase in successful connections and our telemetry indicates that all services are recovering. We're continuing to monitor the environment to validate that service has been restored.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 7:41 PM UTC
    Preliminary root cause: A DNS configuration issue is preventing users from accessing OneDrive for Business content.
    Next update by: Thursday, May 2, 2019, at 10:30 PM UTC
    04.05.2019 04:10:324https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178975')Sev002.05.2019 22:04:3902.05.2019 23:10:00Incident6748785Incident
    OneDrive for BusinessOneDrive for BusinessOD178975Delays or problems loading OneDrive contentUsers may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.02.05.2019 23:04:026Title: Delays or problems loading OneDrive content
    User Impact: Users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
    Current status: We've identified a potential Domain Name System (DNS) issue that could be contributing to the problem. We're working to develop an action plan to mitigate impact.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Next update by: Thursday, May 2, 2019, at 10:00 PM UTC
    04.05.2019 04:10:324https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178975')Sev002.05.2019 22:04:3902.05.2019 23:10:00Incident6748785Incident
    OneDrive for BusinessOneDrive for BusinessOD178975Delays or problems loading OneDrive contentUsers may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.02.05.2019 22:06:146Title: Delays or problems loading OneDrive content
    User Impact: Users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
    Current status: We're analyzing system logs in an effort to understand the problem and determine the next troubleshooting steps.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Next update by: Thursday, May 2, 2019, at 9:00 PM UTC
    04.05.2019 04:10:324https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178975')Sev002.05.2019 22:04:3902.05.2019 23:10:00Incident6748785Incident
    OneDrive for BusinessOneDrive for BusinessOD178975Delays or problems loading OneDrive contentUsers may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.02.05.2019 23:55:595Title: Delays or problems loading OneDrive content
    User Impact: Users may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.
    Final status: We've monitored the environment and have confirmed that service has been restored.
    Scope of impact: This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 7:20 PM UTC
    End time: Thursday, May 2, 2019, at 9:10 PM UTC
    Preliminary root cause: A DNS configuration issue was preventing users from accessing OneDrive content.
    Next steps: - We're reviewing our DNS configuration update policies and procedures to better understand why this issue occurred and to prevent it from happening again.
    We'll publish a post-incident report within five business days.
    04.05.2019 04:10:324https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='OD178975')Sev002.05.2019 22:04:3902.05.2019 23:10:00Incident6748785Incident
    SharePoint OnlineSharePoint FeaturesSP178746Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.04.05.2019 04:09:564A post-incident report has been published.04.05.2019 04:09:564https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178746')Sev002.05.2019 21:41:5102.05.2019 23:10:00Incident13019533Incident
    SharePoint OnlineSharePoint FeaturesSP178746Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.02.05.2019 22:04:286Title: Delays or problems loading SharePoint Online sites
    User Impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites.
    Current status: We're analyzing system logs in an effort to understand the problem and determine the next troubleshooting steps.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Next update by: Thursday, May 2, 2019, at 9:00 PM UTC
    04.05.2019 04:09:564https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178746')Sev002.05.2019 21:41:5102.05.2019 23:10:00Incident13019533Incident
    SharePoint OnlineSharePoint FeaturesSP178746Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.02.05.2019 23:54:345Title: Delays or problems loading SharePoint Online sites
    User Impact: Users may have experienced intermittent delays or navigation errors when accessing SharePoint sites.
    Final status: We've monitored the environment and have confirmed that service has been restored.
    Scope of impact: This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 7:20 PM UTC
    End time: Thursday, May 2, 2019, at 9:10 PM UTC
    Preliminary root cause: A DNS configuration issue was preventing users from accessing SharePoint Online sites.
    Next steps: - We're reviewing our DNS configuration update policies and procedures to better understand why this issue occurred and to prevent it from happening again.
    We'll publish a post-incident report within five business days.
    04.05.2019 04:09:564https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178746')Sev002.05.2019 21:41:5102.05.2019 23:10:00Incident13019533Incident
    SharePoint OnlineSharePoint FeaturesSP178746Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.02.05.2019 21:41:576Title: Delays or problems loading SharePoint Online sites
    User impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites.
    Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.
    04.05.2019 04:09:564https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178746')Sev002.05.2019 21:41:5102.05.2019 23:10:00Incident13019533Incident
    SharePoint OnlineSharePoint FeaturesSP178746Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.02.05.2019 23:02:206Title: Delays or problems loading SharePoint Online sites
    User Impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites.
    Current status: We've identified a potential Domain Name System (DNS) issue that could be contributing to the problem. We're working to develop an action plan to mitigate impact.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Next update by: Thursday, May 2, 2019, at 10:00 PM UTC
    04.05.2019 04:09:564https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178746')Sev002.05.2019 21:41:5102.05.2019 23:10:00Incident13019533Incident
    SharePoint OnlineSharePoint FeaturesSP178746Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.02.05.2019 23:31:075Title: Delays or problems loading SharePoint Online sites
    User Impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites.
    Current status: We've identified and corrected a DNS configuration issue that prevented users from accessing SharePoint Online sites. We've observed an increase in successful connections and our telemetry indicates that all services are recovering. We're continuing to monitor the environment to validate that service has been restored.
    Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 7:41 PM UTC
    Preliminary root cause: A DNS configuration issue is preventing users from accessing SharePoint Online sites.
    Next update by: Thursday, May 2, 2019, at 10:30 PM UTC
    04.05.2019 04:09:564https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='SP178746')Sev002.05.2019 21:41:5102.05.2019 23:10:00Incident13019533Incident
    SharePoint OnlineSharePoint FeaturesSP178789Delays or problems loading SharePoint Online sites or OneDrive for BusinessUsers may experience intermittent delays or navigation errors when accessing SharePoint sites or OneDrive content.02.05.2019 22:24:176Title: Delays or problems loading SharePoint Online sites or OneDrive for Business
    User Impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites or OneDrive content.
    Final status: The investigation is complete and we've determined the service is healthy. A service incident did not actually occur.
    02.05.2019 22:24:176Sev202.05.2019 21:46:5802.05.2019 22:24:15Advisory79704Incident
    SharePoint OnlineSharePoint FeaturesSP178789Delays or problems loading SharePoint Online sites or OneDrive for BusinessUsers may experience intermittent delays or navigation errors when accessing SharePoint sites or OneDrive content.02.05.2019 21:47:026Title: Delays or problems loading SharePoint Online sites or OneDrive for Business
    User impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites or OneDrive content.
    Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.
    02.05.2019 22:24:176Sev202.05.2019 21:46:5802.05.2019 22:24:15Advisory79704Incident
    Yammer EnterpriseYammer ComponentsYA178707Can't load feedsUsers may have experienced intermittent failures when attempting to load feeds in the Yammer service.02.05.2019 06:24:486Title: Can't load feeds
    User Impact: Users may experience intermittent failures when attempting to load feeds in the Yammer service.
    Current status: We've determined that resources within a subset of infrastructure has been exceeded which has resulted in the service performing below expected thresholds. We're working to re-direct traffic to an alternate portion of infrastructure in an attempt to remediate this issue.
    Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 3:05 AM UTC
    Next update by: Thursday, May 2, 2019, at 5:30 AM UTC
    02.05.2019 07:10:436Sev202.05.2019 05:05:0002.05.2019 06:15:00Advisory4074204Incident
    Yammer EnterpriseYammer ComponentsYA178707Can't load feedsUsers may have experienced intermittent failures when attempting to load feeds in the Yammer service.02.05.2019 06:10:336Title: Can't load feeds
    User Impact: Users may experience intermittent failures when attempting to load feeds in the Yammer service.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    Start time: Thursday, May 2, 2019, at 3:05 AM UTC
    02.05.2019 07:10:436Sev202.05.2019 05:05:0002.05.2019 06:15:00Advisory4074204Incident
    Yammer EnterpriseYammer ComponentsYA178707Can't load feedsUsers may have experienced intermittent failures when attempting to load feeds in the Yammer service.02.05.2019 06:49:146Title: Can't load feeds
    User Impact: Users may have experienced intermittent failures when attempting to load feeds in the Yammer service.
    Final status: We've confirmed that re-directing traffic to an alternate portion of infrastructure has fully remediated this issue.
    Scope of impact: Impact was specific to a subset of users who were served through the affected infrastructure.
    Start time: Thursday, May 2, 2019, at 3:05 AM UTC
    End time: Thursday, May 2, 2019, at 4:15 AM UTC
    Root cause: Traffic loads unexpectedly exceeded available resources within a subset of infrastructure which resulted in the service performing below expected thresholds.
    Next steps: - We're reviewing our monitoring services to look for ways to reduce detection time and more quickly restore service. - We're analyzing performance data and trends on the affected systems to identify ways to ensure resources remain adequate according to traffic load in order to prevent this problem from happening again.
    This is the final update for the event.
    02.05.2019 07:10:436Sev202.05.2019 05:05:0002.05.2019 06:15:00Advisory4074204Incident
    Skype for BusinessAudio and VideoLY178266Can't add Skype contactsUsers were unable to add federated Skype contacts.24.04.2019 21:55:0314Title: Can't add Skype contacts
    User Impact: Users are unable to add federated Skype contacts.
    Current status: We've identified that the service is not properly sending invites to the Skype users. We're working to identify what is causing the invite delivery to fail. 
    Scope of impact: All Skype for Business users who are enabled for Skype federation may be affected. 
    Next update by: Thursday, April 25, 2019, at 10:00 AM UTC
    26.04.2019 18:13:4812Sev218.03.2019 13:25:0025.04.2019 21:05:00Advisory8507806Incident
    Skype for BusinessAudio and VideoLY178266Can't add Skype contactsUsers were unable to add federated Skype contacts.24.04.2019 20:21:4014Title: Can't add Skype contacts
    User Impact: Users are unable to add federated Skype contacts.
    Current status: We're reviewing available support case data while we review related incidents to determine our next troubleshooting steps.
    Scope of impact: All Skype for Business users who are enabled for Skype federation may be affected. 
    Next update by: Wednesday, April 24, 2019, at 8:30 PM UTC
    26.04.2019 18:13:4812Sev218.03.2019 13:25:0025.04.2019 21:05:00Advisory8507806Incident
    Skype for BusinessAudio and VideoLY178266Can't add Skype contactsUsers were unable to add federated Skype contacts.25.04.2019 10:43:1113Title: Can't add Skype contacts
    User Impact: Users are unable to add federated Skype contacts.
    Current status: We've identified that there are two issues manifesting in the same impact. One scenario where the client receives the federated invite but it does not appear, and the other scenario where the chat service does not send the invite. We've reproduced the issue in a test environment to gather detailed client logs and are reviewing the logs to formulate a remediation plan.
    Scope of impact: All Skype for Business users who are enabled for Skype federation may be affected.
    Next update by: Friday, April 26, 2019, at 10:00 AM UTC
    26.04.2019 18:13:4812Sev218.03.2019 13:25:0025.04.2019 21:05:00Advisory8507806Incident
    Skype for BusinessAudio and VideoLY178266Can't add Skype contactsUsers were unable to add federated Skype contacts.26.04.2019 17:55:1112Title: Can't add Skype contacts
    User Impact: Users were unable to add federated Skype contacts.
    Final status: We've determined that a recent change intended to filter conversations without timestamps resulted in contact invites being filtered out as well. We've reverted the affecting change and confirmed that contact invites send as expected and impact is remediated.
    Scope of impact: All Skype for Business users who were enabled for Skype federation may have been affected.
    Start time: Monday, March 12, 2019, at 10:18 PM UTC
    End time: Thursday, April 25, 2019, at 7:05 PM UTC
    Root cause: A recent change intended to filter conversations without timestamps resulted in contact invites being filtered out as well.
    Next steps: - We're working to modify and validate the previous change before re-deploying to prevent impact from reoccurring.
    This is the final update for the event.
    26.04.2019 18:13:4812Sev218.03.2019 13:25:0025.04.2019 21:05:00Advisory8507806Incident
    Skype for BusinessAudio and VideoLY178266Can't add Skype contactsUsers were unable to add federated Skype contacts.26.04.2019 11:09:4212Title: Can't add Skype contacts
    User Impact: Users are unable to add federated Skype contacts.
    Current status: We've enabled a change, which will render the invite notifications within an hour. We're developing a full remediation plan to allow invite notifications to render instantly.
    Scope of impact: All Skype for Business users who are enabled for Skype federation may be affected.
    Next update by: Friday, April 26, 2019, at 5:00 PM UTC
    26.04.2019 18:13:4812Sev218.03.2019 13:25:0025.04.2019 21:05:00Advisory8507806Incident
    Skype for BusinessAudio and VideoLY178266Can't add Skype contactsUsers were unable to add federated Skype contacts.24.04.2019 19:58:0914Title: Can't add Skype contacts
    User Impact: Users are unable to add federated Skype contacts.
    Current status: We're investigating a potential issue with the Skype for Business service. We'll provide an update within 30 minutes.
    Scope of impact: All Skype for Business users who are enabled for Skype federation may be affected.
    26.04.2019 18:13:4812Sev218.03.2019 13:25:0025.04.2019 21:05:00Advisory8507806Incident
    Office 365 PortalAdministrationMO178227Usage report content delaysAdmins may have noticed that some usage reports were only showing data prior to April 17, 2019.26.04.2019 05:25:1112Title: Usage report content delays
    User Impact: Admins may have noticed that some usage reports were only showing data prior to April 17, 2019.
    More info: The impacted reports may have included Exchange Online usage reports and OneDrive for Business activity reports.
    Final status: We've confirmed that the backlog has processed and that the issue has been remediated.
    Scope of impact: This issue may have impacted any admin attempting to view the affected reporting data.
    Start time: Saturday, April 20, 2019, at 10:00 PM UTC
    End time: Thursday, April 25, 2019, at 11:56 PM UTC
    Root cause: An unexpected delay occurred during source data transmission, which resulted in a backlog of data and subsequent impact to report freshness.
    Next steps: - We're working to identify what caused the delay during source data transmission to avoid similar impact in the future.
    This is the final update for the event.
    26.04.2019 05:35:5612Sev221.04.2019 00:00:0026.04.2019 01:56:00Advisory21537464Incident
    Office 365 PortalAdministrationMO178227Usage report content delaysAdmins may have noticed that some usage reports were only showing data prior to April 17, 2019.25.04.2019 05:35:1013Title: Usage report content delays
    User Impact: Admins may notice that some usage reports only show data prior to April 17, 2019.
    More info: The impacted reports may include Exchange Online usage reports and OneDrive for Business activity reports.
    Current status: We're continuing to process the backlog, which is taking longer than expected. We're working to identify solutions to expedite the process and we'll provide an estimated timeline as soon as one is available.
    Scope of impact: This issue may impact any admin attempting to view the affected reporting data.
    Start time: Saturday, April 20, 2019, at 10:00 PM UTC
    Preliminary root cause: An unexpected delay occurred during source data transmission, which has resulted in a backlog of data and subsequent impact to report freshness.
    Next update by: Friday, April 26, 2019, at 5:00 AM UTC
    26.04.2019 05:35:5612Sev221.04.2019 00:00:0026.04.2019 01:56:00Advisory21537464Incident
    Office 365 PortalAdministrationMO178227Usage report content delaysAdmins may have noticed that some usage reports were only showing data prior to April 17, 2019.24.04.2019 05:22:3914Title: Usage report content delays
    User Impact: Admins may notice that some usage reports only show data prior to April 17, 2019.
    More info: The impacted reports may include Exchange Online usage reports and OneDrive for Business activity reports.
    Current status: We've received reports of an issue in which admins may be unable to view some usage report data on or after April 17, 2019. Our investigation has determined that an unexpected delay occurred during the source data transmission, which resulted in a backlog and subsequent impact to report freshness. We've confirmed that the source data stream is no longer experiencing delays and we're currently working to process the backlog to resolve the issue.
    Scope of impact: This issue may impact any admin attempting to view the affected reporting data.
    Start time: Saturday, April 20, 2019, at 10:00 PM UTC
    Preliminary root cause: An unexpected delay occurred during the source data transmission process, which has resulted in a backlog of data.
    Next update by: Thursday, April 25, 2019, at 5:00 AM UTC
    26.04.2019 05:35:5612Sev221.04.2019 00:00:0026.04.2019 01:56:00Advisory21537464Incident
    Office 365 PortalAdministrationMO178238Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.24.04.2019 08:11:5314Title: Can't edit group properties
    User Impact: Admins may be unable to edit group properties using the Microsoft 365 admin center.
    More info: Admins may notice that group property information may appear to be blank. While we're focused on resolving the issue, admins can utilize the Exchange admin center or Remote PowerShell to edit the property settings.
    Current status: We're reviewing network traces gathered from your organization to determine the source of the issue.
    Scope of impact: Your organization is affected by this event, and this issue could affect any of your admins that are attempting to edit group properties.
    Next update by: Wednesday, April 24, 2019, at 8:30 AM UTC
    26.04.2019 03:46:1812Sev222.04.2019 04:57:0026.04.2019 01:40:00Advisory21506665Incident
    Office 365 PortalAdministrationMO178238Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.25.04.2019 05:18:2813Title: Can't edit group properties
    User Impact: Admins may be unable to edit group properties using the Microsoft 365 admin center.
    More info: Admins may notice that group property information may appear blank. While we're focused on resolving the issue, admins can use the Exchange admin center or Remote PowerShell to edit the property settings.
    Current status: We developed a fix and have determined that it resolves the problem. We have started to deploy the fix; however, we have identified an issue that is delaying the deployment process. We're working to address the delay and any other unforeseen issues affecting the deployment.
    Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure.
    Root cause: A code regression within the infrastructure resulted in a missing configuration within the admin centre URL, which caused impact.
    Next update by: Friday, April 26, 2019, at 5:00 AM UTC
    26.04.2019 03:46:1812Sev222.04.2019 04:57:0026.04.2019 01:40:00Advisory21506665Incident
    Office 365 PortalAdministrationMO178238Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.24.04.2019 11:03:2114Title: Can't edit group properties
    User Impact: Admins may be unable to edit group properties using the Microsoft 365 admin center.
    More info: Admins may notice that group property information may appear blank. While we're focused on resolving the issue, admins can use the Exchange admin center or Remote PowerShell to edit the property settings.
    Current status: We’ve determined that a code regression within the infrastructure resulted in a missing configuration within the admin centre URL, which caused impact. We’re developing a fix to update the configuration, which will be tested and deployed to the affected environment to mitigate impact. Once the fix is developed and tested, deployment will take approximately 3 hours to complete.
    Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure.
    Root cause: A code regression within the infrastructure resulted in a missing configuration within the admin centre URL, which caused impact.
    Next update by: Thursday, April 25, 2019, at 5:00 AM UTC
    26.04.2019 03:46:1812Sev222.04.2019 04:57:0026.04.2019 01:40:00Advisory21506665Incident
    Office 365 PortalAdministrationMO178238Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.24.04.2019 09:25:3214Title: Can't edit group properties
    User Impact: Admins may be unable to edit group properties using the Microsoft 365 admin center.
    More info: Admins may notice that group property information may appear to be blank. While we're focused on resolving the issue, admins can utilize the Exchange admin center or Remote PowerShell to edit the property settings.
    Current status: We're continuing to review network trace logs and system health information to determine the next troubleshooting steps.
    Scope of impact: Your organization is affected by this event, and this issue could affect any of your admins that are attempting to edit group properties.
    Next update by: Wednesday, April 24, 2019, at 9:30 AM UTC
    26.04.2019 03:46:1812Sev222.04.2019 04:57:0026.04.2019 01:40:00Advisory21506665Incident
    Office 365 PortalAdministrationMO178238Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.26.04.2019 03:29:4612Title: Can't edit group properties
    User Impact: Admins may be unable to edit group properties using the Microsoft 365 admin center.
    More info: Admins may notice that group property information may appear blank. While we're focused on resolving the issue, admins can use the Exchange admin center or Remote PowerShell to edit the property settings.
    Final status: The deployment of the fix has completed and our testing indicates that the ability to edit group properties using the Microsoft 365 admin center has been restored. Once you've validated that the issue has been resolved, please contact support to provide confirmation that the issue has been resolved.
    Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure.
    Start time: Monday, April 22, 2019, at 2:57 AM UTC
    End time: Thursday, April 25, 2019, at 11:40 PM UTC
    Root cause: A code regression within the infrastructure resulted in a missing configuration within the admin center URL, that resulted in the inability to edit group properties.
    Next steps: - We're reviewing our update procedures to better identify potential code regression issues during our development and testing cycles.
    This is the final update for the event.
    26.04.2019 03:46:1812Sev222.04.2019 04:57:0026.04.2019 01:40:00Advisory21506665Incident
    Exchange OnlineE-Mail timely deliveryEX178295Can't access emailN/A25.04.2019 01:34:3113We've identified a potential issue impacting availability of the Exchange Online service. We're reviewing diagnostic and telemetry data to isolate the cause of the problem. We'll provide an update within 60 minutes.25.04.2019 09:13:1113Sev225.04.2019 01:34:2925.04.2019 09:12:58Advisory17982048Incident
    Exchange OnlineE-Mail timely deliveryEX178295Can't access emailN/A25.04.2019 09:13:1113Title: Can't access email
    User Impact: N/A
    Final status: The investigation is complete and we've determined the service is healthy. A service incident did not actually occur.
    25.04.2019 09:13:1113Sev225.04.2019 01:34:2925.04.2019 09:12:58Advisory17982048Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.03.04.2019 19:18:1635Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: The deployment of the fix has reached approximately 98% of the impacted environments at this time. We're continuing to monitor the progress of the deployment. Additionally, we're reaching out to affected users to confirm that they're experiencing resolution as a result of the deployed fix.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Root cause: A subset of networking infrastructure responsible for processing the trace details is performing in a degraded state.
    Next update by: Wednesday, April 3, 2019, at 10:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.04.04.2019 20:32:4534Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: While our additional code fix has resulted in improvements to denied write requests, it’s been unsuccessful in fully processing the backlogged requests. We’ve developed an additional solution that we’re currently testing in a limited environment. Once we confirm that this solution effectively improves backlog processing, we’ll deploy it to all affected environments.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing the trace details is performing in a degraded state.
    Next update by: Friday, April 5, 2019, at 3:00 AM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.05.04.2019 04:11:5233Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Additionally, admins may also experience similar impact to some reporting and logging features within the Security and Compliance Center (SCC).
    Current status: We've confirmed that the solution is improving backlog processing and we're deploying it throughout the affected infrastructure. Although we expect that this solution will expedite the process, we're evaluating additional optimizations which will be implemented as soon as validation has completed.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Friday, April 5, 2019, at 7:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.02.04.2019 16:56:4736Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.05.04.2019 20:24:2033Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Additionally, any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well.
    Current status: The deployment of the additional solution is still ongoing and based on our initial monitoring, some users may see improvements in service performance. We're reviewing monitoring data as the solution saturates to validate service health improvements and that backlogging performance improvement continues.
    Scope of impact: Any admin may also be unable to view message trace details or access reports and logs within the SCC.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Saturday, April 6, 2019, at 3:00 AM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.03.04.2019 22:40:2235Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: Deployment of the fix is nearing completion with a small subset of infrastructure remaining. We're continuing to monitor the deployment until it reaches full saturation.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing the trace details is performing in a degraded state.
    Next update by: Thursday, April 4, 2019, at 3:00 AM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.11.04.2019 23:22:0727Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: This is an incremental update to provide the latest status on the issue.
    Current status: The backlog has been processed for April 3 and we've processed 65 percent of the backlog for April 4. We anticipate that the entirety of the backlog through April 7, 2019, will be fully processed by Monday, April 15, 2019. For complete details on this event, please reference the post from 6:03 PM UTC on April 9, 2019.
    Next update by: Friday, April 12, 2019, at 7:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.12.04.2019 20:55:2026Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.
    While we continue to work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as an historical message trace) as a workaround. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We've confirmed that 75 percent of the backlog from April 4, 2019 has processed. We're exploring quicker methods to increase the processing rate of the remaining backlogs in an effort to expedite complete resolution of this problem. We anticipate we will have a more detailed timeline to resolution by tomorrow, April 13, 2019. 
    Scope of impact: Any admin may be unable to view message trace details or access reports and logs within the SCC.
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Saturday, April 13, 2019, at 7:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.03.04.2019 02:45:4935Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: Our actions to rebalance the resources proved to be an insufficient solution for this problem; however, we've determined the service that helps facilitate message trace details isn't functioning as expected. We've developed a fix and verified that it'll resolve the issue. We're in the process of deploying the fix to a subset of infrastructure to validate that this will resolve the issue. Upon validation, we'll proceed with deployment to the rest of the impacted environments.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Root cause: A subset of networking infrastructure responsible for processing the trace details is performing in a degraded state.
    Next update by: Wednesday, April 3, 2019, at 6:30 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.15.04.2019 19:18:3923Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.
    While we continue to work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as an historical message trace) as a workaround. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: The backlog between April 4 and April 7, 2019, has been processed. We're conducting our final validation steps to ensure that service has been fully restored.
    Scope of impact: Any admin may be unable to view message trace details or access reports and logs within the SCC.
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Tuesday, April 16, 2019, at 12:00 AM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.13.04.2019 20:27:1625Title: Can't see message traces
    User impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.
    While we continue to work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as an historical message trace) as a workaround. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We've confirmed that 85 percent of the remaining backlogs, which contains message trace details from April 4 through April 7, 2019, has processed. Based on current progress, we anticipate that the backlogs will process and the issue will be resolved by Monday, April 15, 2019. While we monitor, we're continuing to evaluate whether any actions can be taken to expedite resolution.
    Scope of impact: Any admin may be unable to view message trace details or access reports and logs within the SCC.
    Estimated time to resolve: Based on current progress, we expect the issue to be fully resolved by Monday, April 15, 2019.
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Monday, April 15, 2019, at 7:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.02.04.2019 19:36:1336Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: We're attempting to reproduce this issue internally to gather additional data to analyze.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Next update by: Tuesday, April 2, 2019, at 7:30 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.02.04.2019 17:28:4736Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: We're analyzing system logs to determine the source of the issue.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Next update by: Tuesday, April 2, 2019, at 5:30 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.02.04.2019 23:31:5835Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: We're continuing to rebalance resources in the environment. We'll validate internally that this action successfully mitigates impact once complete.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Root cause: A subset of networking infrastructure responsible for processing the trace details is performing in a degraded state.
    Next update by: Wednesday, April 3, 2019, at 2:00 AM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.02.04.2019 21:31:5136Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: Our analysis shows that a subset of networking infrastructure responsible for processing the trace details is performing in a degraded state. We're working to rebalance resources to mitigate impact. Once complete, we'll conduct an internal test to confirm that service is restored.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Root cause: A subset of networking infrastructure responsible for processing the trace details is performing in a degraded state.
    Next update by: Tuesday, April 2, 2019, at 9:30 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.09.04.2019 20:03:3729Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.
    Current status: The deployment of the solution has fully saturated, and the underlying problem has been fixed. We're still processing a backlog of message traces from April 3, 2019 and April 4, 2019. The backlog of traces from April 3 are expected to be processed by end of day April 9, 2019. Due to the size of the backlog and processing rate, we anticipate that traces from April 4 will be fully processed by the end of the week. 
    Scope of impact: Any admin may also be unable to view message trace details or access reports and logs within the SCC.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Wednesday, April 10, 2019, at 5:00 AM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.08.04.2019 19:29:1330Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.
    Current status: The initial restoration of the backlogs were incomplete, and the process had to be restarted. The backlog for all message trace details through Tuesday, April 2, 2019, have been processed, and the backlog for April 3 and 4 are currently being processed. Additionally, we're continuing to monitor deployment of the fix. We have no ETA at this time. 
    Scope of impact: Any admin may also be unable to view message trace details or access reports and logs within the SCC.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Tuesday, April 9, 2019, at 6:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.10.04.2019 19:09:0828Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: This is an incremental update to provide the latest status on the issue.
    Current status: We've completed processing the remaining 10% of message traces from April 3, 2019 and have begun processing the backlog of message traces from April 4, 2019. We've processed 35% of message traces from April 4, 2019, and expect backlogs to be fully processed by the end of the week. For complete details on this event, please reference the post from 6:03 PM UTC on April 9, 2019.
    Next update by: Friday, April 12, 2019, at 7:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.10.04.2019 05:14:4828Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: This is an incremental update to provide the latest status on the issue.
    Current status: We're continuing to process the remaining 10% of message traces from April 3, 2019 and will begin processing the backlog of message traces from April 4, 2019 after the remaining message traces from April 3rd are processed. We still expect backlogs from April 4th to be fully processed by the end of the week. For complete details on this event, please reference the post from 6:03 PM UTC on April 9, 2019.
    Next update by: Wednesday, April 10, 2019, at 7:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.16.04.2019 17:25:3822Title: Can't see message traces
    User Impact: Admins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may have been impacted by this event as well; however, we extended the quarantine message expiration time during the impact period to ensure all impacted logs were processed before the expiration time.
    While we worked to resolve the issue with real time message trace, admins could have used the extended message trace option (also known as an historical message trace) as a workaround. This provides full trace details in a downloadable CSV file format, and was not impacted by this incident.
    Final status: We've completed our validation activity and have confirmed that service has been restored. Additionally, the backlog between April 3 and April 7, 2019, has been processed.
    Scope of impact: Any admin may have been unable to view message trace details or access reports and logs within the SCC.
    Start time: Monday, April 1, 2019, at 10:50 PM UTC
    End time: Tuesday, April 16, 2019, at 6:22 AM UTC
    Preliminary root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features was performing in a degraded state, preventing message traces from being viewed. Subsequently, a large number of requests were backlogged and required an extended time to process.
    Next steps: - We're analyzing performance data and trends on the affected systems to better understand the degradation that occurred and problem from happening again.
    We'll publish a post-incident report within five business days.
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.16.04.2019 01:50:0722Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.
    While we continue to work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as an historical message trace) as a workaround. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We're performing an extended validation of the processed data to confirm that the issue is resolved.
    Scope of impact: Any admin may be unable to view message trace details or access reports and logs within the SCC.
    Preliminary root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Tuesday, April 16, 2019, at 9:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.06.04.2019 03:58:0432Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    More info: Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.
    Current status: We're continuing to monitor the deployment of the additional solution as it saturates the environment as expected and we're also monitoring the processing of the backlog to ensure all logs impacted by this event are being processed. Additionally, we're continuing to explore additional mitigation options to ensure similar impact is avoided in the future.
    Scope of impact: Any admin may also be unable to view message trace details or access reports and logs within the SCC.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.
    Next update by: Monday, April 8, 2019, at 6:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.24.04.2019 12:08:0714A post-incident report has been published.24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX176985Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.04.04.2019 03:39:4734Title: Can't see message traces
    User Impact: Admins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.
    Current status: Our initial fix has been successfully deployed to the impacted infrastructure; however, a different code issue is causing write requests to the affected servers to be inadvertently denied. We've developed a new fix and are deploying it to address the underlying issue and mitigate impact to message traces. We expect the fix to take a few hours to deploy and the backlog of the message trace requests to be drained on Thursday. April 4th, 2019 by 8:00 PM UTC.
    Scope of impact: Any admin could experience this issue if they are attempting to view message trace details.
    Start time: Monday, April 1, 2019, at 7:27 PM UTC
    Root cause: A subset of networking infrastructure responsible for processing the trace details is performing in a degraded state.
    Next update by: Thursday, April 4, 2019, at 8:00 PM UTC
    24.04.2019 12:08:0714https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='EX176985')Sev201.04.2019 21:27:0016.04.2019 08:22:00Advisory18083178Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.21.04.2019 20:30:0417Title: Can't view message traces
    User Impact: Admins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.
    More info: While we work to confirm that this issue has been resolved, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We've verified that the message trace backlog we had identified within our service has been processed, and we're requesting admins that had reported this problem confirm the issue is fully resolved.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Preliminary root cause: A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog.
    Next update by: Monday, April 22, 2019, at 8:00 PM UTC
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.19.04.2019 20:25:5219Title: Can't view message traces
    User Impact: Admins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.
    More info: While we work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We're continuing to monitor the progress of the backlog as it processes. We suspect this will take some additional time to reach mitigation.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Root cause: A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog.
    Next update by: Sunday, April 21, 2019, at 8:00 PM UTC
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.22.04.2019 22:07:4716Title: Can't view message traces
    User Impact: Admins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.
    More info: While we work to confirm that this issue has been resolved, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We've identified a potential configuration issue that may be contributing to remaining impact. We're working to confirm our findings and identify the most expedient means to fully resolve the problem.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Preliminary root cause: A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog.
    Next update by: Tuesday, April 23, 2019, at 12:00 AM UTC
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.23.04.2019 22:31:3915Title: Can't view message traces
    User Impact: Admins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.
    More info: Admins may have used the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and was not impacted by this incident.
    Final status: We've completed our initial monitoring and have determined that the issue is resolved.
    Scope of impact: Impact was specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    End time: Saturday, April 20, 2019, at 7:00 PM UTC
    Root cause: A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog. An additional subset of the environment was also affected by an unexpected source of high traffic, which further exacerbated the backlog for some admins.
    Next steps: - We're continuing to monitor the service environment to prevent further issues of this nature.
    This is the final update for the event.
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.23.04.2019 00:37:4015Title: Can't view message traces
    User Impact: Admins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.
    More info: While we work to confirm that the remainder of impact is mitigated, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We’ve confirmed that a configuration issue is not the cause of the additionally reported impact; though, we’ve isolated a source of high traffic directed to the environment that’s causing the additional message trace search latency for some admins. We’ve rebalanced traffic to account for the increased load and will continue monitoring the service to ensure this fully resolves the problem.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Estimated time to resolve: Based on current recovery progress, we estimate that the remaining message trace search latency should be resolved within the next 24 hours.
    Preliminary root cause: A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog. An additional subset of the environment was also affected by an unexpected source of high traffic, which further exacerbated the backlog for some admins.
    Next update by: Tuesday, April 23, 2019, at 10:00 PM UTC
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.18.04.2019 01:00:0120Title: Can't run message traces
    User Impact: Admins may be unable to run message traces.
    More info: This issue occurs when using third-party apps, the Exchange admin center (EAC), and PowerShell.
    Current status: We're gathering system diagnostic and tenant database information to determine the underlying cause of the issue.
    Scope of impact: Your organization is affected by this event, and any admin may be impacted.
    Next update by: Thursday, April 18, 2019, at 7:00 PM UTC
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.18.04.2019 00:22:3520Title: Can't run message traces
    User Impact: Admins may be unable to run message traces.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    Scope of impact: Your organization is affected by this event, and any admin may be impacted.
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineManagement and ProvisioningEX177902Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.18.04.2019 21:16:4820Title: Can't view message traces
    User Impact: Admins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.
    More info: While we work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.
    Current status: We've determined that a temporary problem occurred on a portion of infrastructure that generates message trace data, which created a message trace backlog. The backlog of messages traces are processing and we're monitoring the process to ensure it completes as expected.
    Scope of impact: Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.
    Start time: Monday, April 15, 2019, at 5:00 PM UTC
    Preliminary root cause: A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog.
    Next update by: Friday, April 19, 2019, at 7:00 PM UTC
    23.04.2019 22:31:3915Sev215.04.2019 19:00:0020.04.2019 21:00:00Advisory18158962Incident
    Exchange OnlineE-Mail timely deliveryEX177852Unable to send email due to SPFUsers may have been intermittently unable to send email to some domains.17.04.2019 02:08:5221Title: Unable to send email due to SPF
    User Impact: Users may be intermittently unable to send email to some domains.
    More info: Users may receive an Non-Delivery Report (NDR): "550 5.7.23 The message was rejected because of Sender Policy Framework violation."
    Current status: We received reports indicating an issue in which users were unable to send email to some domains and were receiving a Sender Policy Framework (SPF) validation error. We determined that a recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range. We reverted the optimization and are monitoring the service to confirm that the issue is resolved.
    Scope of impact: Impact is specific to users routed through a specific IPv6 range, therefore we expect that a subset of your users would be impacted but this issue.
    Preliminary root cause: A recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range.
    Next update by: Wednesday, April 17, 2019, at 2:00 AM UTC
    17.04.2019 18:17:0521Sev216.04.2019 22:00:0017.04.2019 01:25:00Incident18083178Incident
    Exchange OnlineE-Mail timely deliveryEX177852Unable to send email due to SPFUsers may have been intermittently unable to send email to some domains.17.04.2019 03:53:2921Title: Unable to send email due to SPF
    User Impact: Users may be intermittently unable to send email to some domains.
    More info: Users may receive an Non-Delivery Report (NDR): "550 5.7.23 The message was rejected because of Sender Policy Framework violation."
    Current status: Our initial monitoring and testing indicates that users should no longer be experiencing impact related to this event. We're performing additional monitoring to confirm issue resolution.
    Scope of impact: Impact is specific to users routed through a specific IPv6 range, therefore we expect that a subset of your users may be impacted by this issue.
    Start time: Tuesday, April 16, 2019, at 8:00 PM UTC
    Preliminary root cause: A recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range.
    Next update by: Wednesday, April 17, 2019, at 4:00 AM UTC
    17.04.2019 18:17:0521Sev216.04.2019 22:00:0017.04.2019 01:25:00Incident18083178Incident
    Exchange OnlineE-Mail timely deliveryEX177852Unable to send email due to SPFUsers may have been intermittently unable to send email to some domains.17.04.2019 04:58:1621Title: Unable to send email due to SPF
    User Impact: Users may be intermittently unable to send email to some domains.
    More info: Users may receive an Non-Delivery Report (NDR): "550 5.7.23 The message was rejected because of Sender Policy Framework violation."
    Current status: Our monitoring and testing continues to indicate that impact has been remediated. We'll perform extended validation over the next several hours to confirm that the issue is resolved.
    Scope of impact: Impact is specific to users routed through a specific IPv6 range, therefore we expect that a subset of your users may be impacted by this issue.
    Start time: Tuesday, April 16, 2019, at 8:00 PM UTC
    Preliminary root cause: A recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range.
    Next update by: Wednesday, April 17, 2019, at 5:00 PM UTC
    17.04.2019 18:17:0521Sev216.04.2019 22:00:0017.04.2019 01:25:00Incident18083178Incident
    Exchange OnlineE-Mail timely deliveryEX177852Unable to send email due to SPFUsers may have been intermittently unable to send email to some domains.17.04.2019 18:17:0521Title: Unable to send email due to SPF
    User Impact: Users may have been intermittently unable to send email to some domains.
    More info: Users may have received a Non-Delivery Report (NDR) stating "550 5.7.23 The message was rejected because of Sender Policy Framework violation."
    Final status: We’ve confirmed via additional monitoring and environment testing that the problem is fixed, and users will no longer experience this issue.
    Scope of impact: Impact was limited to users routed through a specific IPv6 range, which would only have affected a subset of your organization.
    Start time: Tuesday, April 16, 2019, at 8:00 PM UTC
    End time: Tuesday, April 16, 2019, at 11:25 PM UTC
    Root cause: A recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range.
    Next steps: - We've updated the optimization change to prevent any future occurrence of this issue when it is reintroduced to the environment.
    This is the final update for the event.
    17.04.2019 18:17:0521Sev216.04.2019 22:00:0017.04.2019 01:25:00Incident18083178Incident
    Office OnlineWord OnlineOO177786Can't save Word documentsUsers may have experienced errors when attempting to save their Word documents using Office Online.16.04.2019 17:30:0222Title: Can't save Word documents
    User Impact: Users may experience errors when attempting to save their Word documents using Office Online.
    More info: While we're focused on resolving the issue, users can use the Microsoft Word desktop client as a workaround. Additionally, users may see an error message banner at the top of their browser window.
    Current status: We've completed reverting the most recent Office Online version that we suspect led to the impact. While we've not seen additional examples of the problem during peak business hours in Asia and Europe, we'll continue to monitor through peak North and South American business hours to ensure the impact is completely mitigated.
    Scope of impact: This issue could potentially affect any of your users that are attempting to save Word documents using Office Online.
    Start time: Monday, April 15, 2019, at 5:30 PM UTC
    Root cause: A recent update likely introduced an issue affecting Word document save attempts in Office Online.
    Next update by: Wednesday, April 17, 2019, at 11:00 PM UTC
    16.04.2019 23:22:4122Sev216.04.2019 04:55:5316.04.2019 12:00:00Advisory7021578Incident
    Office OnlineWord OnlineOO177786Can't save Word documentsUsers may have experienced errors when attempting to save their Word documents using Office Online.16.04.2019 23:22:2322Title: Can't save Word documents
    User Impact: Users may have experienced errors when attempting to save their Word documents using Office Online.
    More info: While we were focused on resolving the issue, users could have used the Microsoft Word desktop client as a workaround. Additionally, users may have seen an error message banner at the top of their browser window.
    Final status: Service availability has kept stable through North and South American business hours, indicating that impact has been completely mitigated.
    Scope of impact: This issue could have potentially affected any of your users that were attempting to save Word documents using Office Online.
    Start time: Monday, April 15, 2019, at 5:30 PM UTC
    End time: Tuesday, April 16, 2019, at 10:00 AM UTC
    Root cause: A recent update likely introduced an issue affecting Word document save attempts in Office Online.
    Next steps: - We're analyzing our update review processes to prevent similar impact from occurring in the future.
    This is the final update for the event.
    16.04.2019 23:22:4122Sev216.04.2019 04:55:5316.04.2019 12:00:00Advisory7021578Incident
    Office OnlineWord OnlineOO177786Can't save Word documentsUsers may have experienced errors when attempting to save their Word documents using Office Online.16.04.2019 08:11:0022Title: Can't save Word documents
    User Impact: Users may experience errors when attempting to save their Word documents using Office Online.
    More info: While we're focused on resolving the issue, users can use the Microsoft Word desktop client as a workaround. Additionally, users may see an error message banner at the top of their browser window.
    Current status: We've begun rolling back the Office Online version on the affected infrastructure as a preliminary troubleshooting step. Additionally, we're rerouting traffic from impacted infrastructure to alternate resources to provide relief to users while we continue to investigate the possible causes of this issue.
    Scope of impact: This issue could potentially affect any of your users that are attempting to save Word documents using Office Online.
    Next update by: Wednesday, April 17, 2019, at 5:00 PM UTC
    16.04.2019 23:22:4122Sev216.04.2019 04:55:5316.04.2019 12:00:00Advisory7021578Incident
    Office OnlineWord OnlineOO177786Can't save Word documentsUsers may have experienced errors when attempting to save their Word documents using Office Online.16.04.2019 04:56:2122Title: Can't save Word documents
    User Impact: Users may experience errors when attempting to save their Word documents using Office Online.
    More info: While we're focused on resolving the issue, users can use the Microsoft Word desktop client as a workaround. Additionally, users may see an error message banner at the top of their browser window.
    Current status: Our monitoring indicates that there is an issue in which users may be unable to save their Word documents using the Office Online service. We're looking into multiple avenues that may be causing impact to determine our next steps.
    Scope of impact: This issue could potentially affect any of your users that are attempting to save Word documents using Office Online.
    Next update by: Tuesday, April 16, 2019, at 7:00 AM UTC
    16.04.2019 23:22:4122Sev216.04.2019 04:55:5316.04.2019 12:00:00Advisory7021578Incident
    Skype for BusinessAudio and VideoLY177821Not receiving push notificationsUsers may have been intermittently not receiving Skype for Business app push notifications on Android and iOS devices.16.04.2019 20:47:2422Title: Not receiving push notifications
    User Impact: Users may have been intermittently not receiving Skype for Business app push notifications on Android and iOS devices.
    Final status: We've determined that a portion of infrastructure that facilitates Skype for Business app push notifications to Android and iOS devices became degraded, causing impact. We restarted the affected infrastructure and confirmed that push notifications returned to normal levels.
    Scope of impact: This issue may have affected approximately 50 percent of Skype for Business app push notifications on Android and iOS devices for any of your users.
    Start time: Friday, April 12, 2019, at 12:00 PM UTC
    End time: Tuesday, April 16, 2019, at 6:10 PM UTC
    Root cause: A portion of infrastructure that facilitates Skype for Business app push notifications to Android and iOS devices became degraded, causing intermittent push notification failures.
    Next steps: - We're analyzing performance data and trends on the affected systems to help prevent this problem from happening again. - We're reviewing our monitoring services to look for ways to reduce detection time and more quickly restore service.
    This is the final update for the event.
    16.04.2019 21:35:1822Sev212.04.2019 14:00:0016.04.2019 20:10:00Advisory8637660Incident
    Skype for BusinessAudio and VideoLY177821Not receiving push notificationsUsers may have been intermittently not receiving Skype for Business app push notifications on Android and iOS devices.16.04.2019 20:18:5822Title: Not receiving push notifications
    User Impact: Users may be intermittently not receiving Skype for Business app push notifications on Android and iOS devices.
    More info: Up to 50 percent of push notifications may be affected by this issue.
    Current status: We're analyzing system logs to determine why the push notifications aren't being delivered as expected and develop the next troubleshooting steps.
    Scope of impact: This issue may intermittently affect any of your users expecting to receive Skype for Business app push notifications on Android and iOS devices.
    Start time: Friday, April 12, 2019, at 12:00 PM UTC
    Next update by: Tuesday, April 16, 2019, at 8:00 PM UTC
    16.04.2019 21:35:1822Sev212.04.2019 14:00:0016.04.2019 20:10:00Advisory8637660Incident
    Skype for BusinessAudio and VideoLY177299Audio/video calling problemsUsers may have been unable to initiate and accept Skype for Business audio and video calls..08.04.2019 10:17:4830Title: Audio/video calling problems
    User Impact: Users may be unable to initiate and accept Skype for Business audio and video calls.
    More info: Users may also be unable to initiate and join meetings or meetings may take a long time to load. Users who use Public Switched Telephone Network (PSTN) will also be affected.
    Current status: We're analyzing system logs to determine the source of the issue.
    Scope of impact: This issue may potentially affect any of your users attempting to make audio and video calls, or initiate and join meetings.
    Next update by: Monday, April 8, 2019, at 9:30 AM UTC
    15.04.2019 13:22:3023https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='LY177299')Sev208.04.2019 08:55:0008.04.2019 10:45:00Incident3350523Incident
    Skype for BusinessAudio and VideoLY177299Audio/video calling problemsUsers may have been unable to initiate and accept Skype for Business audio and video calls..08.04.2019 11:52:5430Title: Audio/video calling problems
    User Impact: Users may have been unable to initiate and accept Skype for Business audio and video calls.
    More info: Users may have also been unable to initiate and join meetings or meetings may have take a long time to load. Users who use Public Switched Telephone Network (PSTN) would also have been affected when attempting to dial-in or dial-out of audio conference calls.
    Final status: We determined that a service update designed to improve performance inadvertently caused user requests to fail. We restarted the affected Business Voice Directory (BVD) service instances, which mitigated impact.
    Scope of impact: This issue may have potentially affected any of your users attempting to make audio and video calls, or initiate and join meetings.
    Start time: Monday, April 8, 2019, at 6:55 AM UTC
    End time: Monday, April 8, 2019, at 8:45 AM UTC
    Root cause: A service update inadvertently caused user requests to fail, impacting audio and video call, and the ability to initiate, join and dial-in or out of meetings.
    Next steps: - We're rolling back the service update to prevent this problem from happening again. - We're reviewing our standard service update procedures to avoid similar impact in the future.
    This is the final update for the event.
    15.04.2019 13:22:3023https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='LY177299')Sev208.04.2019 08:55:0008.04.2019 10:45:00Incident3350523Incident
    Skype for BusinessAudio and VideoLY177299Audio/video calling problemsUsers may have been unable to initiate and accept Skype for Business audio and video calls..08.04.2019 10:46:3430Title: Audio/video calling problems
    User Impact: Users may be unable to initiate and accept Skype for Business audio and video calls.
    More info: Users may also be unable to initiate and join meetings or meetings may take a long time to load. Users who use Public Switched Telephone Network (PSTN) will also be affected.
    Current status: We've identified high user request error rates and we're continuing our analysis of system logs to determine what is causing this.
    Scope of impact: This issue may potentially affect any of your users attempting to make audio and video calls, or initiate and join meetings.
    Next update by: Monday, April 8, 2019, at 10:30 AM UTC
    15.04.2019 13:22:3023https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='LY177299')Sev208.04.2019 08:55:0008.04.2019 10:45:00Incident3350523Incident
    Skype for BusinessAudio and VideoLY177299Audio/video calling problemsUsers may have been unable to initiate and accept Skype for Business audio and video calls..15.04.2019 13:22:3023A post-incident report has been published.15.04.2019 13:22:3023https://office365servicecomms-prod.cloudapp.net/api/v1.0/ceb371f6-8745-4876-a040-69f2d10a9d1a/ServiceComms/PostIncident/Health.IncidentReportDocument(incidentId='LY177299')Sev208.04.2019 08:55:0008.04.2019 10:45:00Incident3350523Incident
    Yammer EnterpriseYammer ComponentsYA177663Can't view live events on mobile appsUsers may have been unable to view live events via iOS and Android clients.13.04.2019 01:06:4625Title: Can't view live events on mobile apps
    User Impact: Users may have been unable to view live events via iOS and Android clients.
    Final status: We determined that a recent service update caused an issue with backward compatibility for viewing live events. We've developed and deployed a code fix for the service update that has restored live event viewing functionality.
    Scope of impact: Any users attempting to view live events via mobile clients may have been affected.
    Start time: Friday, April 12, 2019, at 6:14 PM UTC
    End time: Friday, April 12, 2019, at 11:02 PM UTC
    Root cause: A recent service update caused mobile clients to fail to render live events.
    Next steps: - We're reviewing our update procedures to better identify backward compatibility issues during our development and testing cycles.
    This is the final update for the event.
    13.04.2019 01:09:2325Sev112.04.2019 20:14:0013.04.2019 01:02:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177663Can't view live events on mobile appsUsers may have been unable to view live events via iOS and Android clients.13.04.2019 00:16:4425Title: Can't view live events on mobile apps
    User Impact: Users may be unable to view live events via iOS and Android clients.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    13.04.2019 01:09:2325Sev112.04.2019 20:14:0013.04.2019 01:02:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177663Can't view live events on mobile appsUsers may have been unable to view live events via iOS and Android clients.13.04.2019 00:33:2225Title: Can't view live events on mobile apps
    User Impact: Users may be unable to view live events via iOS and Android clients.
    Current status: We're currently reviewing system logs to identify the cause.
    Scope of impact: Any users attempting to view live events via mobile clients may be affected.
    Start time: Friday, April 12, 2019, at 6:14 PM UTC
    Next update by: Saturday, April 13, 2019, at 12:00 AM UTC
    13.04.2019 01:09:2325Sev112.04.2019 20:14:0013.04.2019 01:02:00Advisory4012188Incident
    Skype for BusinessAudio and VideoLY177655Can't join or delays joining conferences via Public Switched Telephone Network (PSTN)Users may have been unable to join or experience delays of up to 12 seconds when joining conference calls via PSTN.12.04.2019 20:58:1426Title: Can't join or delays joining conferences via Public Switched Telephone Network (PSTN)
    User Impact: Users may be unable to join or experience delays of up to 12 seconds when joining conference calls via PSTN.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    12.04.2019 21:54:4126Sev212.04.2019 18:37:0012.04.2019 21:00:00Incident2902160Incident
    Skype for BusinessAudio and VideoLY177655Can't join or delays joining conferences via Public Switched Telephone Network (PSTN)Users may have been unable to join or experience delays of up to 12 seconds when joining conference calls via PSTN.12.04.2019 21:54:4126Title: Can't join or delays joining conferences via Public Switched Telephone Network (PSTN)
    User Impact: Users may have been unable to join or experience delays of up to 12 seconds when joining conference calls via PSTN.
    Final status: Our investigation determined that a service update being deployed to the feature that helps facilitate conference PSTN calls contained a code issue. We successfully halted the update and confirmed internally that service is restored.
    Scope of impact: This issue potentially affected any of your users attempting to join conference calls when using PSTN.
    Start time: Friday, April 12, 2019, at 4:37 PM UTC
    End time: Friday, April 12, 2019, at 7:00 PM UTC
    Root cause: A service update being deployed to the feature that helps facilitate conference PSTN calls contained a code issue. 
    Next steps: - We're evaluating the service update to better understand why the code issue wasn't detected during our testing phases and to prevent similar issues from happening in the future.
    This is the final update for the event.
    12.04.2019 21:54:4126Sev212.04.2019 18:37:0012.04.2019 21:00:00Incident2902160Incident
    Yammer EnterpriseYammer ComponentsYA177625Can't use Search function.Users were unable to use the Search function within Yammer.12.04.2019 11:47:5026Title: Can't use Search function.
    User Impact: Users are unable to use the Search function within the Yammer service.
    Current status: We've identified that an expired certificate is the cause of impact. We're applying a new certificate to remediate impact.
    Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure.
    Start time: Friday, April 12, 2019, at 6:55 AM UTC
    Next update by: Friday, April 12, 2019, at 12:00 PM UTC
    12.04.2019 14:53:0826Sev212.04.2019 08:55:0012.04.2019 13:43:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177625Can't use Search function.Users were unable to use the Search function within Yammer.12.04.2019 14:52:0226Title: Can't use Search function.
    User Impact: Users were unable to use the Search function within Yammer.
    Final status: We've routed traffic routed to alternate infrastructure and applied the new certificate. We've confirmed that the issue is resolved after monitoring the environment.
    Scope of impact: Impact was specific to a subset of users who were served through the affected infrastructure.
    Start time: Friday, April 12, 2019, at 6:55 AM UTC
    End time: Friday, April 12, 2019, at 11:43 AM UTC
    Root cause: A certificate used for search functionality had expired, causing impact.
    Next steps: - We're reviewing our certificate management procedures to avoid similar impact in the future.
    This is the final update for the event.
    12.04.2019 14:53:0826Sev212.04.2019 08:55:0012.04.2019 13:43:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177625Can't use Search function.Users were unable to use the Search function within Yammer.12.04.2019 13:33:1726Title: Can't use Search function.
    User Impact: Users are unable to use the Search function within the Yammer service.
    Current status: We continue to apply the new certificate. Additionally, we're rerouting traffic to alternate infrasturue to ensure full remediation.
    Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure.
    Start time: Friday, April 12, 2019, at 6:55 AM UTC
    Next update by: Friday, April 12, 2019, at 3:00 PM UTC
    12.04.2019 14:53:0826Sev212.04.2019 08:55:0012.04.2019 13:43:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177625Can't use Search function.Users were unable to use the Search function within Yammer.12.04.2019 11:06:5326Title: Can't use Search function.
    User Impact: Users are unable to use the Search function within the Yammer service.
    Current status: We're reviewing support case data to determine the next troubleshooting steps.
    Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure.
    Next update by: Friday, April 12, 2019, at 10:30 AM UTC
    12.04.2019 14:53:0826Sev212.04.2019 08:55:0012.04.2019 13:43:00Advisory4012188Incident
    Skype for BusinessAudio and VideoLY177631Unable to join PSTN conference callsUsers were unable to join Public Switched Telephone Network (PSTN) conference calls.12.04.2019 12:20:2026Title: Unable to join PSTN conference calls
    User Impact: Users are unable to join Public Switched Telephone Network (PSTN) conference calls.
    Current status: We're investigating service telemetry data to isolate the cause of the issue.
    Scope of impact: Impact is specific to users who are served through the affected infrastructure.
    Start time: Friday, April 12, 2019, at 8:55 AM UTC
    Next update by: Friday, April 12, 2019, at 1:00 PM UTC
    12.04.2019 13:50:3026Sev212.04.2019 10:55:0012.04.2019 13:50:14Incident6587744Incident
    Skype for BusinessAudio and VideoLY177631Unable to join PSTN conference callsUsers were unable to join Public Switched Telephone Network (PSTN) conference calls.12.04.2019 13:50:3026Title: Unable to join PSTN conference calls
    User Impact: Users were unable to join Public Switched Telephone Network (PSTN) conference calls.
    Final status: We've determined during a routine update procedure, user requests were sent to a subset of PSTN processing infrastructure, which was not correctly configured to handle the user requests. We've monitored the service whilst the update has propagated throughout the environment and the infrastructure was reconfigured to handle the user requests, remediating impact.
    Scope of impact: Impact was specific to users who were served through the affected infrastructure.
    Start time: Friday, April 12, 2019, at 8:55 AM UTC
    End time: Friday, April 12, 2019, at 10:05 AM UTC
    Root cause: Requests were sent to a subset of PSTN processing infrastructure, which was incorrectly configured to handle user requests during routine service updates.
    Next steps: - We're reviewing our standard service update procedures to avoid similar impact in the future.
    This is the final update for the event.
    12.04.2019 13:50:3026Sev212.04.2019 10:55:0012.04.2019 13:50:14Incident6587744Incident
    Yammer EnterpriseYammer ComponentsYA177605Can't load feedsUsers may have been unable to load their feeds on Yammer.com.12.04.2019 01:42:2226Title: Can't load feeds
    User Impact: Users may have been unable to load their feeds on Yammer.com.
    Final status: We deployed a fix to the affected environment and confirmed that the impact was remediated.
    Scope of impact: We deployed a fix to the affected environment and confirmed that the impact was remediated.
    Start time: Thursday, April 11, 2019, at 10:20 PM UTC
    End time: Thursday, April 11, 2019, at 11:13 PM UTC
    Root cause: A recent database configuration change caused unexpected impact to the Yammer.com service.
    Next steps: -We're reviewing our database configuration operations to find better ways to identify similar issues and prevent future impact.
    This is the final update for the event.
    12.04.2019 02:18:1826Sev212.04.2019 00:20:0012.04.2019 01:13:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177605Can't load feedsUsers may have been unable to load their feeds on Yammer.com.12.04.2019 01:07:3626Title: Can't load feeds
    User Impact: Users may be unable to load their feeds on Yammer.com.
    Current status: We've detected that a recent database configuration change is causing unexpected impact for Yammer.com. We're reviewing server logs to to determine the best method of restoring service.
    Scope of impact: Your organization is affected by this event, and the issue could impact any user using Yammer.com
    Start time: Thursday, April 11, 2019, at 10:20 PM UTC
    Next update by: Friday, April 12, 2019, at 1:00 AM UTC
    12.04.2019 02:18:1826Sev212.04.2019 00:20:0012.04.2019 01:13:00Advisory4012188Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.03.04.2019 03:05:1835Title: Microsoft Teams install exclusion issue in Office 365 ProPlus
    User Impact: Admins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.
    More info: The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-install
    Current status: We've completed the testing process and have initiated deployment to a limited portion of service infrastructure for additional validation. Once complete, we'll deploy the fix throughout the affected environment.
    Scope of impact: This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.
    Start time: Monday, March 4, 2019, at 12:00 PM UTC
    Estimated time to resolve: Based on current progress, we expect this problem to be resolved by April 9, 2019.
    Root cause: An update to the deployment code caused the ExcludeApp setting within the Office Deployment Tool to not work as expected.
    Next update by: Wednesday, April 10, 2019, at 2:00 AM UTC
    12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.11.04.2019 00:49:3427Title: Microsoft Teams install exclusion issue in Office 365 ProPlus
    User Impact: Admins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.
    More info: The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-install
    Current status: We're continuing our efforts to ensure that our fix has reached all affected customers as expected.
    Scope of impact: This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.
    Start time: Monday, March 4, 2019, at 12:00 PM UTC
    Root cause: An update to the deployment code caused the ExcludeApp setting within the Office Deployment Tool to not work as expected.
    Next update by: Friday, April 12, 2019, at 2:00 AM UTC
    12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.26.03.2019 02:16:1343Title: Microsoft Teams install exclusion issue in Office 365 ProPlus
    User Impact: Admins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.
    More info: The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-install
    Current status: We've nearly completed the testing process and anticipate that we will be ready to start deployment later this week. We continue to expect this issue to be resolved by April 9, 2019.
    Scope of impact: This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.
    Start time: Monday, March 4, 2019, at 12:00 PM UTC
    Estimated time to resolve: Based on current progress, we expect this problem to be resolved by April 9, 2019.
    Root cause: An update to the deployment code caused the ExcludeApp setting within the Office Deployment Tool to not work as expected.
    Next update by: Wednesday, April 3, 2019, at 2:00 AM UTC
    12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.12.04.2019 00:55:5526Title: Microsoft Teams install exclusion issue in Office 365 ProPlus
    User Impact: Admins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.
    More info: The existing Skype for Business functionality was unaffected throughout this event. While we were fixing the underlying problem, affected customers could follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-install
    Final status: We've confirmed that our fix has reached all affected customers and that the incident is resolved.
    Scope of impact: This may have affected a limited subset of customers who chose to exclude Teams installation and were part of specific builds. The build information was included in the install documentation above.
    Start time: Monday, March 4, 2019, at 12:00 PM UTC
    End time: Tuesday, April 9, 2019, at 12:00 AM UTC
    Root cause: An update to the deployment code prevented the ExcludeApp setting within the Office Deployment Tool from working as expected.
    Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
    This is the final update for the event.
    12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.10.04.2019 00:33:1628Title: Microsoft Teams install exclusion issue in Office 365 ProPlus
    User Impact: Admins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.
    More info: The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-install
    Current status: We're working to verify that our fix has reached all affected customers as expected.
    Scope of impact: This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.
    Start time: Monday, March 4, 2019, at 12:00 PM UTC
    Root cause: An update to the deployment code caused the ExcludeApp setting within the Office Deployment Tool to not work as expected.
    Next update by: Thursday, April 11, 2019, at 2:00 AM UTC
    12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.19.03.2019 01:21:3350Title: Microsoft Teams install exclusion issue in Office 365 ProPlus
    User Impact: Admins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.
    More info: The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-install
    Current status: We're thoroughly testing our fix in preparation for deployment. Our testing is progressing as anticipated and we continue to expect that the issue will be resolved by April 9, 2019.
    Scope of impact: This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.
    Start time: Monday, March 4, 2019, at 12:00 PM UTC
    Estimated time to resolve: Based on current progress, we expect this problem to be resolved by April 9, 2019.
    Root cause: An update to the deployment code caused the ExcludeApp setting within the Office Deployment Tool to not work as expected.
    Next update by: Tuesday, March 26, 2019, at 2:00 AM UTC
    12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    Office 365 PortalAdministrationMO175715Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins were unable to exclude Office 365 from installing as part of the Office 365 ProPlus installations.13.03.2019 03:19:3556Title: Microsoft Teams install exclusion issue in Office 365 ProPlus
    User Impact: Admins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.
    More info: The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-install
    Current status: We've determined that the ExcludeApp setting within the Office Deployment Tool is not working as expected under certain circumstances, which is resulting in Teams being installed in deployments of Office 365 ProPlus, even when Teams was supposed to be blocked. We’re addressing this issue in an update for Microsoft Office 365 ProPlus, which is being prepared for deployment.
    Scope of impact: This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.
    Start time: Monday, March 4, 2019, at 12:00 PM UTC
    Estimated time to resolve: Based on current deployment progress, we expect this problem to be resolved by April 9, 2019.
    Root cause: An update to the deployment code caused the ExcludeApp setting within the Office Deployment Tool to not work as expected.
    Next update by: Tuesday, March 19, 2019, at 2:00 AM UTC
    12.04.2019 00:59:0626Sev204.03.2019 13:00:0009.04.2019 02:00:00Advisory21653170Incident
    SharePoint OnlineTenant AdminSP177484SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.10.04.2019 20:40:5528Title: SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impact
    User impact: Admins may be unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.
    Current status: We’ve determined that there is no resource contention in the environment that would be contributing to the impact. We’re reviewing source code and analyzing additional available system logs to formulate our next troubleshooting steps.
    Scope of impact: Your organization is affected by this event, and impact is specific to administrators.
    Next update by: Wednesday, April 10, 2019, at 10:30 PM UTC
    11.04.2019 01:54:1727Sev208.04.2019 14:00:0011.04.2019 01:42:00Advisory6319693Incident
    SharePoint OnlineTenant AdminSP177484SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.11.04.2019 01:54:1727Title: SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impact
    User Impact: Admins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.
    More info: Affected admins may have received an error indicating that the request uses too many resources.
    Final status: We identified and disabled a code issue that was causing impact to the infrastructure responsible for site provisioning and Remote PowerShell.
    Scope of impact: Impact was specific to administrators performing various tasks in the admin center and through Remote PowerShell.
    Start time: Monday, April 8, 2019, at 12:00 PM UTC
    End time: Wednesday, April 10, 2019, at 11:42 PM UTC
    Preliminary root cause: A code issue caused the infrastructure responsible for site provisioning and Remote PowerShell to become degraded.
    Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles. - We're reviewing our monitoring services to look for ways to reduce detection time and more quickly restore service.
    This is the final update for the event.
    11.04.2019 01:54:1727Sev208.04.2019 14:00:0011.04.2019 01:42:00Advisory6319693Incident
    SharePoint OnlineTenant AdminSP177484SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.11.04.2019 00:29:1427Title: SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impact
    User Impact: Admins may be unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.
    More info: Affected admins may receive an error indicating that the request uses too many resources.
    Current status: We’ve reviewed our code and have identified a potential fix for this problem. We're continuing to troubleshoot to confirm that our fix is a viable solution for this issue.
    Scope of impact: Impact is specific to administrators performing various tasks in the admin center and through Remote PowerShell.
    Next update by: Thursday, April 11, 2019, at 12:30 AM UTC
    11.04.2019 01:54:1727Sev208.04.2019 14:00:0011.04.2019 01:42:00Advisory6319693Incident
    SharePoint OnlineTenant AdminSP177484SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.10.04.2019 17:01:5728Title: Unable to run certain Remote PowerShell commands
    User Impact: Admins may be unable to run certain Remote PowerShell commands.
    Current status: Our preliminary findings indicate that there may be an issue regarding resource contention that's causing degraded performances. We're continuing to test the Remote PowerShell commands in a variety of different scenarios, in addition to our continued analysis of the Unified Logging Service (ULS) logs and system logs, to determine the specific cause of the issue.
    Scope of impact: Your organization is affected by this event, and impact is specific to administrators.
    Next update by: Wednesday, April 10, 2019, at 7:30 PM UTC
    11.04.2019 01:54:1727Sev208.04.2019 14:00:0011.04.2019 01:42:00Advisory6319693Incident
    SharePoint OnlineTenant AdminSP177484SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.10.04.2019 14:57:1128Title: Unable to run certain Remote PowerShell commands
    User Impact: Admins may be unable to run certain Remote PowerShell commands.
    Current status: We're analyzing Unified Logging Service (ULS) logs to determine the source of the issue.
    Scope of impact: Your organization is affected by this event, and impact is specific to administrators.
    Next update by: Wednesday, April 10, 2019, at 3:00 PM UTC
    11.04.2019 01:54:1727Sev208.04.2019 14:00:0011.04.2019 01:42:00Advisory6319693Incident
    SharePoint OnlineTenant AdminSP177484SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.10.04.2019 16:34:4128Title: Unable to run certain Remote PowerShell commands
    User Impact: Admins may be unable to run certain Remote PowerShell commands.
    Current status: We're testing the Remote PowerShell commands in a variety of different scenarios to determine the specific cause of the issue.
    Scope of impact: Your organization is affected by this event, and impact is specific to administrators.
    Next update by: Wednesday, April 10, 2019, at 5:00 PM UTC
    11.04.2019 01:54:1727Sev208.04.2019 14:00:0011.04.2019 01:42:00Advisory6319693Incident
    Yammer EnterpriseYammer ComponentsYA177504Sign in errorsUsers may experience sign in errors when attempting to access Yammer.10.04.2019 21:18:5928Title: Sign in errors
    User Impact: Users may experience sign in errors when attempting to access Yammer.
    Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    10.04.2019 23:35:1027Sev210.04.2019 21:18:2210.04.2019 22:25:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177504Sign in errorsUsers may experience sign in errors when attempting to access Yammer.10.04.2019 21:50:3628Title: Sign in errors
    User Impact: Users may experience sign in errors when attempting to access Yammer.
    More info: Users may see a "Retry later" page.
    Current status: We've identified that traffic is not being routed as expected, preventing users from signing in. We're currently deploying a configuration change to reprioritize traffic and mitigate impact.
    Scope of impact: Any users attempting to access Yammer may be impacted.
    Root cause: Traffic is not being routed as expected, preventing users from signing in.
    Next update by: Wednesday, April 10, 2019, at 9:00 PM UTC
    10.04.2019 23:35:1027Sev210.04.2019 21:18:2210.04.2019 22:25:00Advisory4012188Incident
    Yammer EnterpriseYammer ComponentsYA177504Sign in errorsUsers may experience sign in errors when attempting to access Yammer.10.04.2019 22:52:2628Title: Sign in errors
    User Impact: Users may experience sign in errors when attempting to access Yammer.
    More info: Users may have seen a "Retry later" page.
    Final status: We've verified the configuration changes have resolved the issue.
    Scope of impact: Any users attempting to access Yammer may have been impacted.
    Start time: Wednesday, April 10, 2019, at 5:40 PM UTC
    End time: Wednesday, April 10, 2019, at 8:25 PM UTC
    Root cause: Traffic was not being routed as expected, preventing users from signing in.
    Next steps: - We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar impact in the future.
    This is the final update for the event.
    10.04.2019 23:35:1027Sev210.04.2019 21:18:2210.04.2019 22:25:00Advisory4012188Incident
    Office OnlineWord OnlineOO177408Word documents online issueUsers may have been unable to open Word documents online using the Web Application Client.09.04.2019 12:41:2529Title: Word documents online issue
    User Impact: Users may be unable to open Word documents online using the Web Application Client.
    More info: The issue could potentially impact, but is no limited to, Microsoft Teams, Outlook on the web, the Outlook client and SharePoint Online services.
    As a workaround, users may be able to open Word documents using the local application.
    Current status: We're analyzing diagnostic data to isolate the source of the issue.
    Scope of impact: This issue affects internal Microsoft users only. Impact could potentially affect any user attempting to open Word documents online using the Web Application Client (WAC).
    Next update by: Tuesday, April 9, 2019, at 12:30 PM UTC
    10.04.2019 00:06:2328Sev209.04.2019 12:36:4309.04.2019 13:41:51Advisory6970822Incident
    Office OnlineWord OnlineOO177408Word documents online issueUsers may have been unable to open Word documents online using the Web Application Client.09.04.2019 13:41:5829Title: Word documents online issue
    User Impact: Users may have been unable to open Word documents online using the Web Application Client.
    More info: The issue could have potentially impacted, but was no limited to, Microsoft Teams, Outlook on the web, the Outlook client and SharePoint Online services.
    As a workaround, users may have been able to open Word documents using the local application.
    Final status: We've determined an update to the Web Application Client (WAC) service inadvertently impacted opening Word documents within Office Online. We've reverted the update and confirmed that impact has been remediated.
    Scope of impact: This issue affected internal Microsoft users only. Impact could have potentially affected any user attempting to open Word documents online using the Web Application Client.
    Start time: Monday, April 8, 2019, at 12:30 PM UTC
    End time: Tuesday, April 9, 2019, at 11:00 AM UTC
    Root cause: A recent update to the Web Application Client service impacted Word online functionality.
    Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
    This is the final update for the event.
    10.04.2019 00:06:2328Sev209.04.2019 12:36:4309.04.2019 13:41:51Advisory6970822Incident
    Skype for BusinessAudio and VideoLY177351Can't dial in or out of audio conferences intermittentlyUsers may have been unable to dial in or out of audio conferences intermittently.09.04.2019 00:21:0729Title: Can't dial in or out of audio conferences intermittently
    User Impact: Users may have been unable to dial in or out of audio conferences intermittently.
    More info: Impact was specific to users attempting to dial in using a Public Switched Telephone Network (PSTN).
    Final status: Our investigation showed that a subset of infrastructure responsible for processing the PSTN audio conferencing calls was performing in a degraded state. Our automated systems restarted the affected infrastructure and we verified internally that service had fully restored once fully completed.
    Scope of impact: This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.
    Start time: Monday, April 8, 2019, at 4:56 PM UTC
    End time: Monday, April 8, 2019, at 6:12 PM UTC
    Root cause: A subset of infrastructure responsible for processing the PSTN audio conferencing calls was performing in a degraded state.
    Next steps: - We're reviewing the performance data on the affected infrastructure to determine why automated systems did not perform recovery actions, and how we can improve our response time to either avoid prolonged periods of impact or to mitigate the issue entirely.
    This is the final update for the event.
    09.04.2019 00:34:5429Sev208.04.2019 18:56:0009.04.2019 00:21:07Incident2902160Incident
    ServiceFeatureIDTitleImpactDescriptionPublishedTimePublishedDaysAgoMessageLastUpdatedTimeLastUpdatedDaysAgoUserFunctionalImpactPostIncidentDocumentUrlSeverityStartTimeEndTimeClassificationAffectedTenantCountAffectedUserCountMessageType
    ServiceStatusPublishedTimePublishedDaysAgoTitleUserImpactMoreInfoCurrentStatusScopeOfImpactStartTimePreliminaryRootCauseNextUpdateByFinalStatusOther
    Office 365 PortalService restored08.05.2019 21:28:100Can't launch appsWindows 7 users may have been unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.Affected Windows 7 users would have been shown the template page upon opening an Office app, and then the app would close.This issue affected any enterprise user attempting to launch Office apps on Windows 7.29.03.2019 22:00:00A faulty feature update within the March 2019 Office update caused Office apps on Windows 7 to crash.We've confirmed that the fix has fully deployed to the service environment and the problem is resolved.We'll publish a post-incident report within five business days.
    Skype for BusinessService degradation08.05.2019 20:32:480Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected.The deployment of the fix has achieved 96 percent completion. Admins hosted on infrastructure that has received the fix may already see impact mitigation.This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.15.03.2019 10:00:00A recent change intended to adjust an API used in the records process resulted in incomplete results.10.05.2019 21:00:00
    Office 365 PortalService restored08.05.2019 18:43:280Can't launch appsWindows 7 users may be unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.When users launch the desktop app, they may see the template page, and then the app closes.We've initiated deployment of the fix to the service environment. Users who are able to do so may download and install the fix now via standard Windows update; though, we expect that the deployment will fully complete within the next few hours.This issue affects any enterprise user attempting to launch Office apps on Windows 7.29.03.2019 22:00:00A faulty feature update within the March 2019 Office update, is causing Office apps on Windows 7 to crash.09.05.2019 19:00:00
    Office 365 PortalService restored07.05.2019 18:46:261Can't launch appsWindows 7 users may be unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.When users launch the desktop app, the user may see the template page, and then the app closes.We’ve disabled the feature update responsible for the app crashes and confirmed that this has mitigated impact for most affected users. Additionally, we’ve completed validation of the long-term fix and are preparing to deploy it to the affected environment within the next 24 hours. This issue affects any enterprise user attempting to launch Office apps on Windows 7.A code regression was introduced through a feature update within the March 2019 Office update, which is impacting access to Office apps on Windows 7.08.05.2019 19:00:00
    OneDrive for BusinessPost-incident report published07.05.2019 14:28:501A post-incident report has been published.
    SharePoint OnlinePost-incident report published07.05.2019 14:28:151A post-incident report has been published.
    Office 365 PortalService restored07.05.2019 07:19:301Can't launch appsWindows 7 users may be unable to launch apps, such as Outlook, Word, Excel, PowerPoint and OneNote.When users launch the desktop app, the user may see the template page, and then the app closes.We've determined that a code regression was introduced through a feature update contained within the March Office update. We're performing validation on a potential fix to ensure that it will resolve the issue prior to deployment. In the interim, users may be able to further avoid the issue by opening the files directly and not through the specific Office app.This issue affects any enterprise user attempting to launch Office apps on Windows 7.A code regression was introduced through a feature update within the March 2019 Office update, which is impacting access to Office apps on Windows 7.07.05.2019 19:00:00
    Skype for BusinessService degradation06.05.2019 23:48:261Inaccurate Skype for Business conferencing metrics in Admin Usage ReportsAdmins may notice that usage reports contain inaccurate data for Skype for Business conferencing scenarios.We identified an issue in which Skype for Business usage reports contain inaccurate data for conferencing scenarios. Our investigation determined that a routine service update introduced a code issue which resulted in impact. We've developed and deployed a fix to the affected environment and will be monitoring the deployment as it progresses.Impact is specific to the Conference Organizer Activity and Conference Participant Activity reports.25.04.2019 12:00:00A routine service update contained a code issue that caused Skype for Business usage reports to contain inaccurate data for specific conferencing scenarios. 10.05.2019 21:00:00
    Skype for BusinessService degradation06.05.2019 23:08:092Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Specifically, users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web, the Outlook client for Mac, or the iOS mobile app.We've completed initial validation of the fix and are performing additional testing to ensure it effectively resolves the issue. We'll provide an updated timeline for full deployment to affected users when available; however, we expect this may take two to three weeks to complete.This issue could potentially affect any of your users if they are routed through the affected infrastructure.25.03.2019 14:25:0013.05.2019 21:00:00
    Skype for BusinessService degradation06.05.2019 21:52:432Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.This is an incremental update to provide the latest status on the issue.The fix has been deployed to 83 percent of the affected environment. Some admins may begin to see impact mitigation as the fix reaches their environment. The fix is expected to complete deployment by the end of the week. For complete details on this event, please reference the post from 7:21 PM UTC on May 4, 2019.08.05.2019 21:00:00
    Exchange OnlineService restored06.05.2019 20:47:142Message trace functionality issuesAdmins may have experienced issues with message trace reports and services utilizing message trace functionality.Affected admins would have experienced this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).Impact was specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:00We've confirmed that the backlog has fully drained, and subsequent service monitoring shows that the problem is fixed.We'll publish a post-incident report within five business days.
    Exchange OnlineService restored06.05.2019 06:57:042My Templates add in missingUsers may have been unable to see the My Templates add in for Outlook on the web or the desktop client.This issue may have potentially affected any of your users attempting to use the My Templates add in for Outlook on the web or the desktop client.29.04.2019 23:00:00A recent service update inadvertently caused impact to the My Templates feature.We've verified that disabling the offending update and refreshing the data in all affected environments has resolved the underlying issue. We've determined that the following manual mitigation steps will be required from tenant admins to completely mitigate impact: 1) A tenant admin will need to navigate to the add-in management page in the Exchange admin center (EAC). Disabling and then re-enabling My Templates will bypass an 8-day cache expiration. 2) At this point, it will take up to 3 hours for the add-in to be available to end-users. During this time, some users will see the add-in before others. 3) After 3 hours, a user can restart the Outlook desktop client or refresh Outlook on the web to see My Templates. If a user doesn't restart the Outlook desktop client, they will see the add-in within 4 additional hours.This is the final update for the event.
    Skype for BusinessService degradation04.05.2019 21:21:074Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected.We've successfully validated the code fix and have begun deployment to the affected infrastructure. We expect deployment of the fix to complete in approximately two weeks.This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.15.03.2019 10:00:0006.05.2019 21:00:00
    Office 365 PortalPost-incident report published04.05.2019 04:10:584A post-incident report has been published.
    OneDrive for BusinessPost-incident report published04.05.2019 04:10:324A post-incident report has been published.
    SharePoint OnlinePost-incident report published04.05.2019 04:09:564A post-incident report has been published.
    Exchange OnlineService restored04.05.2019 02:41:024My Templates add in missingUsers may be unable to see the My Templates add in for Outlook on the web or the desktop client.We've successfully refreshed the data in your environment and will be checking in with your representatives early next week to ensure that the remediation steps we've provided have resolved the problem.Your organization is affected by this event, and any user using Outlook on the web or the desktop client may be impacted by this.29.04.2019 23:00:0006.05.2019 20:00:00
    Exchange OnlineService restored04.05.2019 02:40:044Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).The deployment of the fix has completed. We're monitoring the environment to ensure that the backlog of requests processes as expected, which we anticipate will complete by Monday, May 6, 2019.Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:0006.05.2019 20:00:00
    Exchange OnlineService restored04.05.2019 00:59:104My Templates add in missingUsers may be unable to see the My Templates add in for Outlook on the web or the desktop client.Our investigation shows that a recent service update inadvertently caused impact to the My Templates feature. We've disabled the recent service update and we're working to refresh the data in your environment. Once completed, we'll inform your organization and will require the following steps to propagate these changes more quickly in your environment: 1) Admins may need to force a server-side cache refresh by making a change to the organization-wide "My Templates" add-in configuration. Disabling and then re-enabling the add-in is a potential action to complete this process. 2) Affected users may need to refresh their web browser if using Outlook on the web or restart their Outlook client for the mitigation to take effect.Your organization is affected by this event, and any user using Outlook on the web or the desktop client may be impacted by this.29.04.2019 23:00:0004.05.2019 01:00:00
    Skype for BusinessService degradation03.05.2019 21:55:045Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected. We've determined that a recent change intended to adjust an Application Programming Interface (API) used in the records process resulted in impact. We've developed a code fix that is being tested and validated before deployment.This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.15.03.2019 10:00:0004.05.2019 21:00:00
    Skype for BusinessService degradation03.05.2019 21:32:265Incomplete call recordsAdmins may see incomplete results when viewing call records in Call Analytics.Specifically, admins may not see Public Switched Telephone Network (PSTN) dial-in or dial-out sessions as expected. We're investigating a potential issue with the Skype for Business service. We'll provide an update within 30 minutes.This incident impacts all admins attempting to view call records through Call Analytics in the Skype for Business admin center.
    Exchange OnlineService restored03.05.2019 20:28:175Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).The deployment of the fix is in progress and we anticipate that this process will complete within the next three hours. The backlog of requests will require more time to process and we'll be monitoring the environment to ensure it completes as expected.Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:0004.05.2019 02:00:00
    Office 365 PortalPost-incident report published03.05.2019 00:17:015Unable to access Microsoft 365 services or featuresUsers may have been unable to access Microsoft 365 services or features.Affected services included SharePoint Online, OneDrive for Business, Microsoft Teams, Stream, Power BI, Planner, Forms, PowerApps, Dynamics 365, Intune, Azure Active Directory (AAD) and Office Licensing.This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.02.05.2019 19:20:00A DNS configuration issue was preventing users from accessing multiple Microsoft 365 services.We've monitored the environment and have confirmed that service has been restored.We'll publish a post-incident report within five business days.
    OneDrive for BusinessPost-incident report published02.05.2019 23:55:595Delays or problems loading OneDrive contentUsers may have experienced intermittent delays or navigation errors when accessing OneDrive for Business content.This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.02.05.2019 19:20:00A DNS configuration issue was preventing users from accessing OneDrive content. We've monitored the environment and have confirmed that service has been restored.We'll publish a post-incident report within five business days.
    SharePoint OnlinePost-incident report published02.05.2019 23:54:345Delays or problems loading SharePoint Online sitesUsers may have experienced intermittent delays or navigation errors when accessing SharePoint sites.This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.02.05.2019 19:20:00A DNS configuration issue was preventing users from accessing SharePoint Online sites.We've monitored the environment and have confirmed that service has been restored.We'll publish a post-incident report within five business days.
    OneDrive for BusinessPost-incident report published02.05.2019 23:31:465Delays or problems loading OneDrive contentUsers may experience intermittent delays or navigation errors when accessing OneDrive for Business content.We've identified and corrected a DNS configuration issue that prevented users from accessing OneDrive for Business content. We've observed an increase in successful connections and our telemetry indicates that all services are recovering. We're continuing to monitor the environment to validate that service has been restored.This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.02.05.2019 19:41:00A DNS configuration issue is preventing users from accessing OneDrive for Business content.02.05.2019 22:30:00
    SharePoint OnlinePost-incident report published02.05.2019 23:31:075Delays or problems loading SharePoint Online sitesUsers may experience intermittent delays or navigation errors when accessing SharePoint sites.We've identified and corrected a DNS configuration issue that prevented users from accessing SharePoint Online sites. We've observed an increase in successful connections and our telemetry indicates that all services are recovering. We're continuing to monitor the environment to validate that service has been restored.This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.02.05.2019 19:41:00A DNS configuration issue is preventing users from accessing SharePoint Online sites.02.05.2019 22:30:00
    Office 365 PortalPost-incident report published02.05.2019 23:27:476Unable to access Microsoft 365 services or featuresUsers may be unable to access Microsoft 365 services or features.Next update by: Thursday, May 2, 2019, at 10:30 PM UTC
    Office 365 PortalPost-incident report published02.05.2019 23:05:366Unable to access Microsoft 365 services or featuresUsers may be unable to access Microsoft 365 services or features.Next update by: Thursday, May 2, 2019, at 10:00 PM UTC
    OneDrive for BusinessPost-incident report published02.05.2019 23:04:026Delays or problems loading OneDrive contentUsers may experience intermittent delays or navigation errors when accessing OneDrive for Business content.Next update by: Thursday, May 2, 2019, at 10:00 PM UTC
    SharePoint OnlinePost-incident report published02.05.2019 23:02:206Delays or problems loading SharePoint Online sitesUsers may experience intermittent delays or navigation errors when accessing SharePoint sites.Next update by: Thursday, May 2, 2019, at 10:00 PM UTC
    Office 365 PortalPost-incident report published02.05.2019 22:35:406Unable to access Microsoft 365 services or featuresUsers may be unable to access Microsoft 365 services or features.We're investigating an issue in which users may be unable to access multiple Microsoft 365 services or features. We're analyzing system logs in an effort to understand the problem and determine the next troubleshooting steps.This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.02.05.2019 21:30:00
    SharePoint OnlineFalse positive02.05.2019 22:24:176Delays or problems loading SharePoint Online sites or OneDrive for BusinessUsers may experience intermittent delays or navigation errors when accessing SharePoint sites or OneDrive content.The investigation is complete and we've determined the service is healthy. A service incident did not actually occur.
    OneDrive for BusinessPost-incident report published02.05.2019 22:06:146Delays or problems loading OneDrive contentUsers may experience intermittent delays or navigation errors when accessing OneDrive for Business content.We're analyzing system logs in an effort to understand the problem and determine the next troubleshooting steps.This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.02.05.2019 21:00:00
    SharePoint OnlinePost-incident report published02.05.2019 22:04:286Delays or problems loading SharePoint Online sitesUsers may experience intermittent delays or navigation errors when accessing SharePoint sites.We're analyzing system logs in an effort to understand the problem and determine the next troubleshooting steps.This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.02.05.2019 21:00:00
    SharePoint OnlineFalse positive02.05.2019 21:47:026Delays or problems loading SharePoint Online sites or OneDrive for BusinessUsers may experience intermittent delays or navigation errors when accessing SharePoint sites or OneDrive content.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.
    SharePoint OnlinePost-incident report published02.05.2019 21:41:576Delays or problems loading SharePoint Online sites Users may experience intermittent delays or navigation errors when accessing SharePoint sites.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.
    Exchange OnlineService restored02.05.2019 20:50:046Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).Our work to deploy and provision additional capacity to the environment is complete and we've observed that the backlog of requests is decreasing. In parallel, we've initiated deployment of a fix that will address a performance issue that is contributing to impact, and we expect that fix to be fully deployed by tomorrow.Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:0003.05.2019 20:00:00
    OneDrive for BusinessPost-incident report published02.05.2019 18:48:076Can’t sync changes to Office documentsUsers may have been unable to sync recent Office document changes to OneDrive for Business.Users operating Office 2013 or earlier clients may have encountered this issue when editing existing or newly created Office documents with a target save location within OneDrive for Business.Any of your users that were using Office 2013 client or earlier versions may have experienced this problem.28.04.2019 19:00:00We’ve confirmed that the fix has saturated across all of the affected environments and the problem is fixed.We'll publish a post-incident report within five business days.
    SharePoint OnlinePost-incident report published02.05.2019 18:40:246Can't sync changes to Office documentsUsers may have been unable to sync recent Office document changes to SharePoint Online sites.Users operating Office 2013 or earlier clients may have encountered this issue when editing existing or newly created Office documents with a target save location within SharePoint Online.Any of your users that were using Office 2013 client or earlier versions may have experienced this problem.28.04.2019 19:00:00We’ve confirmed that the fix has saturated across all of the affected environments and the problem is fixed.We'll publish a post-incident report within five business days.
    Yammer EnterpriseService restored02.05.2019 06:49:146Can't load feedsUsers may have experienced intermittent failures when attempting to load feeds in the Yammer service.Impact was specific to a subset of users who were served through the affected infrastructure.02.05.2019 03:05:00We've confirmed that re-directing traffic to an alternate portion of infrastructure has fully remediated this issue.This is the final update for the event.
    Yammer EnterpriseService restored02.05.2019 06:24:486Can't load feedsUsers may experience intermittent failures when attempting to load feeds in the Yammer service.We've determined that resources within a subset of infrastructure has been exceeded which has resulted in the service performing below expected thresholds. We're working to re-direct traffic to an alternate portion of infrastructure in an attempt to remediate this issue.Impact is specific to a subset of users who are served through the affected infrastructure.02.05.2019 03:05:0002.05.2019 05:30:00
    Yammer EnterpriseService restored02.05.2019 06:10:336Can't load feedsUsers may experience intermittent failures when attempting to load feeds in the Yammer service.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.02.05.2019 03:05:00
    OneDrive for BusinessPost-incident report published02.05.2019 03:02:076Can’t sync changes to Office documentsUsers may be unable to sync recent Office document changes to OneDrive for Business.Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within OneDrive for Business.The fix is progressing as expected and has been deployed to approximately 60 percent of the affected environment. We anticipate that it will finish within the next 16 hours. We've confirmed with users that the fix does resolve the issue so users will experience service restoration as the fix reaches their environment.Any of your users that are using Office 2013 client or earlier versions may experience this problem.28.04.2019 19:00:0002.05.2019 17:00:00
    SharePoint OnlinePost-incident report published02.05.2019 02:59:356Can't sync changes to Office documentsUsers may be unable to sync recent Office document changes to SharePoint Online sites.Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within SharePoint Online.The fix is progressing as expected and has been deployed to approximately 60 percent of the affected environment. We anticipate that it will finish within the next 16 hours. We've confirmed with users that the fix does resolve the issue so users will experience service restoration as the fix reaches their environment.Any of your users that are using Office 2013 client or earlier versions may experience this problem.28.04.2019 19:00:0002.05.2019 17:00:00
    OneDrive for BusinessPost-incident report published01.05.2019 23:28:047Can’t sync changes to Office documentsUsers may be unable to sync recent Office document changes to OneDrive for Business.Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within OneDrive for Business.We’re continuing to monitor the service while the fix completes deployment and anticipate that it will finish within 24 hours.Any of your users that are using Office 2013 client or earlier versions may experience this problem. 28.04.2019 19:00:0002.05.2019 01:00:00
    SharePoint OnlinePost-incident report published01.05.2019 23:27:307Can't sync changes to Office documentsUsers may be unable to sync recent Office document changes to SharePoint Online sites.Users operating Office 2013 or earlier clients may experience this issue when making edits to existing Office documents or editing newly created Office documents with a target save location within SharePoint Online.We’re continuing to monitor the service while the fix completes deployment and anticipate that it will finish within 24 hours.Any of your users that are using Office 2013 client or earlier versions may experience this problem. 28.04.2019 19:00:0002.05.2019 01:00:00
    Exchange OnlineService restored01.05.2019 21:35:417Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).We've deployed additional capacity within the environment and the provisioning for these machines is 90 percent complete. In parallel, we're investigating a potential performance issue that could be contributing to this problem and are evaluating our mitigation options.Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:0002.05.2019 20:00:00
    OneDrive for BusinessPost-incident report published01.05.2019 20:33:307Can’t sync changes to Office documentsUsers may be unable to sync recent Office document changes to OneDrive for Business.This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions. We’ve identified that a recent service update is inadvertently causing issues syncing Office document changes to OneDrive for Business. We’ve developed and have begun deploying a fix for this issue to the affected environment. We expect this process may require 24 – 48 hours to complete.Your organization is affected by this event, and impact is reportedly limited to a few users.02.05.2019 19:00:00
    SharePoint OnlinePost-incident report published01.05.2019 20:28:507Can't sync changes to Office documentsUsers may be unable to sync recent Office document changes to SharePoint Online sites.This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions. We’ve completed developing the fix and have begun deploying it to the affected environment. We expect this process may require 24 – 48 hours to complete.Your organization is affected by this event, and impact is reportedly limited to a few users.02.05.2019 19:00:00
    SharePoint OnlinePost-incident report published01.05.2019 04:26:357Can't sync changes to Office documentsUsers may be unable to sync recent Office document changes to SharePoint Online sites.This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions. We've confirmed that the issue is the result of a recent update. We're developing a fix which will be applied throughout the affected infrastructure upon completing all required validation checks.Your organization is affected by this event, and impact is reportedly limited to a few users.01.05.2019 19:00:00
    SharePoint OnlinePost-incident report published01.05.2019 01:29:477Can't sync changes to Office documents Users may be unable to sync recent Office document changes to SharePoint Online sites.This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions. We've tentatively confirmed that a recent update has inadvertently degraded the service. We're working to confirm the exact cause and to develop and test a fix to address this issue.Your organization is affected by this event, and impact is reportedly limited to a few users.01.05.2019 06:30:00
    SharePoint OnlinePost-incident report published01.05.2019 00:58:337Can't sync changes to Office documents Users may be unable to sync recent Office document changes to SharePoint Online sites.This issue appears limited to existing Office documents only and will only occur within the Office 2013 client or earlier versions. We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.Your organization is affected by this event, and impact is reportedly limited to a few users.
    Exchange OnlineService restored30.04.2019 20:36:528Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).We're adding additional capacity to help process trace requests more efficiently. In parallel, we're continuing to apply traffic routing optimizations and run a clean-up script for previously-logged message trace results to provide more immediate relief.Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:0001.05.2019 20:00:00
    Exchange OnlineService restored30.04.2019 03:00:398Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).We're preparing to implement a series of traffic routing optimizations within the affected environment. Additionally, we're running the script to clean up previously-logged message trace results in an effort to provide additional relief.Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:0030.04.2019 20:00:00
    Skype for BusinessService degradation29.04.2019 22:53:419Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Specifically, users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web, the Outlook client for Mac, or the iOS mobile app.We've developed a long-term fix for this issue and we're working to validate this internally before initiating a deployment to the affected environment.This issue could potentially affect any of your users if they are routed through the affected infrastructure.25.03.2019 14:25:0006.05.2019 21:00:00
    Exchange OnlineService restored29.04.2019 21:22:359Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).We're continuing our efforts to install additional monitoring functionality within the affected environment to identify the potential cause. Concurrently, we're working to implement additional traffic routing optimizations within the environment to alleviate the message trace latency and reporting issues. We're also preparing to run a script to clean up previously-logged message trace results as a secondary mitigation effort.Impact is specific to admins in your organization attempting to view message trace results or utilize the message trace UI.15.04.2019 17:00:0030.04.2019 02:00:00
    Exchange OnlineService restored26.04.2019 20:17:2612Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).We're continuing to make improvements on the impacted infrastructure to restore the service. In parallel, we've confirmed that the additional improvements have begun draining the affected queues.Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:0029.04.2019 20:00:00
    Skype for BusinessService restored26.04.2019 17:55:1112Can't add Skype contactsUsers were unable to add federated Skype contacts.All Skype for Business users who were enabled for Skype federation may have been affected.12.03.2019 22:18:00We've determined that a recent change intended to filter conversations without timestamps resulted in contact invites being filtered out as well. We've reverted the affecting change and confirmed that contact invites send as expected and impact is remediated.This is the final update for the event.
    Skype for BusinessService restored26.04.2019 11:09:4212Can't add Skype contactsUsers are unable to add federated Skype contacts.We've enabled a change, which will render the invite notifications within an hour. We're developing a full remediation plan to allow invite notifications to render instantly.All Skype for Business users who are enabled for Skype federation may be affected.26.04.2019 17:00:00
    Office 365 PortalService restored26.04.2019 05:25:1112Usage report content delaysAdmins may have noticed that some usage reports were only showing data prior to April 17, 2019.The impacted reports may have included Exchange Online usage reports and OneDrive for Business activity reports.This issue may have impacted any admin attempting to view the affected reporting data.20.04.2019 22:00:00We've confirmed that the backlog has processed and that the issue has been remediated.This is the final update for the event.
    Office 365 PortalInvestigation suspended26.04.2019 03:29:4612Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.Admins may notice that group property information may appear blank. While we're focused on resolving the issue, admins can use the Exchange admin center or Remote PowerShell to edit the property settings.Impact is specific to a subset of users who are served through the affected infrastructure.22.04.2019 02:57:00The deployment of the fix has completed and our testing indicates that the ability to edit group properties using the Microsoft 365 admin center has been restored. Once you've validated that the issue has been resolved, please contact support to provide confirmation that the issue has been resolved.This is the final update for the event.
    Exchange OnlineService restored25.04.2019 20:55:2813Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).We're continuing to implement additional monitoring tools to aid our investigation of the underlying problem. Additionally, we've made infrastructural improvements that should improve the end-user experience and limit impact associated with the event. We're monitoring the rate in which message trace requests are processing to confirm the improvements have helped.Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:0026.04.2019 20:00:00
    Skype for BusinessService restored25.04.2019 10:43:1113Can't add Skype contactsUsers are unable to add federated Skype contacts.We've identified that there are two issues manifesting in the same impact. One scenario where the client receives the federated invite but it does not appear, and the other scenario where the chat service does not send the invite. We've reproduced the issue in a test environment to gather detailed client logs and are reviewing the logs to formulate a remediation plan.All Skype for Business users who are enabled for Skype federation may be affected.26.04.2019 10:00:00
    Exchange OnlineFalse positive25.04.2019 09:13:1113Can't access emailN/AThe investigation is complete and we've determined the service is healthy. A service incident did not actually occur.
    Office 365 PortalService restored25.04.2019 05:35:1013Usage report content delaysAdmins may notice that some usage reports only show data prior to April 17, 2019.The impacted reports may include Exchange Online usage reports and OneDrive for Business activity reports.We're continuing to process the backlog, which is taking longer than expected. We're working to identify solutions to expedite the process and we'll provide an estimated timeline as soon as one is available. This issue may impact any admin attempting to view the affected reporting data.20.04.2019 22:00:00An unexpected delay occurred during source data transmission, which has resulted in a backlog of data and subsequent impact to report freshness.26.04.2019 05:00:00
    Office 365 PortalInvestigation suspended25.04.2019 05:18:2813Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.Admins may notice that group property information may appear blank. While we're focused on resolving the issue, admins can use the Exchange admin center or Remote PowerShell to edit the property settings.We developed a fix and have determined that it resolves the problem. We have started to deploy the fix; however, we have identified an issue that is delaying the deployment process. We're working to address the delay and any other unforeseen issues affecting the deployment.Impact is specific to a subset of users who are served through the affected infrastructure.26.04.2019 05:00:00
    Exchange OnlineFalse positive25.04.2019 01:34:3113We've identified a potential issue impacting availability of the Exchange Online service. We're reviewing diagnostic and telemetry data to isolate the cause of the problem. We'll provide an update within 60 minutes.
    Skype for BusinessService restored24.04.2019 21:55:0314Can't add Skype contactsUsers are unable to add federated Skype contacts.We've identified that the service is not properly sending invites to the Skype users. We're working to identify what is causing the invite delivery to fail. All Skype for Business users who are enabled for Skype federation may be affected. 25.04.2019 10:00:00
    Exchange OnlineService restored24.04.2019 21:17:5214Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).Our monitoring of system logs indicates that the additional optimizations implemented to reduce impact did not yield the anticipated relief, as some users may continue to experience results latency up to six hours. We're implementing additional monitoring tools to the affected infrastructure to enhance the process of isolating the cause of the spike in traffic load and develop our next troubleshooting steps.Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:0025.04.2019 20:00:00
    Skype for BusinessService restored24.04.2019 20:21:4014Can't add Skype contactsUsers are unable to add federated Skype contacts.We're reviewing available support case data while we review related incidents to determine our next troubleshooting steps.All Skype for Business users who are enabled for Skype federation may be affected. 24.04.2019 20:30:00
    Skype for BusinessService restored24.04.2019 19:58:0914Can't add Skype contactsUsers are unable to add federated Skype contacts.We're investigating a potential issue with the Skype for Business service. We'll provide an update within 30 minutes.All Skype for Business users who are enabled for Skype federation may be affected.
    Exchange OnlineService restored24.04.2019 17:59:4414Message trace functionality issuesAdmins may experience issues with message trace reports and services that utilize message trace functionality.Affected admins will experience this issue when requesting message trace reports within the Exchange admin center (EAC) and PowerShell, and when utilizing the message trace User Interface (UI) within the Security and Compliance Center (SCC).We've confirmed that our initial efforts to mitigate latency caused by the additional traffic spike did not successfully resolve the issue. We've implemented additional optimizations to further reduce impact while working to identify the cause of the traffic spike, and we’re monitoring system logs to determine if this configuration change will help alleviate the latency issue. If our testing proves to be successful, we’ll be implementing the configuration change to the remaining impacted infrastructure. In addition, we're continuing to identify the cause of the traffic spikes. Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:0024.04.2019 20:00:00
    Exchange OnlinePost-incident report published24.04.2019 12:08:0714A post-incident report has been published.
    Office 365 PortalInvestigation suspended24.04.2019 11:03:2114Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.Admins may notice that group property information may appear blank. While we're focused on resolving the issue, admins can use the Exchange admin center or Remote PowerShell to edit the property settings.We’ve determined that a code regression within the infrastructure resulted in a missing configuration within the admin centre URL, which caused impact. We’re developing a fix to update the configuration, which will be tested and deployed to the affected environment to mitigate impact. Once the fix is developed and tested, deployment will take approximately 3 hours to complete.Impact is specific to a subset of users who are served through the affected infrastructure.25.04.2019 05:00:00
    Office 365 PortalInvestigation suspended24.04.2019 09:25:3214Can't edit group propertiesAdmins may be unable to edit group properties using the Microsoft 365 admin center.Admins may notice that group property information may appear to be blank. While we're focused on resolving the issue, admins can utilize the Exchange admin center or Remote PowerShell to edit the property settings.We're continuing to review network trace logs and system health information to determine the next troubleshooting steps.Your organization is affected by this event, and this issue could affect any of your admins that are attempting to edit group properties.24.04.2019 09:30:00
    Office 365 PortalInvestigation suspended24.04.2019 08:11:5314Can't edit group properties Admins may be unable to edit group properties using the Microsoft 365 admin center. Admins may notice that group property information may appear to be blank. While we're focused on resolving the issue, admins can utilize the Exchange admin center or Remote PowerShell to edit the property settings.We're reviewing network traces gathered from your organization to determine the source of the issue.Your organization is affected by this event, and this issue could affect any of your admins that are attempting to edit group properties.24.04.2019 08:30:00
    Office 365 PortalService restored24.04.2019 05:22:3914Usage report content delaysAdmins may notice that some usage reports only show data prior to April 17, 2019.The impacted reports may include Exchange Online usage reports and OneDrive for Business activity reports. We've received reports of an issue in which admins may be unable to view some usage report data on or after April 17, 2019. Our investigation has determined that an unexpected delay occurred during the source data transmission, which resulted in a backlog and subsequent impact to report freshness. We've confirmed that the source data stream is no longer experiencing delays and we're currently working to process the backlog to resolve the issue.This issue may impact any admin attempting to view the affected reporting data. 20.04.2019 22:00:00An unexpected delay occurred during the source data transmission process, which has resulted in a backlog of data.25.04.2019 05:00:00
    Exchange OnlineService restored23.04.2019 22:31:3915Can't view message tracesAdmins may have been unable to view message trace results in the Exchange admin center (EAC) or PowerShell.Admins may have used the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and was not impacted by this incident.Impact was specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:00We've completed our initial monitoring and have determined that the issue is resolved.This is the final update for the event.
    Exchange OnlineService restored23.04.2019 00:37:4015Can't view message tracesAdmins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.While we work to confirm that the remainder of impact is mitigated, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.We’ve confirmed that a configuration issue is not the cause of the additionally reported impact; though, we’ve isolated a source of high traffic directed to the environment that’s causing the additional message trace search latency for some admins. We’ve rebalanced traffic to account for the increased load and will continue monitoring the service to ensure this fully resolves the problem. Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:00A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog. An additional subset of the environment was also affected by an unexpected source of high traffic, which further exacerbated the backlog for some admins.23.04.2019 22:00:00
    Skype for BusinessService degradation22.04.2019 22:43:2416Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through various Outlook services.Specifically, users may be unable to create Skype for Business meetings for Outlook events through Outlook on the web, the Outlook client for Mac, or the iOS mobile app.We're continuing to develop and validate a long-term fix for this issue, which is expected to be completely deployed by Friday, May 10, 2019, at 12:00 PM UTC. If users are experiencing issues when utilizing the provided workaround, please contact support and discuss the issues with the workaround and provide available network trace data so a short-term fix may be implemented manually.This issue could potentially affect any of your users if they are routed through the affected infrastructure.25.03.2019 14:25:0029.04.2019 21:00:00
    Exchange OnlineService restored22.04.2019 22:07:4716Can't view message tracesAdmins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.While we work to confirm that this issue has been resolved, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.We've identified a potential configuration issue that may be contributing to remaining impact. We're working to confirm our findings and identify the most expedient means to fully resolve the problem.Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:00A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog.23.04.2019 00:00:00
    Exchange OnlineService restored21.04.2019 20:30:0417Can't view message tracesAdmins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.While we work to confirm that this issue has been resolved, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.We've verified that the message trace backlog we had identified within our service has been processed, and we're requesting admins that had reported this problem confirm the issue is fully resolved.Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:00A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog.22.04.2019 20:00:00
    Exchange OnlineService restored19.04.2019 20:25:5219Can't view message tracesAdmins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.While we work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.We're continuing to monitor the progress of the backlog as it processes. We suspect this will take some additional time to reach mitigation.Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:0021.04.2019 20:00:00
    Exchange OnlineService restored18.04.2019 21:16:4820Can't view message tracesAdmins may be unable to view message trace results in the Exchange admin center (EAC) or PowerShell.While we work to resolve the issue with real time message trace, admins can use the extended message trace option (also known as a historical message trace) as an alternative method. This provides full trace details in a downloadable CSV file format, and is not impacted by this incident.We've determined that a temporary problem occurred on a portion of infrastructure that generates message trace data, which created a message trace backlog. The backlog of messages traces are processing and we're monitoring the process to ensure it completes as expected.Impact is specific to admins in your organization attempting to view message trace results in the Exchange admin center (EAC) or PowerShell.15.04.2019 17:00:00A problem occurred on a portion of infrastructure that generates message trace data, which caused a message trace backlog.19.04.2019 19:00:00
    Skype for BusinessService degradation18.04.2019 16:47:3520Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.Whilst we're continuing to validate a fix for this issue we believe that the fix will be completely deployed by Friday, May 10, 2019, at 12:00 PM UTCThis issue could potentially affect any of your users if they are routed through the affected infrastructure.25.03.2019 14:25:0022.04.2019 21:00:00
    Exchange OnlineService restored18.04.2019 01:00:0120Can't run message tracesAdmins may be unable to run message traces.This issue occurs when using third-party apps, the Exchange admin center (EAC), and PowerShell.We're gathering system diagnostic and tenant database information to determine the underlying cause of the issue.Your organization is affected by this event, and any admin may be impacted.18.04.2019 19:00:00
    Exchange OnlineService restored18.04.2019 00:22:3520Can't run message tracesAdmins may be unable to run message traces.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.Your organization is affected by this event, and any admin may be impacted.
    Exchange OnlineService restored17.04.2019 18:17:0521Unable to send email due to SPFUsers may have been intermittently unable to send email to some domains.Users may have received a Non-Delivery Report (NDR) stating "550 5.7.23 The message was rejected because of Sender Policy Framework violation."Impact was limited to users routed through a specific IPv6 range, which would only have affected a subset of your organization.16.04.2019 20:00:00We’ve confirmed via additional monitoring and environment testing that the problem is fixed, and users will no longer experience this issue.This is the final update for the event.
    Exchange OnlineService restored17.04.2019 04:58:1621Unable to send email due to SPFUsers may be intermittently unable to send email to some domains.Users may receive an Non-Delivery Report (NDR): "550 5.7.23 The message was rejected because of Sender Policy Framework violation."Our monitoring and testing continues to indicate that impact has been remediated. We'll perform extended validation over the next several hours to confirm that the issue is resolved. Impact is specific to users routed through a specific IPv6 range, therefore we expect that a subset of your users may be impacted by this issue. 16.04.2019 20:00:00A recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range. 17.04.2019 17:00:00
    Exchange OnlineService restored17.04.2019 03:53:2921Unable to send email due to SPFUsers may be intermittently unable to send email to some domains.Users may receive an Non-Delivery Report (NDR): "550 5.7.23 The message was rejected because of Sender Policy Framework violation."Our initial monitoring and testing indicates that users should no longer be experiencing impact related to this event. We're performing additional monitoring to confirm issue resolution. Impact is specific to users routed through a specific IPv6 range, therefore we expect that a subset of your users may be impacted by this issue. 16.04.2019 20:00:00A recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range. 17.04.2019 04:00:00
    Exchange OnlineService restored17.04.2019 02:08:5221Unable to send email due to SPFUsers may be intermittently unable to send email to some domains.Users may receive an Non-Delivery Report (NDR): "550 5.7.23 The message was rejected because of Sender Policy Framework violation."We received reports indicating an issue in which users were unable to send email to some domains and were receiving a Sender Policy Framework (SPF) validation error. We determined that a recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range. We reverted the optimization and are monitoring the service to confirm that the issue is resolved. Impact is specific to users routed through a specific IPv6 range, therefore we expect that a subset of your users would be impacted but this issue.A recent IP address optimization inadvertently caused a subset of infrastructure to not route email as expected due to an incorrectly configured IP range. 17.04.2019 02:00:00
    Office OnlineService restored16.04.2019 23:22:2322Can't save Word documentsUsers may have experienced errors when attempting to save their Word documents using Office Online.While we were focused on resolving the issue, users could have used the Microsoft Word desktop client as a workaround. Additionally, users may have seen an error message banner at the top of their browser window.This issue could have potentially affected any of your users that were attempting to save Word documents using Office Online.15.04.2019 17:30:00Service availability has kept stable through North and South American business hours, indicating that impact has been completely mitigated.This is the final update for the event.
    Skype for BusinessService restored16.04.2019 20:47:2422Not receiving push notificationsUsers may have been intermittently not receiving Skype for Business app push notifications on Android and iOS devices.This issue may have affected approximately 50 percent of Skype for Business app push notifications on Android and iOS devices for any of your users.12.04.2019 12:00:00We've determined that a portion of infrastructure that facilitates Skype for Business app push notifications to Android and iOS devices became degraded, causing impact. We restarted the affected infrastructure and confirmed that push notifications returned to normal levels.This is the final update for the event.
    Skype for BusinessService restored16.04.2019 20:18:5822Not receiving push notificationsUsers may be intermittently not receiving Skype for Business app push notifications on Android and iOS devices.Up to 50 percent of push notifications may be affected by this issue.We're analyzing system logs to determine why the push notifications aren't being delivered as expected and develop the next troubleshooting steps.This issue may intermittently affect any of your users expecting to receive Skype for Business app push notifications on Android and iOS devices.12.04.2019 12:00:0016.04.2019 20:00:00
    Office OnlineService restored16.04.2019 17:30:0222Can't save Word documentsUsers may experience errors when attempting to save their Word documents using Office Online.While we're focused on resolving the issue, users can use the Microsoft Word desktop client as a workaround. Additionally, users may see an error message banner at the top of their browser window.We've completed reverting the most recent Office Online version that we suspect led to the impact. While we've not seen additional examples of the problem during peak business hours in Asia and Europe, we'll continue to monitor through peak North and South American business hours to ensure the impact is completely mitigated.This issue could potentially affect any of your users that are attempting to save Word documents using Office Online.15.04.2019 17:30:0017.04.2019 23:00:00
    Exchange OnlinePost-incident report published16.04.2019 17:25:3822Can't see message tracesAdmins may have been unable to see message trace details in the Exchange admin center or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may have been impacted by this event as well; however, we extended the quarantine message expiration time during the impact period to ensure all impacted logs were processed before the expiration time.Any admin may have been unable to view message trace details or access reports and logs within the SCC.01.04.2019 22:50:00A subset of networking infrastructure responsible for processing message traces and other reporting features was performing in a degraded state, preventing message traces from being viewed. Subsequently, a large number of requests were backlogged and required an extended time to process.We've completed our validation activity and have confirmed that service has been restored. Additionally, the backlog between April 3 and April 7, 2019, has been processed.We'll publish a post-incident report within five business days.
    Office OnlineService restored16.04.2019 08:11:0022Can't save Word documentsUsers may experience errors when attempting to save their Word documents using Office Online.While we're focused on resolving the issue, users can use the Microsoft Word desktop client as a workaround. Additionally, users may see an error message banner at the top of their browser window.We've begun rolling back the Office Online version on the affected infrastructure as a preliminary troubleshooting step. Additionally, we're rerouting traffic from impacted infrastructure to alternate resources to provide relief to users while we continue to investigate the possible causes of this issue.This issue could potentially affect any of your users that are attempting to save Word documents using Office Online.17.04.2019 17:00:00
    Office OnlineService restored16.04.2019 04:56:2122Can't save Word documentsUsers may experience errors when attempting to save their Word documents using Office Online.While we're focused on resolving the issue, users can use the Microsoft Word desktop client as a workaround. Additionally, users may see an error message banner at the top of their browser window.Our monitoring indicates that there is an issue in which users may be unable to save their Word documents using the Office Online service. We're looking into multiple avenues that may be causing impact to determine our next steps.This issue could potentially affect any of your users that are attempting to save Word documents using Office Online.16.04.2019 07:00:00
    Exchange OnlinePost-incident report published16.04.2019 01:50:0722Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.We're performing an extended validation of the processed data to confirm that the issue is resolved. Any admin may be unable to view message trace details or access reports and logs within the SCC.A subset of networking infrastructure responsible for processing message traces and other reporting features is performing in a degraded state.16.04.2019 21:00:00
    Skype for BusinessService degradation15.04.2019 22:51:3823Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added. We're continuing to validate a fix for this issue and are working on a deployment schedule. We suspect that the fix will be fully deployed sometime in May, and aim to provide a more solidified estimate next week.This issue could potentially affect any of your users if they are routed through the affected infrastructure.22.04.2019 21:00:00
    Exchange OnlinePost-incident report published15.04.2019 19:18:3923Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.The backlog between April 4 and April 7, 2019, has been processed. We're conducting our final validation steps to ensure that service has been fully restored.Any admin may be unable to view message trace details or access reports and logs within the SCC.16.04.2019 00:00:00
    Skype for BusinessPost-incident report published15.04.2019 13:22:3023A post-incident report has been published.
    Exchange OnlinePost-incident report published13.04.2019 20:27:1625Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.We've confirmed that 85 percent of the remaining backlogs, which contains message trace details from April 4 through April 7, 2019, has processed. Based on current progress, we anticipate that the backlogs will process and the issue will be resolved by Monday, April 15, 2019. While we monitor, we're continuing to evaluate whether any actions can be taken to expedite resolution. Any admin may be unable to view message trace details or access reports and logs within the SCC.15.04.2019 19:00:00
    Yammer EnterpriseService restored13.04.2019 01:06:4625Can't view live events on mobile appsUsers may have been unable to view live events via iOS and Android clients.Any users attempting to view live events via mobile clients may have been affected.12.04.2019 18:14:00We determined that a recent service update caused an issue with backward compatibility for viewing live events. We've developed and deployed a code fix for the service update that has restored live event viewing functionality.This is the final update for the event.
    Yammer EnterpriseService restored13.04.2019 00:33:2225Can't view live events on mobile appsUsers may be unable to view live events via iOS and Android clients.We're currently reviewing system logs to identify the cause.Any users attempting to view live events via mobile clients may be affected.12.04.2019 18:14:0013.04.2019 00:00:00
    Yammer EnterpriseService restored13.04.2019 00:16:4425Can't view live events on mobile appsUsers may be unable to view live events via iOS and Android clients.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    Skype for BusinessService degradation13.04.2019 00:15:3125Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.We're actively working to ensure the best course of action of implementing the fix to the entirety of the affected infrastructures. We're also actively working to establish an optimal resolution time for deployment.This issue could potentially affect any of your users if they are routed through the affected infrastructure.15.04.2019 21:00:00
    Skype for BusinessService restored12.04.2019 21:54:4126Can't join or delays joining conferences via Public Switched Telephone Network (PSTN)Users may have been unable to join or experience delays of up to 12 seconds when joining conference calls via PSTN.This issue potentially affected any of your users attempting to join conference calls when using PSTN.12.04.2019 16:37:00Our investigation determined that a service update being deployed to the feature that helps facilitate conference PSTN calls contained a code issue. We successfully halted the update and confirmed internally that service is restored.This is the final update for the event.
    Skype for BusinessService restored12.04.2019 20:58:1426Can't join or delays joining conferences via Public Switched Telephone Network (PSTN)Users may be unable to join or experience delays of up to 12 seconds when joining conference calls via PSTN.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    Exchange OnlinePost-incident report published12.04.2019 20:55:2026Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.We've confirmed that 75 percent of the backlog from April 4, 2019 has processed. We're exploring quicker methods to increase the processing rate of the remaining backlogs in an effort to expedite complete resolution of this problem. We anticipate we will have a more detailed timeline to resolution by tomorrow, April 13, 2019. Any admin may be unable to view message trace details or access reports and logs within the SCC.13.04.2019 19:00:00
    Yammer EnterpriseService restored12.04.2019 14:52:0226Can't use Search function.Users were unable to use the Search function within Yammer.Impact was specific to a subset of users who were served through the affected infrastructure.12.04.2019 06:55:00We've routed traffic routed to alternate infrastructure and applied the new certificate. We've confirmed that the issue is resolved after monitoring the environment.This is the final update for the event.
    Skype for BusinessService restored12.04.2019 13:50:3026Unable to join PSTN conference callsUsers were unable to join Public Switched Telephone Network (PSTN) conference calls.Impact was specific to users who were served through the affected infrastructure.12.04.2019 08:55:00We've determined during a routine update procedure, user requests were sent to a subset of PSTN processing infrastructure, which was not correctly configured to handle the user requests. We've monitored the service whilst the update has propagated throughout the environment and the infrastructure was reconfigured to handle the user requests, remediating impact.This is the final update for the event.
    Yammer EnterpriseService restored12.04.2019 13:33:1726Can't use Search function.Users are unable to use the Search function within the Yammer service.We continue to apply the new certificate. Additionally, we're rerouting traffic to alternate infrasturue to ensure full remediation. Impact is specific to a subset of users who are served through the affected infrastructure.12.04.2019 06:55:0012.04.2019 15:00:00
    Skype for BusinessService restored12.04.2019 12:20:2026Unable to join PSTN conference callsUsers are unable to join Public Switched Telephone Network (PSTN) conference calls.We're investigating service telemetry data to isolate the cause of the issue.Impact is specific to users who are served through the affected infrastructure.12.04.2019 08:55:0012.04.2019 13:00:00
    Yammer EnterpriseService restored12.04.2019 11:47:5026Can't use Search function.Users are unable to use the Search function within the Yammer service.We've identified that an expired certificate is the cause of impact. We're applying a new certificate to remediate impact. Impact is specific to a subset of users who are served through the affected infrastructure.12.04.2019 06:55:0012.04.2019 12:00:00
    Yammer EnterpriseService restored12.04.2019 11:06:5326Can't use Search function.Users are unable to use the Search function within the Yammer service.We're reviewing support case data to determine the next troubleshooting steps.Impact is specific to a subset of users who are served through the affected infrastructure.12.04.2019 10:30:00
    Yammer EnterpriseService restored12.04.2019 01:42:2226Can't load feedsUsers may have been unable to load their feeds on Yammer.com.We deployed a fix to the affected environment and confirmed that the impact was remediated.11.04.2019 22:20:00We deployed a fix to the affected environment and confirmed that the impact was remediated.This is the final update for the event.
    Yammer EnterpriseService restored12.04.2019 01:07:3626Can't load feedsUsers may be unable to load their feeds on Yammer.com.We've detected that a recent database configuration change is causing unexpected impact for Yammer.com. We're reviewing server logs to to determine the best method of restoring service.Your organization is affected by this event, and the issue could impact any user using Yammer.com11.04.2019 22:20:0012.04.2019 01:00:00
    Office 365 PortalService restored12.04.2019 00:55:5526Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.The existing Skype for Business functionality was unaffected throughout this event. While we were fixing the underlying problem, affected customers could follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-installThis may have affected a limited subset of customers who chose to exclude Teams installation and were part of specific builds. The build information was included in the install documentation above.04.03.2019 12:00:00We've confirmed that our fix has reached all affected customers and that the incident is resolved.This is the final update for the event.
    Skype for BusinessService degradation11.04.2019 23:34:5426Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.We're continuing to work on implementing the fix to correct the configuration issue on the affected infrastructure. In parallel, we're still attempting to establish an estimated time to resolution as we progress closer to the deployment throughout the affected environments.This issue could potentially affect any of your users if they are routed through the affected infrastructure.12.04.2019 22:30:00
    Exchange OnlinePost-incident report published11.04.2019 23:22:0727Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.This is an incremental update to provide the latest status on the issue.The backlog has been processed for April 3 and we've processed 65 percent of the backlog for April 4. We anticipate that the entirety of the backlog through April 7, 2019, will be fully processed by Monday, April 15, 2019. For complete details on this event, please reference the post from 6:03 PM UTC on April 9, 2019.12.04.2019 19:00:00
    SharePoint OnlineService restored11.04.2019 01:54:1727SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may have been unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.Affected admins may have received an error indicating that the request uses too many resources.Impact was specific to administrators performing various tasks in the admin center and through Remote PowerShell.08.04.2019 12:00:00A code issue caused the infrastructure responsible for site provisioning and Remote PowerShell to become degraded.We identified and disabled a code issue that was causing impact to the infrastructure responsible for site provisioning and Remote PowerShell.This is the final update for the event.
    Office 365 PortalService restored11.04.2019 00:49:3427Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-installWe're continuing our efforts to ensure that our fix has reached all affected customers as expected.This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.04.03.2019 12:00:0012.04.2019 02:00:00
    SharePoint OnlineService restored11.04.2019 00:29:1427SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may be unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.Affected admins may receive an error indicating that the request uses too many resources.We’ve reviewed our code and have identified a potential fix for this problem. We're continuing to troubleshoot to confirm that our fix is a viable solution for this issue.Impact is specific to administrators performing various tasks in the admin center and through Remote PowerShell.11.04.2019 00:30:00
    Skype for BusinessService degradation10.04.2019 23:57:0027Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users click on the "Create Skype for Business meeting" button in Outlook on the web; however, no Skype for Business meeting details are added.We've determined that a network misconfiguration occurred on a portion of infrastructure that facilitates communication between the Skype for Business and Exchange Online services, which caused impact to Skype for Business meeting creation functionality via Outlook on the web. We're implementing a fix to correct the configuration issue on the affected infrastructure, and we’re assessing how long the fix will take to fully resolve the event.This issue could potentially affect any of your users if they are routed through the affected infrastructure. 11.04.2019 23:00:00
    Yammer EnterpriseService restored10.04.2019 22:52:2628Sign in errorsUsers may experience sign in errors when attempting to access Yammer.Users may have seen a "Retry later" page.Any users attempting to access Yammer may have been impacted.10.04.2019 17:40:00We've verified the configuration changes have resolved the issue.This is the final update for the event.
    Yammer EnterpriseService restored10.04.2019 21:50:3628Sign in errorsUsers may experience sign in errors when attempting to access Yammer.Users may see a "Retry later" page.We've identified that traffic is not being routed as expected, preventing users from signing in. We're currently deploying a configuration change to reprioritize traffic and mitigate impact.Any users attempting to access Yammer may be impacted.10.04.2019 21:00:00
    Yammer EnterpriseService restored10.04.2019 21:18:5928Sign in errorsUsers may experience sign in errors when attempting to access Yammer.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    SharePoint OnlineService restored10.04.2019 20:40:5528SharePoint Online (SPO) admin center site provisioning and Remote PowerShell commands impactAdmins may be unable to provision sites through the SPO admin center or run certain Remote PowerShell commands.We’ve determined that there is no resource contention in the environment that would be contributing to the impact. We’re reviewing source code and analyzing additional available system logs to formulate our next troubleshooting steps.Your organization is affected by this event, and impact is specific to administrators.10.04.2019 22:30:00
    Exchange OnlinePost-incident report published10.04.2019 19:09:0828Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.This is an incremental update to provide the latest status on the issue.We've completed processing the remaining 10% of message traces from April 3, 2019 and have begun processing the backlog of message traces from April 4, 2019. We've processed 35% of message traces from April 4, 2019, and expect backlogs to be fully processed by the end of the week. For complete details on this event, please reference the post from 6:03 PM UTC on April 9, 2019.12.04.2019 19:00:00
    SharePoint OnlineService restored10.04.2019 17:01:5728Unable to run certain Remote PowerShell commandsAdmins may be unable to run certain Remote PowerShell commands.Our preliminary findings indicate that there may be an issue regarding resource contention that's causing degraded performances. We're continuing to test the Remote PowerShell commands in a variety of different scenarios, in addition to our continued analysis of the Unified Logging Service (ULS) logs and system logs, to determine the specific cause of the issue.Your organization is affected by this event, and impact is specific to administrators.10.04.2019 19:30:00
    SharePoint OnlineService restored10.04.2019 16:34:4128Unable to run certain Remote PowerShell commandsAdmins may be unable to run certain Remote PowerShell commands.We're testing the Remote PowerShell commands in a variety of different scenarios to determine the specific cause of the issue.Your organization is affected by this event, and impact is specific to administrators.10.04.2019 17:00:00
    SharePoint OnlineService restored10.04.2019 14:57:1128Unable to run certain Remote PowerShell commandsAdmins may be unable to run certain Remote PowerShell commands.We're analyzing Unified Logging Service (ULS) logs to determine the source of the issue.Your organization is affected by this event, and impact is specific to administrators.10.04.2019 15:00:00
    Skype for BusinessService degradation10.04.2019 07:43:1528Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.We've developed a configuration fix and have deployed it to a small subset of the network infrastructure. Testing has confirmed that this change fixes the issue. We're deploying the change to the remaining infrastructure, which may take up to 12 hours to complete.This issue could potentially affect any of your users if they are routed through the affected infrastructure.10.04.2019 22:00:00
    Skype for BusinessService degradation10.04.2019 06:56:2528Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.We've determined that a potential misconfiguration on a subset of the network infrastructure may be incorrectly routing traffic. We're working to develop the necessary configuration changes to fix the issue.This issue could potentially affect any of your users if they are routed through the affected infrastructure.10.04.2019 07:00:00
    Exchange OnlinePost-incident report published10.04.2019 05:14:4828Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.This is an incremental update to provide the latest status on the issue.We're continuing to process the remaining 10% of message traces from April 3, 2019 and will begin processing the backlog of message traces from April 4, 2019 after the remaining message traces from April 3rd are processed. We still expect backlogs from April 4th to be fully processed by the end of the week. For complete details on this event, please reference the post from 6:03 PM UTC on April 9, 2019.10.04.2019 19:00:00
    Skype for BusinessService degradation10.04.2019 04:52:2828Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.We're gathering Transport Control Protocol (TCP) trace information to further isolate the source of the problem.This issue could potentially affect any of your users if they are routed through the affected infrastructure.10.04.2019 05:00:00
    Skype for BusinessService degradation10.04.2019 02:51:3528Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.We're continuing to investigate network diagnostic logs to determine the underlying cause of the issue.This issue could potentially affect any of your users if they are routed through the affected infrastructure.10.04.2019 03:00:00
    Skype for BusinessService degradation10.04.2019 01:10:5328Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.We're investigating network diagnostic logs to determine the underlying cause of the issue.This issue could potentially affect any of your users if they are routed through the affected infrastructure.10.04.2019 01:00:00
    Skype for BusinessService degradation10.04.2019 00:35:3128Can't create Skype for Business meetings for Outlook eventsUsers may be unable to create Skype for Business meetings for Outlook events through Outlook on the web.Affected users will click on the create Skype for Business meeting button in Outlook on the web; however, no Skype for Business meeting details are added.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    Office 365 PortalService restored10.04.2019 00:33:1628Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-installWe're working to verify that our fix has reached all affected customers as expected.This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.04.03.2019 12:00:0011.04.2019 02:00:00
    Exchange OnlinePost-incident report published09.04.2019 20:03:3729Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.The deployment of the solution has fully saturated, and the underlying problem has been fixed. We're still processing a backlog of message traces from April 3, 2019 and April 4, 2019. The backlog of traces from April 3 are expected to be processed by end of day April 9, 2019. Due to the size of the backlog and processing rate, we anticipate that traces from April 4 will be fully processed by the end of the week. Any admin may also be unable to view message trace details or access reports and logs within the SCC.01.04.2019 19:27:0010.04.2019 05:00:00
    Office OnlineFalse positive09.04.2019 13:41:5829Word documents online issueUsers may have been unable to open Word documents online using the Web Application Client.The issue could have potentially impacted, but was no limited to, Microsoft Teams, Outlook on the web, the Outlook client and SharePoint Online services.This issue affected internal Microsoft users only. Impact could have potentially affected any user attempting to open Word documents online using the Web Application Client.08.04.2019 12:30:00We've determined an update to the Web Application Client (WAC) service inadvertently impacted opening Word documents within Office Online. We've reverted the update and confirmed that impact has been remediated.This is the final update for the event.
    Office OnlineFalse positive09.04.2019 12:41:2529Word documents online issueUsers may be unable to open Word documents online using the Web Application Client.The issue could potentially impact, but is no limited to, Microsoft Teams, Outlook on the web, the Outlook client and SharePoint Online services.We're analyzing diagnostic data to isolate the source of the issue.This issue affects internal Microsoft users only. Impact could potentially affect any user attempting to open Word documents online using the Web Application Client (WAC).09.04.2019 12:30:00
    Skype for BusinessService restored09.04.2019 00:21:0729Can't dial in or out of audio conferences intermittentlyUsers may have been unable to dial in or out of audio conferences intermittently.Impact was specific to users attempting to dial in using a Public Switched Telephone Network (PSTN).This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure.08.04.2019 16:56:00Our investigation showed that a subset of infrastructure responsible for processing the PSTN audio conferencing calls was performing in a degraded state. Our automated systems restarted the affected infrastructure and we verified internally that service had fully restored once fully completed.This is the final update for the event.
    Exchange OnlinePost-incident report published08.04.2019 19:29:1330Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time.The initial restoration of the backlogs were incomplete, and the process had to be restarted. The backlog for all message trace details through Tuesday, April 2, 2019, have been processed, and the backlog for April 3 and 4 are currently being processed. Additionally, we're continuing to monitor deployment of the fix. We have no ETA at this time. Any admin may also be unable to view message trace details or access reports and logs within the SCC.01.04.2019 19:27:0009.04.2019 18:00:00
    Skype for BusinessPost-incident report published08.04.2019 11:52:5430Audio/video calling problemsUsers may have been unable to initiate and accept Skype for Business audio and video calls.Users may have also been unable to initiate and join meetings or meetings may have take a long time to load. Users who use Public Switched Telephone Network (PSTN) would also have been affected when attempting to dial-in or dial-out of audio conference calls. This issue may have potentially affected any of your users attempting to make audio and video calls, or initiate and join meetings.08.04.2019 06:55:00We determined that a service update designed to improve performance inadvertently caused user requests to fail. We restarted the affected Business Voice Directory (BVD) service instances, which mitigated impact.This is the final update for the event.
    Skype for BusinessPost-incident report published08.04.2019 10:46:3430Audio/video calling problemsUsers may be unable to initiate and accept Skype for Business audio and video calls.Users may also be unable to initiate and join meetings or meetings may take a long time to load. Users who use Public Switched Telephone Network (PSTN) will also be affected. We've identified high user request error rates and we're continuing our analysis of system logs to determine what is causing this.This issue may potentially affect any of your users attempting to make audio and video calls, or initiate and join meetings.08.04.2019 10:30:00
    Skype for BusinessPost-incident report published08.04.2019 10:17:4830Audio/video calling problemsUsers may be unable to initiate and accept Skype for Business audio and video calls.Users may also be unable to initiate and join meetings or meetings may take a long time to load. Users who use Public Switched Telephone Network (PSTN) will also be affected. We're analyzing system logs to determine the source of the issue.This issue may potentially affect any of your users attempting to make audio and video calls, or initiate and join meetings.08.04.2019 09:30:00
    Exchange OnlinePost-incident report published06.04.2019 03:58:0432Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well. Additionally, we're extending the quarantine message expiration time to process all impacted logs before the expiration time. We're continuing to monitor the deployment of the additional solution as it saturates the environment as expected and we're also monitoring the processing of the backlog to ensure all logs impacted by this event are being processed. Additionally, we're continuing to explore additional mitigation options to ensure similar impact is avoided in the future.Any admin may also be unable to view message trace details or access reports and logs within the SCC.01.04.2019 19:27:0008.04.2019 18:00:00
    Exchange OnlinePost-incident report published05.04.2019 20:24:2033Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Additionally, any reporting or logging features within the Security and Compliance Center (SCC) may be impacted by this event as well.The deployment of the additional solution is still ongoing and based on our initial monitoring, some users may see improvements in service performance. We're reviewing monitoring data as the solution saturates to validate service health improvements and that backlogging performance improvement continues.Any admin may also be unable to view message trace details or access reports and logs within the SCC.01.04.2019 19:27:0006.04.2019 03:00:00
    Exchange OnlinePost-incident report published05.04.2019 04:11:5233Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Additionally, admins may also experience similar impact to some reporting and logging features within the Security and Compliance Center (SCC).We've confirmed that the solution is improving backlog processing and we're deploying it throughout the affected infrastructure. Although we expect that this solution will expedite the process, we're evaluating additional optimizations which will be implemented as soon as validation has completed. Any admin could experience this issue if they are attempting to view message trace details. 01.04.2019 19:27:0005.04.2019 19:00:00
    Exchange OnlinePost-incident report published04.04.2019 20:32:4534Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.While our additional code fix has resulted in improvements to denied write requests, it’s been unsuccessful in fully processing the backlogged requests. We’ve developed an additional solution that we’re currently testing in a limited environment. Once we confirm that this solution effectively improves backlog processing, we’ll deploy it to all affected environments.Any admin could experience this issue if they are attempting to view message trace details.01.04.2019 19:27:0005.04.2019 03:00:00
    Exchange OnlinePost-incident report published04.04.2019 03:39:4734Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Our initial fix has been successfully deployed to the impacted infrastructure; however, a different code issue is causing write requests to the affected servers to be inadvertently denied. We've developed a new fix and are deploying it to address the underlying issue and mitigate impact to message traces. We expect the fix to take a few hours to deploy and the backlog of the message trace requests to be drained on Thursday. April 4th, 2019 by 8:00 PM UTC.Any admin could experience this issue if they are attempting to view message trace details.01.04.2019 19:27:0004.04.2019 20:00:00
    Exchange OnlinePost-incident report published03.04.2019 22:40:2235Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Deployment of the fix is nearing completion with a small subset of infrastructure remaining. We're continuing to monitor the deployment until it reaches full saturation. Any admin could experience this issue if they are attempting to view message trace details.01.04.2019 19:27:0004.04.2019 03:00:00
    Exchange OnlinePost-incident report published03.04.2019 19:18:1635Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.The deployment of the fix has reached approximately 98% of the impacted environments at this time. We're continuing to monitor the progress of the deployment. Additionally, we're reaching out to affected users to confirm that they're experiencing resolution as a result of the deployed fix.Any admin could experience this issue if they are attempting to view message trace details.03.04.2019 22:00:00
    Office 365 PortalService restored03.04.2019 03:05:1835Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-installWe've completed the testing process and have initiated deployment to a limited portion of service infrastructure for additional validation. Once complete, we'll deploy the fix throughout the affected environment. This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.04.03.2019 12:00:0010.04.2019 02:00:00
    Exchange OnlinePost-incident report published03.04.2019 02:45:4935Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Our actions to rebalance the resources proved to be an insufficient solution for this problem; however, we've determined the service that helps facilitate message trace details isn't functioning as expected. We've developed a fix and verified that it'll resolve the issue. We're in the process of deploying the fix to a subset of infrastructure to validate that this will resolve the issue. Upon validation, we'll proceed with deployment to the rest of the impacted environments.Any admin could experience this issue if they are attempting to view message trace details.03.04.2019 18:30:00
    Exchange OnlinePost-incident report published02.04.2019 23:31:5835Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.We're continuing to rebalance resources in the environment. We'll validate internally that this action successfully mitigates impact once complete.Any admin could experience this issue if they are attempting to view message trace details.03.04.2019 02:00:00
    Exchange OnlinePost-incident report published02.04.2019 21:31:5136Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.Our analysis shows that a subset of networking infrastructure responsible for processing the trace details is performing in a degraded state. We're working to rebalance resources to mitigate impact. Once complete, we'll conduct an internal test to confirm that service is restored.Any admin could experience this issue if they are attempting to view message trace details.02.04.2019 21:30:00
    Exchange OnlinePost-incident report published02.04.2019 19:36:1336Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.We're attempting to reproduce this issue internally to gather additional data to analyze.Any admin could experience this issue if they are attempting to view message trace details.02.04.2019 19:30:00
    Exchange OnlinePost-incident report published02.04.2019 17:28:4736Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.We're analyzing system logs to determine the source of the issue.Any admin could experience this issue if they are attempting to view message trace details.02.04.2019 17:30:00
    Exchange OnlinePost-incident report published02.04.2019 16:56:4736Can't see message tracesAdmins may be unable to see message trace details in the Exchange admin center (EAC) or PowerShell command window.We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
    Office 365 PortalService restored26.03.2019 02:16:1343Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-installWe've nearly completed the testing process and anticipate that we will be ready to start deployment later this week. We continue to expect this issue to be resolved by April 9, 2019. This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.04.03.2019 12:00:0003.04.2019 02:00:00
    Office 365 PortalService restored19.03.2019 01:21:3350Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-installWe're thoroughly testing our fix in preparation for deployment. Our testing is progressing as anticipated and we continue to expect that the issue will be resolved by April 9, 2019. This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.04.03.2019 12:00:0026.03.2019 02:00:00
    Office 365 PortalService restored13.03.2019 03:19:3556Microsoft Teams install exclusion issue in Office 365 ProPlusAdmins are unable to exclude Microsoft Teams from installing as part of the Office 365 ProPlus installations.The existing Skype for Business functionality remains unaffected. While we're fixing the underlying problem, affected customers can follow the guidance here to mitigate the issue: https://docs.microsoft.com/DeployOffice/teams-installWe've determined that the ExcludeApp setting within the Office Deployment Tool is not working as expected under certain circumstances, which is resulting in Teams being installed in deployments of Office 365 ProPlus, even when Teams was supposed to be blocked. We’re addressing this issue in an update for Microsoft Office 365 ProPlus, which is being prepared for deployment.This may affect a limited subset of customers who chose to exclude Teams installation and are part of specific builds. The build information is included in the install documentation above.04.03.2019 12:00:0019.03.2019 02:00:00
    ServiceStatusPublishedTimePublishedDaysAgoTitleUserImpactMoreInfoCurrentStatusScopeOfImpactStartTimePreliminaryRootCauseNextUpdateByFinalStatusOther
    *
    No data available.
    *
    *
    No data available.
    *