Microsoft has quietly penciled a long-awaited feature into its 365 roadmap: the ability for educators to attach different resources, instructions, or attachments to separate groups of students inside a single Teams for Education assignment. The change, identified as roadmap item 568369 and currently in development, is targeted for general availability in September 2026 across web, desktop, iOS, and Android clients in the standard multi-tenant cloud.

For teachers who have been managing differentiated instruction by cloning the same assignment multiple times—once for each learning tier—the update promises to unify what is substantively one activity under one gradebook entry while allowing material to vary by student group.

The Core of the Update

Currently, when a teacher wants to provide advanced reading to one group and scaffolded worksheets to another within the same class, they must create entirely separate assignments. Each copy carries its own due date, submission flow, and grading column, bloating the Assignments tab and doubling the administrative overhead.

Roadmap item 568369 changes the paradigm. After the update, an educator will be able to designate existing Individual Groups—defined in the class team—and then map specific resources, directions, and attachments to each group. A single assignment will present different material depending on group membership, while keeping the due date, submission workflow, and gradebook entry unified.

Microsoft says students will only see the content mapped to their own group. Before publishing, teachers will get a clear preview of the group-to-content mapping, reducing the risk of accidentally releasing the wrong materials.

Crucially, the feature is not a new authoring surface or submission type. It layers differentiation on top of the existing assignment resource workflows. A teacher builds an assignment as they always have—writing instructions, attaching files, linking Learning Accelerators—but now adds a permission layer that controls which group sees which piece. That means existing training, templates, and grading rubrics remain valid.

What This Means for Teachers and Students

The practical upside is most visible in blended-ability classrooms. Instead of a teacher juggling three assignment variants with three due-date reminders, they publish one assignment that acts as a container. The container holds the shared components (a core prompt, a due date, a rubric) and the differentiated pieces (extension articles for high achievers, graphic organizers for English language learners, audiovisual instructions for struggling readers).

Students get a cleaner view: their Assignments tab shows a single task, not a menu of confusing duplicates. And because submission and grading are unchanged, educators can provide unified feedback or even use rubrics that apply across groups.

For IT administrators, the immediate impact is modest. The feature does not introduce new admin controls or policy scopes, at least not as described in the initial roadmap entry. It works within the existing Groups infrastructure. However, admins who support large-scale differentiated instruction initiatives may want to audit current practices: identifying teachers who regularly clone assignments will help target early adoption when the feature hits preview.

The Road to Differentiation

The gap this feature fills is not new. Differentiated instruction—varying content, process, or product based on learner readiness—has been a pillar of special education and inclusive pedagogy for decades. Most learning management systems offer some form of conditional release or group-based resource visibility, but Teams for Education has lagged.

Teachers built workarounds: cloning assignments, maintaining separate class notebooks with tiered materials, or even creating separate class teams—an administrative headache that fragments data and complicates communication.

Microsoft’s education engineering group has been steadily adding differentiation features. Recent years brought Reading Progress, Reflect check-ins, and assignment categories. But the ability to vary resources within a single assignment was a conspicuous hole. Roadmap item 568369 plugs it without reinventing the assignment model.

What to Do Now—and What to Watch

Roadmap timelines are intentions, not guarantees. The September 2026 target may slip or the feature may change. But there are concrete steps schools can take today:

  • Identify power cloners: Work with department heads to find teachers currently creating multiple assignment copies for differentiation. They will be the natural pilot users once the feature appears in Public Preview.
  • Review group structures: The feature relies on Individual Groups within class teams. Ensure those groups are being used and are named consistently (e.g., “Red Group,” “Blue Group”) so mapping will be intuitive.
  • Stay informed: Monitor the Microsoft 365 Roadmap, the Teams for Education blog, and the Microsoft Education community for preview announcements. IT admins can set up roadmap alerts for item 568369.
  • Manage expectations: Let teachers know a solution is on the horizon but avoid promising a specific launch date until Microsoft confirms a preview.

A few unknowns remain. Microsoft has not published screenshots, so the mapping interface could range from a simple picklist to a more complex matrix. There is no word yet on whether the feature will require a specific Teams for Education license (most likely an A3 or A5 subscription, but that’s speculation). And it’s unclear how group mapping will interact with assignment reuse across classes or with third-party LMS integrations.

Still, the direction is clear. By 2027, the workflow of duplicating assignments for different learners may look as outdated as taking attendance on paper.