A woman works on a laptop in an office, with government documents and workflow icons nearby.
A Word file named "SMCPCSA Letter (ALPR).docx" went into Microsoft Copilot at 5:04 p.m. on September 22. The request came from a city account in Belmont, California. According to Scot Scoop News, the person asking was Kenneth Stenquist, Belmont's interim assistant city manager. The file looks like a police-association letter that criticizes another city's decision not to adopt automated license-plate readers. The chat is a small example, but it raises larger questions for Microsoft 365 administrators about Copilot records, licensing and governance.

A woman works on a laptop in an office, with government documents and workflow icons nearby. What the records reportedly show​

Student reporter Zane Razzak filed a California Public Records Act request on October 5. He asked for three things:

  • the city's generative-AI policies since 2023
  • its AI contracts and invoices
  • all prompts and responses from tools such as ChatGPT, Copilot, Gemini or Claude used for city business between September 1 and October 1

Belmont produced 40 Outlook data files covering 18 accounts. The reporter converted them to a spreadsheet and removed duplicates. The result was 1,752 Copilot interactions.

Most of it was routine. The reporter describes requests to reword messages, tidy them up or make them sound more professional. Only 195 user-side entries were typed by a person. About 600 were triggered automatically. One example is Outlook's suggested reply "Thanks for update," which appeared 169 times.

These counts come from Scot Scoop's reporting and haven't been independently verified. Even so, they are a useful reminder that AI "usage" numbers mix deliberate prompts with background suggestions. Microsoft's own Copilot analytics documentation draws a similar line. It says its metrics count a user's deliberate engagement, not passive or automatic AI behavior.

The September 22 exchange​

According to the report, Stenquist used his city account. He asked Copilot to add language saying the association knew of a recent decision not to pursue ALPR technology and considered it "a bad idea." Copilot wrote that the decision would hurt public safety, regional coordination and the response to serious incidents.

Stenquist then asked for a "strong closing." Copilot urged a city council to reconsider and keep working with regional law-enforcement partners. The closing named the Half Moon Bay community.

The tool also stumbled. When asked for the closing, Copilot couldn't find the file it had just created. It gave Stenquist a paragraph to paste in himself. Anyone who has asked an AI assistant to edit a document, only to be told it can't see the document, will recognize this.

Several things remain unknown:

  • Whether the letter was sent. The reporting doesn't establish this.
  • Which role Stenquist was acting in. He might have been acting as a city employee, as association president or as both. Belmont's June 2 announcement confirms his appointment as interim assistant city manager. The association-president role comes from the reporter's cited May 1 association press release.
  • What the original letter said. The uploaded file wasn't in the production, so the Half Moon Bay reference comes from Copilot's output, not the source document.

The reporter says he sent questions on November 9. Stenquist and the city's communications officer initially offered to meet. After the reporter asked for written answers on November 12 and tried the communications office and City Hall on November 13, there was no response. As of November 20, neither Stenquist nor the city had answered.

Five licenses, no policy​

Two findings matter most to IT administrators.

Policy. For the request about AI policies, guidelines and training materials, the city said it had no responsive records. That is narrower than saying Belmont has no AI governance. It means nothing responsive was produced for this request.

Licensing. The city produced one contract. It is a three-year, $311,550 Microsoft agreement approved in June 2025 through the reseller Crayon Software Experts. It covers Office 365 and security software for about 195 users. Neither the council staff report nor the vendor quote mentions Copilot.

An October 16 internal city email nonetheless refers to "our five co-pilot licenses." Per the reporter, the paid Copilot integrated with Outlook, Word and workplace chat appears in exactly five accounts. Four belong to IT staff. Everyone else used the free web version. The records don't include the purchase of those five licenses.

A cautionary note on counting: Microsoft's documentation separates Copilot licenses purchased from licenses assigned. The assigned figure can be higher because other license types can enable Copilot service plans, such as Copilot for Sales. A figure of "five" should be read with that in mind. The reporting doesn't say how the five were counted.

A separate September 2 chat mentions an AI agent the writer said "they pay for through ChatGPT." The city produced no ChatGPT records. That one remark doesn't show which agent it was, who bought it or whether it was authorized.

Why the records existed​

The reporter says Microsoft stores each chat in a hidden mailbox folder, which is why the records could be exported as Outlook files. That matches how Microsoft and the industry describe it. One guide to Microsoft 365 Copilot auditing says supported Microsoft 365 Copilot prompts and responses are copied to a hidden folder in the user's Exchange Online mailbox. A Microsoft Q&A answer from a volunteer moderator says the data is retained indefinitely by default unless an explicit Microsoft Purview retention policy is configured.

Deletion is more complicated than it looks. Reporting on Microsoft's retention guidance says messages visible in AI apps are not an accurate reflection of whether they are retained or permanently deleted. Expired items can pass through a hidden SubstrateHolds folder first. Other retention policies and holds can suspend that deletion entirely.

That bears on the reporter's follow-up request. He asked for audit logs showing what happened to chats deleted from employees' view. He says those make up two-thirds of what Belmont produced. A chat vanishing from a user's screen doesn't necessarily mean it was erased from the mailbox.

What this means for Microsoft 365 admins​

This is one city and one month of records, so it isn't proof of a widespread problem. It does offer a practical checklist, drawn from the documentation described above. Check these in your own tenant:

  1. Retention policy. Look in the Microsoft Purview portal under Data Lifecycle Management for a retention policy that includes the Microsoft Copilot location. Without one, interactions can be kept indefinitely.
  2. Auditing. Confirm auditing is on. One guide says supported interactions are logged as CopilotInteraction records when auditing is enabled.
  3. eDiscovery and holds. Name Copilot activity explicitly in hold notices and collection templates. Prompts and responses are searchable through Purview eDiscovery.
  4. License inventory. Reconcile Copilot assignments with procurement records. Free Copilot Chat users and paid license holders may produce different records, as the Belmont accounts did.
  5. Acceptable-use rules. Decide whether staff may use organization accounts for outside-group work, and write the answer down.

Public-sector staff should assume that prompts typed into city tools can be requested like email. The test case is already on file.

Bottom line​

Scot Scoop's reporting offers a concrete look at Copilot records from a small city. The licensing and policy gaps it describes are things IT teams can check in their own tenants. Answers to the open questions would settle the rest. Those include the letter's status, Stenquist's capacity, the purchase records and the ChatGPT reference.

 

References

  1. Golden State Records: One month of Copilot inside Belmont City Hall - Scot Scoop News Scot Scoop News Fri, 20 Nov 2026 14:08:48 GMT
  2. How long does CoPilot save files for? - Microsoft Q&A learn.microsoft.com
  3. Auditing Microsoft 365 Copilot: What's Logged and Kept aguidetocloud.com