Some users may be missing options to open files using custom file handlers in Microsoft OneDrive

Title: Some users may be missing options to open files using custom file handlers in Microsoft OneDrive User impact: Users may be missing options to open files using custom file handlers in OneDrive. Final status: We've confirmed that a recent service update to OneDrive changed how custom file handlers were processed, resulting in impact. We completed a rollback of the identified updates responsible for this and confirmed through service-side testing as well as testing with previously affected users that this is mitigated. Due to cache storage, this can take up to 48 hours to resolve for all users. If users are in need of immediate remediation, please follow the articles below:   https://learn.microsoft.com/en-us/onedrive/developer/file-handlers/?view=odsp-graph-online&source=r…   https://learn.microsoft.com/en-us/onedrive/developer/file-handlers/reset-cache?view=odsp-graph-onli…   Scope of impact: Some users attempting to open files using custom file handlers in OneDrive may have been impacted.    Root cause: A recent service update to OneDrive changed how custom file handlers are processed, which resulted in impact.   Next steps:  - We'll continue our review of the impacting update to better understand how the change resulted in impact and what we can do to improve our pre-deployment processes to identify and resolve similar issues.   This is the final update for the event.

Title: Some users may be missing options to open files using custom file handlers in Microsoft OneDrive User impact: Users may be missing options to open files using custom file handlers in OneDrive. More info: Custom file handlers enable users to open files with integrated third-party or line-of-business apps. For example, some users may be missing the “Open in Adobe Acrobat” option for PDF files.   Current status: We've investigated an issue where some users may be missing the option to open files with custom file handlers in OneDrive, and confirmed that the issue is now resolved. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.   Using the retroactive template since we're going straight to resolved shortly after