Monitoring - Microsoft has announced deprecation, or sunsetting, of legacy authentication protocols (Basic Authentication), beginning October 1, 2022. Basic authentication has been replaced with Modern Authentication, which supports Multi-Factor Authentication for enhanced security.
IMPORTANT: What does this mean for your organization? It is very unlikely your organization will be affected by the change as this is a phased rollout that has been occurring over a few years. * Modern Authentication is already enabled by default for all Office 365 tenants. * All versions of Outlook and Office that are still supported today support the use of Modern Authentication. * All modern mobile devices, including iPhones and other iOS devices, as well as Android devices including Samsung and Motorola devices, support Modern Authentication in their native email client applications (including the Gmail app for all modern Android devices). * Outlook for iOS and Android supports Modern Authentication and is the recommended email client for mobile devices * While IMAP and POP protocols now support modern authentication, this is intended for continued use of third-party applications. Microsoft recommends the use of Outlook on the Web (OWA) over POP or IMAP in mail client applications, including Microsoft Outlook desktop applications, for end users email client access. https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online#pop-imap-and-smtp-auth
* AD Connect supports Modern Authentication for organizations with hybrid identity management.
There are a limited number of scenarios where an organization may have client applications that still use Basic authentication which could be affected. We have provided step by step instructions with links to resources for administrators to identify potentially affected applications and users in the following KB article for your reference: https://support.zixcorp.com/app/answers/detail/a_id/1781
Monitoring - What changes is occurring? On October 1st 2022, Hosted Exchange will be disabling TLS 1.0 and TLS 1.1 and moving all of our online services to TLS 1.2.
How does this affect me? As of October 1, 2022, Hosted Exchange will no longer support TLS 1.0 and 1.1. By October 1, 2022, all client and browser combinations should use TLS version 1.2 (or a later version) to ensure connection without issues to our services. This may require updates to certain clients and browser combinations. If you do not update to TLS version 1.2 (or later) by October 1, 2022, you may experience issues when connecting to Hosted Exchange. If you experience an issue related to the use of an old TLS version after October 1, 2022, you will be required to update to TLS 1.2 as part of the resolution.
What do I need to do to prepare for this change? We recommend you proactively address weak TLS usage by removing TLS 1.0/1.1 dependencies in your environments and disabling TLS 1.0/1.1 at the operating system level where possible. Clients using Outlook 2010 for Windows or Outlook 2011 for Mac will need to change to be replaced with newer versions. Clients using Outlook 2013 SP1 (or higher), Outlook 2016 for Mac will need to ensure that they are up to date. Windows 7 users can use TLS 1.2 client applications and browsers if changes are made using the following Microsoft guidance at Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows (microsoft.com).
Jul 14, 16:13 CDT
Update - We have updated our plan of roll out to be March 8th at 9 AM CST.
Mar 7, 13:01 CST
As a security update to help combat spoofing and unauthorized email, we are making improvements to our Relay Server (relay.appriver.com) on March 1st, 2022. This server was mainly used for alerting or scan to email systems.
The security update will be an SPF record validation on incoming connections to our relay server. The SPF record check will verify the sending IP address is listed in the domain's SPF record. We understand this improvement will require many customers to add their sending IP address to their SPF record. The Set Up a SPF Record for AppRiver Hosted Services article provides more information on setting up an SPF record for Zix|Appriver services. An example of an valid SPF record is below.
Update - We have reverted the SPF security update for now. We are planning on implementing this in a future security update to our relay server. We recommend anyone using our relay server to update their SPF to include the IP of the application/software to avoid future issues.
Feb 3, 11:24 CST
Update - We have scheduled this change to go into effect Feb 1st, 2022 (Tuesday). Please ensure your SPF records are correctly listing your IP's you will connect from to ensure no issues with use of our Relay Server.
Jan 26, 11:50 CST
Update - We are updating our security settings for our Relay Server which is normally used for scan-to-email systems. We are implementing an SPF check on incoming connections to ensure the sender of the email is validity listed in their SPF records. Any customer using relay will need to follow the guide below and update their SPF to include their sending IP in their SPF. This will be in the format of "v=sp1 ip4:184.108.40.206 -all" as an example. The below article will go over this as well. If you have any questions please reach out to support via ticket to firstname.lastname@example.org
Identified - We are updating our security settings for our Relay Server which is normally used for scan-to-email systems. We are implementing an SPF check on incoming connections to ensure the sender of the email is validity listed in their SPF records. Any customer using relay will need to follow the guide below and update their SPF to include their sending IP in their SPF. This will be in the format of "v=spf1 include:edgepilot.com ip4:220.127.116.11 -all" as an example. The below article will go over this as well. If you have any questions please reach out to support via ticket to email@example.com
Monitoring - We will continue to monitor as our teams work through the intermittent issues with the Customer Portal login page failing to load properly. We apologize for the inconvenience and appreciate your patience as we work to fully resolve the issue.
Mar 14, 10:22 CDT
Investigating - We are currently investigating an intermittent issue with the Customer Portal login page failing to load properly. We do apologize for the inconvenience and appreciate your patience as we work to resolve the issue.
Mar 14, 08:59 CDT
Monitoring - As of 10:45 PM Central Time on Wednesday, December 15th, 2021, we have reviewed all of our production systems, corporate internal IT systems, and all relevant third-party software for the presence of Log4j vulnerabilities as described by the vendor, and we have completed all vendor-recommended remediations with respect to those systems and third-party software.
We have also completed a review of our supported on-site (on-prem) products and found no Log4j vulnerabilities as described by the vendor in any of those products.
We also continue to monitor our systems (which does not include customer-premise products) for the purpose of detecting certain exploits known to leverage the Log4j vulnerability.
Dec 16, 21:15 CST
This incident has been resolved.
Aug 8, 16:11 CDT
We have confirmed with our vendor that calls appear to be working. We are actively monitoring the systems to ensure everything is fully operational. We apologize for any inconvenience this may have caused.
Aug 8, 14:38 CDT
We are currently experiencing an issue with our phone systems and are working with our vendor to resolve this issue. In the interim please use firstname.lastname@example.org for any support requests.
Aug 8, 12:38 CDT
Incident information Title: Some United states users may be unable to access Microsoft 365 services and features ID: MO409239
Status Service Restored
Restored Services Microsoft 365 suite, Microsoft 365 suite
Details Title: Some United states users may be unable to access Microsoft 365 services and features
User Impact: Users may have been unable to access Microsoft 365 services and features.
Final status: We've redirected user traffic to alternate network infrastructure that isn't experiencing the same connectivity issues, and we've verified via telemetry and with some affected users that impact has been remediated.
Scope of impact: Impact was specific to some United States-based users in the Atlanta and Chicago regions that were served through the affected third-party ISP infrastructure attempting to access any Microsoft 365 services and features.
Start time: Thursday, August 4, 2022, at 5:30 AM UTC End time: Thursday, August 4, 2022, at 3:11 PM UTC
Root cause: A third-party ISP issue caused Microsoft 365 services and features to become unavailable for some United States users. Next steps: - We're continuing to review the affected portion of infrastructure to better understand how impact began, which will assist us preventing similar impact in the future.
This is the final update for the event.
Thank you, The Microsoft team
Aug 4, 12:26 CDT
Microsoft 365 suite service alert
Advisory information Title: Some North America users may be unable to access multiple Microsoft 365 services or features ID: MO409239
Status Service Degradation
Affected Services Microsoft 365 suite, Microsoft 365 suite
Details Title: Some North America users may be unable to access multiple Microsoft 365 services or features
User Impact: Users may be unable to access multiple Microsoft 365 services or features.
More info: As a workaround, users may be able to utilize a Virtual Private Network (VPN) to encounter immediate relief.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some North America users attempting to access multiple Microsoft 365 services or features.
Next update by: Thursday, August 4, 2022, at 4:00 PM UTC