Health status

MetaShare depends on the service health of Microsoft 365 and Azure. You can also get updates on Microsoft’s health status from Twitter (@MSFT365Status).

If there are no ongoing problems with Microsoft 365 and your problem is not listed here, check our known issues.

Ongoing issues

  • Recent documents include only one document

    Start time: 12 November 2025
    Updated: 17 December 2025

    Microsoft has recently deprecated Graph endpoint used for retrieving recent documents which is used by MetaShare. Usually, deprecated endpoints continue to work for some time, giving developers time to update APIs they use. Unfortunately in this case, according to Microsoft, the recent endpoint will continue to work in a degraded state, which appears to mean retrieving only one item. We are working on an update using different APIs to resolve the issue.


Resolved issues

  • Guest users can’t see managed metadata values

    Start time: February 2026
    Published: 9 March 2026

    Guest users in some tenants stopped seeing metadata values (terms) set on documents which they have access to. The issue affects not only MetaShare, but SharePoint sites as well. We’re in contact with Microsoft regarding the issue. It seems that a recent change in SharePoint changed how values are retrieved from Taxonomy Hidden List. Current solution/workaround seems to be adding guest users to a group that has read permissions on Taxonomy Hidden List.

    Update: 2026-03-11

    The issue seems now to be resolved by Microsoft. We’ll continue monitoring the issue and verify if the fix reached all affected tenants.

  • Users unable to access MetaShare

    Start time: 6 October 2025, 8:10 CEST

    Due to an ongoing incident in Microsoft 365 users in some tenants can’t access SharePoint sites and as a result can’t access MetaShare. Administrators in affected tenants can follow the issue SP1166466 in admin portal (note, the issue is not visible for not affected tenants).

    End time: 6 October 2025, 13:00 CEST
    Microsoft informed the issue is now resolved.

    We've identified that a section of service infrastructure is underperforming due to a
misconfiguration, resulting in both reduced site availability and reliability. We're
actively working to resolve the configuration and mitigate impact.


More

All resolved issues