Home > Known Issues
Download this articleKnown Issues
| Known Issues | Identified in Version |
|---|---|
| When connecting a Salesforce tenant in AvePoint Online Services via these steps: Management > Tenant management, then go to Management > User management, and select the Salesforce user sign-in method to add the Salesforce user who consented to the tenant connection app. If the same Salesforce user account is used to sign into AvePoint Online Services more than five times in one day, the tenant connection will become invalid. Root cause: This issue is caused by a limitation in Salesforce's refresh token. Salesforce retains only five refresh tokens per user. When a tenant connection is created using a Salesforce user, a refresh token is generated. Each subsequent sign-in by this Salesforce user into AvePoint Online Services generates a new refresh token. Once the number of refresh tokens exceeds five, the tenant connection's refresh token becomes invalid, causing the connection to fail. | April 2025 |
| In Auto discovery, configure a scan profile to scan Power Automate objects into containers in AvePoint Online Services. The cloud flows at the Off status cannot be scanned into containers in AvePoint Online Services. | October 2023 |
| If you use a scan profile with the app profile authentication method to scan Mailboxes, Microsoft 365 users without the Exchange Online license cannot be discovered and reported in scan history. Root cause: This issue is caused by Microsoft Graph API limitation. | September 2022 |
| If a Microsoft 365 account has multi-factor authentication enabled through a conditional access policy configured in Microsoft Entra ID, the account cannot be used as a service account in AvePoint Online Services. Root cause: This issue is caused by Microsoft API limitations. | March 2022 |
| SharePoint site collections were scanned to a container by using the Creator condition. If the user principal name of a site collection creator is changed in Microsoft Entra ID and the Creator condition is used to scan SharePoint site collections again, the site collections created by the user are removed from the container and the scan result is Out of Policy in the scan history of the scan job. Root cause: If the user principal name of a user is changed in Microsoft Entra ID, the Author attribute of the user's SharePoint site collections cannot be updated in real time. In a scan job, AvePoint Online Services uses the Author attribute to find the site collection creator. If the scan job starts and the Author attribute of a site collection is not updated yet, AvePoint Online Services cannot find the site collection creator by using the original user principal name. Thus, the site collections are removed from the container. The SharePoint site collections that meet the filter rule will be scanned to the container again when the Author attribute is updated. | January 2021 |
| In an advanced mode scan profile, select Country or region as the criterion to scan Mailboxes. The shared mailboxes cannot be scanned. Root cause: AvePoint Online Services uses Microsoft Graph API to retrieve some information like department, country or region. This issue is caused by Microsoft Graph API limitation. Microsoft Graph API does not provide the country or region property value of shared mailboxes. | May 2020 |
| If a Microsoft 365 Group has been added as an AvePoint Online Services user, after the group ID (group email address) is changed in Microsoft 365, the group ID displayed in the User ID column on the AvePoint Online Services User management page is not updated. Users in this group can still use their Microsoft 365 accounts to sign into AvePoint Online Services. | May 2020 |
| Due to the limitation of Microsoft Graph API, AvePoint Online Services cannot scan Exchange Online resource mailboxes. | March 2020 |
| For a Microsoft 365 tenant with the multi-geo license, change an account's mailbox region via PowerShell, and use the app profile authentication method to scan this mailbox in Auto discovery. The scan jobs cannot update the new region of the mailbox into AvePoint Online Services. Root cause: The app profile authentication method uses Graph API to retrieve the region information. After the region information has been changed via PowerShell, the Graph API still returns the previous region information to AvePoint Online Services. | September 2019 |
| The User Role information does not display when viewing the details of a service account profile with MFA enabled. Root cause: The user role information cannot be retrieved when MFA is enabled. | 2.5 |
| In an advanced mode scan profile, the criteria for filtering SharePoint Online site collections contain Size. When a site collection size is calculated, the size of second recycle bin of the site collection is not included. | 2.5 |
On this page