Date: October 29, 2025
Duration: ~17:00–19:08 CET
Impact: Login and connectivity issues across POS, Portal, and APIs due to a Microsoft Azure Front Door outage.
What Happened
On the afternoon of October 29, a global outage in Microsoft Azure affected our systems:
- POS: Most retailers could continue selling. Those who needed to log in could use flight mode to access offline mode. This worked in most cases, though a few users were still unable to log in.
- Portal and APIs: Temporarily unavailable.
The outage was caused by Azure Front Door, Microsoft’s global traffic gateway and web-application firewall. Because Microsoft also uses Front Door for its own admin tools, we were unable to access Azure management consoles until the service was partially restored.
What We Did
We confirmed the cause, provided the offline login workaround, and monitored the situation. At 19:08 CET, Azure access was restored and we rerouted traffic outside Front Door, bringing all services back online.
All sales completed offline will automatically upload to our servers once connectivity returns, ensuring no data is lost. Same goes for events and date to and from integrations hosted by Front Systems.
Next Steps
- Review dependency on Azure Front Door as our single gateway. Although Microsoft guarantees 99.99 % availability, this event shows that even high-SLA services can fail globally.
- Improve POS offline login and error messaging to make offline mode more robust and clearer for users.
Technical Details
- Root Cause: An inadvertent configuration change by Microsoft in Azure Front Door caused widespread connection failures and timeouts.
- Impact: All inbound traffic via Front Door failed, affecting Portal, APIs, and POS backend. Since our failover instance is reached through the same Front Door, it could not be utilized during the incident. Azure’s own admin tools were also down because they depend on Front Door.
- Resolution: At 19:08 CET, Azure access was restored; traffic was rerouted outside Front Door, and all systems recovered.
Integrator Note: For partners affected by the same issue on their side, missed webhook events can be resent using our API.