The short answer

Older Teams retention policies stop covering Copilot from mid-January 2027.

Some older Teams retention policies also keep or delete Copilot chats, even for staff who never use Teams.

Microsoft's notice says that ends in a rollout that starts in mid-January 2027. Teams content keeps the rules it has now.

So Copilot data your firm meant to delete, or meant to keep, no longer follows the rule the firm set.

Before mid-January, have whoever runs your security program and your IT administrator check which policy covers Copilot.

Then search once to see what the firm actually holds.

What the notice actually says

The notice is short. Older Teams retention policies that also cover Copilot will cover Teams alone once the rollout ends.

§

MC1481313 and Microsoft's retention page

+

The new dates. Microsoft now lists the rollout as starting in mid-January 2027 and finishing by the end of January 2027. The source is Message Center post MC1481313, version 2, last updated October 28, 2026. We read it on the third-party mirror mc.merill.net, so confirm it in your own Message Center.

What changes. Some older Microsoft Teams retention policies also apply to Microsoft 365 Copilot interactions. After the rollout, those policies apply only to Teams data and no longer cover Copilot. Retention for Teams content itself stays the same.

Why the two were joined. Microsoft's own retention page for Copilot explains it. Copilot messages sat in the same Teams location "because they were retained and deleted by using the same mechanisms." The page adds: "Users didn't have to be using Teams for the retention policy to apply to Copilot." It then says Copilot retention is "now separate from Teams chats."

What that means for a firm. A firm may have built one policy years ago and called it a Teams policy. Without anyone noticing, it may have been governing Copilot prompts and responses too, and users didn't need to use Teams for that to be true.

Who this reaches. A firm that created a retention policy using the older location named Teams chats and Copilot interactions, and has Copilot in use. A firm that never set a retention policy for Teams isn't changed by this notice. It also never had a retention rule for Copilot, which is a separate gap worth knowing about.

Who it does not reach the same way. Microsoft's page says permanent deletion is suspended when a mailbox is under Litigation Hold, a delay hold, or an eDiscovery hold. A hold placed for a matter or an investigation works through a different mechanism. This notice is about retention policies, not holds, so keep the two apart when someone at the firm says "we are covered."

What the notice leaves out. It describes the change to older Teams policies. It doesn't say what Microsoft does with Copilot data that no longer sits under any policy. We couldn't find that stated in either source, so we won't guess.

The change can break in two directions

A retention policy can keep data for a set time, delete it after a set time, or both. Most firms set it for one reason and forget the other, and the January change can break either one.

§

Keeping and deleting

+

If your policy was there to delete. Some firms set a Teams policy to clear chat history after a period, to limit what sits in the firm's Microsoft 365. If that policy was also clearing Copilot prompts and responses, it stops doing so in January. Client names, figures and notes that staff pasted into Copilot are no longer on the deletion schedule the firm thought it had.

If your policy was there to keep. Other firms set a policy to keep chat for a period, because they wanted a record of client communication or of how work was done. If that policy was also keeping Copilot interactions, it stops in January. The firm may believe it can reconstruct how an AI tool was used on a client file, but the policy it relied on no longer covers that record.

Why this is easy to miss. Both outcomes happen without an error, a banner, or a changed setting in the policy the firm built. The policy still exists under the same name, but it covers less than it did.

What the screen shows is not the record

Staff often check retention by looking at the app. If an old Copilot chat is still on screen, they assume it's kept, and if it's gone, they assume it's deleted. Microsoft's own page says that reasoning doesn't hold.

§

What Microsoft's page says about the screen

+

Microsoft Learn, Learn about retention for Copilot & AI apps

Messages visible in your AI apps are not an accurate reflection of whether they are retained or permanently deleted for compliance requirements.

Microsoft Learn, Learn about retention for Copilot & AI apps

Where the data goes. Microsoft's page says Copilot messages are copied into "a hidden folder in the mailbox of the user who runs the AI app." That folder "isn't designed to be directly accessible to users or administrators." It can be searched with eDiscovery tools.

A user deleting a chat isn't the firm deleting the data. What a staff member clears from their own view and what the firm's policy removes from the mailbox are different things.

The only honest test is a search. If the firm wants to know what it holds after January, the answer sits in the compliance tools, not in anyone's Copilot history. Our Copilot Change Log made the same point about any Microsoft default change: the way to know a control still works is to search it once.

Where this sits in the Safeguards Rule

The FTC Safeguards Rule doesn't mention Copilot, Teams, or retention policies by product. It does set duties that this change touches. The rule is quoted below, in full for (c)(6)(i) and in short fragments elsewhere, or summarized from 16 CFR 314.4. How it applies to Copilot is our reading.

§

What 314.4(c)(6) and (g) ask for

+

16 CFR 314.4(c)(6)(i)

Develop, implement, and maintain procedures for the secure disposal of customer information in any format no later than two years after the last date the information is used in connection with the provision of a product or service to the customer to which it relates, unless such information is necessary for business operations or for other legitimate business purposes, is otherwise required to be retained by law or regulation, or where targeted disposal is not reasonably feasible due to the manner in which the information is maintained

16 CFR 314.4(c)(6)(i)

Disposal. Paragraph (c)(6)(i) asks a firm to maintain procedures for the secure disposal of customer information "in any format." The deadline is "no later than two years after the last date the information is used" in serving the customer it relates to. The rule then lists exceptions. They cover information needed for business operations or other legitimate business purposes, and information that law or regulation requires the firm to keep. They also cover cases where targeted disposal is not reasonably feasible because of how the information is maintained. That list is our summary of the exceptions, not the rule's words.

"In any format." In our reading, a prompt that contains a client's nonpublic personal information is customer information in one more format. If the firm's disposal procedure for that format was a Teams policy, the procedure changes in January whether or not anyone updates the written plan.

The exceptions matter too. The rule allows longer retention for legitimate business purposes or legal requirements. A firm keeping Copilot data on purpose, for a stated reason, is in a different position from a firm keeping it by accident.

Review. Paragraph (c)(6)(ii) asks a firm to "Periodically review your data retention policy to minimize the unnecessary retention of data." A Microsoft change to what a policy covers is a natural point for that review.

Adjusting the program. Paragraph 314.4(g) asks a firm to evaluate and adjust its information security program in light of several things. Among them are "any material changes to your operations or business arrangements" or "any other circumstances that you know or have reason to know may have a material impact on your information security program." Whether this change is material for a given firm depends on how much client information goes into Copilot. Once the firm knows about it, it's hard to say the firm had no reason to know.

Review follows change. Our October issue on WISP review triggers made the broader case: the rule ties review to change and sets no calendar date. This is one of those changes, arriving on a vendor's schedule rather than the firm's.

What the rule does not say. It doesn't set a retention period for AI prompts, require a firm to keep Copilot interactions at all, or name a product. Anyone telling a firm that the Safeguards Rule "requires Copilot retention" is stating more than the text does.

Questions your firm should be able to answer

We won't walk through console settings here, because the right settings depend on what the firm decided to keep and why. These are the questions a firm should be able to answer before mid-January. If the answer to any of them is "I don't know," that is the useful finding.

  1. Does the firm have a retention policy that uses the older location named Teams chats and Copilot interactions?
  2. Was that policy set up to keep data, to delete data, or both? Who decided, and is that reason written down?
  3. Does client information go into Copilot at this firm? In what kinds of work?
  4. After January, what rule will govern Copilot prompts and responses, if any?
  5. Does the written information security plan describe how AI interactions are retained and disposed of? Will that description still be true in February?
  6. Who at the firm would notice a change like this one the next time it happens? Is that a role, or is it luck?
  7. If a client or a reviewer asked tomorrow what the firm holds from Copilot, could the firm answer from a search rather than from memory?

Answer these with whoever holds the Qualified Individual role (the person your firm names to oversee its security program) and whoever administers your Microsoft 365, in the same conversation. They are often different people, and this change falls between them.

Sources

§Sources3 sources · Microsoft 2 · FTC 1+

Message Center posts are visible only inside a firm's own Microsoft 365. MC1481313 was read on mc.merill.net, a third-party mirror. Confirm it in your own Message Center, since Microsoft can change a post. Every other sourced quotation on this page is Microsoft's or the rule's own text.

Microsoft

  1. Microsoft Learn, Learn about retention for Copilot & AI apps
  2. Microsoft 365 Message Center, MC1481313, Legacy Teams retention policies that cover Copilot will be treated as Teams-only, version 2, on the third-party mirror mc.merill.net Mirror

FTC Safeguards Rule

  1. 16 CFR 314.4, Elements: (c)(6)(i), (c)(6)(ii) and (g)

Version 2026.1 · November 19, 2026 · First edition, superseding nothing.

Get a one-page estimate for your firm: what the work would take and what it’s worth, from your own numbers. No charge.

General reference, not legal or tax advice.