Home > Appendices > Manage Account Pool (Obsolete) > Overview
Export to PDF*Note: The information in this section is only for customers who have configured service account pools in the AOS classic UI (before June 2023 release).
SharePoint Online has a built-in throttling feature that prevents one account from processing several requests simultaneously. To avoid getting throttled or blocked in SharePoint Online, you can use an account pool that contains multiple Microsoft 365 accounts.
When AvePoint Online Services (AOS) registers SharePoint Online site collections and OneDrive, AOS grants the site collection administrator permission to the group set in the account pool for Sites, Mailboxes, Groups, and Teams / Project Sites / Exchange Public Folders, and the Microsoft 365 accounts in the account pool will inherit the site collection administrator permission from the group. With the credentials of these accounts, AvePoint services can work smoothly. For example, Cloud Backup for Microsoft 365 can manage a large amount of data simultaneously, and Cloud Governance can process multiple requests simultaneously.
For an overview of what services can use a Microsoft 365 account pool, refer to the What Services Can Use a Microsoft 365 Account Pool? section.
To build an account pool in AvePoint Online Services, create a group in Microsoft 365 first. The group type can be Microsoft 365 Group, mail-enabled security group, or security group. This group should contain a certain number of users, and these users can be unlicensed in Microsoft 365.
The table below lists the required information for each object type.
| Object Type | Need Account Pool? | Need Username? | Need Password? | Need SharePoint Administrator Role? | Need License? |
|---|---|---|---|---|---|
| SharePoint Online Site Collections | Yes | Yes | Yes | No | No |
| OneDrive | Yes | Yes | Yes | No | No |
| Microsoft 365 Group Team Sites | Yes | Yes | Yes | No | No |
| Exchange Online Mailboxes | Yes | Yes | Yes | No | No |
| Microsoft 365 Group Mailboxes | Yes | Yes | Yes | No | No |
| Microsoft 365 Groups | Yes | Yes | Yes | No | YesHave the SharePoint Online and Exchange Online product licenses assigned in Microsoft 365. |
| Microsoft Teams | Yes | Yes | Yes | No | YesHave the Exchange Online and Microsoft Teams product licenses assigned in Microsoft 365. |
| Project Online Site Collections | Yes | Yes | Yes | No | YesHave one of the following Project Online product licenses assigned in Microsoft 365: Essentials, Professionals, or Premium. |
| Exchange Online Public Folders | Yes | Yes | No | No | YesHave the Exchange Online product license assigned in Microsoft 365. |
| Microsoft 365 Users | Yes | Yes | Yes | No* | YesHave one of the following Microsoft Entra ID product licenses assigned in Microsoft 365: Premium P1 or Premium P2. |
| Viva Engage Communities | No | No | No | No | No |
Note the following:
The Tenant Owner and Service Administrators can then manage the account pool by navigating to Management > Service account, and then clicking the classic UI link to open the Manage Account Pool page in a new tab. Follow the instructions below to configure settings on the Manage Account Pool page:
Select a Tenant – Select a tenant from the drop-down list. The tenant is retrieved from the previously configured app profile or Microsoft 365 service account profile.
Configure the account pool for Sites, Mailboxes, Groups, and Teams, Project Sites, or Exchange Public Folders according to the objects you will back up or manage via services for Microsoft 365.
*Note: The Sites, Mailboxes, Groups, and Teams tab includes different object types for the following cloud services:
For the EnPower service, this tab includes SharePoint sites, OneDrive, Microsoft 365 Group team sites, Exchange Online mailboxes, and Microsoft 365 mailboxes.
For the Fly service, this tab includes SharePoint sites, OneDrive, Microsoft 365 Group team sites, Exchange Online mailboxes, Microsoft 365 Groups, and Microsoft Teams.
For other services, this tab includes SharePoint sites, OneDrive, and Microsoft 365 Group team sites.
Click a tab and configure the following settings:
Group Name – Enter the name of the group you prepared.
Click Validate next to the group name. Group members will be displayed in the Group Users field. For the minimum number of users who must be included in the group, refer to the How Many Accounts Should be Added into an Account Pool? section.
Note the following:
If a user account exists in a service account profile, this service account will be used for managing operations in your AvePoint Online Services tenant and will also be used to execute application-level jobs.
For backing up Exchange Online Public Folders, you do not need to provide the password of the account because of the impersonation technology. You can view more information about impersonation by clicking the following link: .
If the account of a user has multi-factor authentication (MFA) enabled in Microsoft 365, click the turn on (
) button to enable MFA, and then enter the app password of this account.
To protect Planner data, the account must be both owner and member of the scanned Microsoft 365 Groups and Teams.
If the account of a user has multi-factor authentication enabled through a conditional access policy configured in Microsoft Entra, the account cannot be added to the account pool.
Custom SharePoint Online Admin Center URL – If you enable MFA for one or more accounts, you must enter your SharePoint Online admin center URL in the text box.
When you finish the configurations for all desired account pools, click Save to save your configurations. If you want to remove the group from the account pool, click Clear next to the group name, and then click Save.
*Note: After an account pool for a tenant is saved, the account pool will take effect on the next scan job.
If you edit the account pool to change the group, a pop-up window will appear recommending you rerun the scan for auto discovery. Rerun the scan profiles to make the changes take effect immediately. If you do not rerun the scan profiles, your changes will be saved but will not take effect until the next scan completes.