St. Mary’s County Public Schools in Maryland has quietly launched a closely managed version of Microsoft Copilot, locking down access with a strict set of rules that bar the use of AI for grading, discipline, or performance evaluations. The rollout, which began with administrative staff on July 1, 2026, will give teachers access on January 1, 2027—halfway through the school year—and students later in 2027.

The deployment is paired with a district-wide AI-use policy adopted on June 24, 2026, after the Maryland General Assembly mandated that all school systems create such guidelines in line with state education department standards. The policy, described in a Southern Maryland News report, requires all staff to complete district-approved training before using Copilot, labels any AI-generated instructional material, and forbids entering sensitive data into the tool without explicit authorization.

Superintendent J. Scott Smith disclosed the timeline during a Board of Education meeting, and Melissa Evans, administrative assistant to the superintendent, emphasized that the goal is to “enhance human thinking, never replace it.” The district tapped a “closed enterprise version” of Microsoft Copilot, according to Will Buckmaster, Supervisor of Information Technology, citing data-protection controls and useful integrations.

A Chained AI: What’s Different About This Deployment

Unlike students or teachers downloading the consumer version of Copilot, the St. Mary’s implementation runs entirely within the district’s Microsoft 365 tenant. That means the tool inherits the organization’s identity, access, and data governance policies. The “closed” descriptor refers to data isolation: prompts and outputs stay inside the district’s controlled environment rather than feeding into public models.

But Buckmaster’s mention of “data-protection controls” does not mean it’s plug-and-play secure. In practice, an enterprise Copilot deployment is only as tight as the tenant configuration. IT staff must still:
- Restrict which data connectors Copilot can pull from (e.g., SharePoint, OneDrive, email)
- Set role-based access so that, for example, a teacher cannot query HR files
- Configure retention and audit logs to track how the AI is being used
- Ensure compliance with the Family Educational Rights and Privacy Act (FERPA) and other student-data regulations

Because St. Mary’s is rolling out in phases, the IT team has months to test and harden these settings before teachers and students come onboard—a luxury many rushed AI deployments lack.

The Policy: What Staff and Students Can—and Can’t—Do

The board’s policy creates bright lines around acceptable use. For staff, the standout prohibition is the ban on using AI “to make critical professional or educational decisions.” Specifically, the policy says no AI-generated grade, no AI-driven disciplinary action, and no AI-based performance evaluation. This squarely addresses the fear that algorithms would short-circuit human judgement in high-stakes moments.

Other staff requirements:
- Label AI content: Instructional materials created or significantly altered by Copilot must be identified as such.
- Train first: No staff member may touch the tool for classroom or administrative tasks before finishing district training.
- Teach ethics: Staff are expected to instruct students on ethical AI use and monitor student use.
- Data hygiene: Entering personally identifiable student information or other sensitive data without authorization is off-limits.

Students will eventually get Copilot access, but not until at least the latter half of 2027. When they do, the policy binds them to:
- Disclose any AI-generated content in assignments
- Never use Copilot for plagiarism or falsifying work
- Avoid any discriminatory or harmful use

These rules mirror emerging frameworks across the U.S., but St. Mary’s is arguably more prescriptive than many districts by outright forbidding AI-aided grading—a practice that some educators view as a time-saver.

What It Means for You: Educators, IT Staff, and Families

The January 2027 teacher launch lands right after winter break, with the school year already two quarters in. That odd calendar placement suggests the district is prioritizing IT readiness over instructional convenience. Teachers will get Copilot midway through a term, which means they’ll need to integrate it into existing lesson plans on the fly. Because the tool runs inside the familiar Microsoft 365 environment—Word, PowerPoint, Teams, Outlook—the learning curve will be modest, but the training requirement cannot be skipped.

Early use cases are likely to be low-risk: drafting emails, summarizing meeting notes, generating discussion prompts, adapting reading materials for different proficiency levels. The human-review mandate means every Copilot output gets a human sanity check, a step that the district believes aligns with its “human-centered AI” ethos.

For district IT staff, the immediate burden is not the chatbot itself but the surrounding scaffolding. Priorities include:
- Data boundary enforcement: Verify that Copilot cannot access sensitive staff or student records by misapplying permissions.
- Auditing and reporting: Turn on Microsoft Purview or equivalent logging to capture prompts and outputs, ensuring policy violations can be detected.
- User provisioning: Roll out access in waves, perhaps by school or department, to avoid a support bottleneck.
- Ongoing training: Document how staff should report issues and where to find approved use cases.

Windows administrators elsewhere should note: this deployment is built on the same Microsoft 365 E3/E5 licensing and Microsoft Copilot for Microsoft 365 setup that any enterprise can purchase. The difference is the policy layer. St. Mary’s shows that a “closed” enterprise Copilot is not a product you buy but a process you configure.

For families and community members, the most reassuring element may be the ban on high-stakes decision-making. Grades and discipline remain in human hands. Still, parents should watch for how teachers label AI-generated materials and whether students understand disclosure rules. The district has yet to announce specific parent-facing communication, but the policy’s ethical-use instruction for students implies classroom discussions will happen.

How We Got Here

The trigger for the policy was House Bill 1234 (or a similar Maryland General Assembly act, per the district’s statement) requiring local school systems to adopt AI policies consistent with Maryland State Department of Education guidance. That law dropped in 2025 or early 2026, giving districts a tight window to comply.

St. Mary’s chose Microsoft Copilot for two reasons: the district was already heavily invested in Microsoft 365, and the enterprise version promised data residency and compliance controls. Buckmaster’s reference to “useful integrations” likely means Copilot’s ability to ground answers in organizational data—pulling facts from internal documents rather than the open web—which is attractive for K-12 environments where accuracy and proprietary content matter.

The phased timeline reflects a deliberate, risk-averse posture. Administrative staff got first access on July 1, 2026, which is the start of the fiscal year and a time when many central-office employees are planning for the fall. By the time teachers log in on January 1, 2027, the IT department will have five months of real-world usage data to identify glitches, permission holes, or training gaps before the tool hits the classroom.

Student access remains the most ambiguous deadline. Smith said “next year,” which in context means sometime during the 2027-2028 school year. That vagueness gives the district room to evaluate how the staff rollout unfolds.

What to Do Now: Actionable Steps

If you’re a St. Mary’s teacher or administrator, the near-term checklist is straightforward:
1. Watch for training announcements: The district has not publicized the exact training format, but it will be required before you can use Copilot. Expect a module or workshop in fall 2026 or early winter.
2. Review the AI-use policy: Download it from the district’s board-docs site, read the student and staff duties sections, and note the data rules. If anything is unclear, ask your department head.
3. Prepare your digital environment: If you store curriculum, lesson plans, or student work in SharePoint or OneDrive, now is a good time to audit permissions. Copilot can amplify access problems—a file shared too broadly could suddenly be surfaced by a colleague’s prompt.
4. Plan low-stakes pilots: Think of one generative task—writing a newsletter blurb, creating a vocabulary list, summarizing a research article—that you’d like to test once access opens. Keep the output for your review only, and label it as AI-assisted.

For IT teams in other school districts watching St. Mary’s, this rollout offers a template:
- Start with a policy, not a product. The board adopted rules before the first admin logged in. That avoids the rush to retroactively govern a tool already in the wild.
- Phase by role, not by school. Admin → teachers → students ensures each group’s needs and risks are addressed before the next wave.
- Enterprise Copilot is a configuration project, not an app install. Budget time for data-mapping exercises, permission reviews, and pilot testing with small groups of users.
- Training must be hands-on and role-specific. Generic AI ethics videos won’t cut it. Teachers need to see how Copilot behaves inside Teams or Word; admins need to understand prompt sanitization.

Outlook

St. Mary’s has set a deliberate pace, but the clock is ticking. The 2027-2028 school year, when student access is promised, will bring a new wave of policy enforcement and potential parent scrutiny. The district will also have to decide whether to extend the AI-use policy to cover newer Copilot features—Microsoft is steadily adding agents, plugins, and deeper data connectors. Each of those could pierce the “closed” boundary if not managed carefully.

For now, the message from St. Mary’s is clear: AI can assist, but it doesn’t get to judge. That principle, written into board policy, may become a model for districts navigating the same tightrope between innovation and accountability.