Microsoft will give Viva Glint administrators a direct, tenant-wide control to set data retention periods for all manner of employee surveys—engagement, always-on, lifecycle, and 360-degree feedback—when the feature reaches general availability in June 2026 for commercial and Government Community Cloud (GCC) customers. The change, documented on the Microsoft 365 Roadmap, moves one of the messiest parts of employee-experience software from support-request purgatory into a self-service toggle, forcing organizations to decide how long they really need to keep sensitive workplace sentiment data.

What’s Actually Changing

Starting in June 2026, service administrators for Microsoft Viva Glint will find a new data retention policy setting in the product’s general settings. Instead of defaulting to indefinite storage—the long-standing behavior—admins can now specify a retention window in months and apply it across all Viva Glint feedback instances in the tenant. Microsoft says the policy covers past, present, and future survey data: engagement programs, recurring and ad-hoc pulses, lifecycle surveys, always-on feedback, and 360-degree review cycles, including associated reporting conversations, action plans, and goals.

The workflow is straightforward. An administrator navigates to the Glint admin console, chooses a retention period (between 6 and 1000 months), and saves the policy. Once active, any survey data older than that period becomes eligible for permanent deletion. Microsoft explicitly warns that deletion is irreversible and that the policy applies to already-closed cycles, not just new ones. The default “until subscription ends” option remains for organizations that prefer to keep everything.

Important nuance: the clock starts differently depending on the data type. For engagement, recurring, ad-hoc, and lifecycle surveys, retention is measured from the survey cycle end date. For always-on surveys, it’s from the individual response date. For 360-degree feedback, it’s the effective due date of the feedback cycle (using the latest subject due date, or the cycle due date if no subjects exist). This granularity means administrators must understand their survey programs well or risk accidentally deleting data that business leaders still consider current.

What This Means for You

The impact spreads across several organizational roles, and smart companies will treat the new toggle as a cross-functional governance event, not just another IT checkbox.

For HR and People Analytics Teams

You’ve likely built dashboards, trend lines, and year-over-year comparisons on years of Glint data. A retention limit could erase the historical baselines you rely on to prove that engagement initiatives work. Before any retention number is chosen, map existing survey programs—their cycle dates, reporting dependencies, and any imported historical data. If you’re mid-migration from a legacy survey tool, coordinate the import timeline with the retention setting; imported data older than the policy’s window could be deleted almost immediately after ingestion. The feature also pushes you to have hard conversations: is a 10-year archive of employee comments analytically useful, or just a liability? HR should own the answer, even if IT owns the configuration.

For Legal, Privacy, and Compliance Teams

Indefinite retention of free-text survey comments, manager ratings, and exit feedback creates discovery and privacy risks. A defined retention period aligns Viva Glint with data minimization principles and other corporate records schedules. But the policy isn’t a catch-all. It applies only to Glint survey data—not to underlying user identities, HRIS imports, or configuration metadata. Deleted-user handling, data subject requests, and cross-border transfer considerations remain separate. Works councils and employee representatives may also expect consultation before old feedback is purged. Treat the Glint retention setting as one control in a broader employee-data governance playbook, not a complete solution.

For IT and Microsoft 365 Administrators

You’ll likely be the one clicking the button, but don’t go it alone. The new setting is a tenant-level control that could delete years of data in seconds. Before touching it, inventory current Glint usage: who runs surveys, what type, how far back they go, and whether any integrations (Power BI, custom reporting) depend on old data. Test the policy in a sandbox or on a single program if possible. Document the chosen retention number, the business rationale, and the approval chain. And remember: the policy is retroactive. The moment you set a 24-month window, any survey cycle that ended more than two years ago is gone. No undo.

For Employees

Workers might never see this setting, but they’ll feel its downstream effects. A clear, communicated retention policy can actually increase survey trust. If people know their candid feedback won’t live forever in a corporate database, they may be more honest. Organizations that use this feature to demonstrate responsible data stewardship should say so plainly in survey invitations. Conversely, a silent purge that later disrupts an engagement trend analysis or a manager’s historical report can erode confidence in HR systems. Transparency matters.

How We Got Here

Viva Glint’s data-handling story has always been a little awkward. When Microsoft acquired Glint (formerly Glint Inc.) in 2018 and eventually folded it into the Viva suite, it inherited a platform that treated survey data as perpetually valuable—great for longitudinal analytics, terrible for compliance officers. Until now, the only way to delete old survey data was to open a support ticket. Microsoft’s own documentation steered customers toward that path. For an enterprise SaaS product in 2026, that’s untenable.

The broader context is Microsoft’s steady push to make all Viva modules behave like governed Microsoft 365 workloads. Over the past few years, we’ve seen retention labels, eDiscovery, and audit logging spread from Exchange and SharePoint to Teams, Viva Engage, and now Viva Glint. The June 2026 rollout, which includes GCC tenants from day one, signals that Microsoft views this as a compliance-first feature, not a nice-to-have. Regulatory pressure, employee privacy expectations, and the sheer volume of workplace sentiment data being collected by large organizations made the move inevitable.

Interestingly, the feature lands amid a wider industry conversation about “data minimization” in HR tech. European data protection authorities have been scrutinizing how long companies keep employee feedback. California’s privacy laws give workers rights to deletion. Even without legal mandates, internal privacy reviews increasingly demand that every system justify its retention periods. Microsoft’s toggle gives administrators a concrete tool to comply—but also forces the organization to defend its chosen number.

What to Do Now

  1. Inventory your Glint data estate. List every active and historical survey program, always-on feedback channel, 360 cycle, and any imported historical data. Note the end dates of the most recent cycles, the business owners, and whether downstream reports or dashboards depend on older data.

  2. Map retention schedules to Glint. If your organization already has a records retention schedule that covers employee relations, performance reviews, or survey results, align the Glint policy to it. If not, use this feature as a forcing function to create one. Legal, compliance, and HR leaders should agree on a single number (or a phased approach) before the June 2026 rollout.

  3. Test the setting before applying broadly. As of the GA date, Microsoft says the feature will be available in the Glint admin console. If you have a non-production tenant or a limited survey pilot, test the retention window there first. Verify that old cycles disappear as expected and that current programs continue to function. Pay special attention to 360-degree feedback; because of the due-date anchoring, partial or late-submitted feedback could be caught in a retention sweep sooner than expected.

  4. Coordinate historical data imports. If you’re planning to bring years of old engagement data into Glint from another platform, do not hit “import” before setting the retention policy appropriately. Microsoft’s documentation warns that imported data older than the configured retention period may be deleted shortly after import. It’s safer to import first into a tenant with indefinite retention, verify the data, then apply the policy (and document that the clock for that import starts at the original survey cycle end date, not the import date).

  5. Communicate to stakeholders. At minimum, inform the HR leadership, employee listening team, and any analytics group that the retention setting will be implemented. Explain what data will be affected, why the chosen period was selected, and how they can prepare. For employees, update privacy notices or survey invitation language if your organization commits to a specific retention window. Trust is built by transparency, not by surprise deletions.

  6. Document the decision. Create a written record that captures: the chosen retention value (in months), the rationale (legal requirement, privacy policy, storage cost, etc.), the date the policy was applied, the person who applied it, and the approval path. This document will be invaluable when someone later asks why a three-year-old engagement cycle is missing—or why it’s still there.

The Outlook

The new Viva Glint retention control is a small toggle with an outsized message: employee feedback is no longer a forever asset simply because it’s housed in Microsoft’s cloud. By bringing retention into the admin console and making it retroactive, Microsoft is handing organizations a tool that can reduce legal exposure, align with data privacy norms, and force overdue governance conversations. But its sharp edges are real. In the coming months, expect to see companion guidance from Microsoft on how this feature interacts with broader Purview capabilities, eDiscovery, and data subject requests. And watch for similar lifecycle controls to trickle into other Viva modules. The era of treating Viva as “HR’s playground” without IT-style governance is ending. That’s good for compliance, good for employee trust, and—if handled badly—a fast track to a lot of deleted data.