The City of Raisio in Finland began a Microsoft 365 Copilot adoption program in autumn 2025 with Sogeti, part of Capgemini, training nearly 100 municipal employees before a broader 2026 push to make data and generative AI part of everyday public-sector work. The notable part is not that another organization bought Copilot licenses. It is that Raisio treated AI rollout as a workforce-change project first and a software deployment second. That distinction may decide whether municipal AI becomes a productivity dividend or just another expensive icon in the Microsoft 365 app drawer.
The public conversation around workplace AI still tends to move in the language of inevitability. Microsoft talks about Copilot as the new interface for work, consultancies sell transformation journeys, and executives worry that hesitation will be mistaken for decline. But inside a city administration, inevitability is not an implementation plan.
Raisio’s project is interesting because it starts from an unglamorous premise: employees will not use AI well merely because the tenant admin has enabled it. They need time, examples, rules, and permission to learn without embarrassment. That is a softer thesis than the usual Copilot pitch, but it is also more realistic.
The city’s own framing puts data at the center of the story. Raisio’s new strategy elevated data as an enabler of day-to-day work and decision-making, alongside employee development. That matters because Copilot is only as useful as the organizational habits surrounding it: how documents are stored, how meetings are summarized, how policies are shared, how staff decide what is safe to paste into a prompt.
The launch also lands at a moment when Microsoft 365 Copilot is moving from novelty to infrastructure. Microsoft has spent the past two years embedding Copilot deeper into Word, Outlook, Teams, Excel, PowerPoint, the Microsoft 365 app, and Copilot Studio. The vendor story is that AI is becoming ambient. Raisio’s story is that ambient AI still needs very deliberate human scaffolding.
That is why the “people-first” label is more than marketing polish here. Municipal workers are not a homogeneous population of knowledge workers waiting to automate slide decks. Some are already fluent in Microsoft 365 habits; others may be approaching generative AI from a standing start. The city’s own participant feedback captures this plainly: one employee described starting “from zero” and later finding Copilot useful as an everyday assistant without replacing their own creativity or writing skills.
That last clause is doing important work. The adoption battle for AI in public administration is not merely about efficiency; it is about agency. Workers must believe the tool is there to reduce friction rather than silently redefine their value. If an AI rollout feels like surveillance, job redesign by stealth, or another management fad, usage metrics may rise for a quarter and then decay into performative compliance.
Raisio’s mayor, Eero Vainio, used a familiar historical analogy, comparing the arrival of AI to the anxiety around early industrial machinery. The spinning jenny comparison is imperfect, as all such analogies are, because generative AI is not a single machine introduced into one trade. It is a general-purpose interface being threaded through the administrative nervous system. Still, the political point is clear: the city wants its employees to approach AI with curiosity rather than fear.
Microsoft 365 Copilot is especially prone to that trap because it appears inside tools workers already use. On paper, that lowers the barrier. In practice, it can obscure the change. If Copilot is “just in Word” or “just in Teams,” managers may assume employees will naturally discover valuable use cases on their own.
Some will. Most will not, at least not consistently and safely. Prompting is not magic, but it is a learned workplace behavior. Asking Copilot to summarize a meeting, compare policy drafts, produce a first version of a resident communication, or find relevant information across Microsoft 365 requires judgment about context, quality, confidentiality, and verification.
Raisio’s CIO, Eero Rostiala, framed the employer’s role as enabling people to succeed. That is a useful corrective to the common “AI readiness” cliché. Readiness is not a property employees either possess or lack. It is built by the organization through training design, governance, data hygiene, management expectations, and visible peer examples.
The city’s decision to bring in Sogeti signals another reality of Copilot adoption: even if the software is bought from Microsoft, the transformation market around it is largely partner-led. Capgemini and Sogeti are not just installing a feature. They are selling a method for converting a software entitlement into changed behavior.
The introductory layer gave staff a common baseline. In a multisector city organization, that baseline matters because otherwise every department invents its own AI folklore. One team may think Copilot can be trusted as a source of truth; another may avoid it entirely because of privacy anxiety; another may use it heavily but informally. Shared training gives the city a common vocabulary for both possibility and restraint.
The role-specific workshops are where the real adoption likely happened. Generic Copilot demos often fail because they show polished scenarios detached from the user’s actual inbox, document library, meetings, and service obligations. Raisio’s project worked from real work scenarios across different city functions, which is the difference between “AI can summarize text” and “AI can help me turn this messy meeting record into a usable internal note.”
The automation stage is more delicate. Once workers see Copilot as an assistant, the natural next question is which processes can be redesigned around AI and automation more broadly. That can unlock major productivity gains, but it also changes the risk profile. A bad draft is one thing; a bad automated workflow touching records, approvals, or resident communications is another.
Raisio appears to have treated that future-facing layer as orientation rather than a rush to wire agents into everything. That restraint is wise. The organizations that get the most from AI will not be the ones that automate first. They will be the ones that understand their processes well enough to know where automation belongs.
Microsoft 365 Copilot’s enterprise pitch rests heavily on the idea that it respects existing Microsoft 365 permissions. That is important, but it is not the same as governance. If permissions are messy, Copilot can make the mess more visible. If old files are overshared, poorly labeled, or stored in the wrong place, AI does not create the underlying problem, but it can make the consequences easier to encounter.
For sysadmins, this is the uncomfortable underside of the Copilot boom. The assistant is often marketed as a front-end productivity tool, but successful deployment depends on back-end discipline: identity, access control, retention, sensitivity labels, information architecture, endpoint posture, and user education. In other words, Copilot adoption is also a referendum on years of Microsoft 365 hygiene.
Raisio’s gradual model suggests a city trying not to confuse technical availability with organizational permission. Employees were not simply told to go experiment. They were given a safer learning space, shared materials, and guidance on appropriate use. That does not eliminate risk, but it does create a defensible path.
There is also a democratic-administration angle here. Cities serve residents who do not get to opt out of the public services they depend on. If AI is used to draft, summarize, or prioritize internal work, the organization needs clear norms for human review and accountability. “Copilot wrote it” cannot become an excuse in a city hall.
It should not. Those are exactly the mundane tasks that consume public-sector capacity. Municipal work is full of documents, meetings, emails, reports, resident communications, internal instructions, and policy fragments. If AI can shave time from those tasks without degrading quality or trust, the aggregate effect can be meaningful.
The key phrase is “without degrading quality or trust.” A faster bad document is not a productivity gain. A confident hallucinated summary is not administrative modernization. A resident communication that sounds polished but misses legal nuance may create more work than it saves.
Raisio’s training reportedly reduced hesitation while helping employees understand both the potential and limitations of AI. That dual outcome is important. The goal is not maximum enthusiasm. It is calibrated confidence. Workers need to know when Copilot is useful, when it must be checked, and when it should not be used at all.
This is where peer learning can be more powerful than top-down instruction. Employees are often more persuaded by a colleague showing how Copilot helped with a real task than by a vendor deck promising transformation. Raisio’s emphasis on shared experiences recognizes that AI adoption is partly social.
That creates tension for customers. Microsoft wants Copilot to become the default way work gets done. Organizations need it to become boring enough to govern. The first objective rewards speed and breadth; the second requires friction, policy, and staged adoption.
Raisio’s approach sits between those forces. The city is not rejecting Microsoft’s AI roadmap. It is accepting the direction while slowing the internal pace enough to make the change survivable. That is probably the most practical posture available to many public-sector IT leaders right now.
It also hints at why partners like Sogeti and Capgemini are central to the Copilot economy. Microsoft can ship features at cloud cadence, but it cannot sit with every HR department, infrastructure team, or school administration unit and translate those features into safe local practice. The partner’s role is to turn a horizontal product into situated work.
The risk, of course, is that “human-centered change management” becomes a reusable slogan pasted onto every AI deployment. In Raisio’s case, the details make the phrase more convincing: pre- and post-project surveys, role-specific workshops, shared materials, flexible scheduling, and usage guidelines. Those are not glamorous, but they are the machinery of adoption.
The first pressure point is data exposure. Copilot’s usefulness depends on access to organizational content, which means existing oversharing can become more consequential. Before broad rollout, IT teams need to understand where sensitive content lives, who can access it, and whether permission models reflect current business reality rather than years of accumulated exceptions.
The second pressure point is user expectation. Employees may assume Copilot is a search engine, a writing authority, a confidential advisor, or a fully reliable analyst. It is none of those things in a simple sense. Training must explain not only what the tool can do, but what kind of human verification remains mandatory.
The third pressure point is support. Once Copilot becomes part of everyday work, help desks will receive questions that are not purely technical. “Why did Copilot find this file?” “Can I use it with this resident information?” “Why is this summary wrong?” “Can it automate this process?” These are governance and workflow questions disguised as tickets.
Raisio’s model implies that IT cannot own the rollout alone. The city paired technical competence with project management, communications, and departmental context. That is a useful pattern: Copilot governance should be co-owned by IT, legal or compliance functions, HR, communications, records management, and business units.
That is not a flaw unique to Raisio. The entire enterprise AI market is still wrestling with measurement. Time saved is hard to prove, quality is harder, and downstream effects are harder still. If an employee saves 20 minutes drafting a document but spends 15 minutes checking it, is that a win? If a better summary prevents a misunderstanding, how should that be counted?
Public-sector measurement is even more complicated because the goal is not simply output per employee. A city must care about service quality, accessibility, transparency, employee well-being, legal compliance, and resident trust. AI that makes internal work faster but public communication worse is not a success.
Raisio’s stated intent to understand employees’ needs for future development work may be the right next metric. Early AI programs should not pretend to deliver final answers. They should reveal which workflows are ripe for improvement, which data practices need repair, and which employees need more support.
The next stage should therefore move from adoption sentiment to operational evidence. Which tasks are being improved? Where is Copilot not useful? Which departments are using it safely and frequently? Which use cases create the most review burden? Which data-access problems surfaced during training? These are the questions that separate durable transformation from a well-received pilot.
Raisio Makes the Quiet Case for Slow AI
The public conversation around workplace AI still tends to move in the language of inevitability. Microsoft talks about Copilot as the new interface for work, consultancies sell transformation journeys, and executives worry that hesitation will be mistaken for decline. But inside a city administration, inevitability is not an implementation plan.Raisio’s project is interesting because it starts from an unglamorous premise: employees will not use AI well merely because the tenant admin has enabled it. They need time, examples, rules, and permission to learn without embarrassment. That is a softer thesis than the usual Copilot pitch, but it is also more realistic.
The city’s own framing puts data at the center of the story. Raisio’s new strategy elevated data as an enabler of day-to-day work and decision-making, alongside employee development. That matters because Copilot is only as useful as the organizational habits surrounding it: how documents are stored, how meetings are summarized, how policies are shared, how staff decide what is safe to paste into a prompt.
The launch also lands at a moment when Microsoft 365 Copilot is moving from novelty to infrastructure. Microsoft has spent the past two years embedding Copilot deeper into Word, Outlook, Teams, Excel, PowerPoint, the Microsoft 365 app, and Copilot Studio. The vendor story is that AI is becoming ambient. Raisio’s story is that ambient AI still needs very deliberate human scaffolding.
The City Hall Version of AI Is Messier Than the Enterprise Demo
A Finnish city is not a neat business unit with one revenue model, one customer profile, and one set of workflows. It is education, infrastructure, HR, communications, planning, resident services, welfare-adjacent coordination, procurement, administration, and public accountability all under one roof. The same AI assistant that helps draft a meeting summary may also touch sensitive internal planning, resident-facing language, or material governed by public-sector recordkeeping expectations.That is why the “people-first” label is more than marketing polish here. Municipal workers are not a homogeneous population of knowledge workers waiting to automate slide decks. Some are already fluent in Microsoft 365 habits; others may be approaching generative AI from a standing start. The city’s own participant feedback captures this plainly: one employee described starting “from zero” and later finding Copilot useful as an everyday assistant without replacing their own creativity or writing skills.
That last clause is doing important work. The adoption battle for AI in public administration is not merely about efficiency; it is about agency. Workers must believe the tool is there to reduce friction rather than silently redefine their value. If an AI rollout feels like surveillance, job redesign by stealth, or another management fad, usage metrics may rise for a quarter and then decay into performative compliance.
Raisio’s mayor, Eero Vainio, used a familiar historical analogy, comparing the arrival of AI to the anxiety around early industrial machinery. The spinning jenny comparison is imperfect, as all such analogies are, because generative AI is not a single machine introduced into one trade. It is a general-purpose interface being threaded through the administrative nervous system. Still, the political point is clear: the city wants its employees to approach AI with curiosity rather than fear.
Licenses Were the Easy Part
One of the most revealing details in the Raisio case is that Microsoft 365 Copilot licenses had already been purchased before the structured rollout began. That sequence will sound familiar to many IT departments. Procurement happens, enthusiasm peaks, and then the organization discovers that access is not adoption.Microsoft 365 Copilot is especially prone to that trap because it appears inside tools workers already use. On paper, that lowers the barrier. In practice, it can obscure the change. If Copilot is “just in Word” or “just in Teams,” managers may assume employees will naturally discover valuable use cases on their own.
Some will. Most will not, at least not consistently and safely. Prompting is not magic, but it is a learned workplace behavior. Asking Copilot to summarize a meeting, compare policy drafts, produce a first version of a resident communication, or find relevant information across Microsoft 365 requires judgment about context, quality, confidentiality, and verification.
Raisio’s CIO, Eero Rostiala, framed the employer’s role as enabling people to succeed. That is a useful corrective to the common “AI readiness” cliché. Readiness is not a property employees either possess or lack. It is built by the organization through training design, governance, data hygiene, management expectations, and visible peer examples.
The city’s decision to bring in Sogeti signals another reality of Copilot adoption: even if the software is bought from Microsoft, the transformation market around it is largely partner-led. Capgemini and Sogeti are not just installing a feature. They are selling a method for converting a software entitlement into changed behavior.
Training Became the Product
Raisio and Sogeti built the rollout around a three-stage learning path: introductory training for the whole organization, role-specific workshops, and a look ahead to automation. That sequence is sensible because it moves from shared language to practical application to future process redesign. It also avoids the mistake of beginning with automation before employees understand the assistant.The introductory layer gave staff a common baseline. In a multisector city organization, that baseline matters because otherwise every department invents its own AI folklore. One team may think Copilot can be trusted as a source of truth; another may avoid it entirely because of privacy anxiety; another may use it heavily but informally. Shared training gives the city a common vocabulary for both possibility and restraint.
The role-specific workshops are where the real adoption likely happened. Generic Copilot demos often fail because they show polished scenarios detached from the user’s actual inbox, document library, meetings, and service obligations. Raisio’s project worked from real work scenarios across different city functions, which is the difference between “AI can summarize text” and “AI can help me turn this messy meeting record into a usable internal note.”
The automation stage is more delicate. Once workers see Copilot as an assistant, the natural next question is which processes can be redesigned around AI and automation more broadly. That can unlock major productivity gains, but it also changes the risk profile. A bad draft is one thing; a bad automated workflow touching records, approvals, or resident communications is another.
Raisio appears to have treated that future-facing layer as orientation rather than a rush to wire agents into everything. That restraint is wise. The organizations that get the most from AI will not be the ones that automate first. They will be the ones that understand their processes well enough to know where automation belongs.
The Real Governance Work Happens Before the Prompt
The Capgemini case emphasizes that Raisio and Sogeti co-created AI usage guidelines, with privacy and security embedded in daily practices. That is exactly where municipal AI adoption must begin. Public-sector organizations cannot rely on after-the-fact caution when employees are using a tool that can summarize, transform, and generate content from workplace data.Microsoft 365 Copilot’s enterprise pitch rests heavily on the idea that it respects existing Microsoft 365 permissions. That is important, but it is not the same as governance. If permissions are messy, Copilot can make the mess more visible. If old files are overshared, poorly labeled, or stored in the wrong place, AI does not create the underlying problem, but it can make the consequences easier to encounter.
For sysadmins, this is the uncomfortable underside of the Copilot boom. The assistant is often marketed as a front-end productivity tool, but successful deployment depends on back-end discipline: identity, access control, retention, sensitivity labels, information architecture, endpoint posture, and user education. In other words, Copilot adoption is also a referendum on years of Microsoft 365 hygiene.
Raisio’s gradual model suggests a city trying not to confuse technical availability with organizational permission. Employees were not simply told to go experiment. They were given a safer learning space, shared materials, and guidance on appropriate use. That does not eliminate risk, but it does create a defensible path.
There is also a democratic-administration angle here. Cities serve residents who do not get to opt out of the public services they depend on. If AI is used to draft, summarize, or prioritize internal work, the organization needs clear norms for human review and accountability. “Copilot wrote it” cannot become an excuse in a city hall.
The Productivity Claims Are Modest, Which Makes Them More Credible
The reported benefits from Raisio are not revolutionary. Employees used Copilot to produce documents more easily, summarize large amounts of information, search more efficiently, and manage email and communications. In a hype cycle full of promises about autonomous agents and reinvented enterprises, that list may sound underwhelming.It should not. Those are exactly the mundane tasks that consume public-sector capacity. Municipal work is full of documents, meetings, emails, reports, resident communications, internal instructions, and policy fragments. If AI can shave time from those tasks without degrading quality or trust, the aggregate effect can be meaningful.
The key phrase is “without degrading quality or trust.” A faster bad document is not a productivity gain. A confident hallucinated summary is not administrative modernization. A resident communication that sounds polished but misses legal nuance may create more work than it saves.
Raisio’s training reportedly reduced hesitation while helping employees understand both the potential and limitations of AI. That dual outcome is important. The goal is not maximum enthusiasm. It is calibrated confidence. Workers need to know when Copilot is useful, when it must be checked, and when it should not be used at all.
This is where peer learning can be more powerful than top-down instruction. Employees are often more persuaded by a colleague showing how Copilot helped with a real task than by a vendor deck promising transformation. Raisio’s emphasis on shared experiences recognizes that AI adoption is partly social.
Microsoft Wins When Copilot Becomes Boring
For Microsoft, stories like Raisio’s are valuable because they normalize Copilot as a public-sector work tool rather than an experimental executive toy. The company has been steadily repositioning Microsoft 365 around Copilot, including renaming and rebranding parts of the Microsoft 365 experience to foreground the assistant. The direction of travel is obvious: Copilot is not meant to be an add-on forever.That creates tension for customers. Microsoft wants Copilot to become the default way work gets done. Organizations need it to become boring enough to govern. The first objective rewards speed and breadth; the second requires friction, policy, and staged adoption.
Raisio’s approach sits between those forces. The city is not rejecting Microsoft’s AI roadmap. It is accepting the direction while slowing the internal pace enough to make the change survivable. That is probably the most practical posture available to many public-sector IT leaders right now.
It also hints at why partners like Sogeti and Capgemini are central to the Copilot economy. Microsoft can ship features at cloud cadence, but it cannot sit with every HR department, infrastructure team, or school administration unit and translate those features into safe local practice. The partner’s role is to turn a horizontal product into situated work.
The risk, of course, is that “human-centered change management” becomes a reusable slogan pasted onto every AI deployment. In Raisio’s case, the details make the phrase more convincing: pre- and post-project surveys, role-specific workshops, shared materials, flexible scheduling, and usage guidelines. Those are not glamorous, but they are the machinery of adoption.
Where Windows Admins Should Pay Attention
For WindowsForum readers, the Raisio case is less about one Finnish municipality and more about the shape of the next wave of Microsoft 365 administration. Copilot adoption will increasingly arrive not as a single IT project but as a combined governance, training, licensing, and change-management program. The admin who treats it only as a license toggle will inherit the cleanup.The first pressure point is data exposure. Copilot’s usefulness depends on access to organizational content, which means existing oversharing can become more consequential. Before broad rollout, IT teams need to understand where sensitive content lives, who can access it, and whether permission models reflect current business reality rather than years of accumulated exceptions.
The second pressure point is user expectation. Employees may assume Copilot is a search engine, a writing authority, a confidential advisor, or a fully reliable analyst. It is none of those things in a simple sense. Training must explain not only what the tool can do, but what kind of human verification remains mandatory.
The third pressure point is support. Once Copilot becomes part of everyday work, help desks will receive questions that are not purely technical. “Why did Copilot find this file?” “Can I use it with this resident information?” “Why is this summary wrong?” “Can it automate this process?” These are governance and workflow questions disguised as tickets.
Raisio’s model implies that IT cannot own the rollout alone. The city paired technical competence with project management, communications, and departmental context. That is a useful pattern: Copilot governance should be co-owned by IT, legal or compliance functions, HR, communications, records management, and business units.
The Human-Centered Pitch Still Needs Hard Measurement
The strongest critique of Raisio’s story is that the public results remain qualitative. We hear that hesitation decreased, employees praised the training, and Copilot became useful for documents, summaries, search, and email. Those are encouraging signals, but they are not the same as a measured productivity outcome.That is not a flaw unique to Raisio. The entire enterprise AI market is still wrestling with measurement. Time saved is hard to prove, quality is harder, and downstream effects are harder still. If an employee saves 20 minutes drafting a document but spends 15 minutes checking it, is that a win? If a better summary prevents a misunderstanding, how should that be counted?
Public-sector measurement is even more complicated because the goal is not simply output per employee. A city must care about service quality, accessibility, transparency, employee well-being, legal compliance, and resident trust. AI that makes internal work faster but public communication worse is not a success.
Raisio’s stated intent to understand employees’ needs for future development work may be the right next metric. Early AI programs should not pretend to deliver final answers. They should reveal which workflows are ripe for improvement, which data practices need repair, and which employees need more support.
The next stage should therefore move from adoption sentiment to operational evidence. Which tasks are being improved? Where is Copilot not useful? Which departments are using it safely and frequently? Which use cases create the most review burden? Which data-access problems surfaced during training? These are the questions that separate durable transformation from a well-received pilot.
Raisio’s Copilot Lesson Is Small Enough to Be Useful
Raisio’s experience offers a grounded version of AI adoption precisely because it does not pretend that one training program transforms a city overnight. The lesson is procedural: buy the tool, but do not mistake the purchase for the change; train broadly, but make examples local; encourage experimentation, but define the guardrails first.- Raisio began its Copilot journey as part of a wider city strategy to make data more useful in daily work and decision-making.
- The city partnered with Sogeti, part of Capgemini, after already purchasing Microsoft 365 Copilot licenses, showing that deployment planning can matter as much as procurement.
- The rollout used introductory training, role-specific workshops, and automation awareness rather than assuming employees would discover valuable use cases alone.
- Nearly 100 employees participated directly, while shared materials and peer learning helped spread knowledge beyond the initial group.
- The most immediate benefits were practical office-work improvements, including drafting, summarization, information search, and email management.
- The project’s long-term value will depend on whether Raisio can connect early enthusiasm to measurable service quality, safer data practices, and better employee workflows.
References
- Primary source: Capgemini
Published: 2026-06-17T18:12:08.574459
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 - Official source: microsoft.com
Microsoft Ignite 2025: Copilot and agents built to power the Frontier Firm | Microsoft 365 Blog
Discover the latest Microsoft Ignite 2025 announcements, including new Microsoft 365 Copilot features, AI-powered agents, and Work IQ innovations.www.microsoft.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 - 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: techradar.com
Microsoft 365 Copilot will be automatically installed on 365 Clients in October | TechRadar
Microsoft is pushing the Copilot app on more userswww.techradar.com - Official source: marketplace.microsoft.com
Unleash a whole new way of working with Microsoft 365 Copilot
<p>Start your journey towards Human-centric, AI-powered workplace with Microsoft 365 Copilot services from Capgemini</p>marketplace.microsoft.com
- Official source: news.microsoft.com
- Official source: support.microsoft.com
Microsoft 365 -sovelluksen siirtyminen Microsoft 365 Copilot-sovellukseen | Microsoft Support
Microsoft 365 (Office) -sovellusta kutsutaan nyt Microsoft 365 Copilot-sovellukseksi. Lue lisätietoja muutoksesta ja siitä, mitä se merkitsee sinulle.support.microsoft.com - Official source: partner.microsoft.com
Capgemini makes data more humane (and helpful) with Microsoft Fabric
Capgemini uses Fabric for efficient, scalable, and innovative AI solutions, transforming data management and helping to drive business value for customers.partner.microsoft.com
- Related coverage: thinkcomputers.org
Microsoft to Mandate Copilot Installation on Most Windows PCs This October
Microsoft is mandating the installation of its Copilot AI app for Microsoft 365 desktop users starting October 2025, with limited opt-out options for personal users.thinkcomputers.org
