Would like for us to have a clearer plan of what we do with groups/sites retention policies. Integrating them is really important.

We have a policy of a minimum of 2 (to 5 owners) per Microsoft 365 group and would love to enforce it with ShareGate Apricot and perhaps the Teams bot.

Would like to give access to ShareGate Apricot to users that aren't admin in SharePoint.

• To assign the admin role only within ShareGate Apricot.
• For example, for the helpdesk or the support team.

We would really like to use Group Purpose tagging to help out Admins filter on the Teams that they own. Out tenant has multiple subsidiaries with differing IT groups managing their own employees. The Group Purpose allows us to tag the groups for IT support, but we don't want to use the Group Sensitivity tagging as of right now.

Remove inactive guests after a pre-determined period of time

Add the ability to turn off inactivity notifications for specific groups OR set a very high inactivity threshold. Currently the maximum allowed value by Apricot is 999 days and I would like to have the option of an infinite value.

What I’m really interested in though is prompting site owners to re-validate users who have access to content in their site.

Exclude service-account activity/ownership. Today I have a backup of my M365-platform including SharePoint, Teams and Groups using a service-account. That membership is counted in apricot as well as its backup-activity. it will even ask my service-account for purpose and will never report any orphans as my service-account is a counted owner..

Have a way of allowing only specified ShareGate Apricot admins to see a group labelled as Sensitive or Confidential inside ShareGate Apricot's UI

We have restricted group creation in our organization. A solution to achieve same through Apricot would be great.

Add ability to choose which options group owners have in Inactivity detection communications (email and chat bot)

Ability to setup an approval workflow when Owners select specific sensitivity labels (i.e. public Teams / Anyone shared links).
The workflow would ask identified users to approve the label.

We really like what Apricot offers in terms OOTB functionality, but like many organizations we also have some custom requirements. Is it possible to implement things like:

• Check for groups that have too many owners

A way for all new groups created to be set as "Guests not allowed" by default so users don't have to change them all manually. To have an option to set a default option that is automatically applied to newly created groups.