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

  • Search refiners not working in some tenants

    Start time: 6 August 2026

    We have found that in some SharePoint tenants selecting refiners containing special characters breaks the search and no results are returned. Since MetaShare’s filters on the “Search for documents” and “Workspaces” pages are based on search refiners, the same issue happens there.

    We’ve contacted Microsoft regarding this issue.

    As a workaround it is possible to search using the filter, instead of selecting it. For example searching for “RefinableString09:Öppen”, or “status:öppen” (if you have added custom search aliases), will find all documents with that search property value. To find the name of the search property to use you can select the filter and check the name of the property that was used in the URL:

    Update: 7 August 2026

    Microsoft has marked our Service Health issue reported in the Admin Portal as “No issue found” in two tenants where it was reported. We continue to work to get the issue acknowledged and resolved.

  • Some workspaces could be temporarily missing from start page

    Start time: 31 July 2026

    We are aware of an issue that causes some workspaces to be missing from start page. This happens because sometimes SharePoint search breaks how SharePoint sites are indexed (the result does not include values for metadata set on the start page). The issue usually is resolved after the site or its start page is reindexed.

    We are currently getting reports from many customers who are affected by the issue after recent SharePoint update. It seems that the update broke search results for all sites. It also seems that SharePoint will try to reindex all sites, so the issue will eventually get resolved on it’s own, which we have seen happen in some tenants.

    If you are affected, there are several things you can do:

    • All workspaces are still there and can be found by searching for any document they contain and selecting “Show in Workspace” action:
    • You can add frequently accessed workspaces to favorites so they are always easy to find.
    • If the issue affects only a small number of workspaces you can open each of them in SharePoint and republish the start page. This will trigger a reindex that will fix the search result for that site.
    • If a large number of workspaces is affected and you don’t want to use workarounds or wait, you can contact us and we can help you by running a script requesting a reindex on all start pages.

  • 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

  • SharePoint issue: Recently mapped crawled properties are not displayed in Admin Center

    Start date: 9 June 2026
    Resolved: 31 July 2026

    When mapping crawled properties to managed properties (e.g. RefinableString) in the SharePoint Admin Center the mapping is not displayed after changes are saved. We were able to confirm that the mapping is persisted and managed properties are populated with values from added crawled properties, even if the Search Schema UI doesn’t show the mapping.

    While this does not affect the functionality of MetaShare directly, we are getting reports and questions about the issue from MetaShare administrators. We have reported our findings to Microsoft but they reported that no issue was found. We continue monitoring the situation.

    Update: 18 June 2026

    Microsoft has now acknowledged the issue and it can be followed in Microsoft 365 admin center (issue SP1393483)

  • 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: 11 March 2026
    The issue seems now to be resolved by Microsoft. We’ll continue monitoring the issue and verify if the fix reached all affected tenants.

More

All resolved issues