Home > New Features and Improvements from Previous Versions > AvePoint Cloud Governance July 2021
Export to PDF#AvePoint Cloud Governance July 2021
Release Date for the Commercial Environment: July 11, 2021
Release Date for the U.S. Government Environment:July 18, 2021
#Newly supported data centers
AvePoint Cloud Governance now has been deployed in the Switzerland North (Zurich) and Germany West Central (Frankfurt) data centers.
#What’s new in the new Cloud Governance admin center?
- When configuring the font color and background color in the rich text editor, there are now built-in standard colors for the IT administrator to select.
- For example, the built-in standard colors are supported when the IT administrator configures the **Message to the renewal task assignee** in a guest user renewal profile, or when they choose to **Customize the signature** and configure the language in **E-mail settings** > **Signature and footer**.
- There is now a menu button on the upper-left corner of the left navigation bar to collapse or expand the navigation menu.
- The IT administrator can now manage the scope of services and questionnaires in **Settings** > **System settings** > **Available services/questionnaires**. The selected services and questionnaires will be available for users when they click **Create a workspace** in a hub or in the MyHub Teams app. Note that this setting will not take effect when the **Native Microsoft 365** is selected as the workspace provisioning method in **Settings** > **Hub settings** > **Workspace provisioning**.
- The IT administrator can now customize the site collection locked messages by configuring the header and footer in **Settings** > **System settings** > **Site collection lock messages**, which will be displayed on modern pages in locked site collections. The information such as site collection locked reason, locked time, and contact information can be included in the header and footer messages. They can configure the messages to desired languages as well as set the background color of the header and footer.
- When configuring the **Message to renewal task assignees** in a guest user renewal profile, the IT administrator can now customize the message into multiple languages. It's required to select a default language, and when the SharePoint site's display language is not any of the eight languages, the message will be shown in the default language.
- When configuring the periodical renewal process for guest users in a guest user renewal profile, the IT administrator can now choose to **Configure a periodic renewal schedule** or **Manually** **specify each renewal task generation time**. When configuring a periodical renewal schedule, the IT administrator can use the **Guest invited time** or select a **Specific date** as the renewal recurrence start time.
- There is now a new **Last renewed by** column in the **Workspace report** and **Guest user report**, which records end users' renewal action.
- There is now a new **Renewal assignee** column in the Guest user report which records the current assignee of the renewal task.
- In the **Guest user report**, the IT administrator can now specify primary and secondary contacts for guest users. The specified contact results will be shown in the **Job monitor**.
- In the **Guest user report**, the IT administrator can now apply a new guest renewal profile to one or more guest users. The applied profile results will be shown in the **Job monitor**.
- In the **Guest user report**, there are now three new columns:
- **Last guest status sync time**
- **Invitation accepted**
- **Invited time**
- When configuring an Invite new guest user service, the IT administrator can now specify a user or user role as the guest user manager or allow business users to specify a manager for the guest user when they submit a request using this service.
- In a people picker filter profile, when the IT administrator adds conditions for the user filter and chooses Azure Active Directory property as the condition, they can now use the property value that **Matches the workspace metadata value** as a condition.
- When the IT administrator configures the **Settings** > **System settings** > **Workspace contact membership** and choose to **Enable group/team/community contact membership management**, they can now choose to automatically remove original contacts from the members or owners group during the Cloud Governance management processes. In addition, they can now **Enable site collection contact membership management** as well. Note these settings will only take effect on workspaces during the following Cloud Governance management processes: automatic import process, provisioning process, change contact process, and renewal process.
- When configuring the **Settings** > **Hub settings** > **Workspace discovery**, the IT administrator can now choose whether to enable the discovery and management for Microsoft 365 Groups, Microsoft Teams, and Yammer communities in hubs. If disabled, business users will only see groups, teams, and communities that they are a member or owner of in hubs.
- Even if the user specified as the administrator contact in a guest user renewal profile does not have a valid e-mail address, the renewal escalation task now will still be generated and assigned properly.
#What’s new in the classic Cloud Governance admin center?
- The IT administrator can now configure the automated lifecycle escalation profiles to define how to manage a Microsoft 365 Group when the group lifecycle task is not completed within the specified time in **Settings** > **Request Management** > **Automated Escalation Profile for Microsoft 365 Groups**.
- The IT administrator can now configure the automated lifecycle escalation profiles to define how to manage a Microsoft Team when the team lifecycle task is not completed within the specified time in **Settings** > **Request Management** > **Automated Escalation Profile for Microsoft Teams**.
- When configuring a workspace automatic import profile that requires end user's confirmation, they can now choose whether to notify the contact when the workspace is successfully imported to Cloud Governance.
- When configuring an automatic import profile, a default policy is not required to be selected by the IT administrator now. If the IT administrator sets **None** for the default policy, business users will be required to select a policy during the confirm governance details process.
- When the IT administrator configures the site collection URL in a Create Site Collection service or configures the list/library URL in a Create List/Library service, the Azure Active Directory Property metadata is supported to be added to the URL.
- When configuring the custom message shown to the renewal process assignee in a workspace renewal profile, the IT administrator can now customize the messages in multiple languages.
- When configuring a webhook in **Webhook Management**, the IT administrator can now select the election process-related event **When all stages of an election process are overdue** whose occurrence will trigger the webhook.
- The original **Department** settings have been removed from AvePoint Cloud Governance. Currently, if there is no existing metadata named **Department** in your tenant, a new metadata named **Department** will be automatically created and added to the services and automatic import profiles created before July 11, 2021. If there is existing metadata named **Department** in your tenant, a new metadata named **Department (built-in)** will be automatically created and added to the services and automatic import profiles created before July 11, 2021.
- In the Create Team service, when the IT administrator has the following configurations:
- **Multi-Geo Locations** - **Enable group team site provisioning in multi-geo locations**
- **Team Template** – **Allow business users to create a team from an existing team** and/or **Allow business users to create a team using a team template**
Then, AvePoint Cloud Governance invokes the Microsoft Teams API in Microsoft Graph to create the team and group team site, but provisioning in different geo-locations is not supported by Microsoft Teams API regardless of the Multi-Geo Locations configuration in a service, so the team and group team site will be created in the default geo location. After the provisioning of the team and group team site, Cloud Governance invokes another Microsoft Graph API to move the team and group team site data from the default geo location to the geo location selected in a service.
- When the properties of site collections or sites are requested to be changed via service requests or profiles in AvePoint Cloud Governance, and a modern site's **DenyAddAndCustomizePages** property is **Enabled**, Cloud Governance will disable the property automatically before updating the site properties' values, then change it back to **Enabled** after the updates complete. If a modern site's **DenyAddAndCustomizePages** property is **Disabled**, Cloud Governance will keep the property as **Disabled** after the updates complete.
- The original **Task Duration** e-mail reference that calls up the specific time when a task is overdue now is newly supported to be inserted in the following e-mail template types:
- Site Collection Renewal Assignment E-mail Template
- Group Renewal Assignment E-mail Template
- Guest User Renewal Assignment E-mail Template
- Currently, the Azure Active Directory Property metadata that gets value from the **$Requester** roles is supported in all services. In addition, the Azure Active Directory Property metadata that gets value from the **$Primary site collection contact** role is supported to be added in a site collection automatic import profile, and the Azure Active Directory Property metadata that gets value from the **$Primary group/team contact** role is supported to be added in a group/team automatic import profile.
- When configuring the Azure Active Directory Property metadata, if the IT administrator chooses to get value from built-in Azure Active Directory properties, then the **Microsoft 365 tenant** is not required to be configured now.
- Even if the user specified as the administrator contact in a workspace renewal profile does not have a valid e-mail address, the renewal escalation task now will still be generated and assigned properly.
#What’s new in the Cloud Governance Portal?
- There is now a menu button on the upper-left corner of the left navigation bar to collapse or expand the navigation menu.
- In the Cloud Governance Portal, when business users are on the **To-do list** page, the URL in the browser's address bar now has been changed as the following:
- If business users are using the commercial production environment, the URL now is **https://go.avepointonlineservices.com/#/tasks**.
- If business users are using the U.S. Government production environment and the Microsoft 365 version is Global Microsoft 365 or Microsoft 365 U.S Government GCC, the URL now is **https://go-gov.avepointonlineservices.com/#/tasks**.
- If business users are using the U.S. Government production environment and the Microsoft 365 version is Microsoft 365 U.S Government GCC High, the URL now is **https://go-gcc.avepointonlineservices.com/#/tasks**.
- In a hub where the workspaces are manually selected to be included when creating the hub, business users now have the option to remove workspaces from the hub.
- In any hub, business users can now sort workspaces by the workspace name in the alphabetical order from **A to Z** or **Z to A**.
- In a hub, business users can now click the icon of the workspace type on a workspace card to access the workspace.
- In a hub, if a workspace is not managed by AvePoint Cloud Governance, business users cannot perform the **Start a request** action on the workspace.
- In the Cloud Governance Portal and the MyHub Teams app, when users leave the page where they are, after they go back to the Cloud Governance Portal or the MyHub Teams app, they will be on the original page if they performed actions related to the Cloud Governance workspace provisioning services, as well as if they performed the following actions on the corresponding pages:
- On the **To-do list** page:
- View request details or task details.
- Process the renewal task or the confirm governance details task.
- On the **Workspaces** page:
- View workspace details.
- Process the renewal task or the confirm governance details task. Note that users will be directed to the page where they start to process the task.
- On the **My tasks** page:
- View task details.
- Process the renewal task or the confirm governance details task.
- On the **Request** page:
- View request details.
- Copy a request. Note that after users go back to the request page, the original configured fields in the request will be cleared and need to be configured again.
If users were submitting a request before they leave the page, after they go back, they will be on the service request page.
#Resolved Known Issue
- Resolved an issue in the Create Team service where sites that were provisioned with the following configurations **Multi-Geo Locations**, **Team Templates** and **Group/Team Name and ID** were set with the default geo location that the IT administrator selected in the service. After a service request is successfully completed, the site can be created in different enabled geo locations.
On this page