The City of Raisio, Finland, began a Microsoft 365 Copilot adoption program in autumn 2025 with Sogeti, part of Capgemini, to prepare municipal employees for broader AI use before the city’s 2026 strategy cycle. The notable part is not the licensing or the tooling. It is that Raisio treated AI adoption as a workforce-change project first and a software rollout second. For public-sector IT, that distinction may matter more than any demo of autogenerated meeting notes.
Most Copilot stories begin with productivity math. How many minutes can be shaved from a meeting summary? How many emails can be drafted before lunch? How many staff hours can be reclaimed from document work?
Raisio’s case starts somewhere more interesting: with municipal anxiety, uneven digital confidence, and the reality that a city government is not a single-purpose corporation. A Finnish municipality touches education, infrastructure, HR, communications, resident services, business support, records, procurement, and political decision-making. That makes it exactly the kind of organization where generative AI can be useful — and exactly the kind of organization where careless rollout can expose weak governance.
The city’s strategy had already elevated data as a practical asset for everyday work and decision-making. That phrasing matters. It suggests Raisio was not merely chasing the current AI fashion cycle, but trying to turn the information it already collects into something staff can actually use.
Mayor Eero Vainio framed the moment in unusually blunt terms, comparing AI anxiety to early industrial fears and arguing that organizations approaching AI with curiosity will remain relevant. That is vendor-friendly language, certainly. But inside a municipal context, it also captures the political problem: public administrations cannot opt out of AI forever, yet they cannot credibly adopt it as though they were a software startup.
But municipalities are not clean-room productivity labs. Their data estates are often old, permission structures are uneven, records retention rules are serious, and staff roles vary wildly. The same tenant may contain classroom planning documents, HR cases, infrastructure projects, council material, procurement records, social communications, and citizen-facing service information.
That means a Copilot deployment in local government is not just a feature enablement exercise. It is a test of whether the organization understands its own information architecture. Copilot generally works within existing Microsoft 365 permissions, which is reassuring only if those permissions are already well governed.
This is where Raisio’s people-first framing becomes more than soft change-management language. If employees do not understand what AI can and cannot do, they will either underuse it, overtrust it, or route around it with unsanctioned tools. Each outcome is bad in a different way.
Underuse wastes licensing and management effort. Overtrust creates risks around factual errors, confidential information, and public communication. Shadow AI use is worse still, because staff may paste sensitive municipal material into tools outside approved contractual and security boundaries.
But the more important skill is judgment. A worker who asks Copilot to summarize a document still has to know whether the summary omitted a legally significant caveat. A communications officer who asks it to draft a resident notice still has to know whether the tone, facts, and obligations are right. A manager who asks it to synthesize meeting notes still has to know what cannot be inferred from the transcript.
That is why the participant quote in the Raisio material is revealing. One employee said they started from zero and that Copilot had become an everyday assistant “without replacing my own creativity or writing skills.” That is the adoption model Microsoft and its partners want to normalize: AI as a companion to skilled labor, not a substitute for it.
The phrase may sound comforting, but it also sets the bar. If Copilot is an assistant, the user remains accountable. If it becomes a perceived authority, the risk profile changes immediately.
The project began with Microsoft 365 Copilot licenses already purchased. In many organizations, that is the moment when IT simply turns things on, posts a quick-start guide, and waits for usage metrics to justify the spend. Raisio instead paused to build a gradual learning path.
That sequencing is important. Buying licenses before building a human adoption plan is common. Treating the license purchase as the beginning rather than the end of the rollout is less common.
Sogeti first assessed the needs of different employee groups, then built a model around organization-wide introduction, role-specific workshops, and a look toward automation. The structure is conventional in the best sense: broad awareness, practical contextualization, and future capability-building. For AI adoption, that progression is healthier than dumping everyone into a prompt-writing seminar and calling it transformation.
That order is doing quiet work. A shared introduction reduces the mystique around AI and gives employees a common vocabulary. Role-specific workshops then prevent the training from floating above actual work. Automation comes last because it is the most organizationally sensitive: once AI moves from helping an individual draft and summarize to reshaping workflows, governance becomes more complex.
This staged approach also recognizes a truth that AI boosters often skip. Most employees do not need to become AI experts. They need to become competent, skeptical, safe users of AI in the context of their job.
That is especially true in a city government, where the work is not organized around one productivity metric. The “value” of Copilot may look different for a school administrator, an HR specialist, a communications employee, and someone working with infrastructure documentation. A generic productivity narrative cannot capture that diversity.
But it is not a magic wand. Copilot can surface information a user is allowed to access, even if the organization did not realize that access was too broad. The classic SharePoint problem — overshared files, old Teams, inherited permissions, abandoned document libraries — becomes more visible when an AI assistant can synthesize across the sprawl.
That is not a reason to avoid Copilot. It is a reason to treat Copilot readiness as a data governance audit with a productivity tool attached.
Raisio’s co-created AI usage guidelines are therefore one of the more meaningful details in the story. Guidelines do not solve every security problem, and no policy document makes users instantly responsible. But the act of creating them forces the organization to decide what responsible use means in its own context, rather than leaving each employee to infer the rules from marketing copy.
That modesty is the point. A local government does not need the theater of scale as much as it needs repeatable trust. A hundred trained municipal employees who understand when to use Copilot, when not to use it, and how to challenge its output may be more valuable than a thousand enabled accounts producing inconsistent results.
The program’s pre- and post-project surveys reportedly showed reduced hesitation and better understanding of AI’s potential and limitations. That is the kind of metric that rarely makes a splashy keynote but matters enormously to IT leaders. In many organizations, AI resistance is not simply fear of change; it is a rational response to unclear expectations.
If staff believe AI is being imposed on them as a performance surveillance tool, a job-cutting mechanism, or a fashionable executive initiative, adoption will be shallow. If they see it as a supported skill-building effort, they are more likely to experiment responsibly.
The strongest case for Copilot is not that it magically makes workers creative. It is that much office work contains a layer of formatting, summarizing, rephrasing, finding, and first-draft generation that consumes attention without always requiring deep expertise. Removing some of that drag can make the day feel less fragmented.
But productivity claims around generative AI still require caution. A faster first draft is not automatically a better final document. A summary can save time only if it is accurate enough to trust after review. An email assistant can improve communication, but it can also create a flood of polished, low-substance messages if used lazily.
The real measurement problem is quality-adjusted productivity. If Copilot saves 20 minutes but introduces five minutes of verification and a subtle factual error, the net benefit depends on the task. Raisio’s people-centered training model is a tacit admission that the software does not deliver value on its own.
Public-sector workforces often include employees with very different levels of digital fluency. Some staff will immediately experiment with prompts and workflows. Others may be anxious about making mistakes, exposing data, or looking incompetent in front of colleagues. A rollout that rewards only the confident early adopter will widen the gap between those groups.
Raisio’s approach — live training, reusable materials, peer learning, and a safe atmosphere — treats AI literacy as a workforce inclusion issue. That may become one of the defining challenges of the next few years. AI tools embedded in everyday software will quietly change what it means to be digitally competent.
There is also a management lesson here. If AI becomes part of normal office work, employers cannot merely tell staff to “use AI responsibly” and walk away. They have to define responsible use, support it, and make room for employees to admit what they do not understand.
That normalization is the commercial engine. Once Copilot becomes part of drafting, search, meeting review, and email triage, it becomes harder for organizations to disentangle AI capability from the Microsoft productivity stack. The more training, governance, and workflow redesign an organization builds around Copilot, the stickier the platform becomes.
For IT pros, that has two sides. The advantage is integration. Copilot can sit inside tools organizations already manage, with familiar identity, compliance, and admin concepts. The drawback is dependency. If AI assistance becomes another layer of the Microsoft 365 estate, licensing, governance, and vendor roadmap decisions become even more consequential.
Raisio’s case does not resolve that tension. It illustrates it. The city is using Microsoft’s platform to build internal capability, while also deepening its reliance on Microsoft’s interpretation of enterprise AI.
Summarizing documents is one category of risk. Automating processes is another. Once AI begins to trigger workflows, route information, generate decisions for review, or connect across systems, the governance burden increases. Who approved the workflow? What data does it touch? How are errors detected? Can a resident challenge an AI-assisted output? What records must be retained?
Municipalities will have to answer those questions well before AI becomes truly autonomous. Even semi-automated administrative work can shape how quickly citizens receive information, how cases are prioritized, and how internal decisions are documented.
Raisio appears to be taking the sensible first step: build staff familiarity before chasing deeper automation. That may feel slow, but it creates an institutional base for later decisions. A workforce that understands Copilot’s limits is better positioned to evaluate where automation is appropriate.
Sysadmins have seen this movie before. Collaboration platforms promised transparency and produced Teams sprawl. Cloud storage promised access and produced permission drift. Search promised discovery and exposed messy information architecture. Copilot sits on top of all of that.
The best preparation for Microsoft 365 Copilot may be deeply unglamorous. Review SharePoint permissions. Clean up stale Teams. Clarify sensitivity labels. Decide what data should not be used in prompts. Train managers not to treat AI output as inherently authoritative. Create reporting channels for mistakes and near misses.
That work is not anti-AI. It is what makes AI usable in a serious organization.
That is less dramatic than an AI moonshot. It is also more believable.
The city’s leaders repeatedly framed the project around employee success and well-being at work. That may sound like the expected language of public administration, but it is politically important. AI programs that are sold only as efficiency drives invite suspicion. AI programs connected to worker capability and service quality have a better chance of surviving contact with reality.
The proof will come later. The initial training may reduce hesitation, but long-term value will depend on whether staff keep using Copilot appropriately, whether governance keeps pace, and whether Raisio can translate internal productivity into better resident services.
Raisio Puts the Human Rollout Ahead of the AI Rollout
Most Copilot stories begin with productivity math. How many minutes can be shaved from a meeting summary? How many emails can be drafted before lunch? How many staff hours can be reclaimed from document work?Raisio’s case starts somewhere more interesting: with municipal anxiety, uneven digital confidence, and the reality that a city government is not a single-purpose corporation. A Finnish municipality touches education, infrastructure, HR, communications, resident services, business support, records, procurement, and political decision-making. That makes it exactly the kind of organization where generative AI can be useful — and exactly the kind of organization where careless rollout can expose weak governance.
The city’s strategy had already elevated data as a practical asset for everyday work and decision-making. That phrasing matters. It suggests Raisio was not merely chasing the current AI fashion cycle, but trying to turn the information it already collects into something staff can actually use.
Mayor Eero Vainio framed the moment in unusually blunt terms, comparing AI anxiety to early industrial fears and arguing that organizations approaching AI with curiosity will remain relevant. That is vendor-friendly language, certainly. But inside a municipal context, it also captures the political problem: public administrations cannot opt out of AI forever, yet they cannot credibly adopt it as though they were a software startup.
A City Is a Harder Copilot Customer Than a Corporate Department
Microsoft 365 Copilot is marketed as a natural extension of Word, Excel, Outlook, Teams, PowerPoint, and the Microsoft Graph. That pitch can make adoption sound deceptively simple. If workers already live in Microsoft 365, the assistant simply appears beside the work they already do.But municipalities are not clean-room productivity labs. Their data estates are often old, permission structures are uneven, records retention rules are serious, and staff roles vary wildly. The same tenant may contain classroom planning documents, HR cases, infrastructure projects, council material, procurement records, social communications, and citizen-facing service information.
That means a Copilot deployment in local government is not just a feature enablement exercise. It is a test of whether the organization understands its own information architecture. Copilot generally works within existing Microsoft 365 permissions, which is reassuring only if those permissions are already well governed.
This is where Raisio’s people-first framing becomes more than soft change-management language. If employees do not understand what AI can and cannot do, they will either underuse it, overtrust it, or route around it with unsanctioned tools. Each outcome is bad in a different way.
Underuse wastes licensing and management effort. Overtrust creates risks around factual errors, confidential information, and public communication. Shadow AI use is worse still, because staff may paste sensitive municipal material into tools outside approved contractual and security boundaries.
Copilot’s Real Test Is Not Whether It Can Write, But Whether Staff Can Judge
The Raisio program aimed to reduce time spent on information searches and routine content creation. Those are sensible use cases because they match where generative AI is currently strongest: summarizing, drafting, rephrasing, structuring, and helping users navigate a large information environment.But the more important skill is judgment. A worker who asks Copilot to summarize a document still has to know whether the summary omitted a legally significant caveat. A communications officer who asks it to draft a resident notice still has to know whether the tone, facts, and obligations are right. A manager who asks it to synthesize meeting notes still has to know what cannot be inferred from the transcript.
That is why the participant quote in the Raisio material is revealing. One employee said they started from zero and that Copilot had become an everyday assistant “without replacing my own creativity or writing skills.” That is the adoption model Microsoft and its partners want to normalize: AI as a companion to skilled labor, not a substitute for it.
The phrase may sound comforting, but it also sets the bar. If Copilot is an assistant, the user remains accountable. If it becomes a perceived authority, the risk profile changes immediately.
Sogeti Sold Raisio a Change Program, Not Just a Technical Engagement
Raisio selected Sogeti partly for Microsoft and AI expertise, but the city’s CIO Eero Rostiala emphasized something else: the partner’s ability to support cultural transformation. That is a notable signal from a public-sector buyer. It suggests the city understood that training slides and license assignment would not be enough.The project began with Microsoft 365 Copilot licenses already purchased. In many organizations, that is the moment when IT simply turns things on, posts a quick-start guide, and waits for usage metrics to justify the spend. Raisio instead paused to build a gradual learning path.
That sequencing is important. Buying licenses before building a human adoption plan is common. Treating the license purchase as the beginning rather than the end of the rollout is less common.
Sogeti first assessed the needs of different employee groups, then built a model around organization-wide introduction, role-specific workshops, and a look toward automation. The structure is conventional in the best sense: broad awareness, practical contextualization, and future capability-building. For AI adoption, that progression is healthier than dumping everyone into a prompt-writing seminar and calling it transformation.
The Three-Stage Model Shows How AI Becomes Mundane
Raisio’s learning path had three parts. The first gave the whole organization a shared grounding in Copilot’s possibilities and basic rules. The second moved into role-specific workshops built around real scenarios. The third introduced automation and the future of knowledge work.That order is doing quiet work. A shared introduction reduces the mystique around AI and gives employees a common vocabulary. Role-specific workshops then prevent the training from floating above actual work. Automation comes last because it is the most organizationally sensitive: once AI moves from helping an individual draft and summarize to reshaping workflows, governance becomes more complex.
This staged approach also recognizes a truth that AI boosters often skip. Most employees do not need to become AI experts. They need to become competent, skeptical, safe users of AI in the context of their job.
That is especially true in a city government, where the work is not organized around one productivity metric. The “value” of Copilot may look different for a school administrator, an HR specialist, a communications employee, and someone working with infrastructure documentation. A generic productivity narrative cannot capture that diversity.
The Security Story Is Only as Good as the Permissions Story
Microsoft’s standard enterprise pitch for Microsoft 365 Copilot rests on a major reassurance: prompts, responses, and Microsoft Graph data accessed by Copilot are not used to train foundation models, and Copilot works within the Microsoft 365 service boundary and existing access controls. For commercial and public-sector customers, that is a necessary baseline.But it is not a magic wand. Copilot can surface information a user is allowed to access, even if the organization did not realize that access was too broad. The classic SharePoint problem — overshared files, old Teams, inherited permissions, abandoned document libraries — becomes more visible when an AI assistant can synthesize across the sprawl.
That is not a reason to avoid Copilot. It is a reason to treat Copilot readiness as a data governance audit with a productivity tool attached.
Raisio’s co-created AI usage guidelines are therefore one of the more meaningful details in the story. Guidelines do not solve every security problem, and no policy document makes users instantly responsible. But the act of creating them forces the organization to decide what responsible use means in its own context, rather than leaving each employee to infer the rules from marketing copy.
Public Administration Needs Slow AI More Than Flashy AI
There is a strong temptation in the AI market to equate speed with maturity. The fastest rollout, the largest deployment, the biggest license count, the most aggressive automation target — these are easy to package as success stories. Raisio’s deployment, covering almost 100 employees in the initial program, is modest by those standards.That modesty is the point. A local government does not need the theater of scale as much as it needs repeatable trust. A hundred trained municipal employees who understand when to use Copilot, when not to use it, and how to challenge its output may be more valuable than a thousand enabled accounts producing inconsistent results.
The program’s pre- and post-project surveys reportedly showed reduced hesitation and better understanding of AI’s potential and limitations. That is the kind of metric that rarely makes a splashy keynote but matters enormously to IT leaders. In many organizations, AI resistance is not simply fear of change; it is a rational response to unclear expectations.
If staff believe AI is being imposed on them as a performance surveillance tool, a job-cutting mechanism, or a fashionable executive initiative, adoption will be shallow. If they see it as a supported skill-building effort, they are more likely to experiment responsibly.
The Productivity Claims Are Plausible, But Not the Whole Story
Raisio says Copilot helped employees produce documents more easily and with better quality, summarize large amounts of information, search more efficiently, and manage email and communication more effectively. Those are the standard Microsoft 365 Copilot use cases, and they are credible because they align with everyday knowledge-work friction.The strongest case for Copilot is not that it magically makes workers creative. It is that much office work contains a layer of formatting, summarizing, rephrasing, finding, and first-draft generation that consumes attention without always requiring deep expertise. Removing some of that drag can make the day feel less fragmented.
But productivity claims around generative AI still require caution. A faster first draft is not automatically a better final document. A summary can save time only if it is accurate enough to trust after review. An email assistant can improve communication, but it can also create a flood of polished, low-substance messages if used lazily.
The real measurement problem is quality-adjusted productivity. If Copilot saves 20 minutes but introduces five minutes of verification and a subtle factual error, the net benefit depends on the task. Raisio’s people-centered training model is a tacit admission that the software does not deliver value on its own.
AI Training Becomes a New Form of Digital Inclusion
One of the more understated parts of the Raisio story is the emphasis on letting employees learn at their own pace without pressure. In an IT industry obsessed with acceleration, that can sound quaint. In a municipality, it is essential.Public-sector workforces often include employees with very different levels of digital fluency. Some staff will immediately experiment with prompts and workflows. Others may be anxious about making mistakes, exposing data, or looking incompetent in front of colleagues. A rollout that rewards only the confident early adopter will widen the gap between those groups.
Raisio’s approach — live training, reusable materials, peer learning, and a safe atmosphere — treats AI literacy as a workforce inclusion issue. That may become one of the defining challenges of the next few years. AI tools embedded in everyday software will quietly change what it means to be digitally competent.
There is also a management lesson here. If AI becomes part of normal office work, employers cannot merely tell staff to “use AI responsibly” and walk away. They have to define responsible use, support it, and make room for employees to admit what they do not understand.
Microsoft Wins When Copilot Becomes Ordinary
From Microsoft’s perspective, stories like Raisio are strategically useful because they move Copilot out of the realm of futuristic demos and into the daily machinery of public administration. The company does not need every customer to build elaborate AI agents on day one. It needs workers to accept Copilot as a normal part of Microsoft 365.That normalization is the commercial engine. Once Copilot becomes part of drafting, search, meeting review, and email triage, it becomes harder for organizations to disentangle AI capability from the Microsoft productivity stack. The more training, governance, and workflow redesign an organization builds around Copilot, the stickier the platform becomes.
For IT pros, that has two sides. The advantage is integration. Copilot can sit inside tools organizations already manage, with familiar identity, compliance, and admin concepts. The drawback is dependency. If AI assistance becomes another layer of the Microsoft 365 estate, licensing, governance, and vendor roadmap decisions become even more consequential.
Raisio’s case does not resolve that tension. It illustrates it. The city is using Microsoft’s platform to build internal capability, while also deepening its reliance on Microsoft’s interpretation of enterprise AI.
The Automation Horizon Is Where the Stakes Rise
The third stage of Raisio’s learning model introduced opportunities for automation and a view into the future of knowledge work. That is where the story becomes more forward-looking and more complicated.Summarizing documents is one category of risk. Automating processes is another. Once AI begins to trigger workflows, route information, generate decisions for review, or connect across systems, the governance burden increases. Who approved the workflow? What data does it touch? How are errors detected? Can a resident challenge an AI-assisted output? What records must be retained?
Municipalities will have to answer those questions well before AI becomes truly autonomous. Even semi-automated administrative work can shape how quickly citizens receive information, how cases are prioritized, and how internal decisions are documented.
Raisio appears to be taking the sensible first step: build staff familiarity before chasing deeper automation. That may feel slow, but it creates an institutional base for later decisions. A workforce that understands Copilot’s limits is better positioned to evaluate where automation is appropriate.
The Lesson for Sysadmins Is Not “Turn On Copilot”
For WindowsForum readers, the Raisio story should not be read as a generic endorsement of enabling Copilot across every tenant. The lesson is more specific: adoption quality depends on the organization’s readiness to govern data, train users, and align AI use with real work.Sysadmins have seen this movie before. Collaboration platforms promised transparency and produced Teams sprawl. Cloud storage promised access and produced permission drift. Search promised discovery and exposed messy information architecture. Copilot sits on top of all of that.
The best preparation for Microsoft 365 Copilot may be deeply unglamorous. Review SharePoint permissions. Clean up stale Teams. Clarify sensitivity labels. Decide what data should not be used in prompts. Train managers not to treat AI output as inherently authoritative. Create reporting channels for mistakes and near misses.
That work is not anti-AI. It is what makes AI usable in a serious organization.
Raisio’s Quiet Bet Is That Trust Scales Better Than Hype
Raisio’s story is small enough to be practical and large enough to matter. The city did not announce a sweeping AI transformation of public services. It trained nearly 100 employees, opened materials for broader reuse, and tried to seed a culture of shared learning.That is less dramatic than an AI moonshot. It is also more believable.
The city’s leaders repeatedly framed the project around employee success and well-being at work. That may sound like the expected language of public administration, but it is politically important. AI programs that are sold only as efficiency drives invite suspicion. AI programs connected to worker capability and service quality have a better chance of surviving contact with reality.
The proof will come later. The initial training may reduce hesitation, but long-term value will depend on whether staff keep using Copilot appropriately, whether governance keeps pace, and whether Raisio can translate internal productivity into better resident services.
Raisio’s Copilot Playbook Is Small Enough to Copy
The practical value of the Raisio case is that other municipalities and mid-sized organizations can actually recognize themselves in it. This is not a hyperscale enterprise deploying AI to hundreds of thousands of employees with a global consulting machine behind it. It is a city trying to bring a mixed workforce into the AI era without pretending that software alone changes culture.- Raisio began with a strategic need to make data more useful in everyday municipal work, not with a standalone AI experiment.
- The city treated Microsoft 365 Copilot adoption as a gradual learning journey shaped around employees’ roles and confidence levels.
- Sogeti’s role combined technical Microsoft expertise with change-management support, which mattered because the rollout crossed many municipal functions.
- The program emphasized safe use, privacy, security, and shared guidelines rather than assuming Copilot’s enterprise controls were enough by themselves.
- The first visible gains were in familiar knowledge-work tasks such as drafting, summarizing, searching, and managing communications.
- The most important long-term test will be whether Raisio can move from individual productivity gains to better public administration without outrunning governance.
References
- Primary source: Capgemini
Published: 2026-06-22T15:12:07.555000
The City of Raisio launches a people-first path to AI with Microsoft 365 Copilot
The City of Raisio partnered with Sogeti to launch a new strategy, setting in motion a people-first AI journey supported by a safe learning environment and shared learningwww.capgemini.com - Related coverage: sogeti.com
The City of Raisio launches a people-first path to AI with Microsoft 365 Copilot - Sogeti Global
Discover how the City of Raisio adopted AI with Microsoft 365 Copilot through a people-first approach and a structured rollout.www.sogeti.com - Related coverage: techspot.com
Microsoft to install Copilot by default on Microsoft 365 devices starting fall 2025 | TechSpot
Microsoft is rolling out an advanced deployment of the Copilot app, which will soon become an integral part of the Microsoft 365 suite. Windows devices with Microsoft...www.techspot.com - Official source: learn.microsoft.com
License Options for Microsoft 365 Copilot | Microsoft Learn
Discover Microsoft 365 Copilot license plans and integration options for your existing Microsoft 365 subscription. Compare plans and find the right fit.learn.microsoft.com - Related coverage: sogeti.us
Microsoft - Sogeti US
With 20+ years of partnership, discover how Sogeti and Microsoft collaborate to deliver cutting-edge cloud, data, and AI solutions.www.sogeti.us - Official source: microsoft.com
- Related coverage: cnbc.com
Microsoft adds Anthropic AI model to Copilot assistant, diversifying from OpenAI
Microsoft is taking another step toward diversification away from OpenAI, which it considers a strategic partner.www.cnbc.com - Official source: techcommunity.microsoft.com
Microsoft Frontier Program expands to individual Microsoft subscribers | Microsoft Community Hub
The Frontier program that gives commercial Microsoft 365 Copilot customers early access to exciting, cutting-edge capabilities is now coming to individuals...
techcommunity.microsoft.com
- Official source: news.microsoft.com
- Related coverage: dataconomy.com
Microsoft will install Copilot to everyone’s PCs from fall 2025
Starting in the fall of 2025, Microsoft will automatically install its AI-powered Copilot application on all Microsoft 365 subscriptions fordataconomy.com
