The core technical point is straightforward: this is not an unavoidable limitation of Microsoft Teams. Microsoft 365 administrators can apply retention policies that retain, delete, or retain-then-delete Teams content. Ontario has apparently chosen a short deletion rule for chats, while directing staff to preserve anything worth keeping by taking a screenshot or copying the text into a document. That makes the question less about Teams as a platform than about whether the province’s recordkeeping process can reliably separate disposable conversation from decisions that the public, a court, or investigators may later need to examine.
Global reported that an Ontario policy titled “Record guidance for Microsoft Teams” says chats are deleted automatically after 30 days and “cannot be retrieved” after that point. The outlet also reported that the May order to halt freedom-of-information processing was delivered through a cross-ministry Teams group chat, despite repeated requests from civil servants to receive the instruction by email. They were told no email would follow.
For Windows administrators, the case is a familiar compliance failure mode: a collaboration platform may be approved, secured, and operationally useful while still becoming a poor system of record for decisions with legal or public-accountability consequences. Approval to use Teams is not the same thing as a defensible retention strategy.
A 30-day Teams rule is an administrative choice
Microsoft’s Purview retention controls allow an organization to apply distinct policies to Teams chats and channel messages. Those policies can preserve content for a defined period, delete it after a defined period, or do both in sequence. A tenant can also use retention holds and eDiscovery workflows when litigation, investigations, audits, or access-to-information obligations require material to remain available.
Ontario’s reported 30-day setting therefore should not be described as Teams “automatically” deleting government conversations by default. The deletion is automatic under the government’s own policy. That distinction matters in a procurement and governance sense: the platform has the capability to retain content, while the tenant owner decides whether the records remain accessible.
The Ministry of Public and Business Service Delivery and Procurement previously told Global News that Teams is an approved enterprise collaboration platform that meets the Ontario Public Service’s information-management and security requirements. That statement may be true as a description of the platform’s approved status, but it does not resolve whether a 30-day deletion schedule is appropriate for every type of government communication conducted on it.
A secure service can still be configured in a way that weakens later reconstruction of an important decision. Encryption, multifactor authentication, device management and access controls answer one set of risks. Retention, classification, legal hold and records capture answer another.
The province has not publicly explained why its Teams chat retention window is 30 days, whether the policy covers all chat types equally, or whether copies are preserved in an archive inaccessible to ordinary users. Global’s account says the internal guidance tells staff chats cannot be retrieved after the retention period. Without a provincial explanation of how legal holds, audits, active freedom-of-information requests and investigations are handled, the practical scope of that claim remains unclear.
Screenshots are a weak substitute for a system of record
The guidance reported by Global News offers two methods for retaining a Teams conversation longer than 30 days: capture it in a screenshot or copy it to a text document. Both can preserve words on a screen. Neither is equivalent to retaining the original Teams record in a managed repository.
A screenshot may omit messages above or below the visible window, conceal the broader conversation, lose searchable text, and fail to show edits, reactions, attachments, membership changes or timestamps in a usable form. Copying text into a document can be better for searchability, but it too can strip away context and metadata unless staff take deliberate steps to preserve them. Either approach also makes preservation dependent on an individual employee recognizing, in real time, that a chat has business value.
That is an unusually fragile control for government decisions. The risk is not merely that staff behave badly. People are busy, chat moves quickly, and the significance of a message often becomes clear only weeks or months later—after a controversy, an appeal, a lawsuit, a public inquiry, or a freedom-of-information request.
Ontario’s Archives and Recordkeeping Act requires public bodies to maintain records schedules that specify how long classes of public records are retained and what happens to them afterward. The province’s own information-management material also says that recordkeeping duties apply to information in all formats. In other words, moving an instruction from an email inbox into a Teams chat does not determine whether it is a record; the content and business purpose do.
The policy challenge is to distinguish transitory messages—routine coordination, duplicate notifications, scheduling and informal exchanges—from messages that document a decision, direction, commitment, rationale or operational action. A blanket 30-day purge can be defensible for genuinely transitory chat only if the organization has a dependable method for capturing the non-transitory material elsewhere before it disappears.
The reported guidance places that burden at the desktop level. It asks the person who sees the message to create a secondary copy. A better design would classify and preserve official decision channels by default, with clear procedures for when chats create records and with retention labels or automated capture where feasible.
The FOI freeze made the retention setting a public issue
The May 2026 freedom-of-information pause turned what might otherwise have been an internal IT governance detail into a transparency issue. Global reported that the freeze followed the April 24 Royal Assent of Bill 97, Ontario’s budget legislation, which amended the province’s access-to-information framework.
The enacted changes excluded records in the custody of ministers, ministers’ offices, parliamentary assistants and their offices from the provincial freedom-of-information law. The Information and Privacy Commissioner of Ontario has separately published updated guidance reflecting changes to the law, including a longer general response timeline for many requests: 45 business days for requests received on or after July 1, 2026.
The sequence matters. On May 14, according to Global’s earlier reporting, senior staff responsible for access requests were told in Teams to stop key parts of their work, including releasing records and advancing requests for approval or disclosure. The pause lasted until May 22. The Information and Privacy Commissioner had not been notified of the freeze before learning of it through news reports, according to the commissioner’s spokesperson quoted by Global.
Civil servants’ reported insistence on receiving an email was therefore more than a preference for a familiar format. They appeared to be seeking a stable, attributable record of a direction to stop statutory work. The answer—“There won’t be anything coming in email,” according to the chat messages published by Global—looks worse now that the province’s own Teams guidance reportedly treats chat as material that will vanish after one month unless someone intervenes.
There is no evidence in Global’s reporting that the May chat was allowed to disappear. In fact, the outlet obtained and published portions of the exchange. Nor does a short retention policy itself prove that officials selected Teams to evade disclosure. It does, however, establish a preventable governance gap: the province relied on a short-lived communication channel for an instruction that affected access to public records across government.
What Ontario needs to disclose
The government can resolve much of the uncertainty without exposing sensitive content. It should publish the scope of its Teams retention policy: whether it applies to one-to-one chats, group chats, meeting chats and channel posts; whether it covers attachments and shared files; whether messages subject to active access requests are preserved; and who has authority to place a hold on relevant material.
It should also explain the workflow staff must follow when Teams conversations contain directions, decisions or other records of business value. “Take a screenshot” is advice, not an auditable lifecycle-management system. A defensible policy needs defined repositories, employee training, managerial oversight, retention schedules, and evidence that preservation occurred.
For enterprise IT teams outside government, Ontario’s experience is a useful warning against treating retention as a storage-cost setting. Teams is where many organizations now make operational decisions. If chat deletes on a fixed timetable while email, SharePoint, ticketing systems and document repositories retain material for years, employees will naturally develop inconsistent and hard-to-defend habits about where official work belongs.
The immediate consequence for Ontario is sharper. Its government has narrowed public access to ministerial records, paused access work during the transition, and now faces questions about a chat policy that can erase internal conversations after 30 days. The province does not need to keep every casual Teams exchange forever. But it does need a verifiable way to ensure that messages documenting government decisions survive longer than the chat window in which they were made.