{"resourceId":"portland-m365-copilot-privacy-impact-assessment-48-risks-validity-ends-20261110","versions":[{"version":"external-97e83835cf999262552a74c59bbc92f5b309dc710967ce622b527609357e589b","resource":{"id":"portland-m365-copilot-privacy-impact-assessment-48-risks-validity-ends-20261110","title":"City of Portland's Microsoft 365 Copilot privacy impact assessment (48 risks, police excluded) reaches its stated validity end on Nov. 10, 2026","organization":"City of Portland, Oregon (Smart City PDX privacy program; Bureau of Technology Services)","sector":"Local government (city operations)","geography":"Oregon, United States","publishedAt":"2025-12-17 (release); final edit 2025-11-10; valid until 2026-11-10","publicationDate":"2025-12-17","eventDate":"2026-11-10","sourceName":"City of Portland eFiles","sourceLabel":"Government privacy impact assessment","sourceUrl":"https://efiles.portlandoregon.gov/record/17699503/file/document","evidenceClass":"government-evaluation","outcomeClass":"cautionary","topics":["governance-procurement","data-security","knowledge-work","accessibility-workforce"],"finding":"Portland's 79-page privacy impact and risk analysis of Microsoft 365 Copilot for city staff identified 48 risks across six areas; the worst case after mitigation was weighted Medium-high. It excludes Portland Police Bureau use. Highlighted risks include unintentional sharing of sensitive data in prompts (Medium), oversurveillance of staff through productivity data (Medium-high) and aggregation of information about individuals. It says Copilot outputs and interaction logs can become public records subject to disclosure. Copilot Chat initially had no Microsoft Graph access, though the assessment covers Graph-integrated risks. BTS adopted Copilot as Standard Technology, was approving a use policy and required training. The document states it is valid until Nov. 10, 2026.","sledRelevance":"Why now: the assessment's stated validity ends on this edition date, and no renewed assessment was found in search. U.S. cities and counties can use it as a model risk register for Copilot and as a reminder that privacy reviews expire while licensing and features (Graph grounding, agents) keep expanding.","evidence":"Government-authored privacy risk analysis using the Smart City PDX impact-likelihood matrix; qualitative ratings, no usage data, incident counts or outcome measures.","architectureImplications":"Risk profile changes when Copilot Chat moves from web-only grounding to Microsoft Graph access across mail, chats and files; agents managed as integrated apps add further scope.","governanceImplications":"Shows a city privacy program rating Copilot risks, scoping out police use, and setting a fixed validity period, which creates a re-assessment checkpoint as features change.","securityPrivacyImplications":"Prompts, outputs and logs can become public records; eDiscovery and overshared documents can expose other users' information; supervisor access to staff data raises oversurveillance risk.","caveats":"Released December 2025, so it predates recent Copilot changes (Copilot Chat fair-use limits, agents, new models). Ratings are expert judgments, not measured incidents. Whether Portland has renewed or extended it is unknown; absence of a renewal in search results is not proof none exists.","streamIds":["microsoft"],"roles":{"sales":"Framing point: privacy assessments for Copilot have expiry dates, and Portland's lapses today. With city and county clients, ask when their own Copilot privacy or risk review was last done and whether it covers Graph grounding and agents. A bounded reassessment against a 48-risk register like Portland's is a credible engagement. Do not claim Portland found Copilot unsafe or safe; the document rates risks qualitatively and reports no incidents or usage outcomes.","engineering":"Framing point: the assessment's scope assumed Copilot Chat without Graph access, so enabling Graph or agents changes the risk baseline. Before expanding, run permission and oversharing reviews on SharePoint and OneDrive, configure Purview retention for Copilot interactions to meet public-records duties, and decide how eDiscovery requests involving prompts will be handled. Keep a separate scope for police or criminal-justice users, as Portland did, because CJIS and evidentiary rules differ.","delivery":"Framing point: treat the privacy assessment as a living control with a renewal date. Put the reassessment on the governance calendar, tie it to feature changes such as Graph grounding or agents, and track each risk's mitigation owner. Pair mandatory training with records guidance that explains when Copilot prompts and outputs are public records. Report to the privacy program and city leadership on mitigation status before the validity date, not after."},"roleDetails":{"sales":{"customerProblem":"Local governments deploy Copilot under privacy reviews that age quickly as Microsoft adds Graph grounding, agents and usage limits.","stakeholders":["City privacy officer","CIO / IT director","City attorney and records manager","HR and labor relations","Police IT (separate scope)"],"discoveryQuestions":["When was your Copilot privacy or risk assessment completed, and when does it expire?","Does it cover Graph-grounded Copilot and agents?","How are Copilot prompts and outputs handled under public-records law?","Is public-safety use scoped separately?"],"valueHypothesis":"A refreshed risk register aligned to current features can reduce records and privacy surprises as Copilot scope expands.","potentialEngagement":"A Copilot privacy reassessment using a 48-risk register modeled on Portland's, scoped to current features.","unsupportedClaims":["That Copilot is safe or unsafe for city use","Incident rates or measured harms","Productivity benefits","That Portland has not renewed the assessment"]},"engineering":{"fit":"City and county Microsoft 365 tenants with Copilot Chat or Microsoft 365 Copilot enabled for staff.","architectureIntegration":"Copilot orchestrates LLMs, Microsoft Graph content and Microsoft 365 apps; agents are managed as integrated apps in the admin center.","prerequisites":["Permission and oversharing review","Purview retention policies for Copilot interactions","Documented feature on/off settings"],"constraints":["Public-records disclosure obligations","Police and CJIS use scoped out","Assessment predates late-2026 Copilot changes"],"security":"Prompts can contain sensitive data; eDiscovery and overshared files can expose other users' information; supervisor access creates surveillance risk.","proofOfValue":["Verify Graph-grounded responses respect sensitivity labels","Test retrieval of Copilot logs for a mock records request","Confirm agent inventory against approved list"]},"delivery":{"work":"Schedule and run a reassessment tied to feature changes, with mitigation owners for each risk and records guidance for staff.","dependencies":["Privacy program capacity","Current Copilot feature configuration","Records retention schedule for AI interactions"],"ownership":"City privacy program with the Bureau of Technology Services as system owner.","skillsAdoption":"Mandatory Copilot training extended with records and privacy modules.","governanceCheckpoints":["Reassessment before validity end","Re-review when Graph or agents are enabled","Separate review before any police use"],"acceptanceCriteria":["Each identified risk has a named mitigation owner and status","Records-request test completed within a defined turnaround","Reassessment published before the next validity date"],"risks":["Assessment lapses unnoticed","Feature changes outpace review","Public-records exposure of prompts","Staff oversurveillance concerns"]}},"retrievedAt":"2026-11-11T04:03:52Z","enrichedAt":"2026-11-11T04:09:32Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Identifies workforce risks including oversurveillance and roles affected by Copilot, with mitigation that may involve unions; mandatory training required.","procurementImplications":"Copilot provided within the city's existing Microsoft licensing bundle; Graph access requires an add-on, affecting cost and risk scope.","operatingModelImplications":"Central IT (BTS) administers Copilot; a separate privacy program assesses it with a fixed validity period.","sourceVerification":{"openedUrl":"https://efiles.portlandoregon.gov/record/17699503/file/document","referenceExcerpt":"This analysis has identified 48 risks in the six areas of revision used by the Smart City PDX","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}