Resolved -
Incident Update
We are pleased to confirm that the issue has been fully resolved, and this announcement is now being closed.
A root cause analysis has already been initiated, and the details will be shared following our standard processes.
Thank you for your collaboration.
Best regards,
AnywhereNow Support
Apr 8, 13:22 UTC
Update -
We are pleased to confirm that the issue has been resolved. We continue to receive positive feedback from affected customers.
We will closely monitor the situation and confirm with the remaining impacted customers. For now, we will keep this incident announcement in a monitoring state.
If you are still experiencing any issues, please reach out to our Support team via our standard channels.
Thank you for your collaboration.
Best regards,
AnywhereNow Support
Apr 8, 10:06 UTC
Update -
Incident Update:
The issue is now resolved. Our internal tests confirm the positive results, and we are also receiving positive confirmations from our customers. We will keep this incident in monitoring status while we continue confirming with impacted customers.
Should you still not experience any improvement, please reach out to our Support team via our standard channels.
Thank you for your collaboration.
Best regards,
AnywhereNow Support
Apr 8, 09:48 UTC
Monitoring -
The latest remediation steps are showing positive results. We are currently in the process of deploying the solution, and customers should begin to notice improvements shortly.
An update will be provided within the next 30min.
Best regards,
AnywhereNow Support
Apr 8, 09:39 UTC
Update -
Incident update:
We are actively implementing immediate enhancements to the affected component to mitigate the impact and restore functionality.
Further updates will be provided within the next 60 minutes.
Thank you for your collaboration.
Best regards,
AnywhereNow Support
Apr 8, 09:29 UTC
Update -
Incident update:
Impact and Root Cause (Preliminary): A short but critical disruption (~
Current Status: Microsoft has marked the event as resolved. However, the OIDC-based login functionality is still degraded. AnywhereNow is actively working on re-establishing services as soon as possible and determining the next steps. There is no evidence of fault within AnywhereNow systems; the root cause appears to be Azure infrastructure-related.
Microsoft has not yet provided root cause details; however, we suspect a backend change or instability may have affected how authentication tokens are being handled.
Next Steps: We continue working on remediation steps, prioritizing the fastest and safest route to resolution while collecting the necessary signals to drive long-term stability improvements.
We apologize for the impact this issue is having on your operations. Please be assured that we are addressing this with the highest priority.
Best regards,
AnywhereNow Support
Apr 8, 09:00 UTC
Update -
Incident Update:
We confirm that only customers set up to use the new login system at "login.anywhere365.cloud" are impacted.
Reference: https://golive.anywhere.now/articles/authentication/create-azure-app-for-authentication.html
Our investigation is ongoing. While the issue with the Microsoft database server remains the most probable cause, it has not yet been confirmed. We have implemented remediation steps, but unfortunately, they have not resolved the issue.
Workaround: The previously communicated workaround is confirmed to be effective. Agents can be set to informal status. Although agents will not be able to log in to WebAgent, they will still receive calls on Teams. Should you require assistance in setting your agents to informal status, please log a case with support. Additionally, you can refer to the product documentation at: https://golive.anywhere.now/gettingstarted/userroles/getting-started-agent.html?Highlight=agent%20formal
Please be assured that we have all hands on deck, and this matter is being addressed with the highest priority. We apologize for the impact this issue is having on your daily operations. Further updates will be provided within the next 60 minutes.
Thank you for your collaboration.
Best regards,
AnywhereNow Support
Apr 8, 08:13 UTC
Update -
We continue to investigate the root cause and remediation steps.
As a workaround for impacted customers, agents can be set to informal status. While agents will not be able to log in to WebAgent, they will still receive calls on Teams.
Further updates will be provided within the next 60 minutes.
Thank you for your collaboration.
Best regards,
AnywhereNow Support
Apr 8, 07:38 UTC
Identified -
An outage of the Microsoft database servers where WebAgent authenticates has been identified as the potential root cause of the issue.
Investigations are ongoing to confirm this and determine the necessary remediation steps on the Anywhere365 side.
An update will be provided within the next 60 minutes.
Thank you for your collaboration.
Best regards,
AnywhereNow Support
Apr 8, 07:14 UTC
Investigating -
Dear valued Customer and Partners,
We are writing to inform you about an incident that has come to our attention. Please find the details below:
User impact (Symptom): Some customers are experiencing issues trying to log to WebAgent
Start Time: Apr 08, 2025, 08:30 UTC
Current status: Investigating
Root Cause: Under Investigation
Next Steps: We are actively investigating the issue and will provide further updates within the next 60 minutes.
Thank you for your collaboration and patience during this time.
Thanks for your collaboration,
Best regards,
AnywhereNow Support
Apr 8, 06:55 UTC