Exchange
June 19, 8:00pm ADT
Network Access and WiFi
Acadia Website
Printing Services
Student Services
Campus Administrative Services
Teaching and Learning Services
Library Services
Browser Services
Colleague Administrative System
Catalog & Accounts
Slate Enrollment Service
Inter Library Loan Services
Moodle (ACORN)
Lime Survey
StarRez Residence Services
myAcadia Online Self Service
WiFi
VPN
Off Campus Access
Co-Op Education Portal (Orbis)
Informer Reporting
Turnitin
WiFi Residence Buildings
Timetable & Exam Scheduling Services
Web Systems
Wifi Administrative/Academic Buildings
HUB Service Portal
Live Chat & Remote Support
Eduroam
Meal Plan Services
Email Services
Door Access & Lock Services
Network Access
Box Office Ticketing & Registration (AudienceView)
Event Management Services (Legend)
Cybersecurity Awareness Training
Acadia Emergency Alert Services
Jun-19, 8:00pm ADT
Date Correction:
Technology Services will be performing scheduled network maintenance on June 19, 8:00pm ADT. The outage is expected to last approximately 60 minutes . During this time, access to campus resources will be unavailable.
Jun-19, 11:55pm ADT
Please note that services have been restored. If you continue to experience issues, please contact the Service Desk.
May 02, 6:00pm ADT
Network Access and WiFi
Acadia Website
Printing Services
Student Services
Campus Administrative Services
Library Services
Browser Services
Colleague Administrative System
Catalog & Accounts
Slate Enrollment Service
Inter Library Loan Services
StarRez Residence Services
myAcadia Online Self Service
WiFi
VPN
Off Campus Access
Co-Op Education Portal (Orbis)
Informer Reporting
WiFi Residence Buildings
Timetable & Exam Scheduling Services
Web Systems
Wifi Administrative/Academic Buildings
HUB Service Portal
Live Chat & Remote Support
Eduroam
Meal Plan Services
Email Services
Door Access & Lock Services
Network Access
Box Office Ticketing & Registration (AudienceView)
Event Management Services (Legend)
Cybersecurity Awareness Training
Acadia Emergency Alert Services
May-2, 6:00pm ADT
Technology Services will be performing scheduled network maintenance on May 02, 6:00pm ADT. The outage is expected to last approximately 2h minutes. During this time, access to campus resources may become unavailable.
May-2, 8:15pm ADT
Please note that services have been restored. If you continue to experience issues, please contact the Service Desk.
February 10, 3:30pm AST
Feb-10, 3:30pm AST
Microsoft recently implemented enhanced email security methods that have impacted some of our users. When trying to access email, some users are receiving error messages: “your email has been blocked”.
There are different ways in which to access your email:
- Through the web application via the Microsoft Portal (portal.office.com) or the Outlook for Web app (https://outlook.office.com/mail/)
- Download the Outlook app onto your device: https://www.microsoft.com/en-us/microsoft-365/outlook-mobile-for-android-and-ios
- Delete your email and then re-install your account from any 3rd party (non-Microsoft) mail applications. Ensure your operating systems and applications are up to date. Please see Set up email instructions.
Please contact the Service Desk if you require support completing any of these options.
Technology Services will continue to investigate and provide updates.
Feb-10, 5:30pm AST
Please contact the Service Desk if you require support completing any of these options.
Technology Services will continue to investigate and provide updates.
February 01, 2:30pm AST
Feb-1, 2:30pm AST
On Tuesday February 1, 2022, Technology Services performed some updating of Microsoft licenses for students.
The updates did not go as planned and as a result some students lost their access to their Microsoft resources, including email. The issue was corrected as soon as it was discovered.
Jan-2, 1:54am AST
Title: Users on-premises may be unable to send or receive email messages from on-premises or Exchange Online users
User Impact: Users on-premises may be unable to send or receive email messages from on-premises or Exchange Online users.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
User Impact: Users on-premises may be unable to send or receive email messages from on-premises or Exchange Online users.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
Jan-2, 2:19am AST
Current status: We’ve identified a latent code issue within Exchange Server 2016 and Exchange Server 2019 that results in a date check failure with the change of the new year for anti-malware updates starting with build version 2201010001. This date check failure will then cause mail-queuing for Exchange users hosted on-premises. We’ve deployed a new version in the *21 range to prevent any new customers from experiencing the issue and are working to finalize a fix for customers to implement that will restore mail flow for these users.
Scope of impact: This issue is specific to Exchange Online hybrid customers operating Exchange Server 2016 or Exchange Server 2019 for their on-premises users with anti-malware build 2201010001.
Start time: Saturday, January 1, 2022, at 12:00 AM UTC
Root cause: A latent version check code issue within Exchange Server 2016 and Exchange Server 2019 is causing the malware engine to crash when encountering anti-malware signature files within the *22 range. This in-turn leads to transport mail queueing for on-premises users within Exchange Online hybrid organizations.
Next update by: Sunday, January 2, 2022, at 9:30 AM UTC
Scope of impact: This issue is specific to Exchange Online hybrid customers operating Exchange Server 2016 or Exchange Server 2019 for their on-premises users with anti-malware build 2201010001.
Start time: Saturday, January 1, 2022, at 12:00 AM UTC
Root cause: A latent version check code issue within Exchange Server 2016 and Exchange Server 2019 is causing the malware engine to crash when encountering anti-malware signature files within the *22 range. This in-turn leads to transport mail queueing for on-premises users within Exchange Online hybrid organizations.
Next update by: Sunday, January 2, 2022, at 9:30 AM UTC
Jan-2, 2:45am AST
Title: Users on-premises may be unable to send or receive email messages from on-premises or Exchange Online users
User Impact: Users on-premises may be unable to send or receive email messages from on-premises or Exchange Online users.
More info: Please navigate to https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-transport-queues/ba-p/3049447 for instructions on implementing the fix for this problem.
Final status: We've finalized and implemented the fix for this issue. This fix requires additional customer actions and we've detailed these steps within the Exchange Team blog address provided above. Once impacted Exchange Online hybrid customers implement these actions, they will experience restored mail flow for their affected users.
Scope of impact: This issue is specific to Exchange Online hybrid customers operating Exchange Server 2016 or Exchange Server 2019 for their on-premises users with anti-malware build 2201010001.
Start time: Saturday, January 1, 2022, at 12:00 AM UTC
End time: Sunday, January 2, 2022, at 6:45 AM UTC
Root cause: A latent version check code issue within Exchange Server 2016 and Exchange Server 2019 caused the malware engine to crash when encountering anti-malware signature files within the *22 range. This in-turn lead to transport mail queueing for on-premises users within Exchange Online hybrid organizations.
Next steps: - We're working on a long-term fix to prevent future builds from encountering this issue.
This is the final update for the event.
User Impact: Users on-premises may be unable to send or receive email messages from on-premises or Exchange Online users.
More info: Please navigate to https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-transport-queues/ba-p/3049447 for instructions on implementing the fix for this problem.
Final status: We've finalized and implemented the fix for this issue. This fix requires additional customer actions and we've detailed these steps within the Exchange Team blog address provided above. Once impacted Exchange Online hybrid customers implement these actions, they will experience restored mail flow for their affected users.
Scope of impact: This issue is specific to Exchange Online hybrid customers operating Exchange Server 2016 or Exchange Server 2019 for their on-premises users with anti-malware build 2201010001.
Start time: Saturday, January 1, 2022, at 12:00 AM UTC
End time: Sunday, January 2, 2022, at 6:45 AM UTC
Root cause: A latent version check code issue within Exchange Server 2016 and Exchange Server 2019 caused the malware engine to crash when encountering anti-malware signature files within the *22 range. This in-turn lead to transport mail queueing for on-premises users within Exchange Online hybrid organizations.
Next steps: - We're working on a long-term fix to prevent future builds from encountering this issue.
This is the final update for the event.
Jan-2, 2:45am AST
Resolved
Dec-20, 1:03pm AST
Title: Users' received email is incorrectly flagged as unsafe and becoming stuck in the Microsoft 365 Defender Action center
User Impact: Users' received email is incorrectly flagged as unsafe and becoming stuck in the Microsoft 365 Defender Action center.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
User Impact: Users' received email is incorrectly flagged as unsafe and becoming stuck in the Microsoft 365 Defender Action center.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
Dec-20, 1:17pm AST
Current status: We're reviewing system logs and samples of affected messages to isolate the origin of this issue.
Scope of impact: Your organization is affected by this event, and any users' incoming messages may be impacted intermittently.
Next update by: Monday, December 20, 2021, at 7:00 PM UTC
Scope of impact: Your organization is affected by this event, and any users' incoming messages may be impacted intermittently.
Next update by: Monday, December 20, 2021, at 7:00 PM UTC
Dec-20, 2:50pm AST
Current status: We're continuing our review of the affected messages to understand what's causing this problem and formulate a remediation plan.
Scope of impact: Your organization is affected by this event, and any users' incoming email messages may be impacted intermittently.
Next update by: Monday, December 20, 2021, at 9:00 PM UTC
Scope of impact: Your organization is affected by this event, and any users' incoming email messages may be impacted intermittently.
Next update by: Monday, December 20, 2021, at 9:00 PM UTC
Dec-20, 4:52pm AST
Current status: We're reviewing events in the the Microsoft 365 Defender Action center User Experience (UX) we suspect may be contributing to the problem to further our understanding of the impact scenario and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and any users' incoming email messages may be impacted intermittently.
Next update by: Tuesday, December 21, 2021, at 7:00 AM UTC
Scope of impact: Your organization is affected by this event, and any users' incoming email messages may be impacted intermittently.
Next update by: Tuesday, December 21, 2021, at 7:00 AM UTC
Dec-21, 3:00am AST
Current status: We've determined this is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs. We're reviewing options for manually canceling the actions that those false positives created in the Microsoft 365 Defender Action Center in order to clear the Action Center queue and release the affected email messages to recipients' mailboxes.
Scope of impact: This issue affects any users attempting to receive email messages that contain a URL that was falsely marked as malicious.
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Wednesday, December 22, 2021, at 7:00 AM UTC
Scope of impact: This issue affects any users attempting to receive email messages that contain a URL that was falsely marked as malicious.
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Wednesday, December 22, 2021, at 7:00 AM UTC
Dec-21, 3:52am AST
More info: Users correctly see the email messages in their inboxes.
Admins can clear the Action Center queue by rejecting the false positive actions.
Current status: After further review, we've determined this isn't affecting users receiving email messages. Users correctly see the email messages in their inboxes. Admins can clear the Action Center queue by rejecting the false positive actions. In an effort to remediate the impact for admins, we're reviewing options for manually canceling the actions that the false positives created in the Microsoft 365 Defender Action Center in order to clear the Action Center queue.
Scope of impact: This issue affects any admins viewing the Microsoft 365 Defender Action Center.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Wednesday, December 22, 2021, at 12:00 PM UTC
Admins can clear the Action Center queue by rejecting the false positive actions.
Current status: After further review, we've determined this isn't affecting users receiving email messages. Users correctly see the email messages in their inboxes. Admins can clear the Action Center queue by rejecting the false positive actions. In an effort to remediate the impact for admins, we're reviewing options for manually canceling the actions that the false positives created in the Microsoft 365 Defender Action Center in order to clear the Action Center queue.
Scope of impact: This issue affects any admins viewing the Microsoft 365 Defender Action Center.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Wednesday, December 22, 2021, at 12:00 PM UTC
Dec-21, 6:06am AST
More info:
- Admins may experience latency in progression of MDO Investigations and actions.
- Users correctly see the email messages in their inboxes.
- Admins can clear the Action Center queue by rejecting the false positive actions.
Current status: We've determined the actions that the false positives had created in the Microsoft 365 Defender Action Center, are now automatically clearing. We're monitoring the queue as it automatically drains.
Scope of impact: This issue may affect any admin when viewing the Microsoft 365 Defender Action Center.
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Thursday, December 23, 2021, at 1:00 PM UTC
- Users correctly see the email messages in their inboxes.
- Admins can clear the Action Center queue by rejecting the false positive actions.
Current status: We've determined the actions that the false positives had created in the Microsoft 365 Defender Action Center, are now automatically clearing. We're monitoring the queue as it automatically drains.
Scope of impact: This issue may affect any admin when viewing the Microsoft 365 Defender Action Center.
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Thursday, December 23, 2021, at 1:00 PM UTC
Dec-23, 8:11am AST
Current status: The queue is draining as expected and we're continuing to monitor it's progress.
Scope of impact: This issue may affect any admin when viewing the Microsoft 365 Defender Action Center.
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Monday, December 27, 2021, at 1:00 PM UTC
Scope of impact: This issue may affect any admin when viewing the Microsoft 365 Defender Action Center.
Root cause: This is residual impact from EX306353, due to Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next update by: Monday, December 27, 2021, at 1:00 PM UTC
Dec-23, 11:30am AST
Title: Admins may have seen a queue of false positive "Soft delete emails" action types in the Microsoft 365 Defender Action Center
User Impact: Admins may have seen a queue of false positive "Soft delete emails" action types in the Microsoft 365 Defender Action Center.
Final status: We've observed the completion of the queue drain, and have received confirmation from your organization's representatives that impact has been fully remediated.
Scope of impact: This issue may have affected any admin when viewing the Microsoft 365 Defender Action Center.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
End time: Thursday, December 23, 2021, at 3:30 PM UTC
Root cause: This issue was residual impact from EX306353, caused by Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next steps: - We're analyzing performance data and trends on the affected systems to help prevent this problem from happening again.
This is the final update for the event.
User Impact: Admins may have seen a queue of false positive "Soft delete emails" action types in the Microsoft 365 Defender Action Center.
Final status: We've observed the completion of the queue drain, and have received confirmation from your organization's representatives that impact has been fully remediated.
Scope of impact: This issue may have affected any admin when viewing the Microsoft 365 Defender Action Center.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
End time: Thursday, December 23, 2021, at 3:30 PM UTC
Root cause: This issue was residual impact from EX306353, caused by Microsoft 365 Defender picking up stale data about false positive malicious URLs.
Next steps: - We're analyzing performance data and trends on the affected systems to help prevent this problem from happening again.
This is the final update for the event.
Dec-23, 11:30am AST
Resolved
Dec-17, 2:24pm AST
Title: URLs are unexpectedly being marked as malicious and removed from incoming Exchange Online email messages
User Impact: Users may notice that URLS are unexpectedly being marked as malicious and removed from incoming email messages.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
User Impact: Users may notice that URLS are unexpectedly being marked as malicious and removed from incoming email messages.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
Dec-17, 2:39pm AST
Current status: We're analyzing example URLs that have been removed from the messages as well as the messages themselves to better understand the root cause of this issue. In parallel, we're investigating any recent changes to the service that generates and enforces these alerts to determine if they are contributing to the issue.
Scope of impact: Your organization is affected by this event, and users may notice that some URLs included in incoming messages through Exchange Online unexpectedly removed from the messages.
Next update by: Friday, December 17, 2021, at 8:00 PM UTC
Scope of impact: Your organization is affected by this event, and users may notice that some URLs included in incoming messages through Exchange Online unexpectedly removed from the messages.
Next update by: Friday, December 17, 2021, at 8:00 PM UTC
Dec-17, 3:51pm AST
Current status: In addition to example URLS and messages, we've expanded our investigation into message headers to narrow down what could be leading to these URLs being marked as malicious.
Scope of impact: Your organization is affected by this event, and users may notice that some URLs included in incoming messages through Exchange Online unexpectedly removed from the messages.
Next update by: Friday, December 17, 2021, at 10:00 PM UTC
Scope of impact: Your organization is affected by this event, and users may notice that some URLs included in incoming messages through Exchange Online unexpectedly removed from the messages.
Next update by: Friday, December 17, 2021, at 10:00 PM UTC
Dec-17, 6:05pm AST
Current status: We’ve determined that one of our subsystems had an outage which led data to be miscategorized and URLs to be incorrectly flagged as malicious. We've confirmed that messages are no longer being incorrectly quarantined. We're working on recovering messages that were incorrectly quarantined due to URLs being flagged as malicious.
Scope of impact: Any user may notice that some URLs included in incoming messages through Exchange Online are unexpectedly removed from the messages.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
Root cause: One of our subsystems had an outage which led data to be miscategorized and URLs to be incorrectly flagged as malicious.
Next update by: Saturday, December 18, 2021, at 3:00 AM UTC
Scope of impact: Any user may notice that some URLs included in incoming messages through Exchange Online are unexpectedly removed from the messages.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
Root cause: One of our subsystems had an outage which led data to be miscategorized and URLs to be incorrectly flagged as malicious.
Next update by: Saturday, December 18, 2021, at 3:00 AM UTC
Dec-17, 10:00pm AST
Title: Users may notice that some incoming email that includes a URL is quarantined or routed to the Junk folder
User Impact: Users may have noticed that some incoming email that included a URL was quarantined or routed to the Junk folder.
Final status: After further review and discussion with affected users, we've clarified that affected messages were likely routed to a user's Junk folder or quarantined instead of arriving as expected. We've completed the email recovery operation on the unexpectedly quarantined messages, and we've confirmed that the messages are now recovering as expected to resolve this issue. These messages were resubmitted for expected evaluations so that they will again be correctly quarantined if other factors were present.
Scope of impact: Any user may have noticed that some incoming email that included a URL is quarantined or routed to the Junk folder.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
End time: Saturday, December 18, 2021, at 2:00 AM UTC
Root cause: One of our subsystems had an outage which led data to be miscategorized and URLs to be incorrectly flagged as malicious.
Next steps: - We're continuing our investigation into the subsystem outage responsible for impact in order to harden our spam filtering codebase against this issue and prevent similar impact in the future.
This is the final update for the event.
User Impact: Users may have noticed that some incoming email that included a URL was quarantined or routed to the Junk folder.
Final status: After further review and discussion with affected users, we've clarified that affected messages were likely routed to a user's Junk folder or quarantined instead of arriving as expected. We've completed the email recovery operation on the unexpectedly quarantined messages, and we've confirmed that the messages are now recovering as expected to resolve this issue. These messages were resubmitted for expected evaluations so that they will again be correctly quarantined if other factors were present.
Scope of impact: Any user may have noticed that some incoming email that included a URL is quarantined or routed to the Junk folder.
Start time: Friday, December 17, 2021, at 1:34 PM UTC
End time: Saturday, December 18, 2021, at 2:00 AM UTC
Root cause: One of our subsystems had an outage which led data to be miscategorized and URLs to be incorrectly flagged as malicious.
Next steps: - We're continuing our investigation into the subsystem outage responsible for impact in order to harden our spam filtering codebase against this issue and prevent similar impact in the future.
This is the final update for the event.
Dec-17, 10:00pm AST
Resolved
December 15, 9:41pm AST
Dec-15, 9:41pm AST
Title: Users are unable to connect to their mailboxes
User Impact: Users are unable to connect to their mailboxes.
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: Based on our initial investigation, this issue appears to be impacting any user.
Next update by: Thursday, December 16, 2021, at 2:00 AM UTC
User Impact: Users are unable to connect to their mailboxes.
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: Based on our initial investigation, this issue appears to be impacting any user.
Next update by: Thursday, December 16, 2021, at 2:00 AM UTC
Dec-15, 9:54pm AST
Current status: We've halted all deployments to the service as a preliminary troubleshooting step. In parallel, we're reviewing network diagnostic data to determine the cause of the problem.
Scope of impact: Based on our initial investigation, this issue appears to be impacting any user.
Next update by: Thursday, December 16, 2021, at 2:30 AM UTC
Scope of impact: Based on our initial investigation, this issue appears to be impacting any user.
Next update by: Thursday, December 16, 2021, at 2:30 AM UTC
Dec-15, 10:20pm AST
Title: Users are unable to connect to their mailboxes
User Impact: Users are unable to connect to their mailboxes.
Final status: We've determined that this issue is a duplicate of another event. Please look for further updates in MO305726. This communication will expire in 24 hours.
User Impact: Users are unable to connect to their mailboxes.
Final status: We've determined that this issue is a duplicate of another event. Please look for further updates in MO305726. This communication will expire in 24 hours.
Dec-15, 10:20pm AST
Resolved
December 15, 9:24am AST
Dec-15, 9:24am AST
Title: Small number of users can't send outbound email due to delays in the unblocking process
User Impact: Users are unable to send outbound email due to delays in the unblocking process.
Current status: We’re reviewing details provided in the support case to determine the next steps needed to resolve this issue.
Scope of impact: Your organization is affected by this event, and the issue impacts a single user.
Next update by: Wednesday, December 15, 2021, at 3:30 PM UTC
User Impact: Users are unable to send outbound email due to delays in the unblocking process.
Current status: We’re reviewing details provided in the support case to determine the next steps needed to resolve this issue.
Scope of impact: Your organization is affected by this event, and the issue impacts a single user.
Next update by: Wednesday, December 15, 2021, at 3:30 PM UTC
Dec-15, 11:13am AST
Current status: We're analyzing diagnostic data to determine the source of the issue and develop a mitigation plan.
Scope of impact: Your organization is affected by this event, and the issue impacts a single user.
Next update by: Wednesday, December 15, 2021, at 5:30 PM UTC
Scope of impact: Your organization is affected by this event, and the issue impacts a single user.
Next update by: Wednesday, December 15, 2021, at 5:30 PM UTC
Dec-15, 12:42pm AST
More info: Admins are experiencing delays in unblocking the users which have been previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Current status: We're continuing to review service telemetry and AntiSpam diagnostics to isolate the source of the issue.
Scope of impact: This issue affects your organization and is limited to users which have been previously blocked by Microsoft 365 Defender.
Next update by: Wednesday, December 15, 2021, at 6:00 PM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Current status: We're continuing to review service telemetry and AntiSpam diagnostics to isolate the source of the issue.
Scope of impact: This issue affects your organization and is limited to users which have been previously blocked by Microsoft 365 Defender.
Next update by: Wednesday, December 15, 2021, at 6:00 PM UTC
Dec-15, 1:55pm AST
More info: Admins are experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We're reviewing example user data alongside the reported errors to determine if there's a particular pattern and formulate appropriate next steps.
Scope of impact: This issue affects your organization, and the problem is limited to users that were previously blocked by Microsoft 365 Defender.
Next update by: Wednesday, December 15, 2021, at 8:30 PM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We're reviewing example user data alongside the reported errors to determine if there's a particular pattern and formulate appropriate next steps.
Scope of impact: This issue affects your organization, and the problem is limited to users that were previously blocked by Microsoft 365 Defender.
Next update by: Wednesday, December 15, 2021, at 8:30 PM UTC
Dec-15, 3:55pm AST
More info: Admins are experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've requested fresh Non-Delivery Report (NDR) examples from some affected users for analysis while reviewing message IDs to better understand the issue and determine our next steps.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Next update by: Wednesday, December 15, 2021, at 10:30 PM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've requested fresh Non-Delivery Report (NDR) examples from some affected users for analysis while reviewing message IDs to better understand the issue and determine our next steps.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Next update by: Wednesday, December 15, 2021, at 10:30 PM UTC
Dec-15, 6:17pm AST
More info: Admins are experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've received fresh DNR examples from some affected users and are now reviewing them to determine the underlying cause of the issue. We're also exploring options to unblock the affected users.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Next update by: Thursday, December 16, 2021, at 1:00 AM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've received fresh DNR examples from some affected users and are now reviewing them to determine the underlying cause of the issue. We're also exploring options to unblock the affected users.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Next update by: Thursday, December 16, 2021, at 1:00 AM UTC
Dec-15, 8:51pm AST
More info: Admins are experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: Our review of the fresh NDR examples suggests this is not an issue with user configurations, and we're continuing to review recent changes to the service as we investigate a potential code issue. In parallel, we've begun unblocking individual users as reported via support cases to provide relief as we continue to investigate long-term solutions.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Next update by: Thursday, December 16, 2021, at 3:00 AM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: Our review of the fresh NDR examples suggests this is not an issue with user configurations, and we're continuing to review recent changes to the service as we investigate a potential code issue. In parallel, we've begun unblocking individual users as reported via support cases to provide relief as we continue to investigate long-term solutions.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Next update by: Thursday, December 16, 2021, at 3:00 AM UTC
Dec-15, 11:16pm AST
More info: Admins are experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've determined that a code issue is causing users to not be unblocked as expected. We're fixing the code issue and continuing to unblock individual users as reported via support cases.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Root cause: A code issue is causing users to not be unblocked as expected, which is preventing some users from sending email to external recipients.
Next update by: Thursday, December 16, 2021, at 6:00 AM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've determined that a code issue is causing users to not be unblocked as expected. We're fixing the code issue and continuing to unblock individual users as reported via support cases.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Root cause: A code issue is causing users to not be unblocked as expected, which is preventing some users from sending email to external recipients.
Next update by: Thursday, December 16, 2021, at 6:00 AM UTC
Dec-16, 1:00am AST
Title: Small number of users are blocked from sending email to external recipients
User Impact: Users were blocked from sending email to external recipients.
More info: Admins were experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may have received the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users could send email to users within their organization as expected.
Final status: We've completed the deployment of a fix to prevent this impact from occurring to additional users as well as unblocking all remaining mailboxes.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and were routed through the affected infrastructure may have been affected.
Start time: Wednesday, December 15, 2021, at 9:47 AM UTC
End time: Thursday, December 16, 2021, at 5:00 AM UTC
Root cause: A code issue hindering users from being unblocked as expected, which was preventing some users from sending email to external recipients.
Next steps: - We're continuing our review of the impacting code to better identify and prevent similar impact in the future.
This is the final update for the event.
User Impact: Users were blocked from sending email to external recipients.
More info: Admins were experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may have received the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users could send email to users within their organization as expected.
Final status: We've completed the deployment of a fix to prevent this impact from occurring to additional users as well as unblocking all remaining mailboxes.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and were routed through the affected infrastructure may have been affected.
Start time: Wednesday, December 15, 2021, at 9:47 AM UTC
End time: Thursday, December 16, 2021, at 5:00 AM UTC
Root cause: A code issue hindering users from being unblocked as expected, which was preventing some users from sending email to external recipients.
Next steps: - We're continuing our review of the impacting code to better identify and prevent similar impact in the future.
This is the final update for the event.
Dec-16, 1:00am AST
Resolved
Dec-16, 1:46am AST
More info: Admins are experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've fixed a portion of the code issue and have manually unblocked individual users that have been reported via support cases. We're continuing to unblock reported users and fix the remaining code issue to remediate the impact.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Root cause: A code issue is causing users to not be unblocked as expected, which is preventing some users from sending email to external recipients.
Next update by: Thursday, December 16, 2021, at 10:30 AM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We've fixed a portion of the code issue and have manually unblocked individual users that have been reported via support cases. We're continuing to unblock reported users and fix the remaining code issue to remediate the impact.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Root cause: A code issue is causing users to not be unblocked as expected, which is preventing some users from sending email to external recipients.
Next update by: Thursday, December 16, 2021, at 10:30 AM UTC
Dec-16, 5:38am AST
More info: Admins are experiencing delays in unblocking the users, which were previously blocked by Microsoft 365 Defender.
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We're continuing with our remediation efforts in repairing the remaining code issue. In parallel, we're processing the manual unblocking of affected users reported via support cases to provide immediate relief.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Root cause: A code issue is causing users to not be unblocked as expected, which is preventing some users from sending email to external recipients.
Next update by: Thursday, December 16, 2021, at 7:30 PM UTC
Affected users may receive the error message: '550 5.1.8 Access denied, bad outbound sender AS(42003)'.
Users can send email to users within their organization as expected.
Current status: We're continuing with our remediation efforts in repairing the remaining code issue. In parallel, we're processing the manual unblocking of affected users reported via support cases to provide immediate relief.
Scope of impact: A small number of users that were previously blocked by Microsoft 365 Defender and are routed through the affected infrastructure may be affected.
Root cause: A code issue is causing users to not be unblocked as expected, which is preventing some users from sending email to external recipients.
Next update by: Thursday, December 16, 2021, at 7:30 PM UTC
Dec-14, 5:15pm AST
Title: Some users' Exchange Online outgoing messages are delayed or stuck in the Drafts folder after sending
User Impact: Users' Exchange Online outgoing messages are delayed or stuck in the Drafts folder after sending.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
User Impact: Users' Exchange Online outgoing messages are delayed or stuck in the Drafts folder after sending.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
Dec-14, 5:51pm AST
More info: Email that is stuck in the Drafts folder as well as some messages showing in the Sent folder aren't received by the recipient.
Current status: We're reviewing examples of affected user mailboxes alongside the associated impacted messages to better understand why this problem is occurring.
Scope of impact: This issue could affect any user sending email through the Exchange Online service.
Next update by: Tuesday, December 14, 2021, at 11:00 PM UTC
Current status: We're reviewing examples of affected user mailboxes alongside the associated impacted messages to better understand why this problem is occurring.
Scope of impact: This issue could affect any user sending email through the Exchange Online service.
Next update by: Tuesday, December 14, 2021, at 11:00 PM UTC
Dec-14, 7:06pm AST
More info: Email that is stuck in the Drafts folder as well as some messages showing in the Sent folder aren't received by the recipient.
Current status: We've identified that a recent routing configuration change on a portion of infrastructure that facilitates message submission resulted in an abnormally large number of messages routing through the affected infrastructure and queueing for delivery We're correcting the routing configuration change problem to mitigate this issue. We expect that this will complete by our next update; however, additional time will be required for all queued messages to be processed.
Scope of impact: This issue affects some users sending email through Exchange Online that are served through the affected infrastructure.
Start time: Tuesday, December 14, 2021, at 5:30 PM UTC
Root cause: A recent routing configuration change on a portion of infrastructure that facilitates message submission resulted in an abnormally large number of messages routing through the affected infrastructure and queuing for delivery.
Next update by: Wednesday, December 15, 2021, at 2:00 AM UTC
Current status: We've identified that a recent routing configuration change on a portion of infrastructure that facilitates message submission resulted in an abnormally large number of messages routing through the affected infrastructure and queueing for delivery We're correcting the routing configuration change problem to mitigate this issue. We expect that this will complete by our next update; however, additional time will be required for all queued messages to be processed.
Scope of impact: This issue affects some users sending email through Exchange Online that are served through the affected infrastructure.
Start time: Tuesday, December 14, 2021, at 5:30 PM UTC
Root cause: A recent routing configuration change on a portion of infrastructure that facilitates message submission resulted in an abnormally large number of messages routing through the affected infrastructure and queuing for delivery.
Next update by: Wednesday, December 15, 2021, at 2:00 AM UTC
Dec-14, 8:35pm AST
Title: Some users' Exchange Online outgoing messages are delayed or stuck in the Drafts or Sent Items folder after sending
User Impact: Users' Exchange Online outgoing messages are delayed or stuck in the Drafts or Sent Items folder after sending.
More info: Email that was stuck in the Drafts folder as well as some messages showing in the Sent folder were actually queued for delivery, but hadn't been sent.
Final status: We've completed the routing configuration change deployment resolving the underlying issue and confirmed with users that current messages and previously queued mail is being delivered as expected.
Scope of impact: This issue affected some users sending email through Exchange Online that were served through the affected infrastructure.
Start time: Tuesday, December 14, 2021, at 5:30 PM UTC
End time: Wednesday, December 15, 2021, at 12:35 AM UTC
Root cause: A recent routing configuration change on a portion of infrastructure that facilitates message submission resulted in an abnormally large number of messages routing through the affected infrastructure, resulting in mail queueing.
Next steps: - We're reviewing our routing configuration update procedures to better identify and prevent similar problems that could result in sub-optimal request routing that effects Exchange Online mailflow.
This is the final update for the event.
User Impact: Users' Exchange Online outgoing messages are delayed or stuck in the Drafts or Sent Items folder after sending.
More info: Email that was stuck in the Drafts folder as well as some messages showing in the Sent folder were actually queued for delivery, but hadn't been sent.
Final status: We've completed the routing configuration change deployment resolving the underlying issue and confirmed with users that current messages and previously queued mail is being delivered as expected.
Scope of impact: This issue affected some users sending email through Exchange Online that were served through the affected infrastructure.
Start time: Tuesday, December 14, 2021, at 5:30 PM UTC
End time: Wednesday, December 15, 2021, at 12:35 AM UTC
Root cause: A recent routing configuration change on a portion of infrastructure that facilitates message submission resulted in an abnormally large number of messages routing through the affected infrastructure, resulting in mail queueing.
Next steps: - We're reviewing our routing configuration update procedures to better identify and prevent similar problems that could result in sub-optimal request routing that effects Exchange Online mailflow.
This is the final update for the event.
Dec-14, 8:35pm AST
Resolved