M365 Add-in Impacted by Microsoft library

Microsoft has extended their full recovery time to 00:40 UTC Oct 30, however they state they are now operating above 98% Availability: https://azure.status.microsoft/en-us/status

Proofpoint has seen signific improvements in connectivity of the Add-in, and monitoring shows healthy functioning since 22:00 UTC

We will continue to monitor overall, and watch for Microsoft to move to fully recovered. At that time, we will provide the final update here.

We've begun to observe intermittent improvement beginning at ~20:30 UTC, for some email sends, the Add-In may now function without latency. However, we will continue to monitor as Microsoft recovery progresses, as users may still run into issues sending email.

For additional updates: https://azure.status.microsoft/en-us/status

For additional updates: https://azure.status.microsoft/en-us/status

Latest Microsoft Update: Oct 29, 2025 19:22 UTC

We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement.

Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted.

Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems.

At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted.

Although we are seeing signs of recovery and have an estimated timeline, customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure.

Potential workarounds:

• Users can attempt to send email via mobile

• Admins can attempt to descope the M365 Add-in from users, however, please note that this is subject to Microsoft's propagation time (up to 24 hours)

• If your organization is utilizing the Smart Alerts manifest. Emails can be sent by utilizing the default Send Mode, the user should be able to choose to "send anyway" even if the add-in can't be loaded

For additional updates: https://azure.status.microsoft/en-us/status

Latest Microsoft Update: Oct 29, 2025 19:01 UTC

We have pushed our ‘last known good’ configuration, and customers may begin to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement.

Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted.

Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems.

We are continuing to monitor progress closely and will provide an ETA for full mitigation within the next 20 minutes as we assess recovery across the AFD service.

Potential workarounds:

• Users can attempt to send email via mobile

• Admins can attempt to descope the M365 Add-in from users, however, please note that this is subject to Microsoft's propagation time (up to 24 hours)

• If your organization is utilizing the Smart Alerts manifest. Emails can be sent by utilizing the default Send Mode, the user should be able to choose to "send anyway" even if the add-in can't be loaded

For additional updates: https://azure.status.microsoft/en-us/status

Latest Microsoft Update: Oct 29, 2025 18:24 UTC

We have initiated the deployment of our last known good configuration, which is expected to complete within 30 minutes. As this deployment progresses, customers should begin to see initial signs of recovery. Once completed, we will begin recovering nodes and routing traffic through these healthy nodes.

Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted.

Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems.

We do not yet have an ETA for full mitigation, but we will provide another update within 30 minutes, once the deployment has completed.

Customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure.

Potential workarounds:

• Users can attempt to send email via mobile

• Admins can attempt to descope the M365 Add-in from users, however, please note that this is subject to Microsoft's propagation time (up to 24 hours)

• If your organization is utilizing the Smart Alerts manifest. Emails can be sent by utilizing the default Send Mode, the user should be able to choose to "send anyway" even if the add-in can't be loaded

Latest Microsoft Update: Oct 29, 2025, 17:51 UTC

Starting at approximately 16:00 UTC, customers and Microsoft services that leverage Azure Front Door (AFD) may have experienced issues resulting in latencies, timeouts and errors. We have confirmed that an inadvertent configuration change as the trigger event for this issue.


We are taking several concurrent actions: Firstly where we are blocking all changes to the AFD services, this includes customer configuration changes as well. At the same time, we are rolling back our AFD configuration to our last known good state. As we rollback we want to ensure that the problematic configuration doesn't re-initiate upon recovery.


Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace).


We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update.


While we don't have an ETA yet. customers can consider implementing failover strategies with Azure Traffic Manager, to fail over from Azure Front Door to your origins: https://learn.microsoft.com/azure/architecture/guide/networking/global-web-applications/overview



Potential workarounds:

• Users can attempt to send email via mobile

• Admins can attempt to descope the M365 Add-in from users, however, please note that this is subject to Microsoft's propagation time (up to 24 hours)



• If your organization is utilizing the Smart Alerts manifest. Emails can be sent by utilizing the default Send Mode, the user should be able to choose to "send anyway" even if the add-in can't be loaded

Lastest Microsoft Update: Oct 29, 2025, 17:17 PM UTC

We've identified a recent configuration change to a portion of Azure infrastructure which we believe is causing the impact. We're pursuing multiple remediation strategies, including moving traffic away from the impacted infrastructure and blocking the offending change. We'll provide an estimated recovery time as soon as possible.

https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/MO1181369

Potential workarounds:

• Users can attempt to send email via mobile

• Admins can attempt to descope the M365 Add-in from users, however, please note that this is subject to Microsoft's propagation time (up to 24 hours)

Microsoft has declared an service incident, which includes impact to their add-ins:

Issue ID: MO1181369
Start time: Oct 29, 2025, 16:06 UTC
Title: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services

"Admins are reporting issues when attempting to access some Microsoft Purview and Microsoft Intune functions. Users are also seeing issues with add-ins and network connectivity in Outlook."

Last Microsoft Update: Oct 29, 2025, 16:36 UTC

• Current status: We're rerouting affected traffic to alternate healthy infrastructure as a near-term resolution while our investigation into the source of the issue is ongoing.

https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/MO1181369

Proofpoint will continue to monitor closely and provide updates as they become available.

We are aware of an issue affecting a critical Microsoft-hosted library used by the M365 add-in starting at 15:41 UTC. This will result in the add-in becoming unresponsive and eventually timing out during use.

Our team is actively monitoring the situation and will provide updates as more information becomes available.

Additional context can be found here: https://github.com/OfficeDev/office-js/issues/6249