Status Page
Identified - Q: What is happening?
A: Starting on 1/27/2025 we will begin removing Appriver Automation app registrations from our M365 customer tenants.

Q: Why is this being done?
A: The Appriver Automation app registrations have been replaced with new authentication methods so the older applications need to be removed. Removing the older applications aligns with Microsoft's security guidelines and best practices.

Q: When is this happening?
A: We will begin removing the AppRiver Automation app registrations in a phased approach starting on 1/27/2025 and we expect the project to be completed within 90 days.

Q: What do I need to do?
A: We will be using an automated process to remove the Appriver Automation app registrations so no actions will be required from our customers/partners.

Q: Will this interrupt our service?
A: There will be no interruption of services.

Jan 16, 2025 - 13:24 CST
Identified -

Unless you are using a third-party app on your tenant that is configured with Azure AD Graph API, you likely will only see Microsoft apps listed on your tenant regarding this notice, such as “Microsoft Office”. If you do have a third-party app listed, you will need to work with that vendor who supplies that app to confirm they have an upgrade available to Microsoft Graph API. If you only see “Microsoft Office” as the listed app, see the information below:



 



Please see the following Microsoft blog for full details:



Action required: Azure AD Graph API retirement | Microsoft Community Hub



Statement from Microsoft Blog -



Some of the service principals using Azure AD Graph in your tenant may be provided by Microsoft. Most of these have an update available that uses Microsoft Graph, instead of Azure AD Graph APIs, such as:





Some Microsoft applications, including Microsoft Office, Microsoft Visual Studio Legacy, and Microsoft Intune, do not yet have an update available without Azure AD Graph API usage. For these, we will provide future Azure AD Graph API retirement blog updates when a replacement version is available. These apps will be granted extended access for Azure AD Graph and sufficient time will be given to update the applications when an update is made available.


Dec 09, 2024 - 11:08 CST
Investigating - Customer advisory

New status page for OpenText Cybersecurity customers

On March 1, 2025, OpenText will retire https://status.appriver.com/ and replace it with https://status.opentext.com/.

To subscribe to updates and get notified whenever OpenText creates, updates or resolves an incident, follow these steps:
1. Visit https://status.opentext.com/
2. Click SUBSCRIBE TO UPDATES.
3. Select your notification method by clicking the mail icon for email notifications or the phone icon for text messages.
4. Click Select "none" to clear the selected components.
5. Select the cybersecurity services you want to receive notifications for by clicking on them. The services are located on the status page under Components > Cybersecurity (Zix).
6. Click Save.
7. Check your email or text messages for your subscription confirmation. Click Confirm subscription.


Note: OpenText has partnered with Atlassian, an Australian software company, for best-in-class incident/maintenance communications. That is why all email notifications will be sent from noreply@statuspage.io instead of an OpenText email domain. We encourage all customers to add noreply@statuspage.io to their safe sender list to help ensure that notifications are delivered straight to their inbox.

Change from CST to UTC
All times will now be listed in UTC on the new status page.

Modifying your subscription or unsubscribing
The OpenText Status Dashboard allows you to manage your service subscriptions, including the option to modify or unsubscribe at any time. Refer to our User Guide to learn how to manage your subscription.

More information
For more information, contact Client Services at client.services@opentext.com

Feb 28, 2025 - 13:54 CST
Monitoring - We are currently in process of upgrading our systems and removing weak TLS ciphers from use on the inbound delivery side of Email Threat Protection. We will begin the process on 2/18 and will continue the upgrades over the upcoming weeks. If you need to confirm the cipher list, please reach out to our support team at support@appriver.com.
Feb 18, 2025 - 15:25 CST
Archive Services ? Operational
Information Archive / ZCP Operational
Erado Archiving ? Operational
Legacy Archive / ZixArchive Operational
CloudAlly Backup Operational
Encryption Services Operational
EMP/DeliverySlip Operational
Erado SecureMail (ESM) Operational
Hosted ZixGateway Operational
Hosted SMB Operational
Secure Cloud Email Encryption (AEE/ZEE) Operational
ZixPortal Operational
Customer Portal Interface Operational
Customer Portal Operational
Partner Portal Operational
Billing Area Operational
ZixCentral ? Operational
Secure Hosted Exchange Operational
Exchange 2013/2016+ (EXG7) Operational
Office 365 Operational
DNS Hosting ? Operational
Support Infrastructure Operational
Phone System Operational
Live Chat Operational
Support Ticketing System Operational
Threat Protection Operational
Email Threat Protection ? Operational
Zix Protect/Spam Stops Here ? Operational
Email Continuity Operational
Secure Cloud Email Continuity Operational
Legacy Continuty Operational
Datacenter Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Mar 24, 2025

No incidents reported today.

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

No incidents reported.

Mar 20, 2025

No incidents reported.

Mar 19, 2025

No incidents reported.

Mar 18, 2025
Resolved - This incident has been resolved.
Mar 18, 07:08 CDT
Monitoring - The final fixes were deployed Friday 2/28/2025. We are continuing to the monitor the system. Please contact support if you are running into any further issues.
Mar 5, 07:28 CST
Update - We are continuing to work on a fix for this issue.
Feb 26, 12:59 CST
Update - We are receiving some reports of the issue occurring at this time. Our engineering team is investigating and making further adjustments.
Feb 25, 08:51 CST
Update - The process is complete, the fix should be applied to all impacted mailboxes. We are currently monitoring. Please contact support if you are running into any further issues.
Feb 24, 07:18 CST
Update - Resolution is being applied to affected mailboxes. It may take a bit of time for the process to complete. Will update once the process is completed.
Feb 21, 13:36 CST
Update - We are continuing to work on a fix for this issue.
Feb 20, 16:20 CST
Identified - The issue has been identified and a fix is being implemented.
Feb 20, 10:49 CST
Update - Our Engineering team is continuing to investigate this issue
Feb 19, 15:35 CST
Investigating - We are aware of an issue with IMAP and POP clients receiving “550 5.7.60 smtp, client does not have permissions to send as this sender” error when sending from outlook.

We are investigating this for resolution.

As a work around users can use OWA - http://exg7.exghost.com to send and receive emails

Feb 19, 09:56 CST
Resolved - Microsoft was experiencing an issue with users unable to access email on IOS native mail app. The issue is now resolved. We appreciate your patience.
Tracking Number: EX1021490

Mar 18, 07:08 CDT
Monitoring - Final Update from Microsoft:

Microsoft confirmed after monitoring service health telemetry that errors associated with impact have reduced to pre-impact thresholds as of Saturday, March 15, 2025 at 9:00 AM CDT
. This confirms that the majority of users are no longer affected by this event and that additional remediation efforts within the Microsoft-managed environment aren't required. As previously mentioned, users whose impact persists should follow the steps outlined in the "More info" of this communication to remediate impact.

More Info:

Users may have been able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users weren't prompted but were still experiencing impact, they may have followed the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e

The problem was specific to the native mail app on iOS devices. Microsoft Outlook for mobile was not affected and could have been used without issue.

Impacted users were encouraged to file a support ticket with Apple to provide valuable logging information to assist with our continued joint investigation with Apple into the source of impact.

----

Microsoft will continue partnering with Apple to gain root cause insights, though this is a best-effort as the underlying issue didn’t reside within the Microsoft-managed environment.
- Follow the steps outlined in the “More info” of this communication in the event you’re still affected.

Mar 17, 14:50 CDT
Update - Update from Microsoft:

After monitoring telemetry, Microsoft confirmed that as affected users continue taking the actions outlined in the "More Info" section of this communication, errors associated with impact are reducing and thus additional remediation efforts within the Microsoft-managed environment aren’t required. Microsoft is continuing to monitor telemetry to ensure that errors and the number of affected users decreases to pre-event levels.
As previously mentioned, please follow the steps outlined in the "More info" of this communication to remediate impact.

More info:

Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e

The problem is specific to the native mail app on iOS devices. Microsoft Outlook for mobile is not affected and can be used without issue.

Impacted users are encouraged file a support ticket with Apple to provide valuable logging information to assist with Microsoft continued joint investigation with Apple into the source of impact.

Mar 13, 15:40 CDT
Update - Update from Microsoft:

While Microsoft continue to communicate with the third-party organization to isolate the source of impact, their telemetry indicates that the impact is receding as the affected users use the actions outlined in the article listed in the "More Info" section. We're monitoring the telemetry to ensure that the impact continues to decrease.

More info:

Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:

https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e

Mar 10, 16:17 CDT
Update - Update from Microsoft:

Microsoft's joint investigation with the third-party is progressing, though it's taking an extended period of time due to the complexity of the issue. Microsoft will provide an update on the status of the investigation, including their findings if pertinent, by the next scheduled update.

Next update by:
Monday, March 10, 2025 at 3:00 PM CDT

Mar 10, 07:40 CDT
Update - Update from Microsoft:

Microsoft joint investigation with the third-party to isolate the source for this event is ongoing. Please note that a support article outlining mitigation steps users can take while we work to address the underlying issue has been provided in the More info of this communication.

More Info:

Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:

https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e

Mar 7, 15:09 CST
Update - Update from Microsoft:

Microsoft is continuing their investigation with the third-party as they isolate the source for this event. Once the root cause is understood, they will continue this collaboration toward a solution for this issue.

Mar 7, 07:06 CST
Update - Update from Microsoft:

Microsoft collaboration efforts with the third-party are progressing as they continue to collect and analyze logs from affected users. Microsoft fully understand the significant impact this incident has had on those affected and are treating this matter with the utmost priority and consideration.

Mar 5, 20:54 CST
Update - Update from Microsoft:

Microsoft is continuing to collaborate and investigate this issue with their third-party partner, along with collecting logs from a subset of affected users, to better understand the underlying root cause. This will help them determine what steps they can take to resolve the impact as swiftly as possible for affected users.

Mar 5, 17:54 CST
Update - Update from Microsoft:

Microsoft is collaborating with their third-party partner and collecting logs from a subset of affected users to help them determine their next troubleshooting steps for remediating the impact.

Mar 5, 13:49 CST
Update - Update from Microsoft:

After monitoring the affected infrastructure, we've determined that reverting the aforementioned update was not a viable mitigation strategy. We're now in the process of gather logs from a subset of affected users to refine our understanding of impact and formulate our remediation strategy.

Mar 5, 07:22 CST
Update - Update from Microsoft:

We're continuing to assess if the aforementioned update we reverted was responsible for impact, while simultaneously exploring other potential causes for this event.

Mar 4, 16:31 CST
Update - Update from Microsoft:

We've reverted a standard service update that we anticipate is resulting in impact. We're reaching out to a subset of affected users to gather a reproduction of impact, which will help validate that the issue is mitigated after the aforementioned change to the affected infrastructure.

Mar 4, 07:01 CST
Update - Update from Microsoft:

Our investigation into the authentication failures has so far revealed that there is an issue with the authentication tokens being sent from the iOS native mail app. We're continuing to investigate and determine the next steps to troubleshoot the issue.

Mar 3, 14:32 CST
Update - Update from Microsoft:

- Our analysis of the diagnostics logs has identified authentication failures, which we're continuing to investigate so that we can isolate the source of the impact.

Mar 3, 11:59 CST
Update - Update from Microsoft:

We're progressing with our review of the aforementioned diagnostic logs to isolate the root cause and confirm our next steps. In parallel, we've received additional feedback from some affected users' Support resources that the steps provided in the "More info" section have successfully alleviated the issue in the short-term.

- More info
Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.

Mar 3, 09:47 CST
Investigating - Microsoft is currently experiencing an issue with users accessing Exchange on the IOS Native Mail App. Microsoft has posted a service incident. We appreciate your patience.
Tracking Number: EX1021490

Summary from Microsoft:

Scope of Impact - Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.

More Info - Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.

Latest update from Microsoft:

- We're conducting analysis of authenticator logs from sample affected devices to confirm whether an issue with Microsoft 365 or a third-party application is responsible for causing impact.

Mar 3, 09:42 CST
Mar 17, 2025
Mar 16, 2025

No incidents reported.

Mar 15, 2025

No incidents reported.

Mar 14, 2025

No incidents reported.

Mar 13, 2025
Mar 12, 2025

No incidents reported.

Mar 11, 2025

No incidents reported.

Mar 10, 2025