Administrator enablement for Microsoft 365 Copilot in Viva Glint

Article
2025-04-24

Prerequisites to enabling Microsoft 365 Copilot in Viva Glint:

You have at least one Recurring or Ad hoc survey administered or closed on the Viva Glint platform
Your dashboard default language is set to English
View Comments is enabled on the Reporting tab in Program Summary

Admins enable Copilot in Viva Glint. Microsoft privacy policies prohibit Copilot in Viva Glint from being enabled by default for any User Roles.

Assign yourself and others using Copilot in Viva Glint to a new User Role. Create the new User Role with access to the Comments Report enabled. Add that User Role to the survey Reporting page in Program Summary.

Important

Users without access to the Comment Report can't access Viva Glint in Copilot.

Grant Comment Report permission

From your admin dashboard, follow this process:

Select the configuration (cogwheel) symbol.
In the Employees section, select User Roles.
Select the User Role to provide Comment Report access. In this example, Company Admin is chosen.

Note

The Manager role has Comment Report permission enabled as a default setting.
Select Permissions.
In the Reporting section of the Permissions and Access page, enable View Comments.

Grant Comment Reports access

The second step to enabling Copilot in Viva Glint for User Roles happens in the program's Reporting section. This step allows users enabled for the Comment Reports to access the report.

Ramp up to full utilization

Copilot in Viva Glint gives you the flexibility to roll out to one or many user roles. Consider what approach is right for your organization. Viva Glint suggests this best practice for ramping to a full rollout:

Admin release: By default, Copilot in Viva Glint is available to the Admin User Role. You may decide that for the first deployment you don't want to provide access beyond this group. This initial release can be a way to first test and better understand the functionality. Admins can also use this time to test the Copilot functionality for previously closed surveys before using it for an upcoming cycle.
Selective deployment: You may decide to deploy to a group beyond the admins but still not your entire eligible population. Consider which groups make sense for you. Perhaps these groups are your extended HRBP team or senior leaders who have large amounts of comments. As long as the group you want to grant access to is part of a set User Role group within Viva Glint, you can provide them with access.
Full deployment: Deploying to all eligible users is the highest level of deployment. This would include all roles who have results access. Even with this deployment, some leaders may not be able to use Copilot if their comments and respondents don't meet your set thresholds. For those teams that have fewer comments, Copilot may be less critical, as often these leaders can read through verbatims quickly.

From your admin dashboard, follow this process for deployment:

Select the Configuration symbol.
In the Surveys section, select Survey Programs.
Select the closed Recurring or Ad hoc program for which you want to grant access.
In Program Summary, select Reporting.
In Program Roles, select the User Role to enable with Copilot in Viva Glint. In this example, the customized role is 'VI'.
Toggle Copilot in Viva Glint to On and then Save Changes.

Ensure Copilot in Viva Glint is enabled

From your admin dashboard, follow this process:

Select the Configuration symbol.
Select User Roles in the Employees section to see the list of all users assigned to a particular role.
Select any employee in a User Role in which you expect Copilot to be enabled.
Once you are on that user's profile, select View As to validate the user's reporting experience.
Be sure you see the Copilot button on the user's Viva Glint dashboard.

Reporting steps before using Copilot in Viva Glint

Follow these steps on the Manager Guide for reviewing feedback results:

Review your scores on the Viva Glint Team Summary dashboard before jumping directly into Copilot.
Review the Strengths & Opportunities section on the Viva Glint Team Summary dashboard. This dashboard shows you strengths to celebrate and opportunity areas to improve upon.
Now, ask Copilot in Viva Glint to dive deeper to uncover insights around your areas of interest.

Get the most from Copilot in Viva Glint

Use these best practices to get the most from Copilot in Viva Glint. Maximize what Copilot can summarize by using these guidelines:

Enable comments

Enabling comments on quantitative items allows for more detailed feedback and context, enhancing the data's richness and usefulness for summarization. This approach provides a more comprehensive view of feedback, even on single-item indices. This practice, in turn, allows Copilot to generate more accurate and insightful summaries.

Bring in relevant filter attributes

Copilot in Viva Glint uses HRIS or demographic attributes that are imported to Viva Glint to filter data. The use of attributes allows for targeted insights based on specific and impactful employee filters. Enable filter attributes that are important for the user roles interacting with Copilot.

Use these quick tips

Use these tips to understand and act on employee feedback quickly.
Need help with writing prompts? Use these tips to get started writing prompts for Copilot in Viva Glint.

Ask open-ended questions

Open-ended survey items are valuable for capturing a wide range of feedback. Open-ended items allow respondents to freely express their thoughts on topics that aren't covered by the survey items. Comment boxes provide a space for any top-of-mind concerns or suggestions. Comments are typically detailed and offer rich data for Copilot to generate comprehensive summaries. Comment summarization may reveal insights not apparent from quantitative data alone.

Use Recurring and Ad Hoc programs

Where it makes sense, use Recurring and Ad Hoc programs. At this time, Copilot in Viva Glint is unable to tap into Always-On and Employee Lifecycle programs. To maximize your ability to use Copilot in Viva Glint, use Recurring program setup for ongoing topics (for example, Engagement) and Ad Hoc for one-off topics (for example, Change Management).