Home > New Features and Improvements from Previous Versions > AvePoint Cloud Governance July 2020
Export to PDF#AvePoint Cloud Governance July 2020
Release Date: July 12, 2020
- In the new Cloud Governance admin center, there is now a **Service request setup assistant** for IT administrators to set up a Create site collection service, Create Microsoft 365 Group service, or Create Microsoft Team service.
- In the new Cloud Governance admin center, the IT administrator can now create an **Invite** **new guest user** service. After the IT administrator defines the service for their business users, users can submit a request to invite a new guest user to their organization's directory using this service.
- The IT administrator can now configure a guest user renewal profile in the new Cloud Governance admin center. A guest user renewal profile enables a renewal process for users to periodically review and change guest contacts, guest users' access to workspaces, and metadata applied to guest users. Guest user renewal profiles can be selected in different Invite new guest user services.
- In the new Cloud Governance admin center, there is now a **Guest user report** to view guest users and relevant information.
- In the new Cloud Governance admin center, the IT administrator can specify the primary and secondary contacts for site collections, groups, and teams in the **Workspace report**.
- There is now a **Reassign import process** button in the **Workspace report** in the new Cloud Governance admin center. The IT administrator can reassign the governance details confirmation tasks for the automatically imported workspaces to other users.
- In the new Cloud Governance admin center and the Cloud Governance Portal, users can copy and paste multiple usernames in the people picker when they specify users.
- There is now a **System settings** section in the new Cloud Governance admin center. The **Custom logo** setting in the **System settings** allows the IT administrator to upload a custom logo to replace the default Cloud Governance logo shown in the user interface of the new Cloud Governance admin center and the Cloud Governance Portal.
- In the new Cloud Governance admin center, the IT administrator can now update the AvePoint Cloud Governance Portal to the MyHub web portal by enabling MyHub in the **MyHub** **settings**. With the MyHub functionality enabled, users can access, organize, and manage Microsoft 365 Groups, Microsoft Teams, Yammer Communities, and SharePoint sites from a single window, but in a more centralized and efficient way.
Additionally, users can still access MyHub as a Teams app in Microsoft Teams. The new version of the app will be published to the Teams app store after Microsoft finishes the approval.
- In the classic Cloud Governance admin center, the records of **Invite new** **guest user** services, requests, and tasks can be monitored in the **User Activity Report**, **Service Request Report**, **Approval Process Report**, **All Requests**, and **All Tasks**.
- There is now a **$New Group/Team Contact** role for the IT administrator to select as the approver when they configure an approval process for a Change Group/Team Settings service.
- There is now a **$Group/Team Metadata (“Metadata Name”)** role for the IT administrator to select as the approver when they configure an approval process for a Change Group/Team Settings service.
There is now a **$Site Collection Metadata (“Metadata Name”)** role for the IT administrator to select as the approver when they configure an approval process for a Grant Permissions service.
- To ensure users can use Microsoft 365 resources smoothly, AvePoint Cloud Governance follows the native behavior of Microsoft 365 Groups and Microsoft Teams by adding group/team owners as both owners and members of the groups/teams. When business users submitted a Change Group/Team Settings request or processed a group/team renewal task, the owners were displayed in both the owner list and member list. Now the owners are only displayed in the owner list. If the requester or task assignee removes the owner role from a user, this user will no longer be the group/team member either.
- When a tenant has custom site designs configured in Microsoft 365, apart from selecting a custom site design for a group team site in a Create Group/Team service or request, the IT administrator or business users can now select the default site design **Team site**.
- When the IT administrator configures **Service Permissions** in a service and selects Azure **Active Directory Property** to **Define conditions for users who can request this service**, the IT administrator can now select the built-in property **CompanyName** as the condition. With this property selected, the service is only available to members of a specific company.
- In a Create Group/Team service and a Change Group/Team Settings service, when the IT administrator configures a conditional approval process and chooses to **Run this approval process if the conditions below are met** in the **Condition Settings** field, there is now a new group property **Newly Added Group/Team Members**. The following conditions are available to be selected: **Does Not Contain Guests**, **Contains Existing Guests**, and **Contains New Guests**.
- In the Cloud Governance Portal, when business users view the workspace details in **Workspaces**, there is a **Classification** field showing the classification for the Microsoft 365 Groups, Microsoft Teams, and communication sites with the classification applied.
- When the IT administrator configures an automatic import profile and selects **Require end user confirmation** as the **Automatic** **Import Method**, they can now choose to select a policy for all workspaces that will be imported by this automatic import profile, or define the site collection policy scope for business users and allow them to select policies when they confirm governance details for the imported site collections. When the IT administrator chooses to **Specify** **a duration** **for the entire automatic import process**, they can now choose to **Enable reminder before the confirmation task is overdue** and select a **Reminder profile**.
- There is now an **Automatic Import Method** field in the automatic import profile. The IT administrator can choose the **Pre-define governance details** option to fully automate the import process. Business users are not required to confirm governance details for the imported workspaces.
- If the IT administrator wants to import Microsoft 365 Groups to be managed by Cloud Governance, and these groups have been connected to the existing Cloud Governance managed SharePoint site collections, the IT administrator should remove the existing site collections from Cloud Governance at first, and then import the Microsoft 365 Groups to Cloud Governance.
- The IT administrator can now use the **Import Existing Microsoft 365 Objects** feature to import guest users that already exist in their organization's directory, so users can use AvePoint Cloud Governance to manage these guest users.
- When configuring the **Azure Active Directory Property** type metadata, the IT administrator can now select one of the following user roles to **Get a user's property value as the default value**: **$Primary Site Collection Contact**, **$Secondary Site Collection Contact**, **$Primary Group/Team Contact**, and **$Secondary Group/Team Contact**.
- When the IT administrator configures a group/team policy and chooses to **Enable archiving of the team**, they can now choose to **Enable team membership and team site permission changes before team archiving**, and then select a team archiving profile for the group or team applied with this policy.
- When configuring the **Duration and Escalation** in a group or team renewal profile, the IT administrator can now select **All at once (parallel)** as the renewal process order. This order will assign the renewal task to all task assignees at the same time. The IT administrator can now **Enable automated team** **archiving**, and then choose whether to **Enable reminder before the team is archived**. The IT administrator can also choose whether to enable the notification about the archived team.
- When configuring a renewal profile for the site collection, group, or team, the IT administrator can now choose to **Notify the newly assigned contacts** if they allow the task assignee to renew the site collection, group, or team contact.
In a Change Group/Team Settings service, the IT administrator can now choose to **Notify the newly assigned contacts** if they allow business users to **Change primary group/team contact** or **Change** **secondary group/team contact**.
In a Create Group/Team service, when the IT administrator configures the primary or secondary contact of the group or team, they can now choose to **Notify the contact when group/team provisioning is completed**.
- There is now a **Previous Assignees of the Renewal Task** reference that can be inserted in e-mail templates with the type of **Site Collection Renewal Assignment E-mail Template** or **Microsoft 365 Group Renewal Assignment E-mail Template**.
- The **Azure Active Directory Property** metadata that gets the property value from the **$Requester** role as the default value can now be added to the following types of services: Change Group/Team Settings service, Create Site Collection service, Manage Permissions service, and Grant Permissions service.
- The IT administrator can now use the **Update Workspace Information in Bulk** feature to update the contact and metadata of Microsoft 365 Groups or Microsoft Teams.
- The IT administrator can now configure a team archiving profile in **Microsoft Teams Archiving Profile Management**, and define how to manage team membership and team site permissions before a team is archived in AvePoint Cloud Governance. A team archiving profile can be applied to a team policy.
- When configuring the **CC** field in an approval process, the IT administrator can now select the **$Primary Group/Team Contact** and **$Secondary Group/Team Contact** user roles. Users with the certain roles will receive notification e-mails when the service request is completed.
- When configuring **Timer Service Configuration Management**, the IT administrator can now select an execution schedule profile to execute the following jobs: site information synchronization, site collection information synchronization, and Group/Team information synchronization.
- When managing SharePoint group permissions in a Manage Permissions service request, business users can now add the **Everyone except external** **users** group as the owner or member of a SharePoint group.
- There is now an **Invalid** phase for a renewal task when the site collection, Microsoft 365 Group, or Microsoft Team is deleted from Microsoft 365 after the renewal task has been generated.
- When configuring the **Duration and Escalation** in a site collection renewal profile, the IT administrator can now select **All at once (parallel)** as the renewal process order. This order will assign the renewal task to all task assignees at the same time. When a renewal task is overdue and the site collection is automatically locked, the task assignees can still complete the overdue renewal task. The locked site collection will be automatically unlocked when the task is completed. There is now a **Renewal Task Link** reference that can be inserted in the e-mail templates with the type of **Site Collection Status E-mail Template**. Business users will be directed to the renewal task when they click the link in the received e-mail.
- When configuring the **Renewal Recurrence** in a renewal profile for site collections or for Microsoft 365 Groups/Microsoft Teams, IT administrators can now select the **Workspace created time** as the time to generate the first renewal task.
- AvePoint Cloud Governance can now synchronize Microsoft 365 Groups/Microsoft Teams membership in real time for group/team renewal tasks. Any updates of group/team membership will be synchronized to the group/team renewal tasks when the task assignees process the tasks.
- There is now an **Advanced Setting for Conflict Task** section in a Site Collection Lifecycle Management or Group/Team Lifecyle Management service when the IT administrator selects **Change Site Collection Policy** as a lifecycle management action. When a business user requests to change the policy for a workspace, the workspace may have an ongoing lifecycle management request, recertification task, or renewal task. If the IT administrator chooses to **Allow requesters to cancel the ongoing lifecycle management request/renewal task or reject the recertification task when they request for policy changes**, requesters will be able to cancel or reject the ongoing request/task and proceed with the new request. Otherwise, they cannot submit the new request until the ongoing request/task is completed.
- When your Microsoft 365 tenant has custom site designs, in a Create Site Collection service, the IT administrator can now select a site design for the **Team site (no Office 365 group)** template.
- In a Change Group/Team Settings service, the IT administrator can now **Allow requesters to switch between classic and dynamic group/team membership assignment methods** in the **Change Group/Team Assignment Settings** section. With this option enabled, business users can choose to add group/team members manually or dynamically when submitting requests using this service.
- In the **Site Collection Report**, **Site Report**, and **Team and** **Group Report**, the IT administrator can now click **Remove from Cloud Governance** to remove specific workspaces and all the corresponding workspace information from AvePoint Cloud Governance.
- There is now a **Deactivated Group/Team Contact Election** section in a group/team policy. The IT administrator can choose whether to **Automatically start** **the ownership election process if either of the group/team contact accounts is deactivated**.
- There is now a **Welcome E-mail** section in the Create Group/Team service. The IT administrator can choose whether to send a welcome e-mail to users when they are added to the Microsoft 365 Groups or Microsoft Teams created using this service.
- When the **Notify the contact upon site collection creation** option is enabled in the **Primary Site Collection Contact** or **Secondary** **Site Collection Contact** section in a Create Site Collection service, the site collection contact will receive a notification e-mail after the request is completed, including the execution of custom actions.
On this page