Microsoft is preparing to close the loop between Copilot usage data and employee feedback. A new feature on the Microsoft 365 roadmap (ID 568072) will let change leaders fire off a Viva Pulse survey directly from the Copilot dashboard, targeting the exact cohort of users currently displayed in their adoption analytics. No more exporting lists, no more manually recreating audience filters in Pulse. The integration enters preview in August 2026, with a broader rollout expected in September.

The Integration: From Dashboard Filter to Survey in One Click

Currently, the Copilot Dashboard in Microsoft Viva Insights already surfaces adoption metrics like active users, usage frequency, and feature adoption across departments or job functions. It also provides a button to create a new Viva Pulse survey. But that workflow still requires the change leader to manually define the survey audience—even if they just spent ten minutes filtering the dashboard down to a specific group they want to hear from.

The planned update changes that. When a change leader applies filters in the Copilot Dashboard—say, the marketing department with unusually low Copilot usage—the new "Targeted Audience Survey" capability will prepopulate the Viva Pulse survey invitation with those same employees. According to Microsoft's roadmap entry, survey audiences will update automatically from Viva Insights data and inherit the dashboard’s existing organization and job-function filters. That means the survey reaches exactly the people in the dashboard view, no reconstruction needed.

Why This Matters for Your Organization

For IT admins and Copilot program owners, the feature removes a pain point and adds precision. Instead of guessing whether a separate survey list matches the dashboard segment, you get a one-click handoff. This lets you run tighter feedback loops:

  • Spot a group with high Copilot usage but perhaps low satisfaction? Send a quick pulse on training quality or AI trust.
  • See a team with low adoption but neutral survey scores? Maybe they're constrained by licensing or lack of relevant use cases—not disinterest. A survey can surface that.
  • Identify a puzzling spike in usage? A pulse can quickly tell you if it's a new champion or a temporary project.

For end users, the surveys will appear like any other Viva Pulse request, typically within Microsoft Teams or Outlook. The key is that they’re relevant—they only get sent if they’re part of the dashboard segment being analyzed. Microsoft says results remain at the population level, meaning no manager will see individual answers. That should ease privacy concerns, but organizations still need to configure Viva Insights minimum-group thresholds to prevent identifying small teams.

A Step-by-Step Look at the New Workflow

Based on Microsoft's existing documentation and the roadmap details, here’s how the new flow is likely to work once live:

  1. A change leader opens the Copilot Dashboard in Viva Insights and navigates to the adoption or usage reports.
  2. They apply filters—by region, department, job role, or even custom attributes—to narrow down the view.
  3. The dashboard shows the aggregated metrics for that cohort. If the leader wants to dig deeper into why the numbers look the way they do, they’ll click a “Send Pulse Survey” button (already present in the dashboard but soon enhanced with audience auto-population).
  4. The system automatically generates a Viva Pulse survey instance, pre-filled with a Copilot-specific survey template and the audience list matching the dashboard filters. The leader can customize the questions if needed.
  5. After the survey is sent, responses flow back into the Copilot Dashboard as sentiment scores, which can be viewed alongside the adoption metrics that prompted the survey.

This integration is not about adding new survey capabilities—Pulse already does that. It’s about removing friction between insight and action. Microsoft has been gradually tightening this link: earlier in 2026, a message center post (MC1422058) announced the ability to measure Copilot sentiment via Pulse and view results in the dashboard. The new roadmap feature is the logical next step: automating the audience step.

How We Got Here: The Sentiment-Measurement Journey

Microsoft laid the groundwork for this integration earlier in 2026. In a message center post (MC1422058), the company announced that Viva Pulse survey results could be displayed directly in the Copilot Dashboard as sentiment scores. That update let organizations correlate employee feedback with adoption metrics for the first time, but the process remained manual: an admin had to create a survey in Pulse, define the audience, and then later view the results in the dashboard. The feedback loop was slower, and many change leaders skipped the step because it required extra work.

Before that, the Copilot Dashboard (released as part of Viva Insights) mainly focused on quantitative data—active users, suggested actions, and usage trends. It didn’t incorporate any qualitative input. The roadmap item 568072 is the next evolution: closing the loop by making survey creation a one-click extension of the dashboard’s own filtering. This progression mirrors how Microsoft has been treating Copilot adoption as a holistic challenge: you need to understand both what users are doing and how they feel about it.

Privacy and Guardrails: What You Need to Check

Because Copilot adoption data can feel sensitive—no one wants to be flagged as a “low user”—Microsoft emphasizes that survey responses are aggregated. The dashboard will show sentiment trends, not individual answers. However, administrators must still ensure their Viva Insights settings respect privacy. That means:

  • Enforcing minimum group sizes for any analytics view. Viva Insights typically requires a minimum of five or ten people to avoid revealing individual patterns.
  • Reviewing Viva Pulse administrative settings to confirm that survey participation is optional and respondents can choose to remain anonymous.
  • Communicating clearly with employees that Copilot adoption dashboards are for organizational enablement, not performance evaluation.

If an organization's Viva Insights data is not already anonymized or aggregated appropriately, the new survey feature won’t magically fix that. It’s additive—it uses the same underlying data permissions. So before turning on targeted surveys, IT teams should double-check their analytics and privacy configurations.

A Practical Example: When Sentiment and Telemetry Clash

Consider a scenario that will become easier to investigate once targeted surveys arrive. A change leader filters the dashboard to show the legal department, which shows a high Copilot adoption rate—80% of licensed users are active weekly. But a targeted Pulse survey reveals that employees rate Copilot’s usefulness as low and report frequent inaccuracies. The quantitative data looked promising, but the sentiment exposed a quality problem. Armed with that insight, the organization could offer additional training on prompt engineering or escalate to Microsoft support about model output issues.

Alternatively, a department with low adoption might report in a survey that they simply don’t see the value—Copilot doesn’t fit their workflow. That’s a different problem from “they don’t know how to use it.” The targeted survey moves the organization from assumption to evidence.

What This Won’t Do

It’s important to set expectations. This feature won’t automatically measure business value or ROI of Copilot. It won’t replace in-depth change management workshops or one-on-one interviews. It’s a lightweight diagnostic tool that works best with focused questions. A badly designed survey—too long, too vague, or sent too frequently—will annoy users and yield poor data. The feature’s value will be directly proportional to the skills of the change leader using it.

What You Should Do Now

If your organization uses or plans to use the Copilot Dashboard and Viva Pulse, here are your next steps:

  1. Verify Viva Settings: Confirm that Viva Insights and Pulse are configured with appropriate privacy controls, group minimums, and data retention policies. Microsoft’s admin guidance for Viva Insights is a good starting point.
  2. Prepare Survey Templates: While the audience automation isn't live yet, you can already create Copilot-focused Pulse survey templates. Think about the questions that would most help your adoption program: usefulness of Copilot, frequency of use, training gaps, trust in AI outputs, etc.
  3. Train Change Leaders: The feature will empower those who own Copilot rollout. Ensure they understand how to filter the dashboard meaningfully and how to interpret side-by-side sentiment and usage data without jumping to conclusions.
  4. Watch the Roadmap: Mark your calendar for August 2026. Since this is a roadmap target, treat dates as directional. Set up an alert on the Microsoft 365 roadmap to get notified when the feature moves to “rolling out.”
  5. Communicate with Users: Before sending surprise Pulse surveys, consider a brief communication to employees explaining that feedback helps improve Copilot experience, not evaluate individuals. Transparency builds trust.

Outlook

For now, the feature is a roadmap entry. But the pattern is clear: Microsoft is building a tighter integration between Copilot analytics and employee voice. As Copilot adoption becomes a KPI for many IT teams, tools that make feedback more surgical will be in high demand. If the August preview arrives on time, expect rapid iteration—possibly including AI-suggested survey questions based on usage anomalies or automatic triggering of surveys when certain thresholds are hit.

The success of targeted Pulse surveys will depend less on the button itself and more on how organizations use the insight. A well-crafted pulse that yields actionable data could accelerate Copilot proficiency across departments. A poorly designed one, or a distrustful workforce, could backfire. The tool is coming. Smart teams will start preparing now.