diff --git a/Viva/insights/advanced/admin/prepare-org-data.md b/Viva/insights/advanced/admin/prepare-org-data.md index 33c518589..e9263cba7 100644 --- a/Viva/insights/advanced/admin/prepare-org-data.md +++ b/Viva/insights/advanced/admin/prepare-org-data.md @@ -95,20 +95,6 @@ The reason for including all licensed employees in the organization is that, if >[!Important] >Make sure the Microsoft 365 admin has assigned licenses to all employees you want to include in reports. Even if you include an employee in your organizational data file, they'll need a license to show up in reports. For more information about licensing and reports, see [When users show up in query results](../setup-maint/assign-licenses.md#when-users-show-up-in-query-results). - -##### Notification of missing data - -If the app detects that data is missing for one or more licensed employees, it alerts admins through a pop-up notification in the top-right corner of the **Data connections** tab. - -###### Upload missing organizational data - -To upload this missing data, the admin can follow these steps: - -1. On the pop-up notification, select **Download** to download a .csv file that contains the names of licensed employees whose organizational data is missing. -1. Open the .csv file. -1. Append the missing data for these employees. This means adding attributes (columns) that describe the employees in a way consistent with previous uploads. -1. Upload the file. Refer to [Upload organizational data (subsequent upload)](./upload-org-data-subsequent.md) for more information. - In addition to including all licensed employees in the upload of organizational data, we recommend that you also include unlicensed employees, as we explained [earlier](#including-all-licensed-employees). ### Step 3 - Get an export of organizational data diff --git a/Viva/insights/advanced/admin/rules-validation-errors.md b/Viva/insights/advanced/admin/rules-validation-errors.md index 599b51a34..88d8b93f9 100644 --- a/Viva/insights/advanced/admin/rules-validation-errors.md +++ b/Viva/insights/advanced/admin/rules-validation-errors.md @@ -104,7 +104,11 @@ Here's an example snippet of a valid .csv export file: ``PersonId,EffectiveDate,HireDate,ManagerId,LevelDesignation,Organization,Layer,Area Emp1@contoso.com,12/1/2020,1/3/2014,Mgr1@contoso.com,Junior IC,Sales,8,Southeast Emp2@contoso.com,11/1/2020,1/3/2014,Mgr1@contoso.com,Junior IC,Sales,8,Southeast Emp3@contoso.com,12/1/2020,1/3/2014,Mgr2@contoso.com,Manager,Sales,7,Northeast Emp4@contoso.com,10/1/2020,8/15/2015,Mgr3@contoso.com,Support,Sales,9,Midwest Emp5@contoso.com,11/1/2020,8/15/2015,Mgr3@contoso.com,Support,Sales,9,Midwest Emp6@contoso.com,12/1/2020,8/15/2015,Mgr3@contoso.com,Support,Sales,9,Midwest`` +## Download log for employees with missing data +The **Data quality** page lets you know if there are missing measured users in your organizational data file. If so, you'll see the message, "{number} measured users have missing organizational data. Download which users have missing organizational data, and upload their data for higher quality insights." + +The download log shows measured users who are missing any data field *except* the Domain and TimeZone system fields. ## Validation errors and warnings @@ -141,7 +145,7 @@ Below are the validation errors and warnings related to field values. If **Uploa | | | {Header name} contains an invalid value. Rows with invalid values are not uploaded. {Header name} should be an email address following the form `employee@contoso.com`.| Warning | All| | | | Invalid {header name} value. {Header name} should be a string. | Error | All | ||| {Header name} contains an invalid value. Rows with invalid values are not uploaded. {Header name} should be a string. | Warning |All | -|||
  • {Header name} contains an invalid value. Rows with invalid values are not uploaded. {Header name} should be a date following the form MM/DD/YYYY, MM/DD/YYYY, MM/DD/YYYY followed by more text (such as time), MM-DD-YYYY, MM-DD-YY, YYYY-MM-DD, Wednesday, March 14, 2012, March 14, 2012, 14-Mar-2012, or 14-Mar-12.
  • OR
  • {Header name} contains an invalid value. Rows with invalid values are not uploaded. {Header name} should be a date following the form DD/MM/YYYY, DD/MM/YYYY followed by more text (such as time), D/MM/YYYY, D/MM/YY, DD-MM-YYYY, DD-MM-YY , YYYY-DD-MM, Wednesday, March 14, 2012, March 14, 2012, 14-Mar-2012, or 14-Mar-12. | Warning |All | +|||
  • {Header name} contains an invalid value. Rows with invalid values are not uploaded. {Header name} should be a date following the form MM/DD/YYYY, MM/DD/YYYY, MM/DD/YYYY followed by more text (such as time), MM-DD-YYYY, MM-DD-YY, YYYY-MM-DD, Wednesday, March 14, 2012, March 14, 2012, 14-Mar-2012, or 14-Mar-12.
  • OR
  • {Header name} contains an invalid value. Rows with invalid values are not uploaded. {Header name} should be a date following the form DD/MM/YYYY, DD/MM/YYYY followed by more text (such as time), D/MM/YYYY, D/MM/YY, DD-MM-YYYY, DD-MM-YY, YYYY-DD-MM, Wednesday, March 14, 2012, March 14, 2012, 14-Mar-2012, or 14-Mar-12. | Warning |All | |||Invalid {header name} value. {Header name} should be a double following the form 23.75. | Error |All | ||| {Header name} contains an invalid value. Rows with invalid values are not uploaded. {Header name} should be a double following the form 23.75. | Warning | All | ||| Invalid {header name} value. {Header name} should be an integer. | Error | All | diff --git a/Viva/insights/advanced/admin/upload-org-data-subsequent.md b/Viva/insights/advanced/admin/upload-org-data-subsequent.md index 59ffd4c33..b9d4005c2 100644 --- a/Viva/insights/advanced/admin/upload-org-data-subsequent.md +++ b/Viva/insights/advanced/admin/upload-org-data-subsequent.md @@ -18,9 +18,9 @@ audience: Admin If organizational data has already been uploaded into the advanced insights app, you as an admin can use the information in this article to: -* Edit existing data. -* Replace existing data. -* Delete organizational attributes from existing data. +* Edit existing data +* Replace existing data +* Delete organizational attributes and employees from existing data Complete these steps after preparing the data as described in [Prepare organizational data](./prepare-org-data.md). @@ -46,16 +46,17 @@ After you prepare the source data, the uploading process follows these steps, wh All three actions share the same two first steps: -1. Select either the **Start** button on the **Data hub** tab or the **Edit or start new upload** button on the **Data connections** tab. +1. Select either the **Start** button on the **Data hub** tab or **Manage data sources** button on the **Data connections** tab. - :::image type="content" source="../images/admin-upload2-start-process.png" alt-text="Screenshot that shows Edit or start new upload option."::: + :::image type="content" source="../images/data-quality-manage-data.png" alt-text="Screenshot that shows the Manage data sources button."::: -2. The resulting page lists three options: +2. The resulting page lists four options: * **Add or edit data** * **Delete optional fields** + * **Delete employee data** * **Replace all data** - :::image type="content" source="../images/org-insights-1.png" alt-text="Screenshot that shows starting data-upload process." lightbox="../images/org-insights-1.png"::: + :::image type="content" source="../images/data-quality-manage-data-options.png" alt-text="Screenshot that shows the four options to manage data." ::: Make your selection based on what you want to do, then navigate to the corresponding section below for step 3. @@ -66,6 +67,7 @@ All three actions share the same two first steps: |Edit fields (columns)|[Update existing organizational data](#update-and-replace-existing-data)|Your file needs to include **PersonId** and other optional fields.| |Delete attributes| [Delete optional fields from existing organizational data](#delete-optional-fields-from-existing-organizational-data)|You can only delete optional attributes. If you delete fields used in autorefreshing queries, those queries will be disabled.| |Replace all existing organizational data|[Replace existing data](#replace-existing-data)|This option *permanently deletes* all organizational data you’ve uploaded in the past. If your file is missing any fields, autorefreshing queries that use those fields will be disabled.| + | Remove employees from organizational data | [Delete specific employees from existing organizational data](#delete-employees-and-data-from-existing-organizational-data) | This option lets you delete specific employees from your organizational data using a .csv file. | ## Update and replace existing data @@ -132,36 +134,56 @@ Finally, if you don’t remember the previous values of the EffectiveDate field, #### File upload -- Replace existing data: - 1. Enter an **Upload name**. - 1. Under **Upload file**, select the .csv file you want to upload. +1. Enter an **Upload name**. +2. Under **Upload file**, select the .csv file you want to upload. - Make sure that the .csv file is: - - * UTF-8 encoded - * Not open in a different program when you begin the upload process - * Not larger than 1 GB - :::image type="content" source="../images/admin-prepare-upload.png" alt-text="Screenshot that shows the Prepare and upload window."::: + Make sure that the .csv file is: + * UTF-8 encoded + * Not open in a different program when you begin the upload process + * Not larger than 1 GB + :::image type="content" source="../images/admin-prepare-upload.png" alt-text="Screenshot that shows the Prepare and upload window."::: >[!Note] >To see the structure and guidelines for .csv files, and to avoid common issues during upload, you can download a template through the **Download .csv** template link. - 3. Upload your file by selecting **Next**. If you need to cancel the upload, select **Cancel**. +3. Upload your file by selecting **Next**. If you need to cancel the upload, select **Cancel**. - Now you’re ready to map fields. For your next steps, go to [Field mapping](#field-mapping). +Now you’re ready to map fields. For your next steps, go to [Field mapping](#field-mapping). ### Delete optional fields from existing organizational data -- Delete fields: - 1. Name your delete action so you can refer to it later. - 1. Identify the attribute you want to delete, then check the corresponding box. - 1. The resulting screen lists which attributes have been deleted. Select **Back** to return to the Data hub. +1. Name your delete action so you can refer to it later. +2. Identify the attribute you want to delete, then check the corresponding box. +3. The resulting screen lists which attributes have been deleted. Select **Back** to return to the Data hub. - The delete process is now complete. +The delete process is now complete. >[!Important] > The following sections apply to *upload* and *replace* actions only. +### Delete employees and data from existing organizational data + +Select this option to remove organizational data you no longer need, or remove historical data for an employee so you can edit your data with a clean slate. After you remove the employees, you can upload a new file to add new data for the employees you deleted. + +#### How to upload the file + +1. Create a .csv file with the names of the employees you want to delete. The file should include a column named "PersonId," with the email address of each person you'd like to delete in each row of that column. Make sure the .csv file is: + * UTF-8 encoded + * Not open in a different program when you begin the upload process + * Not larger than 1 GB + +2. Enter a **Delete action name**. + +3. Under **Upload a file with the employees you want to delete**, select the .csv file. + +4. To upload your file, select **Submit**. To cancel the upload, select **Cancel**. + +5. The **Import history** table shows the status of your deletion. + * Select the download icon to download a list of employees deleted within the past 30 days. + + + + ## Field mapping After you upload your file, you’ll see the field mapping page. To view insights from your data, you need to map fields (columns) from your .csv file to field names that the app recognizes. diff --git a/Viva/insights/advanced/images/data-quality-manage-data-options.png b/Viva/insights/advanced/images/data-quality-manage-data-options.png new file mode 100644 index 000000000..c010bec42 Binary files /dev/null and b/Viva/insights/advanced/images/data-quality-manage-data-options.png differ diff --git a/Viva/insights/advanced/images/data-quality-manage-data.png b/Viva/insights/advanced/images/data-quality-manage-data.png new file mode 100644 index 000000000..c44fe2b21 Binary files /dev/null and b/Viva/insights/advanced/images/data-quality-manage-data.png differ diff --git a/Viva/insights/org-team-insights/copilot-dashboard.md b/Viva/insights/org-team-insights/copilot-dashboard.md index ab9e876ed..614c86696 100644 --- a/Viva/insights/org-team-insights/copilot-dashboard.md +++ b/Viva/insights/org-team-insights/copilot-dashboard.md @@ -67,7 +67,7 @@ If you have access to the dashboard, you can also delegate access to the dashboa ## How access to the Copilot Dashboard is determined -For customers who use Microsoft Entra ID (formerly known as Azure Active Directory) to manage user profile data like organization or manager data, the Copilot Dashboard is automatically available to a limited number of users. Access is based on Microsoft Entra ID Data, specifically the manager hierarchy attribute. Microsoft 366 Global Administrators can disable access at any time. +For customers who use Microsoft Entra ID (formerly known as Azure Active Directory) to manage user profile data like organization or manager data, the Copilot Dashboard is automatically available to a limited number of users. Access is based on Microsoft Entra ID Data, specifically the manager hierarchy attribute. Microsoft 365 Global Administrators can disable access at any time. Users who are senior leaders within large teams as determined by their Entra ID data manager attribute can automatically view the report. Tenants must meet both of the following criteria to qualify: @@ -223,7 +223,7 @@ You can sort the table by the headers. For example, to sort by the metric value, ###### **Insight #2: Breakdown of Copilot usage across different Microsoft 365 apps** -App totals reflect the total number of adoption metrics in the following Microsoft 365 apps: Microsoft Teams, Outlook, Word, Excel, PowerPoint, and Business Chat (work). +App totals reflect the total number of adoption metrics in the following Microsoft 365 apps: Microsoft Teams, Outlook, Word, Excel, PowerPoint, Business Chat (work), and Business Chat (web). Group totals reflect all users based on the filtered group, including groups that are below the minimum group size. @@ -264,7 +264,7 @@ Group totals reflect all users based on the filtered group, including groups tha | Business Chat (work) prompts submitted | The number of prompts submitted by users in Business Chat (work), formerly called Copilot chat (work). Includes prompts submitted through Teams, Outlook, Edge, and the Microsoft 365 app. | | Business Chat (work) prompts submitted in Teams | The number of Business Chat (work) queries submitted by users through Teams, formerly called Copilot Chat (work). | | Business Chat (work) prompts submitted in Outlook | The number of Business Chat (work) queries submitted by users through Outlook, formerly called Copilot Chat (work). | -| Business Chat (web) prompts submitted | The number of queries submitted by users in the web tab of Business Chat, also known as "Coplot with Enterprise Data Protection." Includes prompts submitted through Edge and the Microsoft 365 app. | +| Business Chat (web) prompts submitted | The number of queries submitted by users in the web tab of Business Chat, also known as "Coplot with Enterprise Data Protection." Includes prompts submitted through Edge and the Microsoft 365 app. Data is available from 08/20/2024 onwards. | | Summarize chat actions taken using Copilot in Teams | The number of times users summarized chats and channel conversations in Teams using Copilot. | | Compose chat message actions taken using Copilot in Teams | The number of chats and channel message drafts created in Teams using Copilot. | | Chat conversations summarized by Copilot | The number of chats and channel conversations summarized by Copilot. | @@ -302,7 +302,9 @@ Microsoft 365 global admins can upload aggregated survey results through Adoptio #### Impact page for companies with at least 50 assigned Copilot licenses >[!Important] ->You must enable optional diagnostic data for the following metrics in this section: Copilot assisted hours; Total emails sent using Copilot; Number of Teams meetings summarized; Number of Teams meeting hours summarized; and Total chat conversations summarized by Copilot. +>You must enable optional diagnostic data to get comprehensive data for the following metrics in this section: Copilot assisted hours; Total emails sent using Copilot; Number of Teams meetings summarized; Number of Teams meeting hours summarized; and Total chat conversations summarized by Copilot. +> +> If you disable optional diagnostic data, these metrics might still include product usage collected from *required* diagnostic data. > >All other metrics in the report are powered by required service data and don't require optional diagnostic data enablement. [Learn more about diagnostic data](/microsoft-365-apps/privacy/optional-diagnostic-data). @@ -398,7 +400,7 @@ This analysis helps you compare collaboration activities between employees who u | | Chat (Copilot in PowerPoint) prompts submitted | The number of times users submitted a prompt to Copilot chat in PowerPoint. Includes any prompts that don't map to one of the established PowerPoint Copilot skills such as "Summarize"-, "Add content"-, or "Organize presentation"- actions taken in PowerPoint. | | | Chat (Copilot in Excel) prompts | The number of times users submitted a prompt to Copilot chat in Excel. Includes any prompts that don't map to one of the established Excel Copilot skills such as "Analysis"-, "Formatting"-, or "Formula"- actions taken in Excel. | | **Business Chat** | Business Chat (work) prompts submitted | The number of prompts submitted by users in Business Chat (work), formerly called Copilot chat (work). Includes prompts submitted through Teams, Outlook, Edge, and the Microsoft 365 app. | -| | Business Chat (web) prompts submitted | The number of queries submitted by users in the web tab of Business Chat, also known as "Coplot with Enterprise Data Protection." Includes prompts submitted through Edge and the Microsoft 365 app. | +| | Business Chat (web) prompts submitted | The number of queries submitted by users in the web tab of Business Chat, also known as "Coplot with Enterprise Data Protection." Includes prompts submitted through Edge and the Microsoft 365 app. Data is available from 08/20/2024 onwards. | **Key behavior metrics for this page:** diff --git a/Viva/insights/toc.yml b/Viva/insights/toc.yml index 77c979ff6..61fa86cfc 100644 --- a/Viva/insights/toc.yml +++ b/Viva/insights/toc.yml @@ -100,6 +100,8 @@ items: href: advanced/admin/import-business-data-azure.md - name: Import business data with a .csv file href: advanced/admin/import-business-data-csv.md + - name: File rules and validation errors + href: advanced/admin/rules-validation-errors.md - name: Export Viva Insights data using MGDC href: advanced/admin/dynamic-metric-load.md - name: Integrate Viva Glint and Viva Insights data @@ -112,8 +114,6 @@ items: href: advanced/admin/export-insights-data-glint.md - name: Create partitions href: advanced/admin/partitions.md - - name: File rules and validation errors - href: advanced/admin/rules-validation-errors.md - name: Domain suppression href: advanced/admin/domain-suppression.md - name: Keyword suppression