Blog Post

Education Blog
4 MIN READ

Microsoft 365 Copilot Chat for Students 13+

jseghersMSFT's avatar
jseghersMSFT
Icon for Microsoft rankMicrosoft
May 12, 2025

What Admins Need to Know Now

With Microsoft 365 Copilot Chat coming to students aged 13 and older this summer, we’re ushering in a new era of AI-assisted learning while maintaining a strong focus on privacy, security, and keeping administrators in control. This blog post is your admin-ready guide to ensure your organization is set up to deliver safe, compliant, and productive experiences with Copilot Chat.

Learn more and hear from K-12 institutions who participated in our private preview in today’s announcement: Empowering teen students to achieve more with Copilot Chat and Microsoft 365 Copilot

Copilot Chat is an AI-powered assistant, offered with Microsoft 365, that helps users find answers, generate insights, and complete tasks—drawing from web-based content and, publicly available information, and limited user file uploads. Unlike Microsoft 365 Copilot, it does not have access to organizational data like emails, documents, or meetings through the Microsoft Graph. This version is ideal for institutions who are looking for a free AI chat solution while maintaining a strict boundary from internal or sensitive data sources. Review an overview of AI solutions from Microsoft Education: aka.ms/EducationAIPortfolio

 

🏷️ Tenant Identifier: Set the Education Segment for Proper Feature Access

We recommend all Education customers take additional steps to manage appropriate deployment:

  • Validate your school type as Higher education, Primary/Secondary/K-12, or Other (research institution, academic library, etc.) to help us tailor the search and chat experience for your users.
  • To do this, you will need a PowerShell script: ConfigureTenantEduType.ps1 that you can download here.
  • To run the script, open PowerShell in administrator mode. Also make sure you have the username and password available of a global administrator on your tenant. On your first run, the necessary packages will be installed, hence the administrator mode.
  • Usage:
    • .\ConfigureTenantEduType.ps1 - When no parameter is used the actual setting of the tenant will be retrieved.
    • .\ConfigureTenantEduType.ps1 1 - This sets the tenant identifier to K-12
    • .\ConfigureTenantEduType.ps1 2 - This sets the tenant identifier to HED.
    • .\ConfigureTenantEduType.ps1 3 - This sets the tenant identifier to other.

📘 Please read our Managing Copilot Chat access for Faculty and Higher Education 18+ student | Microsoft Community Hub for full details.

 

✅ Why AgeGroup Matters—and How to Set It

To enable Microsoft 365 Copilot Chat for students, the ageGroup attribute in Entra ID (formerly Azure AD) must be set correctly. This field ensures compliance with child privacy regulations like COPPA and FERPA by verifying whether a user is under 18.

Here’s how to check and set it:

  • Use Microsoft Graph API or Microsoft Entra Admin Center to view and update the ageGroup attribute.
  • Acceptable values: Minor, NotAdult, Adult
  • For students aged 13 and up, use NotAdult. Any student set to NotAdult will have access to Microsoft 365 Copilot Chat.
  • Use bulk update tools or provisioning solutions to automate setting this for all student accounts.

📘 Please read our AgeGroup blog post for full details.

 

🛠️ Managing Agents in Microsoft 365 Admin Center

Copilot now supports agent-based AI experiences that can be scoped, customized, and secured. With the Microsoft 365 admin center, you can:

  • Enable/disable Copilot features for specific user groups
  • Manage access to custom Copilot agents
  • Use the Copilot Control System to monitor usage and enforce security policies from day one

To learn more, check out the Manage agents for Microsoft 365 Copilot in Integrated Apps - Microsoft 365 admin | Microsoft Learn and leverage the Agent Success Kit – Microsoft Adoption

 

🔐 Security and Data Protection You Can Trust

  • Copilot Chat brings the same enterprise-grade security and compliance protections you've come to expect from Microsoft 365. As a part of this enterprise data protection your data stays private (we won’t use your data except as you instruct) and your data isn’t used to train foundation models.  Learn more about enterprise data protection. Highlights include:
  • Built-in data residency and encryption
  • Access controls and permission-based data retrieval
  • Protection from prompt injection and harmful content
  • Advanced reporting on readiness, usage, and security posture

One important consideration: Copilot does not change or override your existing permissions model. It respects the access a user already has in Microsoft 365—whether that’s to files, emails, chats, or other content. However, this also means that if a document is overshared or accessible more broadly than intended, Copilot may surface its content to anyone with permission to see it.

Access to the content is not caused by Copilot—it’s visibility and access that already exists in your tenant. Copilot simply makes that visibility more transparent. Admins should review and remediate over-permissioned content using tools like Microsoft Purview, SharePoint access reviews, or sensitivity labels to avoid unintended exposure of sensitive data.

Administrators can go further by using features like SharePoint Advanced Management, sensitivity labels, and Restricted SharePoint Search.

 

🔍 Next Steps

  • 🏷️ Set your tenant’s education segment (K-12/HED/Other)
  • ✅ Audit and update ageGroup attributes.
  • 🛠️ Configure Microsoft 365 Admin Center to have the right settings for Agents creation and consumption.
  • 🔐 Review your security and data protection settings for Copilot.
  • ⚙️ Explore the Microsoft 365 Copilot technical readiness guide. Microsoft 365 Copilot Chat – Microsoft Adoption

With these steps, you’re not just enabling Copilot—you’re empowering safer, smarter learning with AI.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Updated Jun 17, 2025
Version 2.0

7 Comments

  • Tefty's avatar
    Tefty
    Copper Contributor

    The new downloaded script firstly is named wrong and needs renaming + the file extension changing from PS to PS1. Secondly I had to adapt the Connect-AZACCOUNT to add my tenants ID due to me being a GA with MFA (as it should be per security bla bla bla).

    Lastly getting a 403 error now while trying to output our current setup results and setting a new one with the -eduType 1 switch. Whether its worth noting, I am a UK school.

    In short - Not really working at the moment!

    • Paul_D's avatar
      Paul_D
      Copper Contributor

      I also getting the 403 error using the new script file. Below is the beginning part of the error.

       

      [ERROR] The remote server returned an error: (403) Forbidden.
      Set-Tenant-EduType : Error while trying to set tenant's Copilot EduType classification. Please re-run the script or
      contact support.

  • Curtis's avatar
    Curtis
    Copper Contributor

    ConfigureTenantEduType.ps1 script is failing for us with:

    Tried on multiple computers and 2x different GA accounts.

    _____________________________________________________________

    Fetching tenant's Copilot EduType classification...
    StatusCode: 500                                                                                                         
    StatusDescription:
    [ERROR] Response status code does not indicate success: 500 (Internal Server Error).
    Write-Error: C:\Scripts\ConfigureTenantEduType.ps1:222:16
    Line |
     222 |          $res = Get-Tenant-EduType $token.Token
         |                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         | Error while trying to get tenant's Copilot EduType classification. Please re-run the script or contact support.

    • Paul_D's avatar
      Paul_D
      Copper Contributor

      I get this error too with 2 different GA accounts, has anyone managed to set their tenant Edu Type?

      • Curtis's avatar
        Curtis
        Copper Contributor

        Looks like they just updated the script to "v2" as of June 12th and now it is working for me.

  • JonKilner's avatar
    JonKilner
    Brass Contributor

    We previously disabled Copilot for students by using the CNAME redirection/HTTP header injection, followed up by setting our tenant to K12. My understanding was that this would block sign-in to Copilot for users assigned a M365 for Students license, but allow sign-in for users assigned M365 for Staff licenses. 

    We don't currently use/set the ageGroup attribute.

    How does the change referenced in this blog impact our current setup? If we want to continue blocking all student access (including ages 13+) to Copilot, do we need to start applying the ageGroup attribute to all our users. Or will our students still be blocked from signing into Copilot?