This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 24%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
We have previously registered a file handler following Microsoft documentation: https://learn.microsoft.com/en-us/onedrive/developer/file-handlers/?view=odsp-graph-online
This integration has been working correctly for several months in our tenant.
Issue:
As of today, the file handler has suddenly stopped functioning:
Troubleshooting Performed:
This issue is highly critical as the affected file types cannot be opened natively in SharePoint or OneDrive and are business critical files.
The issue is not affecting only us, but also other M365 tenants where the same file handler technology is used. There the the file handler also suddenly stopped working a day before ours.
The process of building custom applications and tools that interact with Microsoft SharePoint, including SharePoint Online in Microsoft 365.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 28.999999999999996%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I can confirm this issue for our own tenant and for our customers.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 1%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDT%3C/text%3E%3C/svg%3E)
Hi Manuel
Thank you for sharing this information.
I’m sorry to hear that you are experiencing the same issue across your tenant and your customers.
At this point, I would recommend raising a support ticket with Microsoft Support, as suggested in the response below, so the relevant team can further investigate.
I appreciate your patience and understanding.
We are experiencing the same issue in our tenants and our clients’ tenants. Has there been any progress? Do we have any information as to why this is happening?
We are experiencing the same issue in our tenants and our clients’ tenants. Has there been any progress? Do we have any information as to why this is happening?
Unfortunately, there is no feedback from Microsoft even though their response time for critical issues is 1 hour :(. Please open tickets in M365 admin and also in Azure portal. This is the only thing we can do right at the moment. I have suggested the same for our customers too.
I created a support ticket in M365 admin center. Unfortunately, they won't handle it:
Thank you for sharing the issue regarding your custom SharePoint and OneDrive file handlers disappearing. After reviewing the issue carefully, we confirmed that this issue is related to a custom-developed (developer) scenario. Custom file handlers and their manifests are outside the scope of Microsoft 365 break/fix support, and our team is not equipped to troubleshoot developer-specific configurations. To get this investigated properly, we recommend opening a support request with the Microsoft Identity Platform / Developer Support team, who handle issues related to:
You can find the appropriate support options here: Support and help options for Microsoft identity platform developers - Microsoft identity platform |…
Hi Manuel
Thank you for sharing the update and the response you received.
Based on the information provided, this scenario appears to be related to a custom-developed (developer) configuration, which is typically outside the scope of standard Microsoft 365 break/fix support handled through the Microsoft 365 admin center.
Based on Microsoft documentation, certain scenarios, particularly those involving custom solutions such as file handlers, app manifests, or app registrations, are not covered under regular support channels and require specialized investigation.
In this case, I would recommend raising a support request through the Service Hub, as they are better equipped to assist with this type of issue.
Please note that access to the Services Hub depends on your organization’s support agreement and may require a paid support plan. You can review the requirements and sign-in conditions in the Services Hub sign-in FAQs before submitting a request.
Thank you for your understanding.
Answer recommended by moderator
It seems that the handler is back again, just need to be re-loaded (2 times :)) using the:
https://nameofyourtenant.sharepoint.com/_api/v2.0/drive/apps?adminForceRefresh=1
After a long waiting time, I finally got some answer from MS support:
After further check with my internal team, the recent OneDrive File Handler 2.0 issue was caused by a temporary Microsoft backend service regression that prevented registered file handlers from being recognized. No tenant configuration or changes on your side contributed to this. The service has now been fully restored by Microsoft, and functionality is back to normal. Please note that this issue is still under further investigation to ensure it does not recur.
Thank you for sharing this update and the confirmation from Microsoft support. Your update will be helpful for others experiencing the same issue.
Have a great day.
We are experiencing the same issue in our tenants and our clients’ tenants. Has there been any progress? Do we have any information as to why this is happening?
Thank you for sharing that you are experiencing the same issue across your tenants.
At this time, I haven’t come across any official updates or confirmed information that explains why this is happening.
In this situation, the best approach would be to raise a support request through the Service Hub (as mentioned below), so the relevant Microsoft support team can investigate this further from the backend.
Please note that access to the Services Hub depends on your organization’s support agreement and may require a paid support plan. You can review the requirements and sign-in conditions in the Services Hub sign-in FAQs before submitting a request.
Thank you for your understanding.
Thank you for reaching out to the Microsoft Q&A forum and for taking the time to provide detailed information about your issue.
I understand how critical this situation is, especially since the file handler was working previously and the affected file types are business critical. I’m sorry for the inconvenience this has caused.
I’ve done some research based on the details you shared, but I wasn’t able to find any documented changes or information that would explain this behavior from a configuration or tenant‑specific perspective.
Please understand that this is a public peer to peer community forum. While moderators and community members can share guidance and experiences, we don’t have access to backend systems or internal diagnostic tools required to investigate or validate service-side behavior.
Therefore, I recommend raising a support ticket with Microsoft Support via Services Hub for further investigation.
Please note that access to the Services Hub depends on your organization’s support agreement and may require a paid support plan. You can review the requirements and sign-in conditions in the Services Hub sign-in FAQs before submitting a request.
Additionally, you may also consider posting a new thread on GitHub, where engineers and community contributors may be able to provide more targeted insights.
Reference: Participating in a discussion - GitHub Docs.
I apologize that we are unable to assist further in this forum and for having to redirect you to other support channels. I hope your issue will be resolved as soon as possible.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
May I know if you have got any chance to check my answer?
If you have any other questions, please feel free to post back.
Hi @Dora-T ,
The service hub was redirecting me to Azure portal, where I have already created a ticket. Unfortunately I did not get any answer from MS support even though they have max 8 hours of response time :(
I’m sorry to hear that you haven’t received a response yet from the support team.
As a moderator in this public forum, I don’t have access to internal systems and therefore don’t have visibility into support tickets.
I understand the delay is frustrating, and I truly appreciate your patience. I would recommend continuing to monitor your support request, as the support team should follow up with you as soon as possible.
Best regards,
Thank you for the update.
It’s great to hear that the file handler is now appearing again after forcing a refresh. Your finding may be helpful for others experiencing the same issue.
I will convert your comment into an answer. Since you’re unable to accept your own answer, I’ll mark it as recommended on your behalf so it may be easier for other users to find.
I appreciate your sharing and the time you’ve taken to provide this update.
Have a great day.