13 results found
Would love to have an automated creation of groups process that could ask a couple of questions to owners before their group is really created. In brief, to have help with the beginning of the lifecycle of Office 365 groups.
Also, ShareGate Apricot’s inactivity detection would mean that the end of the lifecycle of O365 groups are also covered.7 votes
We're currently building an automated process to assist end user with the creation of M365 Groups. We're starting with Teams!
As we continue to build and improve on our provisioning solution, we appreciate your input to ensure we're building a solution that best fits your needs.
Thanks a lot !
Could you implémente a translate in ShareGate end user Apps ?
We have a french client and he wich get the end user apps in Teams in french.
And for other language.
It would be great if ShareGate Apricot could automatically set the Group Purpose of groups based on naming convention rules, sensitivity labels, or group classification already set up in Microsoft 365.
- It is currently a redundant task for end-users since they have to include these info at group creation (i.e. classification, sensitivity labels and respect naming convention).
- It would be great if Apricot could utilize the classification labels, sensitivity labels, or possibly a regex type tool to use a naming scheme to automatically apply the Apricot Group Purpose to the Team.
Have the option to apply site designs to SGA categories, so it gives the option to trigger flows in the background to complete other actions and provide users with sites according to their groups' purpose (e.g. internal collab).2 votes
Have a way to identify and display groups that do not follow naming convention rules established in our company in the app.
- E.g. Every agency in our organization has its own acronym, that IT asks them to put it as a prefix in their group name.
It would be great if before creating a Team, the tenant could be checked for identically named Teams and the request denied if the Team already exists.1 vote
Our IT Security Team doesn't like users being able to generate email addresses that could be used for spoofing, eg 'itsecurity@xxxxx'.
Would it be possible for an option to add a random string on group creation to the email address? For instance a team called 'HR' with a five character random string would have an email address like h837fHR@xxxxx1 vote
Permit 'suffix' as well as, or instead of, a prefix when provisioning1 vote
Run custom PowerShell scripts during the provisioning process to set various custom options.
For example, set Teams Expiration policy or External Sharing to Off.1 vote
Since the SharePoint URL is not automatically adjusted when renaming a Teams team and that often leads to confusion, we create a SharePoint site with a consecutive number (e.g. https://contoso.sharepoint.com/sites/001) in the URL and afterwads we build the Teams team on it. As this also may be useful for other companies, this would be a useful function for provisioning.1 vote
Would be great the have a possibility to provide file templase (e.g. project document templates) that are available in the files tab in a selected channel of the new created team.1 vote
For us to be able to use the provisioning we would need to be able to customize all strings that the end user sees to (in our case) Swedish. Maybe some template language with placeholders for variables.
Alternatively if there would be some API on the provisioning part, to build our own user interface.1 vote
Would like to have more visibility over time = which categories (reasons of creation) are being used the most – to better understand which reason of creation is used the most and evaluate if efforts should be put in educating end-users to use them correctly.1 vote
- Don't see your idea?