Home > Known Issues
Export to PDF| Known Issues | Identified in Version |
|---|---|
| When sensitivity labels with access control enabled are applied in OneDrive assessment, the application of these labels to risky items may fail if the Let users assign permissions when they apply the label setting is selected. Root cause: The Graph API can't determine if this setting is enabled. | December 2025 |
| When managing user or group access for risky items in OneDrive assessment, the Restricted View permission option is unavailable. Root cause: This is caused by a Microsoft API limitation. | December 2025 |
| Microsoft To Dos are not supported in the 21Vianet environment. | June 2025 |
| When filtering site collections without permissions, the results may sometimes incorrectly include site collections that do have permissions. Root Cause: This is caused by inaccurate data returned by the Microsoft Search API. Workaround: If your organization has an active Insights subscription, you can enable the Retrieve SharePoint site permissions from Insights setting in the MyHub admin center. This setting allows permission data to be fetched from the Insights site permission index instead of the Microsoft Search API, resulting in improved accuracy. | June 2025 |
| End users have permissions to site collections with the Enterprise Search Center or Basic Search Center site template. When end users filter site collections that they have permission, these site collections are not in filter results. Root cause: This issue is caused by the Microsoft Graph API limitation. Site collections with search templates are not available in search results by default. Workaround: To display the site collections in search results, navigate to Site Settings > Search and Offline Availability settings for each site collection, and select Yes in the Allow this site to appear in search results? field. | February 2024 |
| In the following cases, end users have limited access or specific permissions to site collections, but they are regarded as without permissions to site collections. When end users filter site collections by permissions, these site collections are displayed in the without permissions results. • End users are granted permissions to libraries, lists, folders, items, files, or pages of which the permission inheritance has been broken. • End users are shared with permissions via links to libraries, lists, folders, items, files, or pages of which the permission inheritance has been broken. • End users are granted the Records Center Web Service Submitters permission to site collections. • End users are granted the Restricted Interfaces for Translation permission to site collections. • All end users have limited access to site collections with the Document Center template automatically. Root cause: This is caused by Microsoft API limitation. | February 2024 |
| If the group is a role-assignable group, end users cannot leave the group, and group owners cannot add members to the group. | October 2023 |
| To ensure end users can successfully add the MyHub or MyHub for US GCC app to their Teams client, the Chat option in Teams admin center must have ever been turned on. | June 2023 |
| In a hub, business users edit the group settings and update the Send copies of group conversations and events to group members setting. After the edits are saved, it will take about 20 minutes for the updates to take effect. Root cause: This is caused by Microsoft Graph API limitation. | July 2021 |
| When a site collection is created in Microsoft 365, there may be a delay until the site collection is successfully synchronized to MyHub. Root cause: This is caused by a Microsoft Graph API limitation. We have already communicated this issue with Microsoft and the issue will be resolved as soon as possible. | July 2021 |
| The Send an e-mail feature is unavailable in the MyHub app in Teams mobile app. Root cause: This issue is caused by Teams mobile app limitation. | May 2021 |
| If a user is using MyHub with Internet Explorer 11.0.140 (IE 11.0.140) or earlier and applies a new tag to a workspace on the workspace details page, even though the tag has been applied to the workspace, the user can see the tag only after the page is refreshed. Root Cause: This issue is caused by the Internet Explorer limitation. The issue only appears when users use MyHub with Internet Explorer 11.0.140 (IE 11.0.140) or earlier. | March 2021 |
| If a user is using MyHub with Internet Explorer 11.0.140 (IE 11.0.140) or earlier and tries to manage a workspace membership on the workspace details page, such as promoting or removing users from the workspace, even though the configurations succeed, the user can see the updates only after the page is refreshed. Root Cause: This issue is caused by the Internet Explorer limitation. The issue only appears when users use MyHub with Internet Explorer 11.0.140 (IE 11.0.140) or earlier. | March 2021 |