Identified - Microsoft is rolling out deprecation of legacy Exchange tokens that may prevent your users from being able to report emails using the Expel custom Office 365 Phishing button.
Expel is working on development and testing of an updated Expel O365/M365 Phishing button for web and desktop applications that will work with the NAA authentication scheme.
Completed -
The scheduled maintenance has been completed.
Mar 19, 07:00 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 19, 06:00 EDT
Scheduled -
We will be undergoing routine maintenance between 06:00 - 07:00 ET on March 19th. During the maintenance window, Workbench may be intermittently unavailable or slow.
All notifications and alerts will be processed during the maintenance window, but may be affected by intermittent delays.
Mar 13, 12:08 EDT
Resolved -
Microsoft is rolling out deprecation of legacy Exchange tokens that may prevent your users from being able to report emails using the Expel custom Office 365 Phishing button.
Expel is working on development and testing of an updated Expel O365/M365 Phishing button for web and desktop applications that will work with the NAA authentication scheme.
Contact support if you need assistance with this process.
Mar 17, 10:01 EDT
Update -
Microsoft is rolling out deprecation of legacy Exchange tokens that may prevent your users from being able to report emails using the Expel custom Office 365 Phishing button.
Expel is working on development and testing of an updated Expel O365/M365 Phishing button for web and desktop applications that will work with the NAA authentication scheme.
Contact support if you need assistance with this process.
Mar 16, 20:04 EDT
Update -
Phishing submissions continue to be degraded for a small number of customers that use the custom Expel Office 365 button. We have identified the root cause and will be rolling out an update as soon as possible.
If your button isn’t working, talk directly with your Customer Success Manager (CSM), who will be able to offer you direct & tailored support as we work to resolve this. Alternatively, you can submit phishing emails manually. Visit our Help Center for step-by-step instructions.
Mar 15, 08:59 EDT
Identified -
We have identified a potential root cause and are working on a remediation. The Office 365 Phishing Button continues to be degraded. We will provide another update as soon as possible.
Mar 14, 18:30 EDT
Update -
We are continuing to investigate this issue and will provide an update by 6:30PM EDT.
Mar 14, 17:37 EDT
Update -
We are continuing to investigate this issue and will provide an update by 5:30PM EDT.
Mar 14, 17:02 EDT
Update -
We are continuing to investigate this issue and will provide an update by 5:00PM EDT.
Mar 14, 16:32 EDT
Investigating -
We have identified a problem that is preventing Office 365 users from reporting phishing emails to Expel via Outlook. We will provide an update by 4:30PM EDT.
Mar 14, 15:41 EDT
Resolved -
The incident has been resolved, and all systems are once again fully available. No customer data was lost, and SOC operations were not impacted.
Mar 12, 14:01 EDT
Monitoring -
The upstream service provider has resumed healthy service, and we have resumed ingesting alerts. No events were lost during this incident. We will continue monitoring the issue and provide another update by 2:00pm EDT or resolve the incident if we see no further recurrence of the problem.
Mar 12, 13:46 EDT
Update -
We have tentatively identified the root cause as an issue with our upstream service provider. We are continuing to investigate the source of the issue. Alert ingestion from Azure continues to be degraded. SOC operations are not otherwise affected. We will provide another update by 2:00pm EDT.
Mar 12, 13:32 EDT
Update -
We are continuing to investigate the issue. Please expect another update by 1:30pm EDT.
Mar 12, 13:09 EDT
Investigating -
At 12:12pm EDT, we began experiencing a problem with Microsoft Azure security devices that is preventing us from ingesting alerts. We will provide an update by 1:00pm EDT.
Mar 12, 12:41 EDT
Resolved -
This incident has been resolved.
Mar 11, 13:34 EDT
Monitoring -
We have rolled back the code change the caused the issue, and we believe we have resolved the login outage. We will continue monitoring login availability, and will update again or resolve the incident by 2:00pm EDT.
Mar 11, 13:14 EDT
Identified -
We have identified an issue with a recent rollout of code that we believe to be the cause of the outage, and are currently rolling back to the previous known-good version. Please expect another update by 1:30pm EDT.
Mar 11, 13:10 EDT
Investigating -
At 12:40pm EDT, we began experiencing a problem with workbench that is preventing users from logging in. We will provide an update by 1:30pm EDT.
Mar 11, 12:53 EDT