#Helpful Notes When Auto Discovery Scan Results Return Error Codes

The table below lists auto discovery scan jobs’ error messages and related error codes. You can click the error code links to view the helpful notes.

Error Message	Error Code
SharePoint Online has throttled requests from this scan job.	cs0000001
The SharePoint Online environment is temporarily unavailable.	cs0000002
The number of simultaneous PowerShell Sessions a user can open to Exchange Online has reached its limit.	cs0000003
The Group team sites of some Microsoft 365 Groups, Microsoft Teams, and Viva Engage communities cannot be retrieved.	cs0000004
The service account has multi-factor authentication enabled, but MFA has not been configured in the service account profile.	cs0000005
The account in the authentication method profile used by this scan profile does not have the license to access the Environments listed below.	ps0000001
The account in the authentication method profile used by this scan profile does not have sufficient permissions to access the Environments listed below.	ps0000002

#cs0000001

SharePoint Online has a that prevents too many simultaneous requests (SharePoint Online returns the HTTP status code 429). To avoid getting throttled in SharePoint Online, choose the following solutions based on your scenario:

#cs0000002

SharePoint Online has a when the environment is too busy (SharePoint Online returns HTTP status code 503). To avoid getting throttled in SharePoint Online, choose the following solutions based on your scenario:

#cs0000003

Exchange Online PowerShell has a limit for the number of simultaneous sessions a user can open. The screenshot below indicates that an error occurs when the number of sessions exceeds the limit.

To avoid this error, try the following methods based on your scenario:

#cs0000004

Auto discovery uses Microsoft PowerShell to scan Microsoft 365 Groups, Microsoft Teams, and Viva Engage communities, and the Group team sites will be scanned as the Microsoft 365 Groups’ properties. Sometimes, even if there are no existing Group team sites, the property needs to be initialized in Microsoft 365 Outlook.

The scan result of this issue is Partially added. To initialize the Group team sites, sign in to Outlook with a Global Admin account, find Microsoft 365 Groups / Microsoft Teams / Viva Engage communities under the Group tab, and then click Files. Then, the initialization will be completed. You can refer to the screenshot below as an example:

#cs0000005

For organizations that use multi-factor authentication in Microsoft 365 or have enabled conditional access policies in Microsoft Azure, it is recommended to configure the app profiles to be used by the scan profiles in Auto discovery. For additional details on app profiles and auto discovery, refer to Manage App Profiles and Manage Auto Discovery.

If your organization still wants to use scan profiles with the service account authentication method (these scan profiles were transferred from the AOS classic UI in June 2023 release), you must not update the scan profiles. To troubleshoot this error, you can edit the service account profile to update the Microsoft 365 account used in the profile by referring to instructions in Helpful Notes for Passing the Validation Test of a Service Account.

#ps0000001

Go to Microsoft 365 admin center and navigate to Users > Active users, find the account (applied in the service account profile or used to authorize the delegated app), and then click Manage product licenses from the More actions (![The "More actions" icon.](/en/configuration-and-deployment/manage-auto-discovery/images/image91.png "The "More actions" icon.")) drop-down list.

![Clicking "Manage product licenses".](/en/configuration-and-deployment/manage-auto-discovery/images/image92.png "Clicking "Manage product licenses".")

In the account details panel, click the Licenses and apps tab, and ensure that the licenses and apps related to Power Automate or Power Apps have been selected. Click Save changes.

After the changes are saved, check if this account can successfully sign into Power Automate or Power Apps. If so, wait for at least 15 minutes, and then go to AvePoint Online Services to run the scan profile again.

For more information about the Power Platform licenses, refer to the following Microsoft articles: and .

#ps0000002

Go to the Power Platform admin center, click Environments, and click an environment which is reported in the scan history. Click Settings on the ribbon of the environment details page.

![Clicking "Settings" on the ribbon of the environment details page.](/en/configuration-and-deployment/manage-auto-discovery/images/image94.png "Clicking "Settings" on the ribbon of the environment details page.")

On the Settings page, navigate to Users + permissions > Users.

![Clicking "Users + permissions" and "Users".](/en/configuration-and-deployment/manage-auto-discovery/images/image95.png "Clicking "Users + permissions" and "Users".")

On the Users page, find the account (applied in the service account profile or used to authorize the delegated app) and take the following actions based on your scenarios: