Resolved -
This incident has been resolved.
Jun 18, 17:25 UTC
Monitoring -
We are pleased to confirm that the issue impacting inbound calling to Microsoft Teams services has now been resolved.
Following confirmation, services have returned to normal operation. As a result, we have stopped all planned customer migrations and are now proactively contacting affected customers to confirm that services are operating as expected.
We will continue to closely monitor the service to ensure ongoing stability.
We would like to sincerely apologise for any inconvenience caused and thank you for your patience and understanding while we worked with Microsoft to resolve the issue.
Should you experience any further issues, please contact our Technical Support team.
Jun 18, 16:42 UTC
Update -
We are writing to provide an update regarding the ongoing Microsoft incident affecting inbound calling services for some Microsoft Teams customers.
Following work overnight, Onecom has successfully tested and implemented a solution which in test cases has proven to restored service.
To proceed with this workaround, we require some assistance from your side. The attached guide outlines the steps required to prepare your Microsoft tenant for migration. As part of this process, you will need a Microsoft Global Administrator and access to your Microsoft 365 and Teams administration portals.
https://tinyurl.com/Teams-Migration-Guide
A key early step in the process is the creation of the required domains and the generation of the associated TXT verification records. Once you have generated these TXT records, please send them to us and pause the process at that point. Our engineering team will update the necessary DNS records and confirm when you can proceed with the remaining preparation steps.
Once these preparation steps have been completed, we will schedule your tenant into a migration slot. During the migration, our engineers will be available to guide you through the process, validate the configuration, and ensure your inbound calling service is restored as quickly as possible.
As this workaround requires coordination between your team and ours, we would encourage you to review the attached guide and begin the preparation steps as soon as possible. If you require any assistance at any stage, please contact us and a member of our technical team will be happy to help.
We appreciate your patience whilst Microsoft continues to investigate the underlying issue and thank you for your cooperation in helping us restore your service.
Jun 18, 08:26 UTC
Update -
The Workaround is in its final testing phase. We have identified that there is an issue with the current Microsoft domain, and moving to a different domain resolves the inbound calling issues, we will provide you with an update as soon as possible on next steps.
Jun 17, 18:02 UTC
Update -
The issue has been escalated with Microsoft and a possible workaround is currently being tested by our engineers, once testing has been completed, we will confirm if this is successful and an ETA of implementation.
We will provide a further update at 6:30pm.
Jun 17, 16:21 UTC
Update -
We currently have active calls in progress with both Microsoft and the SBC vendors to help accelerate the resolution of this issue. Investigations are ongoing.
After testing, we can confirm that it is possible to add diverts to the affected Teams numbers via our Onecom portal - If you need any assistance, please contact our support teams.
We will provide a further update at 4pm.
Jun 17, 13:47 UTC
Update -
Microsoft are continuing to actively investigate this issue.
At this stage, there is no confirmed fix in place, and the incident is still being treated as a high-priority, potential platform-wide issue. We are closely monitoring the situation.
We will provide a further update at 3pm.
Jun 17, 12:04 UTC
Update -
Microsoft are continuing to actively investigate this issue.
At this stage, there is no confirmed fix in place, and the incident is still being treated as a high-priority, potential platform-wide issue. We are closely monitoring the situation.
We will provide a further update at 1pm.
Jun 17, 11:29 UTC
Update -
Microsoft has deployed a potential fix. However, following our initial testing, the issue remains. We have reported our findings back to Microsoft for further investigation.
We will provide the next update by 12:00 PM.
Jun 17, 10:30 UTC
Investigating -
We are currently investigating a major incident impacting inbound calling for Connect4Teams customers. Affected callers may hear a “number not recognised” message when attempting to reach services.
Outbound calling remains unaffected and is working normally.
Status:
The issue has been escalated to Microsoft and is being treated as a potential platform-wide incident.
We sincerely apologise for the inconvenience caused.
We are actively working with them and will provide a further update by 11:30am.
Jun 17, 09:59 UTC