check before: 2026-03-01
Product:
Copilot, Entra, Microsoft 365 admin center, Microsoft 365 Apps, Microsoft 365 Copilot, Microsoft 365 Groups, Microsoft Viva, Microsoft Viva Glint, Workplace Analytics
Platform:
Online, Web, World tenant
Status:
Rolling out
Change type:
Admin impact, New feature, Updated message, User impact
Links:
Details:
Summary:
Microsoft Viva Glint Copilot will default to ON and be managed exclusively via Viva Feature Access Management (VFAM) in Microsoft 365 admin center, aligning with enterprise AI governance. Existing Glint toggles will be removed. Rollout starts March 2026, completing by April 2026, with resources provided for setup and compliance.
Details:
Updated February 26, 2026: We are extending the rollout timeline to give customers additional time to complete AI governance reviews and configure Viva Glint Copilot access policies in the Microsoft 365 admin center. We have also added additional content providing you with more resources and details surrounding this change. Thank you for your patience.
[Introduction]
Copilot in Viva Glint will align with Microsoft's enterprise AI governance platform: enabling your IT and compliance teams to use centralized governance tools for access management and unified monitoring and reporting across all AI deployments in your tenant. 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 message is associated with Roadmap ID 551197.
Why We're Making This Change to Copilot Access Management
Aligns Viva Glint with Microsoft's enterprise AI governance platform: Managing Copilot access control with the Microsoft 365 admin center enables your IT and compliance teams to use centralized governance tools for access management and unified monitoring and reporting across all AI deployments in your tenant. This reduces governance complexity and audit burden by providing a single control plane for managing AI features across Microsoft 365.
Dynamic Entra Groups for Automatic Access Management
Dynamic Entra groups in the Microsoft 365 admin center automatically maintain Copilot access based on user attributes (department, location, job title, manager status). When VFAM policies are scoped to dynamic groups, membership updates automatically as employees join, leave, or change roles - eliminating manual policy maintenance. For more information, see Create or update a dynamic group in Microsoft Entra ID.
Who can manage Viva Glint Copilot Access in M365 Admin Center
Viva Glint Tenant Administrators
AI Administrators
Microsoft 365 Global Administrators
Three Common Setup Scenarios for Viva Glint Copilot Access Control
Administrators can configure Copilot access using one of three approaches:
Scenario 1: Enable for all Viva Glint users (default) - The organization-wide setting is turned ON with no custom policies. All licensed users with appropriate Viva Glint permissions can access Copilot features.
Scenario 2: Pilot mode with specific groups - The organization-wide setting is turned OFF, and custom policies enable Copilot only for selected Microsoft Entra groups (for example, HR team, senior leadership). This approach supports phased rollouts or limited pilots before broader enablement.
Scenario 3: Broad enablement with exclusions - The organization-wide setting is turned ON, and custom policies disable Copilot for specific Microsoft Entra groups (for example, users in regions pending works council approval). All other users have access by default.
[When this will happen:]
General Availability (Worldwide): Rollout will begin in early March 2026 and is expected to complete by the end of April 2026 (previously late March 2026).
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
General Availability
Created:
2026-01-27
updated:
2026-02-27
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
linked item details
XXXXXXX ... free basic plan only
summary for non-techies**
Starting March 2026, Microsoft will enable Copilot by default for all Viva Glint users, removing individual switches and centralizing access management through Viva Feature Access Management (VFAM) in the Microsoft 365 admin center, with options for default access, pilot mode for specific groups, and broad access with exclusions, while utilizing Dynamic Entra Groups for automatic updates based on user criteria.
Direct effects for Operations**
Removal of Copilot Toggles
Glint service admins will lose the ability to manage Copilot toggles, leading to potential confusion and mismanagement of user access.
- roles: Glint Service Admins, Global/M365/Viva Glint Tenant Admins
- references: https://learn.microsoft.com/viva/glint/copilot/mac-copilot-access, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=551197
Default ON Setting
All users with Glint permissions will have Copilot enabled by default, which may lead to unauthorized access or misuse of features.
- roles: Users with Glint permissions, Global/M365/Viva Glint Tenant Admins
- references: https://learn.microsoft.com/viva/glint/setup/copilot-privacy, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=551197
Centralized Management Complexity
The shift to VFAM for managing Copilot access may overwhelm IT teams if not properly prepared, leading to delays in access management.
- roles: IT Administrators, Compliance Teams
- references: https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=551197
Dynamic Group Management
Failure to configure dynamic Entra groups correctly may result in incorrect access levels for users, impacting productivity.
- roles: IT Administrators, Global/M365/Viva Glint Tenant Admins
- references: https://learn.microsoft.com/entra/identity/users/groups-create-rule, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=551197
Compliance and Governance Risks
Without proper governance reviews, organizations may face compliance risks related to data privacy and security when using Copilot.
- roles: Compliance Teams, IT Administrators
- references: https://learn.microsoft.com/viva/glint/setup/copilot-privacy, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=551197
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
Data Protection**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
Hypothetical Work Council Statement**
XXXXXXX ... paid membership only
DPIA Draft**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2026-02-27 | MC 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. https://learn.microsoft.com/viva/feature-access-management https://learn.microsoft.com/viva/glint/setup/copilot-faqs https://learn.microsoft.com/viva/glint/setup/copilot-privacy https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=551197 | Resources for AI Governance Review and Setup
AI Governance Fact Sheet: Comprehensive documentation addressing common questions from legal, privacy, security, and AI ethics committees, including data privacy protections, confidentiality thresholds, regulatory compliance (such as GDPR, EU AI Act), and responsible AI reviews. See Data, privacy, and security for Microsoft 365 Copilot in Viva Glint. Setup Instructions for Microsoft 365 Admin Center: Step-by-step guidance for configuring the three common access scenarios, including how to create custom policies, scope policies to Microsoft Entra groups, use Dynamic Entra Groups, and understand policy precedence. See Manage Viva Glint Copilot access in Microsoft 365 admin center 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. Compliance considerations: No compliance considerations identified, review as appropriate for your organization. https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#global-administrator https://learn.microsoft.com/entra/identity/users/groups-create-rule https://learn.microsoft.com/viva/glint/copilot/mac-copilot-access https://learn.microsoft.com/viva/glint/setup/copilot-privacy https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=551197 |
| 2026-02-27 | MC MessageTagNames | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact |
| 2026-02-27 | MC Summary | Viva Glint will default Copilot to ON and remove its internal toggles, using Viva Feature Access Management (VFAM) as the sole control for Copilot access starting March 2026. Admins must manage access via VFAM; users see Copilot by default if they have Glint permissions. No M365 Copilot license is needed. | Microsoft Viva Glint Copilot will default to ON and be managed exclusively via Viva Feature Access Management (VFAM) in Microsoft 365 admin center, aligning with enterprise AI governance. Existing Glint toggles will be removed. Rollout starts March 2026, completing by April 2026, with resources provided for setup and compliance. |
| 2026-02-27 | MC Last Updated | 01/27/2026 01:40:07 | 2026-02-27T00:19:05Z |
| 2026-02-27 | MC Messages | [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. | Updated February 26, 2026: We are extending the rollout timeline to give customers additional time to complete AI governance reviews and configure Viva Glint Copilot access policies in the Microsoft 365 admin center. We have also added additional content providing you with more resources and details surrounding this change. Thank you for your patience.
[Introduction] Copilot in Viva Glint will align with Microsoft's enterprise AI governance platform: enabling your IT and compliance teams to use centralized governance tools for access management and unified monitoring and reporting across all AI deployments in your tenant. 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 message is associated with Roadmap ID 551197. Why We're Making This Change to Copilot Access Management Aligns Viva Glint with Microsoft's enterprise AI governance platform: Managing Copilot access control with the Microsoft 365 admin center enables your IT and compliance teams to use centralized governance tools for access management and unified monitoring and reporting across all AI deployments in your tenant. This reduces governance complexity and audit burden by providing a single control plane for managing AI features across Microsoft 365. Dynamic Entra Groups for Automatic Access Management Dynamic Entra groups in the Microsoft 365 admin center automatically maintain Copilot access based on user attributes (department, location, job title, manager status). When VFAM policies are scoped to dynamic groups, membership updates automatically as employees join, leave, or change roles - eliminating manual policy maintenance. For more information, see Create or update a dynamic group in Microsoft Entra ID. Who can manage Viva Glint Copilot Access in M365 Admin Center Viva Glint Tenant Administrators AI Administrators Microsoft 365 Global Administrators Three Common Setup Scenarios for Viva Glint Copilot Access Control Administrators can configure Copilot access using one of three approaches: Scenario 1: Enable for all Viva Glint users (default) - The organization-wide setting is turned ON with no custom policies. All licensed users with appropriate Viva Glint permissions can access Copilot features. Scenario 2: Pilot mode with specific groups - The organization-wide setting is turned OFF, and custom policies enable Copilot only for selected Microsoft Entra groups (for example, HR team, senior leadership). This approach supports phased rollouts or limited pilots before broader enablement. Scenario 3: Broad enablement with exclusions - The organization-wide setting is turned ON, and custom policies disable Copilot for specific Microsoft Entra groups (for example, users in regions pending works council approval). All other users have access by default. [When this will happen:] General Availability (Worldwide): Rollout will begin in early March 2026 and is expected to complete by the end of April 2026 (previously late March 2026). |
| 2026-02-27 | MC How Affect | 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 | 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: Manage Viva Glint Copilot access in Microsoft 365 admin center. 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. 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 Workplace 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 refer to: Data, privacy, and security compliance for Microsoft 365 Copilot in Viva Glint |
| 2026-02-27 | MC Title | Microsoft Viva Glint: Copilot will default to ON and move to VFAM as the single control | (Updated) Microsoft Viva Glint: Copilot will default to ON and move to VFAM as the single control |
| 2026-02-27 | MC End Time | 05/02/2026 09:00:00 | 2026-06-01T09:00:00Z |
Last updated 2 days ago ago
