Where those foundations were solid, Copilot delivered. Where they were thin, no amount of enthusiasm could compensate.<\/p>\n\n\n\n
There was a quieter challenge in those early days that we rarely named: The<\/strong> prompt gap<\/strong>. Copilot worked brilliantly if you knew what to ask it, but most people did not know exactly what\u2014or how\u2014to ask. Successful adoption depended on teaching tens of thousands of our Microsoft colleagues to clearly phrase their intent, and every gain faded the moment their attention moved elsewhere.<\/p>\n\n\n\n It was akin to the frustrating experience of pushing a boulder up a hill only to watch it roll back down, over and over. The value of AI was real, but progress was slow.<\/p>\n\n\n\n Agentic AI changed the physics. Now, an agent doesn\u2019t need to be prompted at every step. It carries context, can take multi-step actions, and returns a result instead of a suggestion. The interaction shifted from prompting to delegating, from \u201chelp me draft this\u201d to \u201chandle this task for me.\u201d<\/p>\n\n\n\n That change rewired the incentives for AI adoption. People no longer had to translate every task into the perfect prompt. Instead, they could delegate meaningful work to agentic AI and stay in the loop as it progressed. The value became easier to see, because it showed up in completed work, not just generated content.<\/p>\n\n\n\n When we introduced Copilot agents such as Cowork<\/a> and Scout into our everyday work, we stopped having to repeatedly sell the idea. People no longer needed a campaign to understand the value of a digital colleague that could do the work; they just needed one good proof point from someone they trusted.<\/p>\n\n\n\n What surprised us most was how the spread of Cowork and Scout happened: Not top-down through a rollout plan, but sideways, desk to desk and team to team. Someone would use these agents to handle a recurring task, show how it worked in a meeting, and within a week three more colleagues had their own ideas for agentic workflows. The change management challenge had switched from driving adoption to creating the conditions for it\u2014providing fertile soil, as it were.<\/p>\n\n\n\n The organic spread of agentic AI was not an accident; it was a deliberate change in how we worked with our employees. In Microsoft Europe South we tested this change most fully with local teams, such as Customer and Partner Solutions Spain.<\/p>\n\n\n\n In a pilot program for this group, we didn\u2019t launch with an AI training initiative. Instead, we started with a pattern we had observed from hackathons and previous community sessions.<\/p>\n\n\n\n Previously, participants were enthusiastic about agentic AI, but often lacked meaningful end-to-end business problems to solve. Many of the strongest ideas overlapped with solutions already being built elsewhere, while other scenarios could be addressed through existing Copilot capabilities. Often, the biggest barrier was the perceived complexity of making sure an agent met security, privacy, accessibility, and responsible AI<\/a> requirements.<\/p>\n\n\n\n So, we changed our adoption efforts, focusing more on helping employees examine their own processes and identify workflows they could automate, and then assisting them in navigating through the compliance issues. We were asking people to challenge everything they did at work\u2014even the routines they had never thought to question\u2014and identify the most repetitive, manual, decision-heavy tasks that quietly consumed their week.<\/p>\n\n\n\n Across a series of ideation workshops, teams generated a wealth of agentic AI opportunities. Yet the true success of the program was not measured by the number of ideas produced, but by the rigor applied to each one. Every idea was scrutinized not only for its potential value and feasibility, but also based on a more fundamental question: Does this problem truly require an agent, or is there a simpler path to solving it?<\/p>\n\n\n\n As a result, our team introduced a basic but powerful principle: Build, Reuse, or Prompt<\/strong>.<\/p>\n\n\n\n Rather than assuming every problem required a new agent, opportunities were explicitly routed to the most appropriate path. Many ideas were already covered by existing solutions. Others could be solved through one or more of the following:<\/p>\n\n\n\n Only a subset of challenges justified building a new agent. This reduced duplication, clarified ownership, and ensured that effort was invested where genuinely new value could be created.<\/p>\n\n\n\n The assessment process itself became part of the adoption journey. Ideas were evaluated against existing agent usage, technical feasibility, role readiness, value measurement, and data and security considerations. We also applied an important principle borrowed from continuous improvement: Sometimes a process should be improved before<\/em> it\u2019s automated.<\/p>\n\n\n\n The shift from just \u201cknowing how to use AI\u201d to \u201cthinking differently about work\u201d was the real outcome.<\/p>\n\n\n\n By the end, a number of colleagues had moved from passive consumers of AI to active builders. The strongest agent ideas rarely came from technical teams. Instead, they came from the people closest to the work. Once someone questioned a process, identified friction, and built a solution to reduce or remove it, they rarely stopped at one idea.<\/p>\n\n\n\n Our pilot program also reinforced another lesson: AI adoption is not only about learning technology. It\u2019s about seeing how work can change. The next measures of success are whether those agents reduce friction, shorten cycle times, improve follow-through, and free people to focus on higher-value activities.<\/p>\n\n\n\n The tough questions we face today regarding AI adoption are about trust, orchestration, and control. Will our people feel comfortable with an agent acting on their behalf? How do dozens of independently built agents coordinate across an organization, instead of colliding? And how do we govern software that actually does the work?<\/p>\n\n\n\n To help answer these questions, agent governance became our center of gravity<\/a>. We learned to build these considerations into our process, beginning with our first interactions with field teams, and not just bolt it on at the end.<\/p>\n\n\n\n \u201cThe technology opens extraordinary possibilities, but the greatest impact comes when it is combined with the right methodology, governance, collaboration, and continuous learning. Transforming ourselves in this way is helping us become a more effective organization while also making us better equipped to guide our customers through their own AI transformation.\u201d<\/p>\nDoris Gomes, customer success lead, Microsoft Spain<\/cite><\/blockquote>\n\n\n\n At Microsoft, every agent has to tread the same garden path before it can be published through approved channels:<\/p>\n\n\n\n Framed early, these stopped being obstacles and became part of what it means to build well.<\/p>\n\n\n\n We also learned that agentic AI adoption accelerates when publishing feels achievable. Making the governance process visible early helped teams understand the path to production and reduced the uncertainty that often discourages experimentation.<\/p>\n\n\n\n Governing what grows also demands visibility, and this is where Agent 365 has become our control plane<\/a>. It lets us monitor every agent across all environments in the Microsoft tenant, making sure the ones appearing at the edge are discoverable, secured, and accountable rather than turning into invisible sprawl.<\/p>\n\n\n\n The principle is simple: Let ideas grow freely, but never lose sight of what your garden contains.<\/p>\n\n\n\n \u201cThe technology opens extraordinary possibilities, but the greatest impact comes when it is combined with the right methodology, governance, collaboration, and continuous learning,\u201d says Doris Gomes, a customer success lead for Microsoft Spain. \u201cTransforming ourselves in this way is helping us become a more effective organization while also making us better equipped to guide our customers through their own AI transformation.\u201d<\/p>\n\n\n\n The organizations that succeed in the next phase of AI adoption will not be the organizations that push the hardest. Success will be achieved by those that cultivate with care: helping employees rethink their work, creating the conditions for experimentation, and ensuring that what grows can scale safely.<\/p>\n\n\n\n \u201cAgentic AI is helping our teams move from working harder to working smarter. We are simplifying processes, improving operational quality, better leveraging information and insights, and creating more scalable ways to serve our customers.\u201d<\/p>\nPaco Salcedo, general manager, Microsoft Spain<\/cite><\/blockquote>\n\n\n\n This is the difference between pushing a boulder and planting a seed. A boulder needs continuous force. A seed needs the right conditions\u2014good soil, a little light, a healthy environment. The plant then grows on its own and reseeds.<\/p>\n\n\n\n We are still early on the path to the Frontier Firm<\/a> future, and there are many ways for us to keep growing and improving. Trust has to be earned, governance has to keep pace with autonomy, and not every seed takes. But with the right nurturing, a brighter agentic future can flower.<\/p>\n\n\n\n \u201cAgentic AI is helping our teams move from working harder to working smarter,\u201d says Paco Salcedo, a general manager for Microsoft Spain. \u201cWe are simplifying processes, improving operational quality, better leveraging information and insights, and creating more scalable ways to serve our customers.” <\/p>\n\n\n\n Salcedo points to innovations such as MSX-IQ, an AI assistant built by our team for Microsoft sellers that provides a \u201cchat with your pipeline\u201d experience and is now used across multiple countries. Its adoption demonstrates how giving people the right tools, governance, and support can accelerate meaningful business transformation.<\/p>\n\n\n\n Here are some tips to keep in mind as you continue to grow your own agentic garden at your organization:<\/p>\n\n\n\n Two years ago, AI adoption at Microsoft felt kind of like pushing a boulder up a hill. We had the technology, the licenses, and the leadership mandate, but when it came to cultural embrace of this new era, we didn\u2019t yet have the momentum to get that rock to the top. In those early days, […]<\/p>\n","protected":false},"author":216,"featured_media":25506,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_hide_featured_on_single":false,"_show_featured_caption_on_single":true,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[199,924,137,904,928,922,237,927,937],"coauthors":[873],"class_list":["post-25505","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-digital","tag-ai","tag-automation","tag-change-management","tag-customer-zero","tag-developer-and-automation","tag-digital-worker","tag-governance","tag-modern-work","tag-security-and-governance","m-blog-post"],"yoast_head":"\nHow the physics changed<\/h2>\n\n\n\n
Organic adoption: Cultivating the garden<\/h2>\n\n\n\n
\n
Trust, orchestration, and tending to what grows<\/h2>\n\n\n\n
![\"A](\"https:\/\/cm-edgetun.pages.dev\/insidetrack\/blog\/uploads\/prod\/2026\/09\/Doris-Gomes.png\")
<\/figure>\n\n\n\n\n
\n
Growing the agentic future<\/h2>\n\n\n\n
![\"A](\"https:\/\/cm-edgetun.pages.dev\/insidetrack\/blog\/uploads\/prod\/2026\/09\/Paco-Salcedo.png\")
<\/figure>\n\n\n\n\n
Key takeaways<\/h3>\n\n\n\n
\n
Try it out<\/h3>\n\n\n\n
\n
Related links<\/h3>\n\n\n\n
\n