Home > Known Issues
Export to PDFKnown Issues
| Known Issues | Identified in Version |
|---|---|
| If the event “When a request is submitted” or “When an approval task is assigned” is configured to trigger a webhook, then when a request to change private channel settings is generated and awaiting approval, the object ID cannot be replaced with the channel ID.Root cause: The channel ID is not in the same GUID format as the object ID, so it cannot be converted to an object ID. | October 2025 |
| The team inactivity threshold is configured for team renewal, however, the renewal task is not generated even when no manual user activity being detected.Root cause: This happens because Opus jobs update the Report.LastActivityDate, creating a false impression of continuous activity, even when users are not actively engaging with the team. | October 2025 |
| When changing a team's privacy to private through a Change Team Settings dynamic service, tenants blocking the Everyone group may temporarily succeed in granting Everyone permissions to the group team site by adding Everyone to SharePoint groups through a subsequent Manage Permissions service that inherits the service scope. Root cause: This is a Microsoft synchronization delay. | June 2025 |
| In the Change Microsoft 365 Group Settings dynamic service, when Remove the custom group picture is selected in the Change group picture setting, the default group picture does not appear immediately after the service request completes, and the custom picture may temporarily remain visible.Root cause: This delay is due to the Microsoft 365 synchronization process. Please wait a moment and try viewing the picture again. | June 2025 |
| If the Viva Engage app is not configured in AvePoint Online Services, Cloud Governance will use the Graph API to import Viva Engage communities and built-in Viva Engage communities that should have been excluded from the import will also be included. | June 2025 |
| In the Microsoft 365 Government GCC High environment, if the Welcome email or Team ID setting is configured for a Create team dynamic service, requests for this service will have a prolonged execution time and result in an error task being generated..Root cause: The Microsoft API requires more time to retrieve the team information than the execution attempts allow.Workaround: Service administrators can manually retry the error task to complete the team creation. | April 2025 |
| The hold status of sites locked in "no access" status cannot be synced to Cloud Governance from Microsoft.Root cause: This is caused by a Microsoft limitation. | February 2025 |
| During the modern renewal process, the renewal task assignee applies a sensitivity label to a group that sets the privacy setting for the group. When the label application is executed, the group's privacy will not be updated in the Workspace report until the synchronization with Microsoft is complete. | December 2024 |
| Once the external sharing setting is changed by a change profile request, it will be reverted to the external sharing setting of the applied sensitivity label, if conflicts, after synchronization with Microsoft.Root cause: The app configured doesn't have sufficient permission to get the label settings.Workaround: Configure the Cloud Governance for Exchange app and assign it the Compliance Administrator role. | December 2024 |
| Deleted site collections from Microsoft continue to appear in the access renewal of guest user renewal tasks and the guest user report.Root cause: The latest site collection status has not been scanned by AvePoint Online Service. Deleted site collections will be removed after the next scan completes. | December 2024 |
| During the guest user renewal process, renewal task assignees removed guest users' access to site collections and group team sites. Although the permissions granted to the guest users are removed after the renewal actions are executed, the guest users still appear in the link sharing list of items within the sites.The behavior is the same as manually removing users from Microsoft. Once the users are removed, they can no longer access the sites and items within the sites via sharing links anymore. | December 2024 |
| When applying the Viva Engage escalation profile to community renewal or contact election tasks, the Restrict posting permission action in the escalation profile is not working for Viva Engage communities created using the modern dynamic service. This action still works for communities not created with the modern service. | December 2024 |
| When choosing to add to the groups or teams in previous service in the Invite guest user service, some error tasks have occurred.Root cause: Due to a synchronization issue, some tenants may experience prolonged delays in synchronizing guest accounts to Exchange. | December 2024 |
| Once the geo-location is changed, any pending classic site collection renewal tasks will be completed automatically, and the site collections will retain their permissions and properties as they were before the renewal tasks. | December 2024 |
| Modern profiles are not supported in the classic Cloud Governance admin center. | October 2024 |
| Viva Engage communities have been deleted but the URLs in the Workspace Report remain accessible immediately after the deletion.Root cause: The synchronization is managed by Microsoft. Wait for it to complete before checking. | October 2024 |
| Guest users are added as Viva Engage community members through community renewal. While the guest users appear as community members in Microsoft 365 immediately, they do not appear in Viva Engage.Root cause: The synchronization between Microsoft 365 and Viva Engage is managed by Microsoft, and the timing of this sync is unpredictable. | October 2024 |
| There is a delay in synchronizing the last post time in the Viva Engage community with Cloud Governance. As a result, if the inactivity threshold is reached, a community renewal task might be incorrectly initiated.Root cause: This is caused by an API delay. | October 2024 |
| External members synchronized via Microsoft Entra B2B cross-tenant collaboration cannot be specified as Viva Engage community admins due to the API limitation. | June 2024 |
| When configuring a Change security group settings request, if the Microsoft Entra roles can be assigned to the group option has been enabled for the security group, the group description and group name cannot be requested to change.Workaround: Assign the Privileged Role Administrator role or RoleManagement.ReadWrite.Directory permisson to related apps. | June 2024 |
| When configuring a Create shared channel or Change shared channel settings service or request, shared mailboxes or resource mailboxes cannot be specified as shared channel owners/members. | February 2024 |
| When you view the shared channel member details of a Create shared channel or Change shared channel settings requests, if the member is a distribution group or mail-enabled security group, only the group members can be displayed on the user card. The group owners cannot be displayed due to the limitation of Microsoft Graph API. | February 2024 |
| If the isAssignableToRole property of a security group/Microsoft 365 Group is true, the group settings such as members and owners cannot be changed by AvePoint Cloud Governance.Workaround: To manage the group settings, assign the Privileged Role Administrator or Global Administrator to the Microsoft 365 (All permissions)/Cloud Governance for Microsoft 365/custom app you use, or you can add the Microsoft Graph API RoleManagement.ReadWrite.Directory permission to the app. | February 2024 |
| An error occurs when IOS users click View details of tasks in Teams.Workaround: Change any system setting for Teams in Settings > Teams on your IOS devices. | February 2024 |
| Business users have permissions to site collections with the Enterprise Search Center or Basic Search Center site template. When business users filter site collections that they have permission in hubs, 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, business users have limited access or specific permissions to site collections, but they are regarded as without permissions to site collections in hubs. When business users filter site collections by permissions in hubs, these site collections are displayed in the without permissions results.Business users are granted permissions to libraries, lists, folders, items, files, or pages of which the permission inheritance has been broken.Business users are shared with permissions via links to libraries, lists, folders, items, files, or pages of which the permission inheritance has been broken.Business users are granted the Records Center Web Service Submitters permission to site collections.Business users are granted the Restricted Interfaces for Translation permission to site collections.All business 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 owner of a Power Automate solution-aware flow is a Microsoft built-in user, the owner cannot be viewed or managed during the Power Automate flow renewal process.Root cause: Microsoft built-in users cannot be retrieved due to the API limitation. | December 2023 |
| If the Microsoft Entra group is a role-assignable group, it cannot be managed via the Microsoft Entra group lifecycle management service. | October 2023 |
| In the classic Cloud Governance admin center, if an IT administrator automatically imports site collections with the Automatically enable AvePoint Cloud Governance App import option selected, the team sites applied with site designs cannot be imported. | August 2023 |
| In the modern Cloud Governance admin center, the IT administrator configures a Change ownership or membership service with the Change ownership setting and with the Generate separate approval tasks for newly added owners option selected. When business users submit a service request to add owners to a distribution group/mail-enabled security group, the owner of the group will be updated to the last approved owner.Root cause: The owners of distribution groups and mail-enabled security groups can only be updated rather than added due to the API limitation. | August 2023 |
| In the modern Cloud Governance admin center, the IT administrator adds a condition of automatic approval for a stage in the generic approval process and configures a distribution group/mail-enabled security group in the condition. When the group owner submits a request with this approval process applied, the stage is not automatically approved.Root cause: The group owners of the distribution group/mail-enabled security group cannot be retrieved due to the API limitation. Only group members can be retrieved. | August 2023 |
| In the modern Cloud Governance admin center, the tenant does not add the Group.ReadWrite.All permission to the custom app but alternatively uses the administrative unit setting to create Microsoft 365 Groups. The IT administrator configures a Create Microsoft 365 Group service for a dynamic service with the Set unique access settings for the group external sharing setting or multi-geo setting enabled.Errors occur when business users submit the service requests.Workaround: Assign the Groups Administrator or Global Administrator role with the administrative unit scope to the custom app. | August 2023 |
| When business users create service requests to manage the ownership or membership of a team via a Change ownership or membership service, they cannot view the team owners or members who are blocked from signing in to Microsoft 365 in the team owners or members lists.Root cause: The team owners or members who are blocked from signing in to Microsoft 365 cannot be retrieved due to the API limitation. | August 2023 |
| For the classic Change Group/Team/Community Settings service and Change team settings dynamic service requests, when business users enter a group, team, or community name that exceeds 120 characters, the group, team, or community cannot be retrieved. | June 2023 |
| When business users configure the scope for a Manage Permission service request, they need to refresh manually to load the group team site containers. | June 2023 |
| If IT administrators use the email templates configured in the classic admin center in dynamic services, the references in the sent emails cannot be replaced with the correct values. | June 2023 |
| When business users review the share links in the renewal task, the external users in a group with access will be displayed in the recommended action. However, if users execute the recommended action, the sharing links with these external users will not be removed. | June 2023 |
| When business users configure the scope for a Manage Permission service request, if the folder name in the URL starts with special characters such as # or %, the URL cannot be validated. | June 2023 |
| If business users add a large number of owners or promote members to owners when renewing the shared channel membership, the task may finish with exceptions.Root cause: This issue is due to the Microsoft API limitation. | June 2023 |
| The Microsoft 365 Global Administrator, who created the Yammer app profile in AvePoint Online Services, submits a request to change Yammer community settings. If their User Principal Name (UPN) and primary email address are different, after the submitted request is approved, the request status will always be shown as In progress in AvePoint Cloud Governance.Root cause: The user's UPN cannot be retrieved via the Yammer API.Workaround: Make sure the Global Admin's UPN and primary email address are the same. | January 2023 |
| An IT administrator configures a questionnaire in Request Management > Questionnaire Management in the classic Cloud Governance admin center. They choose to Add End Points Automatically, configure the custom message for the endpoint, add angle brackets (<>) to the message, for example, , and then save the message. When they edit this custom message again, the content within the angle brackets together with the brackets cannot be shown in the rich text box.Workaround: It's recommended that any angle bracket not be added to the custom message. | January 2023 |
| In Job monitor in the modern Cloud Governance admin center, when IT administrators click the name of the following jobs to download the job result via Excel, if the job name exceeds 211 characters, the downloaded Excel file's name cannot be fully shown; If the job name contains semicolons, only the part before the semicolon will be shown.Update guest user/team/site collection contact election profileUpdate guest user/team/site collection/Power App renewal profileUpdate team/site collection storage management profileUpdate team/site collection external sharing profileDelete guest user/team/site collection contact election profileDelete guest user/team/site collection/Power App renewal profileDelete team/site collection storage management profileDelete team/site collection external sharing profile | January 2023 |
| A business user starts a request via a Create site collection dynamic service. In the request, they select a language that is not English as the site collection language and select Visio Process Repository as the site collection template. After the submitted request is approved, an error task will be generated.Root cause: The Visio Process Repository template is not supported in a non-English site collection. | January 2023 |
| For a site collection created via a create site collection service request, if the user specified as the primary site collection administrator does not have the SharePoint license, they will not be added to the Site admins group in SharePoint. The company administrator and SharePoint administrator will be added to the Site admins group. | January 2023 |
| In Management > Dynamic services in the modern Cloud Governance admin center, an IT administrator configures the Hub site settings in a Create site collection dynamic service and chooses to Register the site collection as a hub site. If a business user submits a request via this service, after the submitted request is successfully completed, a site collection is created and registered as a hub site.Then, an IT administrator configures the Hub site settings in a Create site collection or Create team dynamic service, and chooses to Associate the site collection with a hub site. A business user starts a request via this service and chooses to associate the site with the hub site that was newly registered before. After the submitted request is successfully completed, a site collection or group team site is created and registered as a hub site. However, there will be a delay showing this hub site association in Sites > Active sites in the SharePoint admin center. | November 2022 |
| In Azure Active Directory, if the email address of User A is added as the Other emails for multiple users, when a business user starts a request to create a site collection and enters the email address of User A in the people picker as the site collection administrator, all users whose Other emails are using User A's email address in Azure Active Directory will be loaded in the search results. | November 2022 |
| In Management > Dynamic services in the modern Cloud Governance admin center, if an IT administrator configures the Site collection template in a Create site collection dynamic service and adds the Visio Process Repository template as an available template. Then, in the AvePoint Cloud Governance Portal, a business user starts a request via this service and uses the Visio Process Repository template as the site collection template, after the request is submitted and approved, an error task may be generated. | November 2022 |
| In a Team, Group, and Community Report exported from the classic Cloud Governance admin center, only the renewal task assignees will be displayed under the Assignee column. For other types of tasks, IT administrators can go to the Directory > Workspace report in the modern Cloud Governance admin center and view users under the Phase assignee column. | November 2022 |
| In the modern Cloud Governance admin center, with the site collection contact membership management enabled in Settings > System settings > Contact membership: | |
| When an IT administrator chooses to automatically add primary and secondary contacts as site collection administrators, sometimes, the original contacts will be removed from the site collection administrator group during the following Cloud Governance management processes: Contact electionChange/Specify contactContact renewalUpdate information in bulkWhen an IT administrator chooses to automatically add primary and secondary contacts as members of a specified SharePoint group and Remove original contacts from the group at the same time, sometimes, the original contacts will not be removed from the site collection administrator group during the following Cloud Governance management processes: Contact electionChange/Specify contactContact renewalUpdate information in bulkRoot cause: These are caused by SharePoint CSOM API limitations. | November 2022 |
| When a workspace renewal profile, configured in System > Recertification or Renewal Management in the classic Cloud Governance admin center, is updated with some renewal options changed in the profile, the changes will not influence the renewal task that has already been generated based on the renewal profile. | November 2022 |
| An IT administrator adds new guest users as team members in a Create team dynamic service in Management > Dynamic services in the modern Cloud Governance admin center. If a business user submits requests via this service, after the requests are successfully completed, there will be a delay in adding new guests as team members. | |
| Root cause: This is caused by Microsoft Graph Teams API limitations. | November 2022 |
| If a business user starts a request via a Create team dynamic service, which is configured in Management > Dynamic services in the modern Cloud Governance admin center, and adds team members in the request, after the submitted request is successfully completed, and a team is created:Some team owners may not be added as group owners.Some team owners may not be added as group members.Some team members may not be added as group members. | November 2022 |
| Due to Microsoft Graph Teams API limitations, currently, the multi-geo locations configuration is not supported in a Create team dynamic service in Management > Dynamic services in the modern Cloud Governance admin center. | November 2022 |
| When business users start a request via a Create site collection dynamic service, if the site design pre-defined by IT administrators and the selected site collection template are not of the same type, after the submitted request is approved, an error task will be generated. To use a certain site design for a certain site collection template, IT administrators can configure a Condition or Switch control in the service and use different site designs for different templates.When business users start a request via a Create site collection dynamic service, with the classic site collection template and pre-defined site design configured, after the submitted request is successfully completed, a site collection will be created regardless of the site design. | November 2022 |
| If a business user starts a request via a Create site collection dynamic service to create site collections and selects the Business Intelligence Center template as the site collection template, after the submitted request is approved and processed, an error task will be generated due to limitations of the template. | November 2022 |
| If a business user starts a request via a Create site collection dynamic service to create site collections and selects the Team Site - SharePoint Online configuration template as the site collection template, after the submitted request is approved and processed, an error task may be generated due to limitations of the template. | November 2022 |
| When IT administrators edit an existing Create Team service created before the following dates with sensitivity labels configured in the service, the Default Sensitivity Label will be shown as Select one, and they must select a default sensitivity label from the drop-down list.Insider environment – December 24, 2021Commercial production environment – January 9, 2022U.S. Government production environment – January 16, 2022 | January 2022 |
| In the following scenario: A site collection is created in tenant A. In the Change Site Collection Settings service, IT administrators allow requesters to change sensitivity labels, and select sensitivity labels from multiple tenants, which are available for requesters to select in the request form. If users submit a change site collection settings request in Microsoft Power Automate and select a sensitivity label from another tenant for the site collection, after the request is completed, the sensitivity label will not be applied to the site collection.Root cause: In Microsoft Power Automate, all sensitivity labels that IT administrators configured in a Cloud Governance service are available for users to select in the request regardless of user's tenant. Due to Microsoft Graph API limitations, no error task will be generated while applying an invalid sensitivity label. | January 2022 |
| If business users submitted a group/team lifecycle management service request before the following dates to update the group team site quota of a team, and the team has a private channel, after the following dates, when the request is completed, the storage quota of this private channel site will not be successfully updated.Insider environment – December 24, 2021Commercial production environment – January 9, 2022U.S. Government production environment – January 16, 2022 | January 2022 |
| If business users submit a change group/team settings request for a group/team with hidden membership and select a sensitivity label for the group/team in the request form. After the request is completed, the sensitivity label will not be successfully applied to the group/team.Root cause: Due to Microsoft Graph API limitations, an exception will occur when applying sensitivity labels to a group/team with hidden membership. | January 2022 |
| In the modern Cloud Governance admin center, IT administrators enable the sensitivity label for a tenant, and select a sensitivity label whose privacy is public in a change group/team settings service. If business users submit a change group/team settings request using this service for a public group/team, and change the sensitivity label to a private one, after the request is completed, the private sensitivity label is successfully applied and shown in Microsoft 365. However, in the Workspace report in the modern Cloud Governance admin center, the privacy is still shown as Public temporarily.Root cause: Due to Microsoft Graph API limitations, the privacy of a sensitivity label cannot be retrieved in real-time.Workaround: After the Cloud Governance workspace information synchronization scan job is completed, the privacy of a sensitivity label can be synchronized successfully, and the privacy of a sensitivity label will be displayed properly. | January 2022 |
| In the modern Cloud Governance admin center, IT administrators enable the renewal permission index for a tenant. If the audit log functionality for this tenant is turned off via Exchange Online PowerShell, IT administrators can still save their renewal permission index configuration even though the audit log is turned off.Root cause: This is caused by Microsoft Graph API limitations. | January 2022 |
| If a tenant name has been changed in the Microsoft 365 admin center, and IT administrators configure a Yammer community manual export profile to export Yammer communities from the tenant, in the exported Excel file, the Yammer community network name will not be updated along with the latest tenant name.Workaround: Delete the existing Yammer community app profile from AvePoint Online Services and create a new Yammer app profile. | January 2022 |
| A Yammer community is pending renewal in AvePoint Cloud Governance, and the Microsoft 365 connected Yammer group is deleted in Microsoft 365. Due to the Yammer API delay, the community will not be deleted in Cloud Governance immediately after the group deletion, and it will be active for a while. | November 2021 |
| In AvePoint Cloud Governance, when business users submit a request to create a private channel in a team, and the request is approved, if the site of the General channel in a team has never been previously accessed before, the private channel site's provisioning will fail 12 hours after the request's approval, and an error task will be generated.Workaround: In Microsoft Teams, navigate to the General channel in the team and click the Files tab in the channel. | November 2021 |
| In an Excel file, the total number of characters that a cell can contain is 32,767 characters. In AvePoint Cloud Governance, when the IT administrator exports a report to an Excel file, and the column value's length of an exported object exceeds 32,767 characters, then the report cannot be successfully exported. | November 2021 |
| Note the following issues about private channel provisioning in AvePoint Cloud Governance:If business users submit a request to create a private channel and add a user as a channel member, if the specified user has signed in to Microsoft Teams before the private channel's provisioning, after the private channel is successfully created, this user may not be shown as a channel member. The user must sign out of Microsoft Teams and sign in again. This phenomenon is consistent with Microsoft 365's behavior.After a create private channel task completes, and users click the newly created private channel's link on the request details page, they may not have permissions to visit the private channel temporarily, and they can try again later. This is caused by Microsoft Graph API limitations. | November 2021 |
| When business users submit a request to create a team and choose to create a team from an org-wide team in Team template, after the request is approved, an error task will be generated.Root cause: There is no available API to retrieve an org-wide team. | November 2021 |
| When business users submit a request to copy the group permissions from a source site collection to a destination site collection, when the request is completed, the Microsoft 365 Groups' permissions to the source site collection cannot be successfully copied to the destination site collection.Root cause: The content move job is executed by DocAve Online, and copying Microsoft 365 Groups is currently not available in DocAve Online. | November 2021 |
| Beginning October 1, 2022, Microsoft has disabled Basic Authentication in all tenants.If your organization is using the commercial environment of AvePoint Cloud Governance, influenced by the Basic Authentication retirement, the following configuration in a Create Group/Team service may not take effect after the request is completed:Welcome Email Subscribe MembersIf your organization is using the U.S. Government environment of AvePoint Cloud Governance, influenced by the Basic Authentication retirement, the following configurations in a Create Group/Team service may not take effect after the request is completed:Welcome Email Subscribe MembersOutlook ExperienceExchange Global Address List | November 2021 |
| With the sensitivity label integration enabled, the following issues will occur due to Microsoft Graph API limitations:After a sensitivity label is newly created in Microsoft 365, it's not available in Cloud Governance services immediately after its provisioning, and this performance is consistent with Microsoft 365 as it'll take a while for the newly created sensitivity labels to take effect.For sensitivity labels that without Groups & sites enabled as the label's scope in the Microsoft 365 compliance center, they are still available in Cloud Governance.After workspaces with sensitivity labels applied are created via Cloud Governance, privacy settings of the sensitivity labels cannot be retrieved immediately. Therefore, after the successful workspace provisioning, in the Workspace report in Cloud Governance, the column value for Privacy will be shown as Private regardless of the actual privacy settings. Until the workspace information synchronization job is completed, the actual privacy settings can be retrieved and shown correctly. After site collections with sensitivity labels applied are created via Cloud Governance, privacy settings of the sensitivity labels cannot be retrieved immediately. Therefore, after the successful site collection provisioning, in the Workspace report in Cloud Governance, the column value for External sharing for site will be shown as Not allowed regardless of the actual privacy settings. Until the site collection information synchronization job is completed, the actual privacy settings can be retrieved and shown correctly.Once the multi-factor authentication (MFA) is enabled for the service account, the sensitivity label cannot be applied successfully to a group/team, and an error task will be generated. | September 2021 |
| When a business user start a request to change Yammer community settings and copy the community's e-mail address to the people picker field to specify the community name, if the community e-mail address is not consistent with the community name, the e-mail address check can pass, but it will be shown as an invalid format.Root cause: If a community's e-mail address is not consistent with the community name, the Yammer community information cannot be retrieved via the Yammer REST API. | July 2021 |
| In a Create Team service, the IT administrator has the following configurations:Multi-Geo Locations – Enable group team site provisioning in multi-geo locationsTeam Template – Allow business users to create a team from an existing team and/or Allow business users to create a team using a team template Due to current Microsoft Graph Teams API limitations, Cloud Governance is unable to set a specific geo-location at the time of provisioning when these settings are enabled. After the team is created in the default geo location, Cloud Governance invokes another Microsoft Graph API to migrate the team and group team site to the geo location selected in the Create Team service. Due to Microsoft Graph API limitations, an error may occur during the team and group team site migration process. If any error occurs, Cloud Governance will delete the team and group team site from the default location, and the deleted group team site can still be found in your recycle bin. | July 2021 |
| When the IT administrator created the Yammer app profile in AvePoint Online Services, a user who is the Yammer Verified Admin was used to log in Yammer. When business users start a request to create a Yammer community, they add this user as a community member. After the request is completed, this user will not receive an invitation e-mail as the e-mail is sent from the user who logs in to Yammer when creating the app profile, and it is sent by Microsoft 365. | July 2021 |
| When a site collection is created in Microsoft 365, it may take a moment for the site collection to be successfully synchronized to and found in any hub.Root cause: This is caused by Microsoft Graph API limitations. We have already communicated this issue with Microsoft, and the issue will be resolved as soon as possible. | July 2021 |
| When the IT administrator sets terminology for terms in the following types: | |
| requester (Auto-generated task), workspace type, workspace phase, workspace status, task type, service type, and geo location. Then, the IT administrator immediately clears the cache of the browser, signs in to the Cloud Governance Portal, and go to the Home page or the My tasks page to check the current terminology. However, the new terminologies do not take effect.Root cause: It will take about 10 minutes for the new terminology of terms in specified types to take effect in the Cloud Governance Portal. | July 2021 |
| When an IT administrator configures E-mail settings in the modern Cloud Governance admin center and chooses to use A Microsoft 365 account as the E-mail sender, if they also choose Send as a group to allow the Microsoft 365 account to send notification e-mails on behalf of a group, the Actionable messages configurations will not take effect in notification e-mails.Root cause: This issue is caused by the limitations of actionable messages in Outlook. | March 2021 |
| When an IT administrator configures E-mail settings in the modern Cloud Governance admin center and chooses to use A Microsoft 365 account as the E-mail sender, if they also choose Send as a group to allow the Microsoft 365 account to send notification e-mails on behalf of a group, the dynamic distribution group is not supported to be specified as the e-mail sender.Root cause: The dynamic distribution groups added in the Microsoft Exchange admin center will not be synchronized to the Azure Active Directory. So dynamic distribution groups cannot be retrieved via Microsoft Graph API, and they are not supported in AvePoint Cloud Governance. | March 2021 |
| When an IT administrator configures E-mail settings in the modern Cloud Governance admin center and chooses to use A Microsoft 365 account as the E-mail sender, if they add a Microsoft 365 account with the free trial license and send a test e-mail, the test e-mail may not be delivered to the mailbox successfully.Root cause: This error may happen to a Microsoft 365 trial tenant. A Microsoft 365 account with the free trial license may be limited by Microsoft as it may be regarded as a low-reputation IP address.Workaround: Contact Microsoft support for assistance or add a Microsoft account with a paid license as the e-mail sender. | March 2021 |
| When configuring the Lookup metadata, if the IT administrator chooses to Select metadata and an additional SharePoint library/list column to refine lookup results and lookup value from a SharePoint library/list Calculated column, after a request is started via the service with this Lookup metadata applied, the metadata value cannot be successfully retrieved and shown in the request form.Root cause: This issue is caused by SharePoint API limitations. | March 2021 |
| When an IT administrator configures E-mail settings in the modern Cloud Governance admin center and chooses to Enable actionable messages on notification e-mails, if the default branding logo is set, in notification e-mails sent from AvePoint Cloud Governance, the banner will be displayed in the default color. If the custom branding logo is set, in notification e-mails sent from AvePoint Cloud Governance, the banner will not be shown.Root cause: This issue is caused by the limitations of actionable messages in Outlook. | March 2021 |
| The original default message body in the Built-in Site Collection Renewal Task Auto-Cancellation E-mail Template has been updated to The renewal task for "Site Collection Title" has been canceled. No further action is required for this task. | |
| The original default message body in the Built-in Group/Team Renewal Task Auto-Cancellation E-mail Template has been updated to The renewal task for "Group Name" has been canceled. No further action is required for this task. | |
| Note that for customers who signed up for AvePoint Cloud Governance before November 8, 2020, the message body updates will not take effect. | March 2021 |
| In Team templates in the modern Cloud Governance admin center, the IT administrator adds a team template whose locale is not English. When configuring the Team Template in a Create Team service, the IT administrator chooses to Allow business users to create a team using a team template and adds this template to the service. Then, a business user submits a request via this service to create a team using this template. After the request is submitted and approved, an error task is generated.Root cause: Due to Microsoft Graph API limitations, it is not supported to create a team using a team template whose locale is not English. | March 2021 |
| When configuring the Team Template in a Create Team service, the IT administrator chooses to Allow business users to create a team using a team template and adds a team template that is newly created in the Microsoft Teams admin center if a business user submits a request via this service to create a team using this template, after the request is submitted and approved, an error task may be generated.Root cause: Due to Microsoft Graph API limitations, it may be failed to create a team using a template immediately after the template is newly created in the Microsoft Teams admin center. | March 2021 |
| If a user is using Cloud Governance 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 Cloud Governance with Internet Explorer 11.0.140 (IE 11.0.140) or earlier. | March 2021 |
| If a user is using Cloud Governance 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 Cloud Governance with Internet Explorer 11.0.140 (IE 11.0.140) or earlier. | March 2021 |
| When a business user submits a request to create a team via a Create Group/Team/Community service, in the request form, the business user chooses to Create a team from template and copy members from the team template, after the request is submitted and approved, an error task is generated and the team members cannot be copied from the team template.Root cause: This is caused by Microsoft Graph API limitations.Workaround: Do not configure the request form to only copy team members from the team template. | January 2021 |
| When configuring the people picker filter profile in the modern Cloud Governance admin center, if the IT administrator enables user filters to only allow users of a mail-enabled security group to be specified in the people picker, when a business user specifies a user who is the owner of the mail-enabled security group in a request form or renewal task limited by this people picker profile, the user cannot be searched out.Root cause: Due to the Microsoft Graph API limitations, the owner of a mail-enabled security group cannot be retrieved. | November 2020 |
| In the following scenario: The IT administrator created Azure Active Directory Property metadata when configuring the services as listed below and chose to get the property value of a primary/secondary contact as the default metadata value. Create User serviceChange User Properties serviceCreate Group/Team/Community serviceChange Group/Team/Community Settings serviceUser Lifecycle Management serviceGroup/Team/Community Lifecycle Management serviceThe metadata is then applied to a Create Group/Team/Community service, Create Site Collection service, Change Group/Team/Community Settings service, or Change Site Collection Contact or Administrator service. When a business user starts a request using one of these services and edits the contact in the request form, the metadata value cannot be updated automatically corresponding to the newly specified contact. Note that this issue only occurs if the metadata was configured before November 8, 2020.Workaround: Navigate to Cloud Governance Settings > Metadata. Select the metadata, click Edit, and then click Save and Update to All Applied Services. | November 2020 |
| If an organization's Azure Active Directory has a deny or allow domain list configured in the External collaboration settings > Collaboration restrictions, when a business user submits a request to invite a new guest user to their organization's directory, AvePoint Cloud Governance cannot validate whether the guest user’s domain is allowed. If a guest user's domain is not allowed, Cloud Governance cannot add the guest user to the organization's directory even if the request is approved. The request status is Problem encountered and an error task is assigned to the administrator contact of the service. The administrator contact can see the following error message when viewing the error task details: Your organization does not allow collaboration with the domain of the user you're inviting. Contact your admin to allow collaboration with this domain.Root cause: Due to Microsoft Graph API limitations, AvePoint Cloud Governance cannot retrieve the deny or allow domain list configured in an organization's Azure Active Directory. | July 2020 |
| If a Create Group/Team service is designed to automatically populate group/team ID with group/team name and hide group/team ID from business users, in a request for this service, if the length of the new group/team name exceeds 64 characters, the first 64 characters are used to construct the group/team ID. If there is an existing group/team with the same ID, an error task will be generated when AvePoint Cloud Governance executes the request to create the group/team and the following error message will be displayed in the error task: There is an existing group/team that has the same group/team ID. | July 2020 |
| If an administrator sets up a naming policy on Microsoft 365 Groups in Azure Active Directory, and an attribute is added as the prefix or suffix in the naming policy, in the Create Group/Team service, the Construct group/team name and Set group/team ID rule options are not enabled. When business users request to create a Microsoft 365 Group or Microsoft Team in AvePoint Cloud Governance via this service request, an error task will be generated and the group/team will not be created successfully.Root Cause: This issue is caused by Microsoft Graph API limitations. | July 2020 |
| AvePoint Cloud Governance no longer uses the Microsoft 365 service account to create Microsoft Teams. Now the app profile authentication method is used to create teams. When AvePoint Cloud Governance invokes Microsoft Graph API to create teams, the Microsoft Graph API may be unstable at times and will return an error. AvePoint Cloud Governance will retry up to ten times. If the issue still exists after ten retries, an error task will be generated. | May 2020 |
| The administrator sets up a naming policy on Microsoft 365 Groups in Azure Active Directory, and an attribute is added as the prefix or suffix in the naming policy. In the Create Group/Team service, the Construct group/team name and Set group/team ID rule options are not enabled. When business users request to create a Microsoft 365 Group or Microsoft Team in AvePoint Cloud Governance via this service request, an error task will be generated and the group/team cannot be created successfully.Root cause: This issue is caused by Microsoft Graph API limitations. | May 2020 |
| When a team owner or member is removed from the team via a Change Group/Team Settings request, team membership recertification task, or team renewal task and the user is the last owner of a private channel in the team, upon the request/task completion, the user is removed from the team and the private channel. Root cause: Removing the last owner of a private channel is not allowed in the Microsoft Teams client. However, the last owner can be removed via invoking Microsoft Graph API. | March 2020 |
| A team owner or member is removed from the team via a Change Group/Team Settings request, team membership recertification task, or team renewal task. This user is a member or owner of a private channel in the team. Upon the request/task completion, the user is removed from the team as well as the private channel, but the user can still be searched for in the channel. Once the user is added back to the team, the user is still the owner or member of the private channel.Root cause: This issue is caused by Microsoft Graph API limitations. | March 2020 |
| If you start one of the following types of requests from the Site Information Card app part or Cloud Governance Panel, the request page that you will be brought to in the AvePoint Cloud Governance Portal will be blank: Create User, User Lifecycle Management, and Change User Properties.Root cause: AvePoint Cloud Governance has finished the transition to the new end user experience – The AvePoint Cloud Governance Portal. When you start a request from the Site Information Card app part or Cloud Governance Panel, you are directed to the AvePoint Cloud Governance Portal. The AvePoint Cloud Governance Portal does not support these request types. This issue does not exist if your tenant is using the Japan West (Osaka) data center and the Direct business users to the AvePoint Cloud Governance Portal checkbox in Settings > Preferred End User Interface is deselected. | November 2019 |
| A filter has been set in the Site Collection Report before September 15, 2019. The filter is used to filter site collections by specific primary site collection contacts. After September 15, 2019, view the Site Collection Report. The report is blank.Root cause: AvePoint Cloud Governance now uses users' object IDs as the unique identifier for Microsoft 365 users. The filter saved before September 15, 2019 did not contain the primary site collection contacts' object IDs.Workaround: In the Site Collection Report, click Set Filter on the ribbon, and then click Generate Report to re-generate the report. | September 2019 |
| If your tenant has no impersonation account configured in AvePoint Cloud Governance, AvePoint Cloud Governance will use Microsoft Graph APIs to create Microsoft 365 Groups and Microsoft Teams. The Microsoft Graph APIs method has the following limitations:Multiple domains are not supported. AvePoint Cloud Governance will create groups and teams in your default domain.AvePoint Cloud Governance cannot change the language of the welcome e-mail that Microsoft sends to the group or team mailbox upon the group or team provisioning. The welcome e-mail is in English.AvePoint Cloud Governance cannot retrieve the last modified time of groups or teams. Only the last modified time of group team sites can be retrieved.If the impersonation account configured in AvePoint Cloud Governance does not have the Exchange Administrator role, you cannot configure settings for Subscribe Members and Outside Senders using the AvePoint Cloud Governance classic Create Microsoft 365 Group or Microsoft Team service, or classic Change Group/Team Settings service. | May 2019 |
| Limitations for the Azure Active Directory Property metadata:For security concern, the password property and the properties in Authentication contact info cannot be used as the data source.The built-in properties assignedLicenses and assignedPlans are not supported.The values of the built-in property UsageLocation retrieved from Microsoft Graph API are abbreviated, such as CN.If the Azure Active Directory Property metadata value retrieved from an Azure AD property value is not a user or group and the metadata is used to set approval process approver, an error task will be generated for the corresponding request. | March 2019 |
| When a Microsoft Team has multiple team owners and one or more team owners do not have a license for Microsoft Teams in Microsoft 365, due to a Microsoft Graph API issue, the team may not be created successfully.Workaround: Make sure all owners of the team have the license for Microsoft Teams in Microsoft 365. | March 2019 |
| If a Create Group/Team service was created before November 25, 2018, and Assign by Business User was selected in the Microsoft Teams section, requesters were able to enable Microsoft Teams functionality for new Microsoft 365 Groups. From November 25, 2018, the Create Group/Team service has been updated to include team settings. With this change, only an IT administrator can decide if the service is for group provisioning or team provisioning. If you have a Create Group/Team service with the Assign by Business User option selected for Microsoft Teams, business users can no longer choose whether to enable Microsoft Teams functionality. If Enable Microsoft Teams functionality is selected in the service, the team will be created upon completion of the request. If Enable Microsoft Teams functionality is deselected in the service, only the group will be created upon request completion but no team will be created for the group.Workaround: Create an additional Create Group/Team service. With two Create Group/Team services, one service can be used to create groups, and the other one can be used to create teams. | November 2018 |
| The site collection policy icon configured in a site collection policy cannot be displayed on the site collection homepage if the policy is applied to a modern team site or communication site. | September 2018 |
| When you access AvePoint Cloud Governance via its URL, rather than via AvePoint Online Services, single sign-on (SSO) is supported. If you are using a Microsoft 365 account to sign into another app on the same browser, you will be automatically signed into AvePoint Cloud Governance. However, the Session Timeout Setting configured in AvePoint Online Services does not take effect. The session timeout duration is one hour. | September 2018 |
| Actionable Messages are enabled in Settings > E-mail Settings. A Microsoft 365 group is assigned as the approver of a service request. A member of the group logs into the Outlook client. In the reading pane, the Approve and Reject buttons do not show up in the notification e-mail for request approval.Workaround: Double-click the e-mail to open it in a separate window, and you can see the Approve and Reject buttons. | July 2018 |
| The automatic deployment of the Cloud Governance Panel is enabled in the AvePoint Cloud Governance App and App Part section within Create Site Collection services, Create Site services, or Create Group/Team services. Adding the Cloud Governance Panel to modern team sites, communication sites, or group team sites will result in a blank homepage, but users can edit the site homepage.Root Cause: This is due to a Microsoft 365 limitation.Workaround: Download the Cloud Governance Panel app package (the SharePoint Framework extension version), and then manually upload the app package to the app catalog. For details, refer to the instructions in the AvePoint Cloud Governance Administrator Guide. After the app package is uploaded to the app catalog, the Cloud Governance Panel will be automatically added to all modern sites in your tenant. Disable the automatic deployment of the Cloud Governance Panel in the Create Site Collection/Create Site/Create Group/Team services and make sure the automatic deployment of the AvePoint Cloud Governance App is enabled in the services.Note that the icon of the Cloud Governance Panel (the SharePoint Framework extension version) will be displayed on every page of the modern team sites, communication sites, or group team sites. | April 2018 |
| An IT Admin specifies a group as the additional site collection administrator in a Create Site Collection service, and then saves and activates this service. A business user starts a request via this service. After the site collection is created, a member of the group logs into AvePoint Cloud Governance, and then navigates to the My Sites report. The created site collection is not displayed in the report. | April 2018 |
| AvePoint Cloud Governance cannot clone or transfer user permissions if your tenant only has app profiles configured in AvePoint Online Services, but does not have any Microsoft 365 service account profiles or service account pool.Workaround: Configure Microsoft 365 service account profiles or service account pool in AvePoint Online Services. | January 2018 |
| AvePoint Cloud Governance cannot create communication sites if your tenant only has app profiles configured in AvePoint Online Services, but does not have any Microsoft 365 service account profiles or service account pool.Workaround: Configure Microsoft 365 service account profiles or service account pool in AvePoint Online Services. | January 2018 |
| An IT Admin creates User Profile Property metadata but cannot get values from user profile property if the AvePoint Online Services Administration for Azure app is failed to be re-authorized in AvePoint Online Services.Root Cause: Without the successful re-authorization, the Read and write all users' full profiles permission is not granted to the AvePoint Online Services Administration for Azure app, and AvePoint Cloud Governance cannot obtain user profile properties of the current tenant via this app. | January 2018 |
| Create metadata without enabling the Display the metadata in reports option and add this metadata to a Create Site service. Sites are created applied with this metadata, or import sites applied with this metadata to AvePoint Cloud Governance. Edit this metadata to enable the Display the metadata in reports option. In My Sites report and Site Report, the value of this metadata is N/A. | January 2018 |
| Due to SharePoint Client API limitations, AvePoint Cloud Governance cannot create site collections with the templates of Visio Process Repository and Review Center. | January 2018 |
| The language selected in a Create Site Collection service or service request does not take effect when the site collection template is Communication Site.Root cause: The issue is caused by a limitation of Microsoft 365 API. | 1.9.4 |
| [Microsoft Edge Browser] In a Create Library/List request, select the Keep the following number of major versions option, do not enter any number, and then submit the request. The page does not respond for a while, and then it automatically recovers. | 1.9.3 |
| In Microsoft Edge Browsers, in Import Existing Microsoft 365 Objects > Export Mode > Export Location, choose the Export to an export location method, and click Add New Location. The New Report Export Location window appears. There's no vertical scroll bar in the window, which results in the situation that the Validation Test button is not available.Root cause: The issue is caused by special styles of the Microsoft Edge browser. | 1.9.3 |
| For site collections with the Publishing Portal, Enterprise Wiki, or Communication Site template, AvePoint Cloud Governance cannot lock the site collections in "read-only" status.Root Cause: Microsoft does not provide site policies to Communication Sites, Publishing Portal, or Enterprise Wiki site collections. Therefore, AvePoint Cloud Governance cannot lock the site collections in "read-only" status by creating a site policy. | 1.9.3 |
| In Microsoft Edge Browsers, in Metadata Management: When defining the description of metadata, cannot only apply indent, bullet, and numbering styles to the selected content. The style is applied to all content.Root cause: The issue is caused by special styles of the Microsoft Edge browser. | 1.9.0 |
| When a business user submits a request via the Create Group service, a new Microsoft 365 group is created. If the business user then submits a Change Group Settings service request for this group, after the request is approved, an error task is generated. The group settings cannot be successfully changed.Root Cause: The schedule timer job of Exchange Online has not finished the initialization for the mailbox of the newly created Microsoft 365 group.Workaround: The approver can click Retry in the error task after the mailbox for the group has been initialized. | 1.8.4 |
| In the User Policy configuration page or Change Group Settings request page, an error page may appear and the task for applying user policy, creating Microsoft 365 group, or changing Microsoft 365 group settings may generate an error task with the following error message: Processing data from remote server outlook.office365.com failed with the following error message.Root Cause: AvePoint Cloud Governance manages User Policy and Microsoft 365 groups via Exchange Online PowerShell. The error is related to Exchange Online PowerShell. The maximum number of open Exchange Online PowerShell connections for each tenant is three, which is the Microsoft 365 limit. If the ongoing applications (including AvePoint Cloud Governance, DocAve Online, and other products) connect to Exchange Online PowerShell at the same time, and the number of connections exceeds three, this error will occur. | 1.8.1 |
| When an IT Admin creates and saves a site template in SharePoint Online and the template file name contains special characters such as t!e@s't, when a Create Site service > Site Template, the IT Admin selects the newly created site template, and the business user submits a request via this service, after an approver approves the request, an error task is generated. The system error message is The selected site template is not supported for creating this type of site.Root Cause: When a custom template is retrieved from the SharePoint Online API, the SharePoint Online API will automatically filter out the template file whose file name contains special characters; therefore, the template file will not be returned in search results using the SharePoint Online API. | 1.7.2 |
| In the Service Permissions field of a service, if an IT Admin chooses the Select users or groups to use this service option, enters a Microsoft 365 group in the text box, and saves and activates the service then users within the entered Microsoft 365 group will not be able to find this service in the Start a Request page.Root Cause: The Microsoft 365 group does not exist in AvePoint Online Services, but does exist in the AvePoint Cloud Governance database.Workaround: Navigate to AvePoint Online Services > Settings > UserManagement, and add the Microsoft 365 group as AvePoint Online Services users. | 1.7.1 |
| If the Import Existing Site Collections and Sites feature is used to import the following SharePoint Online built-in site collections .../portals/community and .../portals/hub, they cannot be imported to AvePoint Cloud Governance even if the Custom Script settings are enabled. AvePoint Cloud Governance cannot update the AllProperties property of these site collections. | 1.6 |
| In a Create Site Collection service if the Select template later option is selected in the Site Collection Template field and if the Automatically enable AvePoint Cloud Governance App as well as Automatically add the Site Information Card app part into the homepage options are enabled, after a request for this service is completed the site collection is created, but the AvePoint Cloud Governance App and app part are not deployed to the site collection. | 1.5 |
| When adding the AvePoint Cloud Governance App to a site collection or site, there is a Select Installation Language option in the Do you trust AvePoint Cloud Governance window. The language selected here does not take effect on the AvePoint Cloud Governance App because the display language of this app inherits the language of the site collection or site. | 1.5 |
| When checking members in SharePoint Online, members and All Users (membership) are retrieved. The display names of members and All Users (membership) are in conflict. In SharePoint Online, different users or security groups can have a same display name, but AvePoint Cloud Governance can only use the display name that is the first selected, so All Users (membership) is used for the metadata value. | 1.2 |
| There is no support for configuring questionnaires when accessing AvePoint Cloud Governance via Internet Explorer 8. | 1.1 |
| AvePoint Cloud Governance cannot retrieve the last access time of site collections. Instead, the site collection's last modified time will be the last access time.Root Cause: This issue is caused by SharePoint Online API. SharePoint Online API does not have "GetSiteCollectionLastAccessDate". Due to a SharePoint Online API limitation, AvePoint Cloud Governance retrieves the site collection Last Modified Time as the Last Accessed Time. | 1.1 |
| When viewing the AvePoint Governance Automation expiration notification e-mail via Windows Mail, the e-mail content and the pictures are not displayed properly. When you use Internet Explorer 9 to access Microsoft 365 Outlook, the pictures within the e-mail are not displayed properly. | 1.1 |
| Site size does not update in database when using AvePoint Cloud Governance to create a site. When you create a site, edit the site title and create a library/document in the site. In Timer Service Configuration Management, enable the site information synchronization job and modify the interval. After the site information is synchronized, the site size is not updated in the database. | 1.0 |
| If you create a custom library template in SharePoint Online with Include content selected and then create a Library/List service for this custom library in AvePoint Cloud Governance, approving a Create List/Library request will create a library without content. This is due to a SharePoint Online API limitation. | 1.0 |
| In the Create Site service, site collection URLs that contain -public in the Template store field will not be checked as valid. This is due to a SharePoint Online API limitation. | 1.0 |
On this page