Microsoft is preparing a significant update for education tenants that will break down AI feature controls into distinct levers for educators and learners. According to a roadmap entry published in late July 2025, Microsoft 365 admins will gain the ability to enable or disable Learning Activities for educators and for students aged 13 and older independently, while the Teach experience can be toggled on or off for educators. The change targets the Microsoft 365 admin center and is penciled in for general availability in September 2026.
That deadline gives K-12 districts and higher education institutions more than a year to map out who should have access to what—and to verify that the administrative scaffolding around student accounts is ready for the switch.
What Actually Changed: The New Toggle Layout
Today, both Learning Activities and Teach are available as part of Microsoft 365 Copilot for education tenants. Microsoft Learn documentation describes the two experiences as enabled by default at the broad organization level, with only a single control to turn everything on or off. Starting in September 2026, that binary lever splits into three independent switches inside the web-based Microsoft 365 admin center.
The new layout, described under roadmap ID 568370, introduces:
- Learning Activities – Educators: Toggle that grants or blocks access for teachers and staff.
- Learning Activities – Students 13+: Toggle that applies only to learners who meet the age requirement.
- Teach – Educators: Toggle that governs the educator-facing section of the Microsoft 365 Copilot app, covering lesson plans, quizzes, rubrics, and other instructional materials.
Because each toggle operates independently, IT departments can phase adoption. For example, a school might let teachers experiment with Teach for a semester while holding back student access to Learning Activities—or they could permit all instructional staff to use both tools but keep students out until training is complete. The model replaces a blunt instrument with a set of precise dials.
Why This Matters for K-12 and Higher Ed
Classroom technology rollouts rarely work as “turn it on and walk away.” Teachers need time to learn new tools; students need clear rules and safeguards; parent consent forms often drive policy. A single switch that enables everything at once forces a district to say “yes” to the entire package or “no” to everything—an unworkable choice for communities that want AI assistance for lesson planning but want to evaluate how students interact with generative features before flipping the switch.
The separate controls let education teams stage AI adoption around their own readiness calendar, not Microsoft’s default settings. Administrators can match each toggle to a phase: initial pilot with volunteers, controlled expansion to all faculty, and only later student access after age verification and parent communication are complete. This granularity also aids compliance with local policies that may treat educator tools and student-facing services differently under data-handling rules.
The Age Restriction and Its Ripple Effects
Microsoft has drawn a clear line: student access to Learning Activities is limited to users aged 13 or older. The company does not offer a way for K-12 tenants to lower that floor for learners under 13, even with parental consent configured inside the tenant. For primary and middle schools, that effectively means Learning Activities is off the table for most pupils.
This makes student identity data suddenly urgent. If a tenant has not properly populated birth dates or age-group attributes, the toggle for “Students 13+” could behave unpredictably—granting access to some who should be blocked, or blocking users who are older but misclassified. Microsoft’s documentation does not specify how the system resolves ambiguous or missing age data, so administrators should treat the intervening months as an opportunity to scrub directory records and test age-boundary behavior before the new controls arrive.
Creating vs. Consuming: A Policy Headache You Can’t Ignore
There is a second distinction buried in the support documentation that changes how districts will write internal policies. Students can use a Learning Activity that an educator has already created and shared, even if the student does not have a Copilot Chat license. But creating an activity requires Copilot Chat.
That operational split means a teacher who does not have a Copilot Chat license cannot generate fresh flashcards or interactive study material themselves. If the teacher’s account is licensed for Copilot Chat and Teach is enabled, they can build activities and push them to students—who can then engage with the materials regardless of their own licensing status.
For IT admins, this has immediate licensing implications:
- Identify which educators need Copilot Chat so they can originate content.
- Map student consumption separately; if students only consume, licensing costs might stay flat.
- Communicate clearly that “students can access activities” does not mean “students can create activities.”
Policy decisions around parental consent, training, and classroom support will need to account for this creator-consumer divide. A school that believes it is “enabling AI for students” by turning on the toggle may inadvertently introduce a tool that students cannot fully use unless additional licenses—or permissions—are in place.
How We Got Here: The Gradual Infusion of AI into Classrooms
Copilot for Microsoft 365 launched in November 2023, and education-specific features have steadily trickled out since. By early 2025, Learning Activities and Teach were available inside the Copilot app, but they followed the same pattern as most enterprise Copilot features: the organization either had Copilot or it didn’t, and little in between.
Feedback from schools consistently flagged the all-or-nothing model as a barrier. Administrators wanted to greenlight AI for lesson planning but pause student-facing tools until their communities caught up—a capability that generic Copilot licensing never provided. The roadmap item 568370 is Microsoft’s direct response to that feedback, giving IT teams the “per-feature” controls that have already become standard in other parts of Microsoft 365, such as Teams policy packages.
The September 2026 target suggests Microsoft is treating this change as a deliberate, engineered release rather than a rushed toggle. It also aligns with typical school procurement and planning cycles: a feature landing right before the 2026-2027 academic year gives districts a full school year to pilot and adjust.
What Should IT Admins Do Right Now?
The feature is not available yet, and Microsoft’s roadmap dates are targets—not guaranteed delivery dates. Still, a 14-month runway is enough to get the administrative pieces in place. Education IT teams can start with five concrete steps:
-
Inventory existing Copilot licenses and assignments. Know precisely which faculty and staff already have Copilot Chat. Cross-reference with those who would benefit from creating Learning Activities, so you can budget for additional licenses if necessary.
-
Verify student age attributes. If your tenant uses Azure AD (Microsoft Entra ID), check that birth date or age-group fields are populated for every student. For hybrid environments with on-premises sync, run a delta report to catch mismatches. Any student whose age is missing or ambiguous could face access errors when the new toggle is activated.
-
Decide on a rollout phasing now, not later. Draft a simple matrix: which groups get Teach first? Which groups get Learning Activities and when? Write that into a timeline so you can communicate it to principals and department heads before September 2026.
-
Align Copilot policies with the new controls early. Review existing Copilot administration settings in the Microsoft 365 admin center. Even if the new toggles are not visible yet, confirm that your broader Copilot policy (on/off, app-level permissions) does not conflict with the future granular switches. For example, if Copilot Chat is globally turned off for students, the Learning Activities toggle won’t override that; the most restrictive setting wins.
-
Prepare communication and training templates. Teachers will ask what Teach does, how it differs from Learning Activities, and who is allowed to use each. Prepare one-pagers, FAQs, and training session outlines now so you are not scrambling in August 2026.
What to Watch Next
The September 2026 release applies to web-based Microsoft 365 admin center in standard multi-tenant environments. Government clouds, education-specific sovereign clouds, and other specialized installs often follow later. No date has been published for those variants, but past Copilot rollouts suggest a 3-6 month lag.
Administrators should also monitor whether Microsoft extends the age boundary downward, perhaps with additional parental consent flows. For now, the 13-year-old cutoff is firm. Watch for signals in subsequent roadmap items or Microsoft Learn updates that hint at expansion to younger learners.
Beyond the immediate toggles, the move signals a broader shift: education AI features are being decoupled from the monolithic Copilot umbrella. That decoupling could eventually bring per-feature controls to other Copilot experiences—inside Word, PowerPoint, and Teams—that schools want to manage with the same surgical precision Microsoft is now giving to Learning Activities and Teach.