Strategic PartnersIssue 043 records
Microsoft
A thin, governance-heavy edition covering Oct. 30 to Nov. 1. Two Washington local governments show how public-records law is shaping Copilot use. Chelan's council got a first look on Oct. 27 at a draft AI policy (reported Oct. 31). It makes Microsoft Copilot the preferred tool, with free Copilot only for public information and enterprise Copilot for city data, reserves an enterprise Claude for complex work, and treats prompts and outputs as potential public records. King County's October records guidance names Copilot Chat as the approved tool. It warns that its 30-day storage setting is not legal retention, so substantive uses must be captured into county records by hand. Separately, a Microsoft blog sets a forced migration: SharePoint Agents move to Copilot Agent Builder from mid-November, legacy .agent files stop working after March 2027, and Copilot Chat-only users may incur Copilot Credit charges. No independent measured outcomes were found, and there were no new Microsoft items for HHS, public safety, transportation, K-12 or higher education in the window.
- Evidence records
- 3
- Cross-source patterns
- 1
- Evidence classes
- 1 independent reporting1 standards or public-body guidance1 vendor claim
- Outcomes
- 2 emerging1 cautionary
- Source freshness
- 3 new this fortnight
- Research completed
- 2026-11-03
Choose a role to see its takeaway beside every record in the ledger.
Patterns across the evidence
Synthesis · Lighthouse Advisory interpretation
Copilot prompts and outputs are being treated as public records, and default storage is not legal retention
In Washington, two local governments reached the same conclusion in the same week. Chelan's draft policy says AI prompts, conversations and outputs may be public records and must be kept in approved city systems. King County's records guidance says both prompts and results are subject to disclosure and retention law. It also says Copilot Chat's 30-day enterprise storage setting is not legal retention, so non-transitory uses must be captured by hand, and Export to Word omits prompts. Agencies adopting Copilot Chat under state public-records law need a deliberate capture and retention design, plus training on what counts as transitory, before AI use becomes routine.
Operating questionWhen a Copilot conversation informs a decision, how is it captured, kept for the right schedule and found for a public-records request?
Supporting evidenceCity of ChelanKing County Records and Information Management Program (CRIMP)
Evidence ledger
Full record · every source keeps its link and limitations
Chelan, Wash., drafts an AI use policy that makes Microsoft Copilot the preferred tool, reserves an enterprise Claude for complex work, and treats AI prompts and outputs as potential public records (council first look Oct. 27; reported Oct. 31)
The Lake Chelan Mirror reports that Chelan's council got its first look at a draft AI use policy on Oct. 27 and took no action. Microsoft Copilot would be the preferred platform because it works inside Outlook, Word and Excel. Free Copilot could be used only with publicly available information; licensed enterprise Copilot could be used with authorised city information. For complex tasks such as technical analysis, the city would favour an enterprise version of Claude. Personal ChatGPT and Gemini accounts would generally be barred. AI could not be the sole basis for permitting, enforcement or employment decisions. Prompts, conversations and outputs may be public records, and qualifying records must be kept in approved city systems.
Why it matters, evidence and limitations
- Why it matters
- A small US city is writing a tiered Microsoft policy: free Copilot for public data, enterprise Copilot for city data, and a second vendor for heavier work. It also treats Copilot conversations as records under Washington public-records law. That is the decision many small local governments face when Copilot Chat arrives inside Microsoft 365.
- Evidence and measured results
- A local reporter's account of a staff presentation and council discussion. The draft policy text was not published with the article and was not read.
- Limitations and uncertainty
- Draft only; council took no action and the policy may change. Based on news reporting, not the policy text. A small city, so scale and staffing differ from large jurisdictions. The Claude element is outside this stream and is noted only for context.
King County, Wash., records guidance (10/2026): Copilot Chat is the county's approved generative AI tool, its enterprise storage setting is 30 days, and non-transitory prompts and results must be captured into county records
King County's records programme says Copilot Chat is the county's approved enterprise generative AI tool. Both prompts and results are potentially subject to disclosure under RCW 42.56 and retention under RCW 40.14.010. The enterprise storage setting for Copilot Chat records is 30 days, and content not saved before then cannot be retrieved. The guidance says this setting is not the same as legal retention. Transitory uses (quick edits, brainstorming, search-like questions) need no action. Non-transitory uses (substantive changes, decision support, legal or compliance guidance, anything public-facing) must be copied into other county records and filed under the right schedule (for example 6, 3 or 2 years). Export to Word does not include prompts.
Why it matters, evidence and limitations
- Why it matters
- A large US county has documented the gap between Copilot Chat's default storage and public-records retention law, with a manual capture procedure. Any SLED agency rolling out Copilot Chat under state records law faces the same gap.
- Evidence and measured results
- A primary county guidance document with legal citations, retention examples and a step-by-step capture procedure. It is guidance, not an audit; it reports no data on how often staff capture records.
- Limitations and uncertainty
- Guidance only; no compliance data. The document is dated 10/2026; the day (Oct. 26) comes from PDF creation metadata. The retention periods are simplified, per the document. Microsoft retention capabilities beyond the 30-day setting are not discussed, so this is the county's chosen configuration, not a product limit.
How to read this edition
Source findings, measured results and limitations come from the cited publications. Patterns, operating questions, role takeaways and implementation considerations are Lighthouse Advisory interpretation, stated as questions to validate locally rather than guaranteed outcomes. Vendor and operator claims are labeled as claims. Full research method.
- Independent reporting
- Independent reporting with attributable sources but without a formal evaluation design.
- Standards or public-body guidance
- Normative or advisory guidance from a standards body or public institution.
- Vendor claim
- A supplier-provided assertion that has not been upgraded to independent evidence.