AvePoint Cloud Governance January 2021

    Release Date: January 10, 2021

    - The following features are now available in the new Cloud Governance admin center: - In **Settings** > **System settings**, the IT administrator can now configure the **Group/Team contact membership**. They can choose whether to add the primary and secondary group/team contacts as owners or members after the groups/teams are imported to AvePoint Cloud Governance via an automatic import process. - In the **Workspace report**, there is now a new **Active lifecycle tasks** column to display if a workspace has an ongoing lifecycle management process, renewal task, or recertification task. - In the **Workspace report**, the IT administrator can now apply a new policy to multiple workspaces. The selected workspaces must be in the same workspace type. The apply policy results will be shown in the **Job monitor**. - The **Job monitor** now provides records of the following jobs initiated by the IT administrator: - Lock site collection jobs - Unlock site collection jobs - Apply site collection policy jobs - Apply group policy jobs - Apply team policy jobs - Delete workspace jobs - Specify workspace contact jobs - In the **Workspace report**, the IT administrator can no longer export a report in the **XLSX** format. The XLSX file type was removed because exporting large number of workspaces to an XLSX file may be failed. - In **MyHub** **settings** > **Default** **hub display settings**, the IT administrator can now choose whether to display the following hubs to users: **All workspaces**, **Favorite workspaces**, and **Recent workspaces**. - When configuring a Group/Team Lifecycle Management service, the IT administrator can now configure the **Group/Team Scope** to define the scope of groups/teams whose lifecycle can be managed via a request. - In an exported **Microsoft 365 Workspace Activity Report**, there is now a new **Initiated By (E-mail Address)** column to display the e-mail address of the user who performs the action on Microsoft 365 workspaces within AvePoint Cloud Governance. - When the IT administrator configures an automatic import profile and selects **Require** **end user** **confirmation** as the **Automatic Import Method**, they can now enable the following escalation actions for the overdue governance details confirmation task: automated site collection locking, automated group team site locking, or automated team archiving. - When the IT administrator uses the **Update Workspace Information in Bulk** feature to update workspace information in bulk and modifies the workspace information report, they can now add the metadata to a workspace or remove the metadata from a workspace. To apply the metadata to a workspace, change the metadata value from **N/A** to a valid value. To remove the metadata from a workspace, change the existing metadata value to **N/A**. - When configuring a reminder profile for the upcoming expiration task, the IT administrator can now configure the **CC** field to specify the users or groups (Microsoft 365 Groups, distribution groups, or mail-enabled security groups) who will also receive a copy of the reminder e-mail before the task is overdue. - When configuring a renewal profile, the IT administrator can now choose to **Send a reminder e-mail to the renewal task assignees before each renewal process is overdue**. If **One at a time (serial)** is selected as the renewal order, a reminder e-mail will be sent to the task assignees of both the current and previous stages. If **All at once (parallel)** is selected as the renewal order, a reminder e-mail will be sent to all specified renewal task assignees. - A workspace is to be imported to AvePoint Cloud Governance, and the governance details confirmation task of the workspace is pending to be confirmed. If the workspace is deleted in Microsoft 365, the governance details confirmation task will be canceled and the workspace will be automatically removed from Cloud Governance. - AvePoint Cloud Governance optimizes the pattern of the **Renew workspace** button and the **Confirm governance details** button shown in the task panel to make it more convenient for the task assignees to process the task in the Cloud Governance Portal. - In the Cloud Governance Portal, a workspace link displayed in the **View details** panel of a task, workspace, or request is now replaced with a hyperlink and the display text is the workspace type. - In the Cloud Governance Portal, when an automatic import process of a workspace completed with exception, there is now an error message displaying the detailed error information in the workspace information panel. - In the Cloud Governance Portal > **Workspaces**, business users can now save a default view based on the columns they selected and the filter and sort rules they configured. - A business user submits a request via a Change Site Collection Contact or Administrator service or a Change Site Contact service to change the contacts/administrators of multiple site collections/sites. If the contacts/administrators of some site collections/sites are not successfully changed, the request status shown in the Cloud Governance Portal will be **Partially completed - Please contact {serviceAdmin}**. - The following actions of the AvePoint Cloud Governance connector in Microsoft Power Automate now support Site Collection Lifecycle Management - Change Policy requests: **Get a request**, **Submit** **a request**, and **Update** **a request**. - The following actions of the AvePoint Cloud Governance connector in Microsoft Power Automate now support the Create Site Collection service requests: **Get a request**, **Submit** **a request**, and **Update** **a request**. - In hubs in the Cloud Governance Portal, when users create workspace hubs or filter workspaces, they can now filter groups, teams, communities, and sites by using same filter rules. They no longer need to configure separate rules for each workspace type. Moreover, the filter rules have been updated to provide a better user experience. - If the MyHub functionality has been enabled and a user selects multiple filter rules to filter workspaces, workspaces that meet all filter rules can be filtered and included in a hub. For example, if a user selects **Public**, **I'm a member of**, and **Active in** **last_days** as filter rules to filter Microsoft Teams and enters **30** as the value of the **Active in** **last**_**days** rule, the public teams that the user is a member of and have activities in the last 30 days will be filtered and included in the hub. - In hubs, the workspaces are now sorted by their last active time regardless of the workspace types. If two workspaces have the same active time, the workspaces will then be sorted by the workspace names in alphanumeric order (from the lowest to highest). - In the card view or list view of a hub, when a user goes to the **Tag management** page, **Hub management** page, or workspace details page, the scrolled position can now be kept when the user returns to the card view or list view page of the hub. - In the MyHub Teams app, when a user is in a hub and the user goes to chats, teams, apps, etc. and then returns to the hub, the original page or panel the user accessed will be kept.