Microsoft Viva Glint: Copilot will default to ON and move to VFAM as the single control

Introduction

We are simplifying how your organization manages Copilot access in Viva Glint. Viva Glint will now use Viva Feature Access Management (VFAM) as the single control plane for Copilot access, consistent with other Microsoft Copilot experiences. As part of this change, the existing Glint service‑level Copilot toggles will be removed, and Copilot will default to ON at the Glint service level.

This removes unnecessary admin friction caused by the current dual‑gate model and ensures a clearer, more consistent governance experience across Microsoft 365.

This message is associated with Roadmap ID 551197.

When this will happen:

General Availability (Worldwide): Rollout will begin in early March 2026 and is expected to complete by late March 2026.

How this affects your organization

Who is affected

• All organizations using Viva Glint.
• Viva Glint service admins who previously managed Copilot toggles within Glint.
• Global/M365/Viva Glint Tenant Admins who manage feature access using VFAM.
• Users with Glint permissions (Reports + Comments access) who will see Copilot by default unless restricted in VFAM.

What’s changing

• The Copilot enable/disable settings currently found in Viva Glint admin pages (per survey program, per role, and Company Admin settings) will be removed.
• Copilot will default to ON for all customers at the Glint service layer.
• VFAM becomes the single, authoritative control for Copilot access in Viva Glint.

What stays the same

• VFAM access policies (tenant, group, user) continue to apply and default to ON. Learn more: Control access to features in Microsoft 365 | Microsoft Learn.
• Users will only see Copilot if they have the required Glint permissions (Reports access and Comments access).

Impact

• Glint service admins: No more Copilot toggles to manage; reduced admin workload.
• Global/M365/Viva Glint Tenant Admins: Manage Copilot access exclusively in VFAM.
• Users: Copilot will appear by default, unless disabled in VFAM.

Licensing & Compliance Clarifications

• A license for Viva Glint, Microsoft Viva Suite, or Microsoft Viva Workforce Analytics and Employee Feedback is required to access Copilot in Viva Glint.
• A license for Microsoft 365 Copilot is not required to access Copilot in Viva Glint.

For compliance and feature FAQs, refer to:

• Data, privacy, and security compliance for Microsoft 365 Copilot in Viva Glint
  
• Microsoft 365 Copilot in Viva Glint-Enablement and general FAQs
  

What you can do to prepare:

Admins can take the following steps:

Review your VFAM settings

• Go to admin.microsoft.com → Settings → Viva → Viva Glint → Manage settings for Microsoft Copilot in Viva Glint.
• Verify tenant‑level Copilot access.
• If you need to restrict Copilot for specific groups or users, configure custom VFAM policies.

Inform your Glint service admins

• They will no longer manage Copilot access inside the Glint admin portal.

Get help from the product team

Join the Feb 12th Viva Customer Connection Program (VCCP) session to learn more about this update. During the session, you will:

• Get early visibility into what’s changing and why Microsoft is making this update.
• Learn how this update simplifies setup and expands access to AI powered insights for managers and leaders. With additional Copilot capabilities coming soon, admins should maintain their current VFAM settings and keep Copilot enabled for all Glint users to ensure they benefit from upcoming enhancements.
• Understand what stays the same for permissions, privacy, and compliance. Glint Copilot uses only existing Glint data and honors current permissions, making privacy, security, compliance, and works council review much simpler than M365 Copilot approvals. Additionally, no M365 Copilot premium license is required to enable Glint Copilot for all users.
• Ask the product team questions.

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.