Viva Insights has a new URL – https://analysis.insights.viva.office.com/

To Manage Data Sources – Azure AD is the default data source.

Microsoft provides an additional option if you wish to add other data like cost center or gender, for example, where this data is unavailable in the Azure ad or stored in ERP. But it has to be uploaded periodically and maintained. CSV is a painful option to take.

Data Sources cannot be chosen later if you use the CSV, for example. If you have an enterprise subscription, there is a chance that you can reach the product team to switch back to an Azure ad, for example. When writing this article, quickly changing it back to an Azure ad is impossible.

It has three roles.

Insights Administrator – Has administrative access to the Microsoft 365 Insights app. (Usually a Global and M365 admin to adjust data sources and manager size)
Insights Analyst – Access the analytical capabilities in Microsoft Viva Insights and run custom queries. (For the BI guy to generate custom reports)
Insights Business Leader – Can view and share dashboards and insights via the M365 Insights app. (For C Level Executives / CEO and VPs, for example)

This has to be enabled – Meeting Insights for Managers for Group insights who can see them in the viva insights teams app. shows managers aggregated well-being and productivity insights about their direct and indirect reports based on organization hierarchy.

The minimum team size for this can be changed to a minimum of 10

In Advance Viva insights, you have the option to generate reports using Power BI

You can use the partition identifier and query identifier to connect your power bi desktop. For example

In Microsoft 365 (M365), the labels used for data classification and protection can vary depending on an organization’s specific configuration and requirements. However, the labels you mentioned—public, sensitive, confidential, and restricted—are commonly used to classify and protect data within M365.

Here’s a breakdown of these labels and their general meanings:

1. Public: This label is typically assigned to data that can be freely shared and accessed by anyone within or outside the organization. It usually indicates that the information doesn’t contain sensitive or confidential content and has no legal or compliance restrictions.
2. Sensitive: The sensitive label is used for data containing information requiring protection due to privacy, compliance, or business requirements. It signifies that the data should be handled cautiously and only shared with authorized individuals or groups within the organization.
3. Confidential: The confidential label is applied to data that contains highly sensitive information, such as trade secrets, financial data, personally identifiable information (PII), or any other information that requires strict protection. Access to confidential data is usually limited to a small group of authorized individuals or specific roles within the organization.
4. Restricted: The restricted label represents the highest data classification and protection level within M365. It is typically used for highly regulated data, legally protected, or subject to specific compliance requirements. Restricted data often includes classified information, intellectual property, or data related to national security. Access to restricted data is tightly controlled, and strict security measures are implemented to ensure its confidentiality and integrity.

It’s important to note that these labels are not fixed and can be customized based on an organization’s specific needs. Organizations may define additional labels or modify the existing ones to align with their data classification policies and compliance requirements. The label names and definitions can vary depending on the organization’s industry, regulatory environment, and internal guidelines.

This article contains instructions for using PowerShell cmdlets to create and update groups in Azure Active Directory (Azure AD), part of Microsoft Entra. This content applies only to Microsoft 365 groups 

Install PowerShell cmdlets

Be sure to uninstall any older version of the Azure Active Directory PowerShell for Graph Module for Windows PowerShell and install.

1. Open the Windows PowerShell app as an administrator.
2. Uninstall any previous version of AzureADPreview

Uninstall-Module AzureADPreview

3. Install the latest version of AzureADPreview.

Install-Module -Name AzureADPreview

4. Connect to AzureAD

Connect-AzureAD

Connect-AzureAD

Create settings at the directory level.

These steps create settings at the directory level, which apply to all Microsoft 365 groups in the directory. The Get-AzureADDirectorySettingTemplate cmdlet is available only in the Azure AD Powershell.

1. In the DirectorySettings cmdlets, you must specify the ID of the SettingsTemplate you want to use. If you do not know this ID, this cmdlet returns the list of all settings templates.

Get-AzureADDirectorySettingTemplate

This cmdlet call returns all available templates:

2. To add a usage guideline URL, first, you need to get the SettingsTemplate object that defines the usage guideline URL value: the Group. Unified template:

$TemplateId = (Get-AzureADDirectorySettingTemplate | where { $_.DisplayName -eq "Group.Unified" }).Id
$Template = Get-AzureADDirectorySettingTemplate | where -Property Id -Value $TemplateId -EQ

3. Next, create a new settings object based on that template:

$Setting = $Template.CreateDirectorySetting()

4. Then update the settings object with a new value. The two examples below change the usage guideline value and enable sensitivity labels. Set these or any other setting in the template as required:

$Setting["UsageGuidelinesUrl"] = "https://guideline.example.com"
$Setting["EnableMIPLabels"] = "True"

5. Then apply the setting:

New-AzureADDirectorySetting -DirectorySetting $Setting

6. You can read the values using:

$Setting.Values