As AI reshapes how we work and live, it brings with it both transformative potential and complex challenges. Across the industry, concerns about bias, safety, and transparency are growing.

At Microsoft, we believe that realizing AI’s benefits requires a shared commitment to responsibility—one we take seriously. As a result, we aren’t just creating AI solutions. We’re taking the lead on infusing responsible AI principles into our technology and organizational practices.

Prioritizing responsible AI across Microsoft

The most impressive AI-powered capabilities in the world mean nothing if people don’t trust the technology. Microsoft and many of our customers across all industries are working to strike the right balance between innovation and responsibility.

“We’re on a multi-year journey born out of the need to support innovation—and do it in a way that builds trust. Along the way, we’ve continued to iterate and evolve the program through a series of building blocks.”

Mike Jackson, head of AI Governance, Enablement, and Legal, Microsoft Office of Responsible AI

IT leaders and CXOs aren’t just deploying AI tools. They’re also thinking of the right guardrails to implement around those tools as their organizations mature. Meanwhile, developers and deployers want to be sure they’re building and implementing AI solutions within the bounds of responsibility.

As an organization that’s mapping the frontier of AI while creating business-ready tools for our customers, Microsoft is shaping the global conversation on responsible AI. We don’t only accomplish that through policy and governance, but also by embedding responsibility into the ways we build, deploy, and scale AI.

Laying the foundation for this work is the duty of our Office of Responsible AI (ORA). This team brings policy and governance expertise to the responsible AI ecosystem at Microsoft.

“We’re on a multi-year journey born out of the need to support innovation—and do it in a way that builds trust,” says Mike Jackson, head of AI Governance, Enablement, and Legal for the Office of Responsible AI. “Along the way, we’ve continued to iterate and evolve the program through a series of building blocks.”

ORA advances AI development, deployment, and secure and trustworthy innovation through governance, legal expertise, internal practice, public policy, and guidance on sensitive uses and emerging technology. The team focuses on empowering innovation while ensuring it falls within Microsoft’s governance, compliance, and policy guardrails.

ORA also partners closely with product and engineering teams as well as other trust domains like privacy, digital safety, security, and accessibility. The team created our Microsoft Responsible AI Standard, the cornerstone of our governance framework, and ensures internal AI initiatives align with it.

The Responsible AI Standard translates our six principles into actionable requirements for every AI project across Microsoft:

ORA reports into the Microsoft Board of Directors and collaborates with stakeholders and teams across the company to operationalize these principles, implementing policies and practices that apply to AI applications. They determined that every AI initiative should undergo an impact assessment to ensure it aligns with the standard.

If ORA is our compass for responsible AI, our companywide Responsible AI Council has its hands on the steering wheel.

The council, led by Chief Technology Officer Kevin Scott and Vice Chair and President Brad Smith, was formed at the senior leadership level as a forum and source of representation across research, policy, and engineering. It provides leadership, strategic guidance, and executive support and sponsorship to advance strategic objectives around innovation and responsible AI.

“ORA has established clear principles and a step-by-step assessment framework and tool. Our responsibility is to rigorously follow this process and ensure compliance across our products and initiatives.”

Naval Tripathi, principal engineering manager and co-lead, Microsoft Digital Responsible AI team

Under the council’s guidance, responsible AI CVPs, division leaders, and a network of responsible AI champions across the company operationalize the implementation of our Responsible AI Standard and compliance with our policies.

The structure of these teams is straightforward.

Every division has a designated CVP and division lead to steer the work and connect their team to the overarching Responsible AI Council. Within those divisions, each organization has a lead responsible AI champion or a set of co-leads to steer their team of champions. Those champions act as subject matter experts, reviewers for the impact assessment process, and points of contact for the teams developing AI initiatives.

Implementing AI governance within Microsoft IT

As members of the company’s IT organization, Microsoft Digital’s responsible AI division lead and champion team have a special role to play. They helped develop a critical internal workflow tool, which has now become a mandatory part of our responsible AI assessment process.

“The key is to ensure full alignment of responsible AI practices with ORA,” says Naval Tripathi, principal engineering manager and co-lead for Microsoft Digital’s Responsible AI Team. “ORA has established clear principles and a step-by-step assessment framework and tool. Our responsibility is to rigorously follow this process and ensure compliance across our products and initiatives.”

This tool logs every project, guides AI developers through initial impact assessments all the way to final reviews, and facilitates those workflows for champions.

“As organizations develop a diverse ecosystem of AI agents, often created by multiple engineering teams, it becomes essential to establish a standardized evaluation process. This ensures every agent adheres to enterprise-level standards before we deploy and distribute it to end users.”

Thomas Po, senior product manager, Microsoft Digital

By streamlining the process through a unified portal, the tool increases efficiency and minimizes errors that can arise from manual processes. It also encourages teams to make responsible AI part of the software development lifecycle (SDL) itself, not a hurdle or an afterthought.

“As organizations develop a diverse ecosystem of AI agents, often created by multiple engineering teams, it becomes essential to establish a standardized evaluation process,” says Thomas Po, a senior product manager working on Campus Services agents. “This ensures every agent adheres to enterprise-level standards before we deploy and distribute it to end users. That makes it more manageable in the long term, and having it all in one tool gives us more transparency.”

Our unified internal workflow looks like this:

• Project initiation and system registration: During the design phase for an AI initiative, the engineering team accesses the portal and registers a new AI system. From there, they fill out fields with crucial information, including a title, description, the developer team’s division, whether the project will include internal or external resources, the relevant champion who should review their initiative, and other details. Within this initial form, different scenarios will trigger different review parameters and requirements, for example, when a team intends to publish a tool externally or engage with sensitive use cases.
• Release assessment: After the system registration is complete, the team initiates the release assessment, a much more thorough review designed to ensure the AI-powered solution is ready to go live. At this point, the engineering team needs to provide detailed documentation. That includes the volume and kinds of data the system will use, potential harms and mitigations, and more. A release assessment includes experts in our Office of Responsible AI, Security, Privacy, and other teams, who review sensitive use cases or initiatives that include generative AI.

If the project clears all the requirements and reviews, it’s ready to go live. Crucially, we don’t think of these stages as a set of hurdles teams need to clear to complete their projects. Instead, the process guides engineering teams through the design elements they need to consider and provides opportunities for feedback from subject matter experts.

“The tool captures all the requirements from ORA and incorporates them into a developer-friendly workflow,” says Padmanabha Reddy Madhu, principal software engineer and responsible AI champion for Employee Productivity Engineering in Microsoft Digital. “It’s also a great way to pull AI champions into the design phase so we can support our colleagues’ work.”

With more than 80 AI projects currently underway across Microsoft Digital, logging and streamlining are essential. Teams are working on all kinds of ways to boost enterprise processes and employee experiences, like the following examples from Campus Services that users can access through our Employee Self-Service Agent:

• A facilities agent helps employees take action when they discover an issue at one of our buildings, like a burnt-out light, a spill, or physical damage. The agent creates a ticket to alert a Facilities team so they can resolve it and allows the submitter to follow up on progress.
• A campus event agent makes onsite gatherings like talks and Microsoft Garage build-a-thons more discoverable through simple queries. Using this agent, employees can more easily discover and plan around events that interest them, adding value to the in-person experience and incentivizing community.
• A dining agent addresses the challenges of multiple on-campus restaurants featuring menu options that shift daily. Employees can use natural language queries like “Where can I get teriyaki today?” The agent does the rest. This kind of agent can be especially helpful for employees with allergies or dietary restrictions, providing a boost to accessibility for the on-campus dining experience.

“AI is rapidly becoming a standard part of how we build and operate. As adoption accelerates, Responsible AI becomes imperative and enables teams to innovate at speed while maintaining safety and accountability at scale.”

Qingsu Wu, principal group product manager, Microsoft Digital

Our policies and practices have embedded a culture of responsibility and trust into our internal AI development processes. With that trust comes the confidence to experiment.

“AI is rapidly becoming a standard part of how we build and operate,” says Qingsu Wu, principal group product manager in Microsoft Digital. “As adoption accelerates, Responsible AI becomes imperative and enables teams to innovate at speed while maintaining safety and accountability at scale. By embedding Responsible AI into our engineering practices, teams have the clarity and confidence they need to manage risk proactively and deliver value without compromising safety or trust.”

Far from thinking of responsible AI assessments as an administrative or policy burden that creates additional work, teams now recognize their benefits. They look at the process as an extra set of eyes from a trusted partner. By minimizing legal and compliance risks through our Responsible AI Council’s expertise, our teams save time and stress, and we avoid problems like delayed releases or rollbacks.

“What we’re doing is entirely novel in the tech world. Microsoft is really the lead learner here, and we have a passion for corporate citizenship that we’re embedding in our tools.”

Jamian Smith, principal product manager and co-lead, Microsoft Digital Responsible AI team, Microsoft Digital

Lessons learned: Embedding responsible AI into our development efforts

Throughout this process, we’ve learned lessons that will be helpful for other organizations just beginning their AI journeys:

• We empowered early adopters and enthusiasts as responsible AI champions. They act as anchors and resources for developers who use AI, so we made sure they had the knowledge and training they needed to unlock downstream value.
• Culture has been crucial to our success, especially our growth mindset and our focus on trust. Emphasizing these aspects of our company culture helped us embed responsible AI into core SDL processes and naturalize it on our engineering teams.
• Processes are one thing, and tooling is another. If your responsible AI assessment workflow isn’t attuned to your needs, simply building a review portal tool won’t get you the rest of the way. First, we thought about the process we needed to put in place to solidify responsible AI practices and support our teams’ work. Then we built a tool that supports those workflows as easily and seamlessly as possible.
• Accuracy is reliant on data, and data has a tendency to reflect the biases of the humans who organize it. It’s necessary to correct bias actively through introspection and testing.

“What we’re doing is entirely novel in the tech world,” says Jamian Smith, principal product manager and co-lead for Microsoft Digital’s Responsible AI team. “Microsoft is really the lead learner here, and we have a passion for corporate citizenship that we’re embedding in our tools.”

As your organization begins to experiment with its own AI projects, take these concrete steps to infuse responsibility into the solutions you create:

1. Establish a strong foundation based on core principles and standards that align with your organizational culture. The Microsoft Responsible AI Standard is a great place to start because it reflects our experience and the expertise we’ve built as AI technology leaders and providers.
2. Seek out the activators across your organization: people with a passion for AI, security, transparency, and other challenge areas, along with a willingness to learn and the ability to lead. Think about how to place them in both centralized and distributed positions.
3. With the rapidly evolving regulatory climate around AI, it’s crucial to have a broad understanding of compliance and continue to follow its developments. Involve dedicated regulatory, compliance, and legal professionals in researching and monitoring global standards while communicating that information to your organization, particularly through training and updates that help teams adapt new regulations into their core processes.
4. Create a process for responsible AI assessment. Consider ways to break it into stages that propel projects forward rather than hindering them. Enlist the right people to assess projects, and consider tooling that streamlines actions for both creators and assessors. Our AI Impact Assessment Guide can help you get started.
5. Benefit from pioneers in the space, including our experts at Microsoft. Our journey has produced ready-to-use resources that can accelerate your progress. Examples include our Responsible AI Toolbox for GitHub, hands-on tools for building effective human-AI experiences, and our AI Impact Assessment Template.

“It’s not about how fast you can move, but how prepared you are. Responsible AI processes might seem like speed bumps, but ultimately they’re accelerators.”

Naval Tripathi, principal engineering manager and co-lead, Microsoft Digital Responsible AI Team

Building your capacity to create AI tools responsibly won’t happen without careful planning and strategy. As part of that process, embed responsible AI into your development workflows by emulating the practices we’ve pioneered at Microsoft.

“It’s not about how fast you can move, but how prepared you are,” Tripathi says. “Responsible AI processes might seem like speed bumps, but ultimately they’re accelerators.”

By prioritizing responsible AI, businesses of all kinds, all over the world, can ensure that the AI revolution is a truly human movement.

Key takeaways

These insights can help you as you begin your own journey through responsible AI:

• Realize that this isn’t just a technical transition. It’s also a gradual evolution and an ongoing journey.
• Work with people across your organization to establish goals and standards, because different disciplines bring different expertise and insights to the table. This will also align your responsible AI standards with your organizational values.
• Start with the basics and build from there. Establish principles, create processes, and construct tooling around those structures.
• A wide array of tooling is readily available in the world of AI. Seek out providers that model responsible values.
• Lean on your existing experts across privacy, security, accountability, and compliance. Their skills will be crucial in this new technological landscape.
• Conducting your own responsible AI groundwork is crucial, but you can also partner with Microsoft. We run on trust, and we’ve thought about these issues to pave the way for your success. Follow our lead, consider the best ways to adapt our lessons to your organization, and come to us with questions.

Try it out

Learn more about our responsible AI principles here at Microsoft.

Related links

• See how we’re responding to the AI revolution with an AI Center of Excellence.
• Learn how a data council is powering our unified data strategy at Microsoft.
• Read our guide to becoming a Frontier Firm in the age of AI.
• Explore ways that we’re accelerating employee support with our new Employee Self-Service Agent.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post Responsible AI: Why it matters and how we’re infusing it into our internal AI projects at Microsoft appeared first on Inside Track Blog.

At an organization the size of ours—with a global workforce, massive cloud footprint, and millions of identities to protect—relying on passwords wasn’t a sustainable security posture. We needed something stronger, simpler, and more secure.

This led to the introduction of Windows Hello for Business, which was first built into Windows 10 and then Windows 11. Windows Hello for Business replaces traditional passwords with hardware‑backed keys tied to a user’s device.

So, instead of typing a “secret phrase” that can be phished or leaked, our employees authenticate with biometrics or a PIN that never leaves the device. It’s fast, intuitive, and—most importantly—resistant to the kinds of attacks that plague password‑based systems.

“This wasn’t just a technology shift—it was a structural change in how we establish trust across the organization. The lessons we learned offer a practical blueprint for any organization looking to strengthen their security while also reducing friction for their workforce.”

Abu Kabir, director of IT service management, Microsoft Digital

Rolling out passwordless authentication at a large company like ours took more than just introducing new technology. It also required that we come up with a new way to onboard our employees securely, no matter where they work.  

The first step we took toward passwordless credentials was to create Identity Pass, which included an emphasis on Day 1 authentication (on a new employee’s first day at Microsoft). By combining strong identity proofing, a Temporary Access Pass (TAP), and automated onboarding workflows, we forged an identification system where employees could unbox their device, sign in securely, and register their credentials without ever needing a password.

The result wasn’t just a smoother user experience.

“This wasn’t just a technology shift—it was a structural change in how we establish trust across the organization,” says Abu Kabir, a director of IT service management in Microsoft Digital, the company’s IT organization. “The lessons we learned offer a practical blueprint for any organization looking to strengthen their security while also reducing friction for their workforce.”

How we launched passwordless authentication

To understand how we worked through the details of passwordless authentication, it’s helpful to explain how it was implemented in the first place.

Our passwordless security system includes several components, including face or fingerprint, a PIN tied to their device, and a physical security key (like a YubiKey), but this story focuses these on two:

• Identity Pass: the internal system for secure, passwordless onboarding and recovery
• Windows Hello for Business: the phishing‑resistant credential that Identity Pass helps users register

Identity Pass

Identity Pass, which is only used internally here at Microsoft, uses several tools to “bootstrap” the user, which is the first step in establishing trust among a user, a device, and an identity system. It’s the moment when you go from “nothing trusted” to “something trusted.” Everything that happens afterward depends on getting that moment right.

Identity Pass relies on three core elements:

• Verified ID is what we use internally to establish proof of identity. It’s an initial step and is valid for 30 days.
• Temporary Access Pass (TAP) establishes authentication.
• Conditional access enforces policy.

Identity Pass is where risk signals matter most, because onboarding and recovery are the moments when identity assurance is weakest. Those risk signals include:

• Authentication behavior detection: If a user tries to redeem a TAP or Verified ID from an unusual location, device, or pattern, Authentication Behavior Detection can flag a sign in as risky. Identity Pass can then require stronger identity proofing or block the flow.
• Global high‑risk detection: If our threat intelligence determines the user is likely compromised, Identity Pass will not allow TAP issuance or passwordless registration until the risk is remediated.
• Strong fraud indicators: If the user’s session or token shows signs of fraud (token replay, hijacking, malicious infrastructure), Identity Pass will force remediation and block bootstrap flows.
• Risk‑based identity assurance: This is the decision engine that takes security signals and determines what level of assurance is required. For example:
  • Low risk = allow TAP issuance
  • Medium risk = require Verified ID reproofing
  • High risk = block and escalate

Identity Pass is essentially the front door where these signals decide whether a user can even begin the passwordless journey.

Windows Hello for Business

Windows Hello for Business is the strong, phishing‑resistant credential that Identity Pass helps users register. Once this is in place, the risk signals listed above continue to influence authentication.

• Authentication behavior detection: Windows Hello for Business sign‑ins are evaluated like any other. If the user suddenly authenticates from an impossible location or unusual device, this system flags it as a sign‑in risk.
• Global high‑risk detection: If our detects a high‑confidence compromise, Windows Hello for Business sessions can be revoked via Continuous Access Evaluation. The user then reregisters through Identity Pass.
• Strong fraud indicators: If a Windows Hello for Business token is replayed or misused, this system triggers immediate revocation and forces secure recovery.
• Risk‑based identity assurance: This determines whether Windows Hello for Business alone is sufficient, or whether the user must step up to a stronger method based on risk.

Windows Hello for Business is the credential, but the risk signals determine whether that credential is trusted at any given moment.

What we learned: Rollout and implementation

While our toolsets and protocols offer a clear path for any organization moving toward passwordless authentication, transferring users from a typical user/password security setup can have a variety of challenges—especially at the outset.

Devices, environments, and remote work all matter

When an organization adopts identity‑based, passwordless authentication, one of the first realities it confronts is that the onboarding experience isn’t uniform. Employees don’t all show up with the same hardware, the same operating system version, or the same security capabilities. That diversity has a direct impact on how smoothly a user can complete the initial Day 1 setup and register a strong, phishing‑resistant credential.

“It’s not one-size-fits-all. The onboarding experience can be different by platform, version, and device. The further away you get from a homogenized environment, the more complexity you introduce.”

Matt Scott, senior IT service manager, Microsoft Digital

Device and platform diversity is one of the defining factors in designing a successful passwordless onboarding experience. Any organization adopting identity‑based authentication needs an onboarding system that can adapt to a wide range of hardware, OS versions, and security capabilities while still enforcing a consistent, high‑assurance security model.

Identity proofing and credential registration don’t look the same across platforms. A laptop might support credential setup directly at the login screen, while a mobile device might require an app‑based flow, and a non‑traditional platform might rely entirely on browser‑based enrollment. The underlying model stays consistent, but the user experience varies depending on where the user begins.

“It’s not one-size-fits-all,” says Matt Scott, a senior IT service manager in Microsoft Digital. “The onboarding experience can be different by platform, version, and device. The further away you get from a homogenized environment, the more complexity you introduce.”

Support volume

With Identity Pass in place, we have seen dramatic reductions in password reset volume (80%), onboarding delays, and help desk tickets related to account access. At the initial rollout stage, however, most organizations should anticipate a temporary spike in support needs.

“We expected an increase in volume, because we had recently gotten to 99% in terms of users being identified through Phish-Resistant Multi-Factor Authentication,” Scott says. “In reality, what’s happening is you have a lot of users who are unhappy with the experience as part of the move to a passwordless environment.”

No matter how solid the argument is for a passwordless approach or how cleanly an organization implements it, our experience shows that organizations should expect initial confusion from employees and increased pressure on support teams.

“Moving into a passwordless environment is obviously good for everyone, but we needed to make it easier for users to get the information they needed,” Scott says. “It’s not just one fell swoop of moving from password to passwordless. It’s truly a journey. And it’s very important that change management is part of that journey.”

Helping employees help themselves

Another key learning during our implementation of passwordless authentication was the importance of accessible documentation. This gives users who have yet to establish their identity credentials a way to get unblocked without having to immediately call IT support.

That documentation must stay accurate over time, so it’s crucial to build a governance strategy that ensures updates are made quickly as new devices, platforms, and scenarios emerge.

“During onboarding, if there’s a problem and a user is locked out, they may not have access to the corporate network,” Kabir says. “Having a site that they could access, with actual instruction based on which device they’re using and that shows them how to get past key blockers, was very helpful.”

Maintaining a direct line to leadership in order to help unblock lingering change requests also proved to be essential. In one case, bugs lingered in the engineering queue for days, even weeks, because the escalation path was limited (by design).

“Approval requests were blocked, and so approvals needed to be accelerated to the skip-level approver,” Kabir says. “We were able to move fast to fix that, because we had a clear understanding of the pain that folks were feeling on our side and could effectively communicate that to leadership.”

Short-term pain, long-term gain

The impact has been significant. Instead of spending long cycles troubleshooting forgotten passwords or manually verifying user identities, IT teams can focus on higher‑value work: strengthening identity protection, refining automation, and improving the user experience. This shift not only reduces operational overhead, it also aligns with our Zero Trust principles by removing weak authentication steps from the identity lifecycle.

For employees, the experience is equally transformative. New hires can unbox a device, authenticate using a TAP delivered through a secure Verified ID workflow, and immediately register passwordless methods like Windows Hello for Business. Although the onboarding journey may vary across platforms and devices, the process is fast and intuitive.

For existing users who lose access—whether due to a forgotten PIN, a lost device, or a credential reset—Identity Pass provides a self‑service recovery path that avoids the delays and security risks of traditional reset processes.

Our experience demonstrates that when these processes are redesigned around strong, hardware‑backed, phishing‑resistant credentials, organizations gain both security and efficiency. The result is a more resilient identity foundation that supports the realities of modern work.

Key takeaways

Here are some suggestions for getting started with Windows Hello for Business and Day 1 onboarding:

• Passwordless authentication start with strong identity proofing. Establishing user identity up front is essential to creating a secure foundation for all future authentication.
• Day 1 onboarding is the riskiest moment. The initial bootstrap step is where trust is first established, and risk signals matter most.
• Temporary Access Pass replaces temporary passwords. TAP provides a secure, time‑bound way for users to authenticate and register passwordless credentials without exposing the network to attack.
• Device and platform diversity shapes the user experience. Different hardware, operating systems, and compute environments require flexible onboarding paths that still enforce consistent security.
• Support demand spikes before it drops. Organizations should expect short‑term confusion and increased help‑desk volume before passwordless security benefits fully materialize.
• Long‑term gains are significant. Once deployed, passwordless authentication reduces operational overhead, strengthens security, and improves the user experience across the identity lifecycle.

Try it out

• Explore Windows Hello for Business.
• Check out Microsoft identity and access management services.

Related links

• Learn more about implementing strong user authentication with Windows Hello for Business.
• Read about phishing-resistant authentication with Microsoft Entra ID.
• See how Microsoft is using AI to reinvent network security.
• Discover how we developed a Zero Trust security model at Microsoft.
• Find out how Windows Hotpatch transformed security and compliance at Microsoft.
• Learn how Microsoft hardened our defenses with Microsoft Baseline Security Mode.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post Getting started with Windows Hello for Business and Day 1 authentication at Microsoft appeared first on Inside Track Blog.

Maybe you’re a product manager with a backlog that you can’t ever get to. Perhaps you’re a designer who can never seem to get engineering resources assigned to you. Or maybe you’re a program manager who routinely gets stuck copying data between systems by hand.

These are common challenges knowledge workers face everywhere, including here at Microsoft. A year ago, AI enthusiasts knew agents with tools could fix these problems—they just didn’t know where to start.

Some of our employees in Microsoft Digital, the company’s IT organization and Customer Zero for the company, took a grassroots approach to solving this problem. They built something called the Frontier Forge, our pro‑code “harness” that enables our less-technical employees to get work done with agents. They use it to quickly build agentic instructions and instantly share their solutions with peers, which accelerates our productivity across the company.

The Frontier Forge represents a cultural shift in how our product managers, designers, program managers and other “I’m not an engineer but I want to build stuff” employees now apply AI tools directly to their work.

What first began as a hackathon experiment has evolved into a thriving Microsoft-internal community with nearly 100 engaged contributors, an active Teams channel, and a GitHub repository filled with templates, learning modules, and ready-to-use AI agents. The impact is measurable: Forecasting, backlog grooming and communication tasks that collectively took weeks now take hours or minutes.

“I saw myself and others spending too much of our time on data wrangling and admin tasks when we wanted to be strategizing. Nobody was building what felt truly agentic. So, we did it ourselves.”

Brett Reifers, senior product manager, Microsoft Digital

Employees who never saw themselves as technical are now building sophisticated data visualizations, automating workflows, creating prototypes, and generating learning modules. These were capabilities previously reserved for specialized engineering teams.

The “Forge” is where it’s all happening now.

From a hackathon to a movement

In early 2025, Brett Reifers, a senior product manager in Microsoft Digital, spotted a problem he couldn’t ignore. His peers, smart and driven product managers, kept asking the same question: “How do I use agents for my actual work?”

Beginner tutorials about prompt engineering felt trivial. Advanced agents with tools assumed engineering expertise. The middle ground, where AI meets real jobs, didn’t exist.

“I saw myself and others spending too much of our time on data wrangling and admin tasks when we wanted to be strategizing,” Reifers says. “Nobody was building what felt truly agentic. So, we did it ourselves.”

So, Reifers partnered with colleague Humberto Arias, a senior product manager in Microsoft Digital whose work explores the intersection of AI and productivity. Arias had been independently researching agentic solutions that could click through interfaces, open applications, and complete tasks autonomously.

The insight that unlocked everything came from a deceptively simple observation:

“Everything on the internet is a form—every site, mobile app, every click,” Reifers says. “If agents could fill out my forms in Azure DevOps, they could handle any web-based task.”

They pitched the concept of Copilot fulfilling form-based processes as an entry for Microsoft’s annual hackathon to Sean MacDonald, partner director of product management in Microsoft Employee Experience. MacDonald immediately recognized its potential.

“My reaction was simply, ‘This sounds amazing,’” MacDonald says. “This solution was exactly what we needed.”

The event proved agents could automate PM workflows: managing Azure DevOps items, generating summaries, and querying data systems. After the hackathon validated the concept, Arias suggested pushing the project to GitHub for wider exposure. Reifers then used GitHub Copilot itself, recursively using the very tools they were building, to open source the first Frontier Forge repository in 15 minutes.

A pro-code environment with natural language accessibility

The Forge combines GitHub Copilot, Visual Studio Code (VS Code), and MCPs into a framework that makes professional development tools easily accessible to non-engineers.

“The Frontier Forge is a place where you can learn regardless of your skill level. You can adopt what’s out there, even if you don’t know where to start.”

Sean MacDonald, partner director of product management, Microsoft Employee Experience

The core idea: Give employees a workspace seeded with community-created templates, learning modules, and custom agents tailored to Microsoft Digital contexts. Then let them build from there.

For MacDonald, the Forge has proven to be an accessible entry point for almost anyone, regardless of experience.

“The Frontier Forge is a place where you can learn regardless of your skill level,” MacDonald says. “You can adopt what’s out there, even if you don’t know where to start.”

An architecture for context-first AI

The technical architecture of The Frontier Forge leverages three layers simultaneously:

• VS Code provides the enterprise managed workspace where everything happens.
• GitHub Copilot offers chat functionality and AI assistance, with access to multiple models including Claude, GPT, and Gemini.
• Tools like Model Context Protocols (MCPs) act as standardized connectors that let agents access tools, data, and services locally. This unlocked what Copilot could decide and do with user approval.

“With GitHub Copilot and MCPs, there are literally no boundaries. It’s hard to explain just how transformational this can be for a product manager. Whatever you ask is transformed into code with a purpose, allowing you to do something you couldn’t before.”

Humberto Arias, senior product manager, Microsoft Digital

The MCPs connect to services like Azure DevOps (for roadmap planning and backlog management), Microsoft Documentation, Figma (for design work), and dozens of other platforms that are essential to product manager workflows. New MCPs appear daily, expanding capabilities organically as the community builds them.

Employees can even ask GitHub Copilot to build custom MCPs for services lacking official integrations. When Arias needed a PowerPoint creator that didn’t exist, he asked GitHub Copilot to create one.

“With GitHub Copilot and MCPs, there are literally no boundaries,” Arias says. “It’s hard to explain just how transformational this can be for a product manager. Whatever you ask is transformed into code with a purpose, allowing you to do something you couldn’t before.”

The shift from prompt engineering towards context engineering is another reason why the Forge works. Its workspace settings, agent instructions, skills and hooks provide a harness with guardrails that help colleagues adopt and use this.

The Forge provides a curated starting point: Microsoft Digital-specific templates, governance frameworks, security guidelines grounded in Microsoft’s Responsible AI framework, and working examples employees can immediately use and modify.

Transformational impact

The productivity gains generated by The Frontier Forge are very real. Our employees report saving weeks or even months on certain projects, especially those that previously required extensive manual work or specialized technical skills.

Case in point: Laura Oxford, a senior content program manager in Microsoft Digital, had four years’ worth of Excel files and communication metrics reports. She had always intended to use the data to create marketing forecasts, but she could never find the necessary time or resources to perform the analysis.

“The key to creating the agent was going deep into the context. It was an iterative conversation, going back and forth to fine-tune the agent until I was consistently getting the output I wanted. But it truly was just a conversation—no tech skills needed.”

Laura Oxford, senior content program manager, Microsoft Digital

Through iterative, conversation-based prompting, Oxford’s agent analyzed patterns, created projections, and produced visualizations. Oxford now has a robust historical analysis that enables prediction of future campaign performance.

“The key to creating the agent was going deep into the context,” Oxford says. “It was an iterative conversation, going back and forth to fine-tune the agent until I was consistently getting the output I wanted. But it truly was just a conversation—no tech skills needed.”

Drafting clear, executive-ready communications for complex initiatives was what brought Mark Stratford, a senior product manager with the email and calendaring service team in Microsoft Digital, to the Forge.

Before the Forge, communicating status updates to leadership meant he had to manually synthesize data from CSVs, track several approval chains at once—often in messy emails—and iterate on visualizations for what seemed like days and days.

Put more succinctly, these tasks are time-consuming chores that are perfect for AI.

“The Forge’s architecture changes how you think about the problem,” Stratford says. “Instead of iterating on prompts, you declare intent and desired outcome. The Forge’s architecture handles the rest.”

Using this pattern, Stratford created:

• Over a dozen interactive dashboards for portfolio roadmaps, migration tracking, and service health monitoring.
• Approval matrix visualizations mapping multi-stakeholder sign-off dependencies.
• Data analysis pipelines transforming raw telemetry into executive-ready narratives.

“I didn’t need to fight ambiguity or handhold the model. The architecture gave the agent a stable, skills-driven foundation from the start, which dramatically accelerated development time and improved clarity.”

Mark Stratford, senior product manager, Microsoft Digital

The Forge’s clean separation between intent, constraints, tools, and data inputs eliminated the prompt-tuning loop. Stratford mapped his objectives into the agent framework once, relying on built-in structure and guardrails.

His analysis and drafting time dropped from days to minutes. Outputs like roadmaps and data visualizations went directly into decision workflows with no manual cleanup required.

“I didn’t need to fight ambiguity or handhold the model,” Stratford says. “The architecture gave the agent a stable, skills-driven foundation from the start, which dramatically accelerated development time and improved clarity.”

Building community and sharing knowledge

A simple continuously improving repository has grown into something larger: a community of nearly 100 enthusiasts. Contributors are building templates, learning modules, and specialized MCPs tailored to their job functions. Teams are sharing wins and unlocked achievements.

“At its core, The Frontier Forge is an open-source, community‑driven experience. It’s a safer environment that will help people learn and apply Microsoft’s AI at work.”

Brett Reifers, senior product manager, Microsoft Digital

The Forge succeeds because of its emphasis on community and knowledge sharing. Its GitHub repository serves as collaborative workspace where employees contribute agents, templates, and learning resources.

This sharing culture creates a compounding cycle. One employee’s outcome becomes another’s starting point. Contributors share useful agents immediately, without lengthy approvals. This grassroots approach lets innovation spread at the pace of curiosity.

“At its core, The Frontier Forge is an open-source, community‑driven experience,” Reifers says. “The Forge is a safer environment that will help people learn and apply Microsoft’s AI at work.”

Building a safe-to-fail path

For IT leaders looking to replicate something like the Forge, MacDonald’s guidance starts with reframing the challenge.

“Find the people who are super curious and who want to learn. They will be the ones who drive innovation with AI agents and other newly developed tools.”

Sean MacDonald, partner director of product management, Microsoft Employee Experience

The barrier to agent adoption for non-engineering roles isn’t access to tools. It’s all about giving them the confidence needed to build them and then put them to work. Providing a safe, hands-on environment where people can learn at their own pace, regardless of skill level, has been an essential key to success.

Another key has been to empower the people in your organization who are eager to innovate and try new things. The Forge began with two curious product managers who decided to experiment and then shared their idea with peers.

“Find the people who are super curious and who want to learn,” MacDonald says. “They will be the ones who drive innovation with AI agents and other newly developed tools.”

For IT leaders currently trying to prepare their organizations for an AI-driven future, the story shows that the answer isn’t to wait around for perfect tools or comprehensive employee training.

“The leaders that create safe spaces for non-engineers to build with AI now will compound that advantage for years,” Reifers says. “The ones that wait will spend 2027 trying to catch-up.”

Our knowledge workers don’t need to wait for help any longer, now they can forge their own path with an agent or other AI tool they build themselves.

Key takeaways

Here are some insights your leaders can use to build grassroots-led, AI-forward communities in your organization:

• Start with volunteers, not mandates. The Forge grew to 100 contributors with zero top-down requirements. Organic growth from curious employees creates sustainable adoption.
• Highlight your quick wins. Reifers’ and Arias’ live demos of MCPs, Oxford’s 90-minute forecast and Stratford’s 20-minute drafts became the recruiting pitch for the next wave of adopters. Show your people results like these, then hand them the tools.
• Lower barriers without lowering standards. Accessibility and quality aren’t mutually exclusive. Governance and security are non-negotiable. Configure it all into the harness.
• Prioritize knowledge sharing and attribution. When one person solves a problem and shares it, dozens benefit immediately. Reward provenance.
• Ship fast, improve later. The Forge repo was built in 15 minutes. Four months later, it contained 50+ templates and agents. As much of 80% what is produced in the Forge is rewritten every other week as tools evolve. Ship MVPs and evolve based on real usage.
• Reframe outcomes > tools. Shifting from “developer tool” to “Copilot workspace” helps knowledge workers see they belong.

Try it out

Start building and sharing AI agents today with GitHub Copilot.

Related links

• See how we enable Microsoft employees to build AI agents that help them complete important tasks.
• Learn more about GitHub Copilot for Azure.
• Discover how we’re transforming our employee experience with AI. 
• Take a course on building AI agents for beginners in GitHub Copilot.
• Follow our step-by-step guide to building API-powered agents. 
• Find out how continuous improvement helps us identify agentic opportunities, and how it can help your company, too. 

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post The Frontier Firm: How knowledge workers are forging their own AI tools at Microsoft appeared first on Inside Track Blog.

In parts of Europe and elsewhere, relationships with our employees are governed by works councils. These councils play a major role in vetting and approving any new technology that might impact our workers and their jobs.

At Microsoft Digital, the company’s IT organization, we have gained a ton of insight by working closely with our works councils, especially as we all embrace the rise of generative AI and new tools like Microsoft 365 Copilot.  

“With the speed of AI innovation today, we can’t sit and wait. We need our internal users, including our works council members, to be forward-thinking early adopters and help us drive AI transformation.”

Irina Chemerys, regional experience lead, Microsoft Digital

This experience means we are able to help guide customers who are dealing with their own works councils—many of which also have questions and concerns about the agentic workplace of the future, which is coming fast.

As we continue on our journey to becoming an AI-first Frontier Firm, we are collaborating closely with our works councils to make sure that we address their concerns and follow all applicable regulations. This process also helps us make better products that meet the evolving needs of our customers, wherever they are.

“With the speed of AI innovation today, we can’t sit and wait,” says Chemerys, a regional experience lead who oversees works council engagements within Microsoft Digital. “We need our internal users, including our works council members, to be forward-thinking early adopters and help us drive AI transformation.”

How works councils work

Our works councils serve as the voice of our employees in some geographies (especially in Europe), advocating for their rights and interests within the workplace. Typically, they have purview over topics like workplace health and safety, pay and benefits, hiring, business reorganizations, training, and more.

 As AI technology becomes increasingly commonplace across many industries, our works councils—along with all of our employees—are at the forefront of the complex discussions regarding the implications of AI for the modern workforce.

While our relationship with Microsoft works councils has always been cooperative and collaborative, how we engage with them for product reviews has evolved over time. What used to be somewhat impromptu or inconsistent engagements have changed to become more strategic and programmatic opportunities for feedback, which can end up greatly improving our products.

Chemerys helped lead the Microsoft Digital effort to streamline the approval process for new technology across works council countries. She drove the development of a global solution that uses a single request form and platform for our works councils worldwide, helping them communicate with Microsoft Digital, product groups, legal, HR, and others at the company.

This simplified communication across the board, and facilitated collaboration among all works councils, allowing smaller countries to take advantage of resources from larger ones and creating a more cohesive community. The unified approach significantly improved coordination, collaboration, and, importantly, trust among works councils.

“Trust is more essential than anything else in terms of collaborating with works councils effectively, especially in the context of AI,” Chemerys says. “To build that trust, you need transparency. And the way you build transparency is by having a well-documented and effective request process.”

Approving Copilot: The tolerance phase

Trust and good communication were linchpins of the process we used to gain works council approval for Microsoft 365 Copilot. Considering how new generative AI tools are, and the widely promoted fears surrounding their potential impact on the workforce, there were understandable concerns raised by some of our works councils about Copilot.

Germany was one country where our works councils were particularly wary of AI. They raised questions about the ways that Copilot could be used to evaluate individual employee performance or make impermissible inferences about individual employees without the data to support them. For example, Copilot might be asked to generate a ranking of employee performance during a meeting, something that fell outside the boundaries of our Microsoft responsible AI principles.

“The earliest versions of these generative AI tools lacked guardrails,” says Carsten Schleicher, chairman of the Microsoft works council in Germany. “You could ask them anything and get an answer back—even questions about religion, race, gender, ethnicity, etc. There were also concerns about AI tools generating false information—so-called ‘hallucinations.’”

“AI is in the world; if you deny your employees access to it, you’ll fall behind. It was absolutely necessary to find a constructive way to deal with AI, and to use it in a fair and transparent way in our company.”

Carsten Schleicher, chairman, Microsoft German Works Council

Faced with these concerns, but also wanting to get as much feedback on Copilot from our European employees as possible, we decided to introduce a tolerance phase.

Countries such as Germany, France, and the Netherlands were included in this approach, which allowed for controlled deployment of the tool while still enabling employees to try it out.

“As a works council, it’s your goal to protect the employees, but you also want the company to be successful,” Schleicher says. “AI is in the world; if you deny your employees access to it, you’ll fall behind. It was absolutely necessary to find a constructive way to deal with AI, and to use it in a fair and transparent way in our company.”

Some members of our works councils were part of the first Copilot deployment wave, and their feedback was then channeled back to the product engineering team. This early access helped the councils quickly reach an agreement that deployment of Copilot could continue, while also leading to product improvements that benefited all our customers.

The tolerance phased ended in the spring of 2025, and Copilot is now approved for use by Microsoft employees worldwide.

Getting ready for the agentic future

After Copilot was approved, the next challenge for our works councils was the world of AI agents. As a Frontier Firm, Microsoft is gearing up for a workplace where employees are routinely aided in their work by digital agents. Eventually, agents may become our “digital colleagues” or even run entire business processes independently.

“For the Employee Self-Service Agent, it was an easy and straightforward process. We made a presentation to people from Microsoft HR in France, which went well. So, when we went to the works council, there were not a lot of concerns. We got the green light very quickly.”

Isabela Cardoso, regional experience lead for France and Ireland, Microsoft Digital

One example of a digital agent that we’ve launched across the entire company (as well as externally to our customers) is the Employee Self-Service Agent. This AI-driven tool offers a “one-stop shop” that our employees can turn to for help with IT support, HR questions, and facilities requests.

Because the tool can access potentially sensitive personal information about employees, we were careful to make sure that our works councils were consulted during the internal deployment of this agent. Their experience reviewing Copilot—and the simplified process that Chemerys spearheaded—were key to winning rapid approval of the Employee Self-Service Agent.

“For the Employee Self-Service Agent, it was an easy and straightforward process,” says Isabela Cardoso, a regional experience lead for France and Ireland within Microsoft Digital. “We made a presentation to people from Microsoft HR in France, which went well. So, when we went to the works council, there were not a lot of concerns. We got the green light very quickly.”

Edith Dubuisson, a senior business program manager in Microsoft Digital who manages our relationship with the Microsoft works council in France, agreed.

“AI is a massive change, so getting the councils engaged early helps to deal with the fear and questions. We see the works councils as a true partner in this transformation of the company with AI.”

Edith Dubuisson, senior business program manager, Microsoft Digital

She stressed how important the concept of partnership is in making sure works council reviews go as smoothly as possible, especially with AI-related technologies.

“We make a point of including the works council in early discussions, telling them that we need them as a partner,” Dubuisson says. “AI is a massive change, so getting the councils engaged early helps to deal with the fear and questions. We see the works councils as a true partner in this transformation of the company with AI.”   

Chemerys notes that as employee-created agents proliferate across the company, the review process will typically take place at the platform level, not the agent level. In this way, agents created with Microsoft 365 Copilot Studio will be treated much like tools created with something like the Microsoft Power Platform are handled.

“When it comes to low-code/no-code agents, you can compare the process to something like Power BI,” she says. “We’ve approved that platform to build reports, and then employees can create reports using it. In some countries, if an employee creates an AI agent using Copilot Studio that could impact the workplace in a sensitive way, then it’s their responsibility to get the proper approvals from our works councils. They can submit it through our standard process, which is why having that is so helpful.”

Embracing the future with our works councils

If there’s one true thing about technology in the age of AI, it’s that things continue to evolve at lightning speed. New tools and features are constantly being created, tested, and launched across Microsoft and many other cutting-edge, innovative companies.

Amidst all this rapid change, we continue to keep our works councils in the loop as these new technologies emerge. It’s a challenge that Microsoft is ready for, Chemerys says.

“There’s an avalanche of new solutions emerging all the time—so many different types of agents and other AI tools,” she says. “And the level is complexity is very high. But we have a great platform for works council reviews, so we can give them an early heads-up, which helps us maintain trust. They hate surprises, so we strive to stay ahead of things and make sure they stay informed.”

In the end, our works councils continue to be a source of invaluable feedback in this new fast-moving AI era. They play a role that transcends mere oversight and embraces proactive engagement, which makes for better products and happier employees—and customers.

Key takeaways

Here are some things to remember as you engage your own works councils with product reviews and discussions in the age of agentic AI:

• Engage your works councils early and often. Bringing them into conversations at the start—well before deployment—reduces uncertainty, surfaces valid concerns, and ensures smoother adoption of new AI tools like Copilot and employee-facing agents.
• Build trust through transparency and structure. A clear, well-documented approval process helps works councils understand new AI technologies and establishes the trust needed for productive, long-term collaboration.
• Simplify and unify communication channels. A single global request platform (like the one we use at Microsoft) improves coordination across works councils of different sizes, enabling smaller countries to benefit from shared expertise and creating a more consistent review experience.
• Balance innovation with worker protections. Structured tolerance phases, like those used for Microsoft 365 Copilot, allow employees to test new AI tools under controlled conditions while ensuring compliance with responsible AI principles and local regulations.
• Treat works councils as strategic partners in the agentic future. Their early feedback on digital agents—like our Employee Self-Service Agent—helps improve product design, accelerate approvals, and reduce fear or misconceptions about AI in the workplace.
• Design governance that scales with low-code and agentic tools. With AI agents proliferating, platform-level approvals—similar to the Power Platform model at Microsoft—ensure innovation can move quickly while still requiring review for individual high-impact scenarios.
• Stay ahead of rapid AI change with proactive communication. Works councils “hate surprises,” so providing early visibility into emerging tools helps maintain trust, reduces friction, and enables Microsoft to build better products for employees and customers alike.

Try it out

Try out Microsoft 365 Copilot at your company.

Related links

• Learn how we’re deploying Microsoft Places with the help of our works councils.
• Find out how we’re becoming an AI-first Frontier Firm at Microsoft.
• Read the full guide on how we managed the internal deployment of Microsoft 365 Copilot at our company.
• See how we’re embracing the agentic future with our Customer Zero approach in Microsoft Digital.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post Transforming into an AI-first Frontier Firm in partnership with our works councils appeared first on Inside Track Blog.

• Deploying Microsoft 365 Copilot: A next-generation business tool
• Chapter 1: Getting governance right
• Chapter 2: Implementation with intention
• Chapter 3: Driving adoption to capture value
• Chapter 4: Building a foundation for support
• Chapter 5: Extending Copilot through agents
• Applying our deployment lessons at your company

Deploying Microsoft 365 Copilot: A next-generation business tool

Welcome to the new era of productivity

Generative AI has captured the world’s attention, and businesses are taking notice.

According to our Work Trends Annual Report, 70% of people would delegate as much work as possible to AI to lessen their workloads.

“I’m inspired by the transformative power of AI. I’ve been impressed with how quickly our employees have put it to work for them.”

Andrew Osten, general manager, Microsoft Digital

Capitalizing on this trend will mean the difference between surging ahead or getting left behind, including here at Microsoft, where we’re the first enterprise to deploy Microsoft 365 Copilot fully.

“I’m inspired by the transformative power of AI,” says Andrew Osten, general manager of Business Operations and Programs in Microsoft Digital, the company’s IT organization. “I’ve been impressed with how quickly our employees have put it to work for them.”

He would know. His team is responsible for driving usage and adoption of Copilot and any new features to more than 300,000 employees and vendors across the world.

“Customers are looking to us to share what we’ve learned as the first enterprise to deploy Copilot,” Osten says. “Our team has a unique opportunity to help them deploy and get to value as quickly as possible.”

Meet Microsoft 365 Copilot

Copilot combines the power of large language models (LLMs) with your organization’s data to turn your employees’ words into some of the most powerful productivity tools on the planet—all within the flow of work. Employees can access intelligent assistance through Microsoft 365 Copilot Chat or the apps they use every day, including Word, Excel, PowerPoint, Outlook, Teams, and more, to provide real-time intelligent assistance. It also forms the foundation for new, agentic capabilities that apply the power of Copilot orchestration to more specific knowledge sources and tasks.

According to our Work Trends annual report, employees who use AI are seeing significant benefits.

Organizations like ours that are unlocking AI assistance within employees’ everyday workflows are poised to gain a distinct advantage in terms of productivity, engagement, and innovation.

“We’re using it to reduce our IT expenses and enhance our productivity,” Osten says. “We’re also excited by its potential to create a lasting competitive advantage for us here at Microsoft and for our customers.”

Our mission in Microsoft Digital is to empower, enable, and transform the company’s digital employee experience across devices, applications, and infrastructure. We also provide a blueprint for our customers to follow in the form of this guide for deploying and adopting Copilot.

“The contents of this guide are based on the lessons we’ve learned deploying Copilot,” Osten says. “The tips and ideas you’ll read here will help you accelerate your own time to value with Copilot so you can realize the same benefits as our employees.”

Are you an executive?

View our condensed, CIO version of the guide here.

Chapter 1: Getting governance right

Maintaining privacy, security, and compliance while respecting regulatory frameworks.

Before you begin your Microsoft 365 Copilot implementation, you’ll want to consider how this tool impacts your data. Copilot employs LLMs that interact with data and content across your organization. It uses information your employees can access to transform user prompts into personalized, relevant, and actionable responses throughout Microsoft 365 apps.

Giving your employees this level of access means proper data hygiene is essential. At Microsoft Digital, we use sensitivity labeling to empower our employees with access while also protecting our data. Our colleagues on the product side designed Copilot to respect labels, permissions, and rights management service (RMS) protections that block content extraction on relevant file labels. By implementing effective sensitivity labeling practices, you can rest assured that anything you intend to remain private or confidential will stay that way.

Pick the governance path that’s right for you

This chapter outlines the highly robust, best-case scenario we created at Microsoft, but we know not every organization has a fully deployed data governance system and strategy. If you’re in that position, don’t worry! You can use techniques like Restricted SharePoint Search that provide value and protection without exposing Copilot to your internal resources.

Laying the groundwork with proper labeling

Throughout our internal governance efforts within Microsoft Digital, we’ve developed four labeling practices that make up our foundation for appropriate policies and settings.

Responsible self-service

Support and enable your employees to create new workspaces like SharePoint sites, ensuring your company data is on your Microsoft 365 tenant and employees don’t simply re-use and overload existing spaces with mismatching permissions. That enables your employees to take full advantage of Copilot in ways that align with your organizational data hygiene while you keep your company’s information safe.

Top-down defaults

Label containers for data segmentation by default to ensure your information isn’t overexposed. At Microsoft, we default our container labels to “Confidential\Internal Only.” That ensures alignment with our policies and settings that limit external sharing. We use Microsoft Purview to manage this process.

Consistency within containers

Derive file labels from their parent containers. Being consistent here boosts security across every layer and reduces the administrative burden on your employees to label every file they create. Copilot will reflect file labels in chat responses, so employees know the level of confidentiality behind each portion of AI-created responses.

Employee awareness

We train our employees to understand how to handle and label sensitive data. By making your workers active participants in your data hygiene strategy, you increase accuracy and your overall security posture.

Self-service with guardrails

The data hygiene practices we outlined above form a foundation for compliance and security, but backstopping those efforts through Microsoft 365 features adds an extra layer of protection. That’s a core principle of Zero Trust.

At Microsoft Digital, we use Microsoft Purview Data Loss Prevention (DLP) policies to define the rules and actions for detecting and protecting sensitive data across Microsoft 365, SharePoint, OneDrive, and Teams. DLP policies support vulnerable data types and scenarios that require protection. Those include any kind of information that might introduce inappropriate access to company data or intellectual property. Examples include access to credentials like keys or tokens, personally identifying information, financial data, or non-public source code.

Sign-in information, reports, and dashboards are available via Purview to help our team monitor and analyze content activity and compliance across the organization. They also provide insights into the volume, location, and usage of sensitive data, as well as any incidents and alerts that indicate potential data breaches or violations.

For example, an employee might label something as “General,” but it contains credentials or other sensitive end-user identification information (EUII). In those instances, Purview will automatically block the file from access beyond its owner or reapply a more appropriate label.

Between proper labeling and backstopping self-service through DLP guardrails, we’re able to keep Copilot Chat from surfacing documents it shouldn’t share in the wrong context or to the wrong people. Using Purview and other tools at our disposal, the five practices below help us keep our employees and our company’s data safe.

Trust, but verify

Empower self-service with sensitivity labels, but verify them by checking against DLP standards, then use auto-labeling and quarantining when necessary. Internally, we’ve configured Microsoft Purview DLP to detect and control sensitive content automatically.

Expiry and attestation

Put strong lifecycle management protocols in place that require your employees to attest containers to keep them from expiring. We don’t keep items that don’t have an accountable employee or that might not be necessary for our work.

Controlling the flow

Limit oversharing at the source by enabling company-shareable links instead of forcing employees to grant access to large groups. At Microsoft, we add an extra layer of highly confidential items that users can only share with specific people on a need-to-know basis. To enforce these behaviors, you can set default link types based on labels through Purview.

Oversharing detection

Even under the best circumstances, accidents happen. When one of our employees does overshare sensitive data, we use Microsoft Graph Data Connect extraction in conjunction with Microsoft Purview to catch and report oversharing.

International compliance: No size fits all

Europe has extra requirements in the form of EU Data Boundary regulations and works councils, internal organizations that provide employee co-determination on workers’ rights or regulatory issues, including performance management or monitoring. Our Copilot deployment meant we needed to partner closely with our Microsoft works councils when launching AI technology with complex data and privacy implications.

Your experience will vary depending on your industry and where you operate, but we’ve learned that it’s best to work closely with local subsidiaries to ensure you have a complete picture of a region’s regulatory situation. Local insiders are poised to liaise with their works councils, as we’ve done at Microsoft, or other bodies through direct relationships. Start the process early so you can manage feedback cycles effectively, make adjustments, synthesize any answers that works councils need, and resolve any concerns through configurations that make sense for your employees.

Learning from Microsoft’s governance, security, and compliance practices

Bring the right people into the conversation

Don’t keep this conversation in the IT sphere alone. Bring in all the relevant security, legal, and compliance professionals.

Build a foundation for automation

Microsoft Purview DLP has powerful intelligent detection, but it relies on establishing good defaults.

Think about how your employees will use Copilot

Determine the primary use cases for Copilot. The kinds of collaboration and access employees need will affect your default labeling architecture.

Take this opportunity to train employees

If you’ve been looking for an excuse to refresh employee knowledge around data privacy, let this moment be your milestone. It will be far easier to start with a clean data estate.

Don’t overwhelm your users

Make labeling simple and intuitive and ensure it isn’t overwhelming. Employees should have a limited set of choices to keep things comprehensible. It’s also valid for different employees to see different choices.

Balance good governance with time to value

Because of the scope and complexity of our deployment, we took a very thorough approach to governance. If speed is your priority, you might consider a faster deployment with a less comprehensive governance approach, for example, using Restricted SharePoint Search to constrain both Enterprise Search and Copilot experiences to a curated set of SharePoint sites of your choice.

Key takeaways

Use these tips to tackle governance, security, and compliance at your company. It’s based on what we learned deploying Copilot internally here at Microsoft.

1) Labeling

• Develop a labeling taxonomy. This should include:
  • Classification levels, not exceeding five primary labels and five sub-labels
  • Descriptions clearly outlining a label’s meaning for employees
  • Examples to clarify usage for employees
• Determine policies and settings that correspond with labels. Consider the following:
  • Storage type and location
  • External allowance
  • Encryption
  • Access control
  • Data destruction
  • Data loss prevention
  • Public disclosure
  • Logging and tracking access
• Establish container defaults
• Configure container labels to set the default file label in document libraries
• Initiate an employee education initiative

2) Data loss prevention

• Configure Microsoft Purview DLP standards and quarantining protocols
• Establish lifecycle management and attestation protocols
• Configure Microsoft Graph Data Connect to discover where you’re oversharing

3) International compliance

• Initiate conversations with local subsidiaries
• Engage works councils or other advocacy bodies
• Address concerns
• Determine the feasibility of regional deployment and segment if necessary

Key actions:

How we did it at Microsoft

• Read our guide to governing Microsoft 365 Copilot. This step-by-step resource, based on our internal experience at Microsoft, will help you adapt your existing governance standards to reflect the new realities of AI.

• Check out how we’re using sensitivity labels to empower our employees while making Microsoft more secure. This article shows you how having a pre-established plan for labeling helped our Microsoft Digital team quickly deploy Copilot with proper guardrails.

• See how we’re riding the wave of agents that’s washing over Microsoft through good governance. This post talks about the ways good governance also pertains to enterprise AI extensibility through agents.

Further guidance for you

• Conduct the Microsoft 365 Copilot Optimization Assessment to understand your level of AI adoption and chart your course.
• Access Microsoft Learn documentation to read more about data, privacy, security, and Zero Trust principles.
• Follow the company’s governance and security overview for Copilot Studio to ensure your agents are managed safely and efficiently.

Chapter 2: Implementation with intention

Building a strategy for licensing, administration, and rolling Microsoft Copilot out to different groups within your organization.

Implementing Microsoft 365 Copilot isn’t as easy as just turning on licenses and alerting your users. It takes organizational partnerships, early assessments of your concrete business needs, and careful planning.

Design for the “who”

Copilot is a new concept in business software. At the time of our implementation, we were the first company to roll it out anywhere in the world, and our Microsoft Digital implementation team had to choose from countless ways to approach a licensing strategy—different mechanisms of licensing, automation, management, and the list goes on. Regardless of your overall approach, we’ve learned from experience that it almost always makes sense to start with pilot groups who can validate the tool and enable the rest of your organization.

For us, that looked like this:

Phase zero

We gave our Copilot engineering team early access so they could test Copilot from an insider’s perspective. We shared our early feedback with the product team.

• Product engineers

Phase one

We issued a limited number of on-demand licenses in core scenarios to get validation and feedback for key use cases.

• Sales
• Marketing

Phase two

We extended licenses to teams who needed to understand and support Copilot or provide approval for use.

• Support
• HR
• Legal
• Security
• Works councils

Phase three

We deployed Copilot and started working on adoption across the entire company.

• Advancing in phases, we deployed Copilot to more than 300,000 Microsoft employees and external staff.

Scaling out your licenses

After you decide on the general shape of your rollout, you can begin building your licensing strategy. Fortunately, if your organization uses Microsoft 365, you’ll already have access to most of the apparatus you need. The inherent flexibility of Microsoft 365 licensing means you can easily adjust your strategy as you progress based on scale, organization changes, or any other factors.

At Microsoft Digital, we started with individual licenses at the single-user level. As our implementation scaled, we tied licensing automation to Microsoft 365 security groups to implement targeted licensing changes at scale. Those groups could include tailor-made subsets of employees or entire organizations within Microsoft, and we keyed our automation logic to their expanding and contracting eligibility.

We highly recommend defining a phased rollout strategy and structuring your groups accordingly. That creates accountability and gives your IT admins a crucial point of contact for understanding the licensing needs of different groups within your organization.

Based on our implementation experience, there are three main benefits to using security groups:

Optimize licensing costs: Create groups that reflect your business needs and goals that align with your respective business sponsors. Sync your licensing status changes with group membership changes. That way, you can assign the right licenses to the right users and adjust easily if you require frequent changes, for example, in your early initial validation phase, to avoid paying for licenses you don’t need or use.

Refine admin costs: Group-based licensing lets your admins assign one or more product licenses to a group. This depends on your rollout strategy and progress. Your admins will be able to streamline your group setup at scale, reducing your admin overhead. This strategy is helpful, considering all the licenses you likely need to manage.

Enhance compliance and security: This ensures that only authorized users receive licenses and get access to resources, enhancing your security and compliance. Your admins can use audit logs and other Microsoft Entra services to monitor and manage your group-based licensing activities.

Pre-adoption communications

Given the excitement around AI tools, one of the biggest challenges during our phased implementation was support requests from employees outside our initial pilot groups. Most of our support requests at this stage were essentially asking, “Where’s my license?” It was a key learning for our Microsoft Digital implementation team.

You can easily avoid the issue through clear and honest communication. For example, when you alert your initial implementation groups about their Copilot access, you could simultaneously deploy “Coming soon” emails to the rest of your organization. That will help you avoid any confusion while simultaneously generating excitement and boosting general adoption when the time comes.

In the end, what’s most important is building a strategy for getting all users access to Copilot, structuring your rollout, and helping people build the daily habit of using AI. While leadership sponsorship is especially important in later phases of adoption, it’s also crucial here as a way of identifying who should be part of pilots and subsequent cohorts. Leaders can help communicate those decisions.

The bottom line is that your IT implementation team can’t work in isolation. Communication—especially from organizational leadership—will be a key part of your licensing and implementation strategy.

Learning from our implementation 

Design for the “who”

When you determine your initial cohorts, base your decisions on which roles have the largest coverage and will provide the most relevant feedback.

Get your groups in place

Be thoughtful about your Microsoft 365 groups and make sure everyone knows who owns them and who’s responsible.

Engage your support team from the start

This is a new technology, so your support teams will receive requests. Ensure they’re ready by giving them early access.

Manage expectations to minimize blowback

Proactively help users understand why they have licenses or don’t. Note that your rollout strategy might be subject to change.

Bring leadership on board early

Executive sponsorship isn’t just useful for adoption. Leaders will also help you identify the key use cases within their organizations to determine if they belong in early rollout phases.

Product feedback at every level

Encourage feedback for employees in your early implementation phases, because that will guide your wider adoption efforts.

Key takeaways

Use these tips to help you with your internal implementation and admin process. They are based on our experience here at Microsoft.

1) Get ready

• Perform the Microsoft 365 Copilot optimization assessment
• Identify key implementation phases and groups
• Secure leadership involvement
• Build out your implementation plan and map it to a licensing strategy

2) Onboard and engage

• Assemble security groups and assign responsibilities
• Build an automated Microsoft 365 licensing management workflow
• Enable roles for Copilot reports and the Copilot dashboard
• Assign licenses and configure them using the setup guide
• Analyze pilot data:
  • Access in-app feedback
  • Facilitate feedback sessions
  • Analyze usage reports
• Deploy communications: For strategy around this element, see the next section

Key actions

How we did it at Microsoft

• Learn about the councils steering our AI projects here at Microsoft.
• Find out how we’re unlocking the value of Microsoft 365 Copilot at Microsoft.

Further guidance for you

• Use the Microsoft Copilot Success Kit to accelerate your implementation with templates, onboarding guides, and technical readiness resources.
• Follow step-by-step instructions for assigning licenses and onboarding users in the Microsoft 365 admin center.

Chapter 3: Driving adoption to capture value

Effective adoption: From readiness to empowerment

The fact that your employees are excited to try out a powerful new technology platform isn’t enough. We found that you need strategic, coordinated change management efforts to drive Microsoft 365 Copilot adoption.

That way, you can be sure to get your employees onboard at the right time in the ways that you want. The idea is to give them the freedom to be themselves with proper guardrails.

Consider breaking your company-wide adoption into cohorts, for example, subsidiaries or business groups. We divided our adoption along two vectors: internal organizations like legal or sales and marketing, and regions like North America or Europe. Different cohorts have different focuses, but the strategy is similar.

Microsoft 365 Copilot change management

Effective change management needs careful planning. Our adoption efforts took inspiration from the Microsoft Engagement Framework, which we’ve developed specially for driving adoption of our products. If you’re an adoption specialist or change manager, you might notice similarities with Prosci’s ADKAR model, which progresses through awareness, desire, knowledge, ability, and reinforcement.

Whichever framework you choose, the techniques we use here at Microsoft will apply. Either way, the process starts with your people.

Get ready

Begin by working with your company-wide adoption leads, then identify members of your target cohorts who will support the adoption, including change managers, leadership sponsors, and employee champions.

Champions boost adoption by filling several important roles:

• Pinpointing key usage scenarios for Copilot based on their cohort’s culture or processes.
• Deciding on the best methods of communication.
• Providing insights that help adoption leaders build out their rollout plans.
• Extending the reach of our adoption team through peer-to-peer support and guidance.
• Most importantly, demonstrating the value of Copilot and showing their peers how powerful this tool can be in their day-to-day work.

When champions socialize their tips and tricks, our experience at Microsoft Digital has revealed that it’s best to share specific prompts and the value they provide as a concrete entry point for users. For example, a champion could say, “I saved three hours drafting this sales script in Microsoft Word using this prompt,” then share their Copilot prompt as a place for peers to start. You’ll find advice below for how you can effectively incorporate champs into your adoption efforts.

Works councils also play a key role at this stage. They offer the benefit of local cultural expertise and can help you identify challenges employees face in their jurisdictions. Even something as simple as understanding proper modes of address helps smooth the road to adoption through effective communication.

Each of these sets of stakeholders has a role to play in your rollout. We recommend using Microsoft Copilot adoption resources to build out your adoption plan.

Onboard and engage

At Microsoft, we implemented this phase across each adoption cohort. Because every group will have its own champions and leadership sponsors, it’s important to treat each of them as its own organization, with its own unique adoption needs.

In advance of our general rollout, we deployed jump-start communications with links to learning opportunities:

• Localized training took the form of Power Hours in different languages and time zones. These training sessions demonstrated key Copilot scenarios across Microsoft 365 apps.
• Self-learn assets included user quick-start guides, demo videos, and the Microsoft Copilot Academy to accommodate different learning styles and preferences.

From our experience at Microsoft Digital, pre-rollout communications fulfill two needs. First, this messaging is a great opportunity to launch your champion communities because early access to Copilot licenses and learning material helps peer leaders build their expertise. Second, these communications build your general adoption population’s desire and excitement for their incoming Copilot licenses, then prepare them to hit the ground running when they finally get access. Clear messaging also helps ward off questions from eager employees asking why they don’t have licenses yet.

After your Copilot licenses are live, your launch-day welcome communications are relatively simple. Just invite employees to access Copilot, play with this new tool, and start to experiment with how it can fit into their daily workflows. It’s also helpful to include information about where employees can get support. There are many possible vectors for deploying these communications, but a multi-pronged effort that includes Microsoft Viva Amplify will deliver the maximum impact.

For support in building out your own communication plan, our adoption team has created a user onboarding kit for Copilot. These ready-to-send emails and community posts can help you onboard and engage your users.

Deliver impact

After everyone has access, it’s time to promote Copilot usage and ensure your employees are getting the best possible experience and the most value. For Microsoft’s cohorts, employee champions and leadership sponsors were essential levers.

It’s important to remember that Copilot isn’t just another tool. It introduces a whole new way of working within employees’ trusted apps. At Microsoft Digital, we took great care to encourage employees to be adventurous and lean into a mindset shift to see it as part of their daily work—not just something they play with when there’s time.

Microsoft Viva Engage or a similar employee communication platform is a helpful forum for peer community support. In our case, it provided an organic space for champions to share their expertise and change managers to provide further recommendations and adoption content. For employees who explore best on their own, Copilot Lab provides in-the-flow learning opportunities to build their prompt skills.

Meanwhile, leadership sponsors diversified our communications strategy by deploying and amplifying messaging through executive channels like org-wide emails or Microsoft Viva Amplify. Because we broke our adoption out by both organization and region, employees benefited from two sets of communications, each focusing on the scenarios that are most relevant to them.

Extend and optimize

Finally, successful adoption depends on measurement, feedback, and listening.

Understanding overall usage patterns and impact is crucial to optimizing adoption. Our Microsoft Digital team employed a combination of controlled feature rollout (CFR) technology while tracking usage through Microsoft 365 Admin Center, the Copilot Dashboard, and Viva Insights. Together, these tools gave us the visibility and tracking we needed to establish and communicate adoption patterns. Meanwhile, IT admins and user experience success managers accessed simple in-app feedback through Microsoft 365 admin center. But to really maximize value, our Microsoft Digital employee experience teams conducted listening sessions and satisfaction surveys.

All of these insights are helping us establish a virtuous cycle to drive further value and better adoption for future rollouts, extend usage to new and high-value scenarios, incorporate Copilot into business process transformation, and understand custom line-of-business opportunities.

Driving user enablement with Microsoft Viva 

We used Microsoft Viva to help enable our 300,000+ global users. Microsoft Viva is an Employee Experience Platform that brings communication and feedback, analytics, goals, and learning into one unified solution. Our team in Microsoft Digital used Viva across a range of change management scenarios, including building awareness, communicating with our employees, providing access to readiness and learning resources, and measuring the impact of our deployment. 

Accelerating Microsoft 365 Copilot with Viva

Viva Connections

Sharing key news related to deployment and enablement, generating “buzz,” and tying Copilot to Microsoft culture.

Viva Amplify

Producing and efficiently distributing employee communications to build awareness and excitement.

Viva Learning

Courses and training for our employees on how to maximize value from Copilot, inclusive of building effective prompts.

Viva Engage

Actively engaging employees, providing leader updates, listening to feedback, and enabling Champs community.

Viva Insights

Using the Microsoft 365 Copilot Dashboard beta to identity actionable insights and usage trends.

Viva Pulse

Instant feedback from employees on their Copilot experience to fine-tune our landing and adoption approach.

Viva Glint

Understanding employee sentiment and gauging the overall effectiveness of our Copilot deployment effort.

Consider these examples:

• A human resources professional might use Copilot to create job descriptions by prompting it to suggest essential skills, qualifications, and responsibilities for a prospective role.
• A salesperson could ask Copilot to generate a table comparing their company’s flagship product with a competitor’s to address customer questions more efficiently.
• A finance professional might prompt Copilot to review and summarize a new contract to reduce the time it takes to search for key data.

Any single approach would never be adequate to address every different discipline and use case. With the rise of agents, specialized AI-powered assistants that customize and focus the capabilities of Copilot, certain roles derive the most value from tailored assistance for specific tasks.

So, we created a playbook that our employees can use to construct their own role-based scenarios according to their individual teams’ unique needs.

We designed it to help adoption professionals accomplish the following objectives:

1. Understand the top responsibilities, challenges, needs, and wants of prioritized roles.
2. Articulate and communicate hero scenarios by clearly depicting how Copilot can enable them.
3. Share deliverables that include roles, scenarios, and prompts with the wider organization to drive awareness, adoption, engagement, and value.

Through internal testing and scenario crafting, we developed a four-part framework for creating, delivering, and socializing hero scenarios across any organization. These are the steps you can follow to create Copilot support content for adoption efforts tailored to specific roles.

Phase 1: Ready

This phase will help your organization, department, or team prepare for the process. It involves aligning with leadership and sponsors who will be accountable for driving value using Copilot. It’s also where you’ll select the priority roles, draft outlines of those roles so you can clarify your understanding of their needs and wants, and seek out feedback from leaders, managers, and subject matter experts.

Phase 2: Engage

Engaging with employees is the key to uncovering Copilot’s core value. In this phase, you’ll identify participants from your priority roles who demonstrate enthusiasm and early aptitude with the tool. From there, you can choose an approach, which might include in-person group sessions, virtual Microsoft Whiteboard sessions, one-on-one interviews, Microsoft 365 Loop collaboration, or whatever modality works best, then communicate the process to participants. Whatever you choose, the final step in this phase is conducting your employee engagements to document existing and aspirational Copilot usage scenarios.

Phase 3: Deliver

Ideating hero scenarios is how you discover value. The delivery phase defines that value and organizes it into a useful, consumable format. It starts with reviewing and analyzing the outcomes of your sessions to gain insights and identify themes. Now is the time to document your hero scenarios and the value they add, as well as blockers and accelerators. Finally, you’ll provide your output: a comprehensive deck that includes your priority roles, hero scenarios, next steps, and more.

Phase 4: Share

The final phase of this process involves socializing your scenarios across your team or organization to realize value. If you’re part of a large organization, it’s helpful to radiate these outputs beyond the target group as an opportunity for further Copilot momentum. This stage includes diving deeper into blockers and accelerators that can help your organization as a whole speed time to value.

Learning from our adoption of Copilot

Cascade adoption efforts through localization

Regional differences, priorities, even time zones—they can all block your centralization efforts. Your insider adoption leaders within each adoption cohort can help.

Empower your employee champions with trust

Monitor your user-led adoption communities at the start to provide support. As this community of power users becomes product experts, they’ll take over.

Empower employees as innovators

You’ll be surprised by what your employees dream up. Provide every opportunity for them to share their favorite tips and usage scenarios.

Create excitement, but set expectations

Encourage a healthy mindset around what Copilot can accomplish and where it fits. Don’t overpromise.

Gamify learning to build engagement and experience

Friendly competitions or cooperative challenges like prompt-a-thons generate excitement and invite creativity.

Understand that for many, AI is emotional

Overcome AI hesitancy by encouraging employees to tackle easy tasks with Copilot assistance. That will help minimize reluctance through practice.

Key takeaways

Use these tips as your guide as you build out and implement your adoption plan. They are based on our own experience internally at Microsoft.

1) Get ready

• Identify and ramp up the person who will lead adoption for your organization
• Create an adoption team and identify who will lead each workstream within each cohort, including:
  • Change managers
  • Executive sponsors
  • Employee champions
• Conduct a kickoff meeting with your adoption team and set up a meeting cadence and workflow
• Identify users and usage within your cohorts:
  • Pinpoint key usage scenarios, for example, CRM-connected email communication for salespeople or customer-facing copy support for marketers
  • Identify cohort-specific personas, for example, software engineers, customer support specialists, and business operations project managers
• Determine communication preferences for each cohort and their personas and optimize messaging for each
• Define success criteria with KPIs and a success measurement plan
  • Examples include usage by app or feature and user sentiment
• Complete user enablement strategy training
• Define a user experience and feedback strategy
• Build deployment communications and an enablement asset library
  • Localize for international audiences

2) Onboard and engage

• Deploy readiness communications with onboarding content:
  • Led by cohort adoption team
  • Led and amplified by leadership sponsors
• Launch champion communities
• Deploy launch communications
  • Led by cohort adoption team
  • Led and amplified by leadership sponsors
• Socialize employee engagement communities
• Run live learning sessions
• Provide self-learning opportunities
• Upscale the working environment with digital banners, posters, and other promotional materials to help employees visualize Copilot

3) Deliver impact

• Promote usage through internal cohort channels
  • Follow-up communications
  • Viva Engage champion posts
• Report on KPI success at predetermined intervals
• Facilitate listening
  • Satisfaction surveys
  • Listening sessions
• Gather and amplify success stories
• Apply learnings to further adoption activities
• Nurture existing champions through a technical training track
• Develop reinforcement, resistance, and maintenance plans

4) Extend and optimize

• Explore new high-value scenarios
• Investigate business process transformation via agents, Copilot Studio, plugins, and connectors
• Source custom line-of-business opportunities

Key actions

How we did it at Microsoft

• Learn how we’re unlocking the value of Copilot at Microsoft. This post shares our overall journey from planning to measuring impact.
• Discover ways we’re approaching change management around Microsoft 365 Copilot. This story identifies the challenges and opportunities around adopting a new and revolutionary technology.
• See how we’re using Microsoft Viva to drive Copilot adoption. This article shares how Microsoft Viva acted as a comprehensive adoption tool during our Copilot rollout.
• Find out how we made Microsoft 365 Copilot adoption fun with Camp Copilot. This post shares how a grassroots, gamified community initiative became one of our most effective adoption drivers. Pair that story with this one that shares our seven tips for driving a successful virtual Copilot skilling event, and check out this article about our three-week Copilot Expo.
• Find out how a Copilot Champs community can help you drive adoption. This post shares how peer-to-peer adoption support helps drive greater engagement for employees.
• Learn how we’re helping our employees build daily Copilot habits with these 10 tips and check out our tips list for engineers.
• Explore how we created a Center of Excellence to guide our adoption and use of AI.
• Learn how we’re applying the Microsoft Responsible AI Standard here in Microsoft Digital and across the company.

Further guidance for you

• Explore the company’s essential guide to Copilot adoption for practical steps to onboard, engage, and measure impact across your organization.
• Use the Microsoft Customer Hub to access community resources and skilling events that can help you build a champions network and foster peer-to-peer support.

Support for adoption leaders

• Access the Copilot scenario library to understand different user needs and opportunities.
• Gain insights from your Microsoft Copilot Viva Insights dashboard.
• Deepen Copilot engagement through the Microsoft Modern Collaboration Architecture (MOCA).
• Help users build daily habits around Copilot using our suite of user engagement tools and templates.

Resources for IT practitioners

• Offer your employees training opportunities through a Microsoft Learn training module.
• Access different Copilot user help and learning resources.
• Give your employees a leg up on creating AI prompts with this blog post.

Chapter 4: Building a foundation for support

Setting your Support team up for success

Empowering employees means making sure they have access to the right support channels, especially if they have concerns with a new technology. The fact that Microsoft 365 Copilot operates across a wide spectrum of Microsoft 365 apps adds complexity to your support apparatus.

As a result, it’s important to give your support teams early access along with your earliest pilot implementations. For Microsoft Digital, that included members of our internal support teams who help Microsoft employees when they run into technical issues, as well as our Customer Experience and Support team that engages with external customers to troubleshoot problems with new Microsoft products. We also invited subject matter experts for Microsoft 365 apps featuring Copilot experiences, including Teams, Outlook, and more.

A small group of users across both internal and external support teams, as well as our Microsoft 365 subject matter experts, gained access at first, and we encouraged them to experiment and try to break features. This was a crucial learning phase for Microsoft Digital because it surfaced interesting issues that wouldn’t come up if our teams didn’t have access and an opportunity to experiment.

Building insights and product experience was step one, but we needed to collect that knowledge so it would be actionable in real situations. To accomplish that, we created a special Teams channel where our support team members collaborate with pilot users of Copilot and representatives of the product group. From there, we worked with marketing and communications professionals to start building our support team’s knowledge base, which would also serve as the foundation for our user-facing content.

Eventually, the time came to provide access to our wider support team. At that point, our support pilot members operated as learning leaders. When it came time to share their knowledge, it took the form of informal brown-bag sessions. We also engaged in shadow/reverse-shadow role-playing exercises so our support agents could practice addressing common issues.

Principles of good support

Available

Highly available and in-context support should deliver both self-help and assisted experiences wherever and however the user needs them.

Consistent

Coherent and seamless access to support across the entire journey eliminates frustration and keeps the experience consistent.

Contextual

Base your support experience on where the user is and what they’re trying to accomplish.

Personal

Anchor support in a user’s goals and preferences.

Strategizing for support

Building experience and knowledge is one thing, but coming up with your approach to support requires planning and a strong idea of your users’ ideal experience. At Microsoft Digital, we take a “shift-left” approach. That means we save our human support staff time by attempting to create excellent self-service options for our users. As a result, they won’t need to access a human agent unless they’re at a genuine impasse.

Shift-left principles can apply to many different support contexts, but with Copilot, we’ve found that the most important upfront action is ensuring your employees have accessible self-service support channels and communicating their availability. That might come through in-app support or access to knowledge bases.

Work with your adoption teams to ensure they include those self-service support vectors in their rollout communications. For us, self-service was able to answer many of our users’ questions, and for any extra-tricky issues, we had them access human-led support.

Seven things we learned preparing our Microsoft 365 Copilot support

Preliminary access

Select your initial support specialists. Include people with different Microsoft 365 app focuses, support tiers, and service audiences.

Communication hub

Establish a community space where your support team can connect and collaborate on issues. Invite non-support professionals as needed.

Knowledge base

Start a collaborative document and add learnings. This will eventually evolve into your knowledge base for internal support.

Widen access

Host information sessions with the wider support team and extend access so all relevant support professionals can ramp up.

Rehearse

Conduct role-playing and shadowing sessions so support teams can build practical knowledge and confidence.

Support go-live

Get your support resources and processes ready and push them live in advance of your Copilot deployment. Consider a dry run.

Track

Determine a tracking cadence and gather data on Copilot issues that arise so support teams can identify trending issues and tickets.

Common questions, issues, and resolutions

As the first enterprise organization to go through the Copilot deployment process, we’ve identified a few challenges and questions you might have. Feel free to add these to your support knowledge base and employee-facing communications.

We’re getting questions about why particular employees don’t have licenses.

Ideally, your adoption communication waves solve this issue by alerting employees when to expect their licenses and when they receive them. Otherwise, consider having a readily available link that answers licensing questions for users or directs them to their relevant managers or admins. You can also automate this process.

Users are coming to us with questions that would be better served by adoption and employee material, and that isn’t our role as support.

Work with your adoption team to preempt these issues with proactive communications. Update your self-help content and provide your support agents with ready access to different employee education resources, including your user-facing knowledge base, self-help videos, and Viva Engage communities focused on Copilot.

Teams are looking for integration support. Where do I send them?

Share this list of pre-built connectors to help your users integrate various data sources into your Microsoft Graph. This list shares the types of content supported.

Can employees put confidential information into Copilot?

As long as your employees are signed in to Copilot with their Entra ID, they can enter confidential information.

My organization has concerns about who owns the IP that Copilot generates. Does the Microsoft Customer Copyright Commitment apply to Copilot?

Microsoft does not own the IP generated by Copilot. Our universal terms state, “Microsoft does not own customers’ output content.” Those terms also include our Customer Copyright Commitment.

What’s the best way to verify the accuracy of the information Copilot provides?

Where possible, Copilot is transparent about where it sources responses from. It answers complex questions by distilling information from multiple web sources into a single response. Copilot provides linked citations to these answers so the user can verify further. 

Key takeaways

Use these tips as your guide as you build out and implement your adoption plan. They are based on our own experience internally at Microsoft.

1) Onboard and engage your support team

• Start with a small set of support leaders:
• General support
• Microsoft 365 product specialists
• Establish a Teams channel for communication and knowledge sharing
• Create a collaborative knowledge base foundation
• Widen access to the full Copilot support team
• Train your full support team:
  • Conduct information sessions
  • Conduct role-playing exercises
• Establish your escalation process
• Engage your internal communications team:
  • Finalize your user-facing knowledge base
  • Discuss the inclusion of knowledge base material and the support process in rollout communications

2) Deliver impact for your users

• Signal support availability in user communities on Viva Engage and other platforms
• Publish your user-facing knowledge base
• Establish self-service automations if applicable

3) Extend and optimize your services

• Review support issues and product feedback
• Calibrate the optimization of your support workflows

Key actions

How we did it at Microsoft

• Read how we’re using AI to transform our Support business at Microsoft. This article shares how our Support team in Microsoft Digital is using AI to overhaul the business from end to end.
• Learn how we deployed the Employee Self-Service Agent here at Microsoft. This blog post shares how we’re using this agent to help our employees with their support needs in the flow of where they work in Copilot.
• Discover ways that AI is revolutionizing support for corporate functions at Microsoft. This post shares an overview of areas where AI can help support teams do their work more effectively.
• See how we’re supercharging our support experience with Microsoft Dynamics 365 and AI. This story outlines ways that AI is boosting our HR team’s support for employees.

Further guidance for you

• Follow the Microsoft IT admin guide for Copilot onboarding, enablement, and support resources to ensure a smooth rollout.
• Access the Copilot Success Kit for launch day assets, support templates, and troubleshooting guides.

Chapter 5: Extending Copilot through agents

Unlocking more tailored experiences by enabling employees and teams to create agents

As organizations and employees have matured with respect to AI, agentic extensibility is expanding the frontiers of this technology. By using and even creating agents that surface knowledge, take actions, and reinvent workflows, employees can personalize AI’s capabilities to fulfill more specific needs.

At Microsoft, we’re leaning into the agentic future by empowering employees and teams to create agents of their own. Agents and their capabilities are incredibly varied. They range from pre-made out-of-the-box agents in Microsoft 365 embedded directly into Copilot Chat; to straightforward agents that employees create themselves using a simplified process also available through Copilot Chat; to Copilot Studio agent builder or SharePoint agent builder; all the way up to complex agents that can take action on behalf of users, designed using tools like Microsoft Copilot Studio and Azure AI Foundry.

Our goal has been to provide access and enable their use at appropriate levels for our employees and the company as a whole. To make that happen, we’ve adopted a maturity model for agentic AI deployment. Early phases focus on using Copilot, grounded in enterprise data, to enhance knowledge discovery and retrieval. Later phases will enable our employees to act on that knowledge and even fully automate business workflows.

Phases of maturity

Each of these levels of agentic capability requires different tools to create and depends on different policies to govern. In the simplest terms, this involves three levels of agent, each of which can handle progressively more complex tasks:

Retrieval agents

Employees use low-code solutions like Copilot Chat or Copilot Studio agent builder, or they can access ready-made agents in Microsoft 365 or SharePoint to quickly train models and retrieve knowledge for specialized scenarios.

Knowledge and action

Powered by built-in connectors in Copilot Studio, agents go beyond simple knowledge retrieval, offering next steps and actions that help employees defragment their day-to-day experience.

Workflow reinvention

Human-led, agent-operated teams perform fully autonomous actions to complete end-to-end workflows, enabling employees to focus on the highest value work while agents take care of repetitive tasks.

While the third level of maturity is still in its initial stages, our employees and teams are already creating retrieval agents and knowledge and action agents. Because retrieval agents don’t require special tooling, we allow employees to create them at will through Copilot Chat and simplified agent builders in Copilot Studio and SharePoint.

For more complex agents intended to meet enterprise needs across lines of business or the company as a whole, our developers use more full-featured tools like Copilot Studio or Azure AI Foundry. For these kinds of agents, we apply the same rigor, reviews, and software development lifecycle (SDL) we use as part of our standard internal app development.

As you explore the different kinds of agents available to your users and decide how and where to enable them, adoption.microsoft.com provides an excellent place to start. It provides three different approaches to creating agents: Microsoft 365 Copilot, Azure AI Foundry, and Copilot Studio. Once you determine who should have access to each of these creation methods, you can follow our advice on driving adoption for this new practice.

Of course, all of this choice adds complexity, so maintaining visibility and control over the agents your employees create can be a challenge. As a result, we take a matrixed approach to creating and governing agents based on different parameters. They include the type of agent, how the user creates it, its knowledge sources, the need for custom tooling, sharing and publishing permissions, and more. It will be helpful to review our strategy in full to help you think through the different parameters behind your agents, in addition to the processes and policies you’ll need to put in place to govern them.

Keeping agents safe and effective through good governance

As you enable your employees and teams to create and use agents, you’ll need structures in place to govern these tools. At Microsoft, we incorporated elements of our tenant’s minimum bar for governance into our policies for managing agents. These measures include Microsoft Information Protection, a functional inventory, activity logging, lifecycle management, and the ability to properly isolate agents against crossing data boundaries.

Our general governance strategy operates at the container level, but agents bring extra functionality to the table. To govern these capabilities, we introduced further controls like sharing limits, breadth of knowledge sources, agent metadata, and information about an agent’s behaviors. The result is a proactive approach to governance backstopped by reactive structures that catch any issues.

As you think about governing your own agents, consider the four core principles we’ve established at Microsoft Digital.

We empower employees to create and share simple, low-risk agents

We provide a safe space and personal flexibility that allows individual employees to experiment without implicating company data or content users don’t own.

We capture and vet sensitive data flows at the enterprise level

More complex or far-reaching agents owned by teams or lines of business need enterprise documentation to account for external audits or security and privacy validation. Builders need to demonstrate that they’ve thought through the security and privacy implications of their agents, so these projects go through approval process flows similar to other professionally developed apps before we trust them with potentially sensitive data.

We protect data designated confidential or higher

We contain data flows to tenant mandates and only trust suitable storage destinations for content. That depends on the ability to gate which connectors can work with particular source data and sensitivity labels.

We honor the enterprise lifecycle 

Both user-based and attestation-based lifecycles come into play. We treat agents that individual employees own like any other user-created app and delete them when that individual leaves the organization. Agents owned by teams have a lifecycle defined by the tenant and tied to attestation, the SDL, and accountability confirmations.

Once you have your governance policies and procedures in place, you can begin your rollout to users through many of the same strategies and processes we’ve discussed in this guide.

Learning from our experience with agents

Connect with relevant stakeholders

Establish early communication and collaboration with members of your security, legal, compliance, IT, and other teams who can help you define ways to configure Copilot Studio agent builder safely.

Trust and empower

Provide safe spaces with appropriate guardrails for individual employees to experiment with simple agents. Copilot Studio agent builder is a great place to start.

Expand enterprise capabilities

Empower a small number of trusted creators to experiment with more powerful agent-building tools under the close watch of IT, Governance, Security, Privacy, Data, and HR teams. This will reveal gaps in process and policy and inform future reviews.

Solidify labeling and data

Revisit your labeling structures and data flows. It will be important to have these structures in place to support this new agentic environment. Start by learning from our experience governing Copilot at Microsoft.

Extend your review process

Adapt any review processes you already have in place to agents, including security, privacy, and accessibility. Embed those reviews into your publishing workflow for agents operating above the individual level. Consider adding reviews for Responsible AI.

Prevent agent sprawl

Establish a reasonable enterprise lifecycle for agents that includes attestation. That will keep agents from sprawling or remaining in place after employees have left your organization or simply no longer need a particular agent.

Key takeaways

Use these tips as your guide as you build out and implement your adoption plan. They are based on our own experience internally at Microsoft.

1) Plan and adapt

• Connect with stakeholders on relevant teams, including Security, Legal, Compliance, HR, and IT.
• Revisit your overall governance and labeling policies and procedures and update them to reflect the needs of agents.
• Plan and document your intended review process.
• Build your matrix of agent capabilities and parameters and map governance policies and procedures to each aspect of agents.
• Decide how your SDL procedures will map to agents.

2) Run pilots with select teams

• Determine your pilot teams. IT and other teams who will be responsible for determining policy are good places to start, for example, Security and HR.
• Establish a feedback and monitoring pipeline.
• Fine-tune your review and remediation procedures based on your learnings.

3) Enable agents across your organization

• Ensure Purview DLP, Microsoft Information Protection, and other backstops are in place before widely enabling agents for users.
• Deploy adoption communications and change management efforts.
• Enable simple agent builder capabilities for your general workforce.
• Enable more complex agent creation for developers on IT and line of business teams.

Key actions

How we did it at Microsoft

• Read about how embracing the agentic future is enabling us to become an AI-first Frontier Firm. This post shares our vision for using agents to transform the workplace.
• Read how good governance is helping us ride the wave of agents washing over Microsoft. This article outlines the governance strategies we’ve adapted to the new agentic moment.
• Find out more about our deployment of Microsoft Agent 365 at Microsoft. This post shows how we’re using this new platform to manage our agent ecosystem. 
• See how we’re unlocking enterprise AI extensibility with Copilot Studio. Read about Microsoft’s internal AI development initiatives and how we’re using and governing Copilot Studio.
• Learn how we’re enabling our employees to build custom retrieval agents. These agents are empowering our workers to accomplish more.
• Discover how we’re keeping our network infrastructure healthy at Microsoft with an employee-built AI agent. This article shares how our team built an agent to improve how we manage our network.
• Access our internal learnings and a step-by-step guide for unleashing API-powered agents at Microsoft. This article explains API agents and shares lessons from our journey using them internally.

Further guidance for you

• Explore the company’s official AI agent adoption guidance to plan, govern, and operate agents using proven frameworks and best practices.
• Visit the AI Agents Hub on Microsoft Adoption to access webinars, quick-start guides, and business scenarios for Copilot, Foundry, and Copilot Studio.
• Follow the Microsoft 365 Copilot Agents Deployment Blueprint to enable agents at scale with security, governance, and measurement strategies.
• Download the Agentic Automation Adoption Guide to learn migration strategies, governance models, and business value for agentic automation.
• Secure your agents at scale with Microsoft Agent 365 guidance for unified identity, compliance, and control across platforms.
• Learn about the Responsible AI policies and practices that we use to guide our use of AI at Microsoft.

Applying our deployment lessons at your company

You’ve learned from our Copilot deployment. It’s time to get started on yours.

Embarking on your Microsoft 365 Copilot deployment journey might seem daunting, but by capitalizing on the lessons that we’ve learned during our internal deployment, you can both speed up the process and avoid any pitfalls.

“Deploying Copilot internally has inspired us to dive deeper into the power of AI assistance, which is enabling us to enhance our employee experience.”

Stephan Kerametlian, business program management senior director, Microsoft Digital

By anchoring your work in careful planning and using the steps and resources provided in this guide, you can unleash a new era of productivity through Copilot.

You’re not in this alone. If you’re looking for support or knowledge on any aspect of your deployment, reach out to our customer success team.

For inspiration around ways that Copilot can become your employees’ AI assistant at work, read stories about how we’re using AI within Microsoft Digital and Microsoft as a whole.

“Deploying Copilot internally has inspired us to dive deeper into the power of AI assistance, which is enabling us to enhance our employee experience,” says Stephan Kerametlian, a business program management senior director within Microsoft Digital. “With the lessons we learned from our deployment, we’re confident that we can support businesses around the world as they achieve more through the next generation of intelligent experiences.”

Key takeaways

This guide reflects our learnings and the processes we followed during our internal rollout of Microsoft 365 Copilot. This last set of tips summarizes the major actions you can take to get started with Copilot at your company.  

• Start with strong governance: Build a clear labeling and data protection strategy before deploying Copilot to safeguard sensitive information and meet compliance needs.
• Pilot, then scale: Roll out Copilot in phases, beginning with pilot groups to gather feedback and refine your approach before expanding companywide.
• Communicate early and often: Proactive communication and leadership sponsorship are essential for managing expectations and driving successful adoption.
• Empower champions: Identify and enable employee champions to share best practices, tips, and real-world scenarios that help others get value from Copilot.
• Invest in training: Provide tailored learning resources and support to help users build confidence and skills with Copilot in their daily workflows.
• Measure and optimize: Track usage, collect feedback, and continuously refine your deployment to maximize impact and uncover new opportunities.
• Plan for support: Set up self-service and human support channels early so employees can get help quickly and keep momentum going.
• Extend with agents: As your organization matures, explore agentic AI to automate workflows and unlock even greater productivity gains.

Key actions

How we did it at Microsoft

• Read our IT playbook for becoming a Frontier Firm in the era of AI.
• Review our five-step AI maturity guide for IT leaders.
• Use our detailed Copilot governance readiness guide—based on our internal experience here at Microsoft—to manage the governance of your Copilot deployment.
• Learn how our IT organization is powering our companywide digital transformation.
• View our condensed, CIO version of this guide.

Further guidance for you

• Use this technical readiness guide to manage your Copilot deployment (PowerPoint download).
• Check out this content map to help you organize your Copilot deployment (PowerPoint download).
• Find the best overall Copilot deployment and adoption guidance at adoption.microsoft.com.

Try it out

• Learn how to get ready for Microsoft 365 Copilot at your company.

We’d like to hear from you!

• Want more information? Email us and include a link to this story, and we’ll get back to you.

The post Deploying Microsoft 365 Copilot in five chapters appeared first on Inside Track Blog.

That’s where the promise of AI transformation comes in.

We at Microsoft Digital, the company’s IT organization, have developed and implemented a diverse portfolio of agentic, AI-driven capabilities that are now embedded directly in our day-to-day IT operations. These agentic systems—AI solutions that can reason across data, recommend actions, and, in some cases, execute workflows with human oversight—turn telemetry and insights into action, making our IT infrastructure and processes more resilient, auditable, and proactive.

“We’ve crossed an important threshold in the evolution of AI for IT. We’re now using the capabilities these technologies provide to transform all our core IT services, making everything we do on that side more efficient and secure.”

Brian Fielder, vice president, Microsoft Digital

While your organization’s IT infrastructure may not match our size or complexity, we believe any company can benefit from the AI-driven innovations that we’ve implemented in recent years.

We focus our AI investments across three core areas:

• Network management and infrastructure
• Tenant and device management
• Employee and engineering productivity

We’re also using AI across our IT systems to increase security, both as a standalone initiative and an integrated priority. This principle is baked into all our compliance, vulnerability response, and governance scenarios.

“We’ve crossed an important threshold in the evolution of AI for IT,” says Brian Fielder, vice president of Microsoft Digital. “We’re now using the capabilities these technologies provide to transform all our core IT services, making everything we do on that side more efficient and secure.”

Enterprise IT maturity

This article is part of series on Enterprise IT maturity in the era of agents. We recommend reading all four of these articles to gain a comprehensive view of how your organization can transform with the help of AI and become a Frontier Firm.

1. Becoming a Frontier Firm: Our IT playbook for the AI era.
2. Enterprise AI maturity in five steps: Our guide for IT leaders.
3. The agentic future: How we’re becoming an AI-first Frontier Firm at Microsoft.
4. AI at scale: How we’re transforming our enterprise IT operations at Microsoft (this story).

Pillar One: AI in network management and infrastructure

We have applied AI throughout our global network and IT infrastructure, enabling us to keep up with the ever-increasing demands for capacity and services while reducing disruptions and incidents.

The different innovations we’ve made that fall under this pillar demonstrate the breadth of the opportunity to reimagine IT services with AI.

Supporting enterprise IT at Microsoft: Our three pillars

Network management with AI

• AIOps
• Network infrastructure Copilot (NiC)
• Vuln.AI
• MyWorkspace AI Assistant

Tenant and device management with AI

• Digital Asset Management Copilot
• Works councils and tenant trust review
• Enterprise vulnerability management
• IntelLicense
• myDevice AI Agent

Employee and engineering productivity with AI

• ADO Copilot
• ADO Work Item Assistant
• Automation Hub/Automation Catalog

The impact of AI technologies on enterprise IT operations at Microsoft can be divided into three main areas: network management, tenant and device management, and employee and engineering productivity.

AIOps: Transforming network management with operational excellence

AIOps, or Artificial Intelligence for IT Operations, involves the application of machine learning, big data analytics, and automation to streamline and improve IT operations processes. In Microsoft Digital, we use AIOps to help us to manage our complex global IT infrastructure.

Our AIOps solution leverages sophisticated data insights to detect and remediate network issues before they become impactful. We use our internally developed AIOps tools to turn raw signals and institutional know-how into guided actions that have led to major time and cost savings.

AIOps benefits include:

• Enhanced productivity: AIOps reduces cognitive load by automating routine tasks, allowing teams to focus on more strategic activities.
• Proactive issue resolution: AIOps executes automatic troubleshooting and remediation, minimizing downtime and reducing incident impact.
• Improved decision-making: AIOps leverages advanced analytics and machine learning to provide actionable insights, which enhances our decision-making capabilities.

The impact of our AIOps work is huge: thousands of hours of engineering time saved and a significant reduction in total disruption time for employees across the company’s global workforce.

Related products:

Microsoft 365 Copilot and Azure AI Services

NiC: A network engineer’s companion

Our Network Infrastructure Copilot (NiC) serves as an everyday companion for our network engineers and field IT professionals. With NiC, our IT pros can use natural-language queries to gain quick, accurate insights into network health, configuration states, documentation, troubleshooting resources, and live device data—all in one place.

Some of the typical use cases for NiC include:

• Summarizing syslogs for specific devices
• Recommending circuit upgrades
• Checking deployment status
• Listing devices missing required controls (such as AuditD)

In aggregate, NiC streamlines network device lifecycle management and operation, delivering significant time savings while improving the consistency of operational decisions.

Related products:

Microsoft 365 Copilot, Microsoft Foundry, Azure OpenAI, Azure Data Explorer

Vuln.AI: Proactively keeping our systems safe

Leaving just a single connected device unpatched could put our entire enterprise at risk. That’s why we developed Vuln.AI (Vulnerability Management Copilot), our intelligent agentic system that has transformed the way we identify, prioritize, and resolve these vulnerabilities across our enterprise network.

Vuln.AI coordinates two agents that enable our network engineers to gather, analyze, and respond to vulnerabilities proactively using AI insights. The research agent maps the vulnerability to the Microsoft infrastructure, significantly increasing accuracy and reducing manual effort and time involved. It then feeds this information to an interactive AI agent, which becomes a gateway for a security engineer or device owner to interface with the data, ask detailed questions, and gather the required information.

Thanks to Vuln.AI, we’ve been able to accelerate infrastructure compliance, reduce exposure windows, streamline security operations, improve endpoint hygiene, and lower operational risk. Our data show thousands of hours of engineering time saved and meaningful improvement in the accuracy of impacted-device identification.

Related products:

Microsoft 365 Copilot, Microsoft Foundry, Azure OpenAI, Azure Data Explorer

MyWorkspace AI Assistant: Scaling support to meet demand

Engineering disciplines across Microsoft rely on production-like Azure lab environments for testing Windows updates, investigating incidents, and building customer demos. We created the MyWorkspace AI Assistant to enable the rapid creation and management of these lab environments in the face of increasing user demands across our operations. This tool uses AI to help speed tasks such as the development and testing of Windows updates, investigating security incidents, and creating prototypes for customer demos.

Time is a critical component for all lab scenarios, whether it be resolving a customer support issue or testing a Windows Update ahead of a patch release. Our goal is to reduce “Customer Pain Time” (CPT), which measures the amount of time it takes to solve a customer’s problem. Every hour saved in the support process represents a multi-hour reduction in customer pain.

Our most recent data shows that My Workspace AI Assistant reduced tickets submitted to our Tier 1 teams by 50% and saved 500 hours by leveraging support chats, configuration guides, and other artifacts In addition, new user onboarding training tickets were reduced by 90%, and individual support interaction time was reduced from an average of 20 minutes to 30 seconds.

Related products:

Azure OpenAI, Azure Cognitive Search, Azure Bot Framework, Azure Adaptive Cards

Pillar Two: Tenant and device management

One of the most complicated dimensions of managing IT services at Microsoft is our tenant. This refers to the internal instance of all our cloud services, including Teams channels, SharePoint sites, Power BI workspaces, apps, and email accounts, as well as the millions of devices used by our global workforce.

In Microsoft Digital, we’ve developed a number of AI-powered tools and solutions to help us manage this gigantic management challenge.

Digital asset management with AI: Governing the tenant

Microsoft empowers our employees to create assets—apps, groups, sites, Power Platform environments, Power BI workspaces—at self-service speed, and our governance must match that pace. Our Digital Asset Management Copilot is a multi-agent solution that surfaces risk and policy violations, recommends fixes, and enables self-service remediation.

Our employees can access a Copilot-like experience to self-manage their assets and ensure app compliance accountability. The agent surfaces insights and recommendations related to asset compliance like oversharing of sensitive documents, highlights tenant assets that pose a security risk, offers remediation mechanisms, and can execute compliance tasks with end-user or admin validation.

The benefits include a more secure enterprise tenant and an embedded culture of compliance: Simplify compliance responsibilities, making them intuitive and seamless for our employees. Success is gauged through end user NSAT scores from our compliance solutions.

The scope of this tool spans more than 1.5 million digital assets in the tenant. The benefits include a more secure enterprise tenant and an embedded culture of compliance. With the help of the Digital Asset Management Copilot, we aim to reach our overall goal of 90% compliance with policies covering ownership, labeling, oversharing, and periodic attestation across the tenant.

Related products:

Microsoft 365 Copilot, Dynamics 365 Copilot, Azure AI Service, Power BI Copilot

Works councils and tenant trust reviews: Optimizing tenant onboarding

In the past, fragmented and manual processes around works councils and tenant trust reviews consultations in the European Economic Area  could result in delays to our product launches by as much as four to six months. Our AI-driven optimization program streamlines the end-to-end process, improving submission quality and routing and providing other efficiency recommendations.

The result of these efforts is significant: We’ve managed to reduce the average works councils and tenant trust review cycle times from 133 days to 40—about a 70% improvement—while strengthening trust and transparency across roughly 17 European Economic Area countries.

Related products:

Microsoft 365 Copilot, Azure AI Service, Power BI

Enterprise Vulnerability Management: Reducing risk to our device fleet

Our extensive companywide Windows device fleet is exposed to vulnerabilities for extended periods after remediations (patches) are applied, increasing the risk of security breaches and operational inefficiencies. Relying on manual processes can lead to slow response times.

Enterprise Vulnerability Management (EVM) is a multi-phase strategy that uses AI technology in combination with Microsoft first-party vulnerability management solutions to proactively secure and maintain the fleet. While Vuln.AI helps us keep our enterprise infrastructure safe and secure, EVM does the same for our fleet of Windows devices.

EVM minimizes risk and reduces manual effort by integrating advanced detection, automated remediation, and compliance acceleration, minimizing risk and manual effort. This holistic approach ensures our devices stay secure and compliant with minimal IT intervention, delivering resilient, self-healing endpoints across the enterprise.

AI-driven EVM delivers measurable impact across our security, compliance, and IT efficiency. Our goal is to reach 95% compliance within a week of a major patching event while reducing operational overhead and enhancing enterprise resilience.

Related products:

Windows Autopatch, Intune, Windows Update

IntelLicense: Our AI-driven license optimization and audit readiness

Managing a software estate the size of ours—including 28 disconnected systems, 400,000 software assets, and more than 800 suppliers—requires license intelligence. IntelLicense is a set of advanced, AI-driven solutions we’ve developed to help us revolutionize our software discovery and acquisition processes.

These solutions optimize our software asset management throughout the enterprise software lifecycle, reducing fragmented data, lowering audit risk, and accelerating decision-making. These changes have delivered substantial cost savings and efficiency improvements. One standout example: Our external vendor audits that previously took an average of 154 days are targeted to drop to about 15 minutes, thanks to IntelLicense changes.

Related products:

Microsoft 365 Copilot, Microsoft Fabric, Power BI Copilot, Microsoft Foundry, Azure AI Service

myDevice AI: Transforming our IT asset management

Ensuring the security of our physical assets requires a unified and accurate inventory. Fragmented IT asset data leads to inconsistent policies and exposes vulnerabilities, making it difficult for security teams to quickly isolate threats and limit potential impact.

The myDevice AI Agent advances an AI-native approach to IT asset management across our IT tenant. The agent automates our high-volume employee requests, clarifies inventory, and streamlines our procurement. While this is occurring, the agent’s recommendation engine matches devices to our users’ needs to improve satisfaction and security.

Early results from myDevice AI include an approximately 50% reduction in time and costs in asset management (eliminating thousands of hours in manual processes annually), as well as improved security and a more personalized device-procurement experience for employees. In time, we will broaden this impact as agentic workflows expand to include labs, printers, conference rooms, and Internet of Things devices.

Related products:

Microsoft 365 Copilot, Azure AI Service

Pillar Three: Our employee and engineering productivity

Building the software and systems needed to power Information Technology at Microsoft is a time-intensive job. Our engineers have been hard at work building AI-powered solutions that make building and maintaining those systems more efficient and streamlined, answering the question, “How can we apply AI to make this more efficient?”

Here are a few of the solutions we’ve found to help cut down the time and effort involved in some of the routine, day-to-day IT procedures that help keep our systems running smoothly.

ADO Copilot: AI with Azure DevOps

ADO Copilot empowers all our developers and product managers by providing instant, AI-driven insights and automation within Azure DevOps (ADO). This AI-driven assistant seamlessly integrates into ADO and acts as a “trusted copilot” with natural-language capabilities that automate workflows; enhance productivity, compliance, and velocity; and amplify decision-making across the planning, building, and deployment phases.

This agentic solution reduces the time we spend searching for information, managing permissions, planning sprints, summarizing KPIs, and resolving engineering friction points. It enables our engineering teams to move from planning to execution faster and with greater quality and consistency.

The early results from our use of this tool show extensive time savings, which projected over a full year would mean 73,000 fewer hours of engineering time required for the same output.  We’ve also seen greater developer satisfaction and faster movement from planning to execution.

Related products:

Azure DevOps, Azure AI Service

ADO Work Item Assistant: Automating our ADO processes

Building consistent, high-quality ADO work items manually can be time-consuming and prone to errors. Our ADO Work Item Assistant is a generative AI-powered tool that streamlines the creation and understanding of Azure DevOps work items, including features, user stories, tasks, bugs, and custom item types.

The benefits of our assistant include:

• Greater efficiency: The potential to cut the amount of time it takes to craft an ADO feature or user story in half (50%).
• Project delivery enhancement: A streamlined approach mitigates errors and inconsistencies.

By leveraging the power of AI within Azure DevOps, we can significantly simplify and accelerate the work-item authoring process for our product management and engineering teams, improving quality and reducing workload.

Related products:

Azure DevOps, Copilot Studio, ES Chat

Automation hub and catalog: Solving task fragmentation

Large enterprises face major productivity challenges stemming from scattered information, fragmented systems, and reliance on numerous disconnected apps. This fragmentation leads to increased meetings, duplicative effort, and significant time spent on lower-level tasks.

Automation Hub/Automation Catalog is our customizable Teams app—built on Power Platform and Power Catalog—that addresses this challenge by applying AI-powered automation solutions that integrate seamlessly with your existing systems. Common automations include a daily consolidated task list, cancelled-meeting alerts, flags for important emails, and nudges on unanswered messages. The app streamlines workflows and jump-starts productivity gains, enabling you to enhance operational efficiency while maximizing your ROI.

Related products:

Microsoft 365 Copilot, Microsoft Teams, Power Platform

The future of AI in IT

As enthusiastic as we are about our progress so far, we’re even more excited about the great potential that AI agents show in terms of lowered costs, time saved, and boosted productivity across our IT operations.

“The advent of AI agents is the next big step in AI-powered innovation. We are actively working towards our vision of deploying, governing, and managing a fleet of agents across our IT organization, pushing Microsoft to the boundaries of the AI Frontier.”

Monika Gupta, partner group engineering manager, Microsoft Digital

We’re anticipating that these solutions will continue to scale up as we further optimize and standardize large language models and agent patterns in our engineering organizations. Multi-agent orchestration will make an impact on governance and vulnerability response, and autonomous actions will become more common in everyday IT workflows. Measurement rigor will continue to sharpen, ensuring that value is tracked and amplified as AI tools and technologies proliferate across the enterprise.

“As exciting as it’s been to see the many practical applications of AI across our IT portfolio the last two years, 2026 is shaping up to be even more exciting,” says Monika Gupta, partner group engineering manager in Microsoft Digital. “The advent of AI agents is the next big step in AI-powered innovation. We are actively working towards our vision of deploying, governing, and managing a fleet of agents across our IT organization, pushing Microsoft to the boundaries of the AI Frontier.”

Key takeaways

Here are some important factors to consider as you contemplate adding AI tools and innovations to your IT operations and workflows:

• Think holistically: Evaluate the major categories of your IT organization where AI can drive transformation—network management, tenant and device governance, and employee productivity.
• Leverage AIOps for resilience: Use AI-driven operational tools to automate troubleshooting, reduce downtime, and improve decision-making across your network infrastructure.
• Embed compliance into workflows: Implement AI-fueled governance solutions that make compliance intuitive and self-service, reducing risk while fostering a culture of accountability.
• Accelerate vulnerability response: Adopt multi-agent AI systems to proactively identify, prioritize, and remediate security vulnerabilities, minimizing exposure windows and operational risk.
• Boost productivity with AI assistants: Deploy AI Copilots and automation hubs to streamline engineering tasks, reduce cognitive load, and eliminate inefficiencies caused by fragmented systems.
• Plan for scale and autonomy: Prepare for the next wave of AI in IT—multi-agent orchestration, autonomous workflows, and rigorous measurement frameworks to amplify value across the enterprise.

Try it out

Learn more and sign up for a free trial of Microsoft Azure AI apps.

Related links

• Learn how we’re enhancing our network reliability with AIOps and Network Infrastructure Copilot.
• Find out more about our AI-powered leap into vulnerability management at Microsoft.
• Check out our playbook for becoming a Frontier Firm in the AI era.
• Explore our 5-step guide to enterprise AI maturity.
• Discover how we’re transforming the employee experience at Microsoft with AI.
• Read about how we’re using AI to reinvent our network security practices.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post AI at scale: How we’re transforming our enterprise IT operations at Microsoft appeared first on Inside Track Blog.

As threats grow more varied, widespread, and sophisticated, enterprises need to rethink how they protect their environments. That’s why we, in Microsoft Digital, the company’s IT organization, took a necessary step forward and deployed Microsoft Baseline Security Mode internally across the company.

Baseline Security Mode is a new approach to endpoint protection that enforces secure-by-default configurations across our enterprise. And it’s not just about locking things down—it’s about doing so in a way that’s scalable, manageable, and respectful of user experience.

This is a story for every organization trying to balance usability with security. Baseline Security Mode is designed to help IT teams enforce protections without breaking productivity. It’s a shift toward proactive defense with standardized secure settings.

Understanding the need for Microsoft Baseline Security Mode

Security must evolve with the environment.

At Microsoft Digital, we’ve built a strong foundation of endpoint protection over the years. But as our ecosystem expanded—more devices, more workloads, more diverse user needs—we saw an opportunity to take our security posture to the next level.

Our existing configurations were effective, but they reflected the natural complexity of a large enterprise. Different teams had different requirements. Some relied on legacy technologies that had served them well. Others needed flexibility to support specialized workflows. Over time, this led to variation in how security policies were applied.

We wanted to unify that approach.

Baseline Security Mode emerged as a way to streamline and strengthen our defenses. It was about building on what worked. We started by identifying areas where legacy protocols and configurations could be modernized. That included technologies like ActiveX controls and older authentication flows, which we carefully evaluated and phased out where appropriate.

We also improved how we gather and use telemetry. Initially, we had limited visibility into how certain features were used. That made it harder to predict the impact of changes. So, we ran pilots, collected feedback, and refined our approach. Baseline Security Mode was a game changer here, providing built-in reports that gave us the visibility we needed to observe the impact of applying settings in our environment. For example, when we reviewed blocking legacy file formats, we discovered that some workflows depended on them. We responded quickly, offering alternatives and guiding users through the transition.

Ease of use was a priority.

We built intuitive controls into the Microsoft 365 admin center, allowing IT admins to manage policies with just a few clicks. No more manual scripts. No more guesswork. We also introduced exception handling to support specialized needs, ensuring that security didn’t come at the cost of productivity.

We worked closely with internal stakeholders, including compliance teams and work councils, to validate every step and build trust. We made sure the experience was smooth, the tools were reliable, and the changes were clearly communicated.

This wasn’t just a technical upgrade—it was a cultural shift.

Baseline Security Mode gave us a way to unify our security posture while honoring the diversity of our environment. It’s a smarter, more scalable way to protect our endpoints, and it reflects everything we’ve learned from years of experience.

Putting consistent security configuration into practice

Baseline Security Mode establishes a new standard, enabling organizations to be secure by default.

It is the result of a collaborative effort of multiple product teams at Microsoft, building on their security and incident-handling expertise.  It’s designed to simplify and strengthen endpoint protection across Windows and Microsoft 365. The feature lives in the Microsoft 365 admin center, where IT admins can enforce modern security policies with just a few clicks.

“When we blocked certain file formats, users were confused by the error messages and thought they were blocked from saving the file. So, we ran pilots, gathered feedback, and helped the product team build an improved error experience to save blocked formats to safe, newer formats.”

Harshitha Digumarthi, senior product manager, Microsoft Digital

The product teams delivered 20 features across five workloads: Office, OneDrive and SharePoint, Teams, Substrate, and Identity. Each one targets a specific risk—blocking legacy authentication, disabling insecure protocols, restricting ActiveX, and more.

When we deployed Baseline Security Mode as Customer Zero at Microsoft Digital, our job was to validate these features and controls in real-world enterprise conditions.

We pushed for exception handling.

Some users still relied on legacy formats or protocols. Certain teams, for example, needed access to older Office features. So, we worked with the product team to ensure exceptions could be built into the UI.

That flexibility was key. We knew from experience that without it, customers might hesitate to adopt the feature.

“When we blocked certain file formats, users were confused by the error messages and thought they were blocked from saving the file,” says Harshitha Digumarthi, a senior product manager at Microsoft Digital. “So, we ran pilots, gathered feedback, and helped the product team build an improved error experience to save blocked formats to safe, newer formats.”

We also pushed for better telemetry.

“When we heard about Baseline Security Mode, it was still in ideation. There were no tools in the Microsoft 365 admin center yet. We had to figure out how to enable this internally while the product team built the capabilities in parallel.”

Markus Gonis, senior service engineer, Microsoft Digital

At first, we had only a few days of data. That wasn’t enough to understand how features were used or what impact they would have. So we worked with the product team to expand telemetry, improve error reporting, and reduce false positives, including identifying bugs that skewed metrics and made troubleshooting harder.

We ran the deployment through our Tenant Trust Program and work council reviews to ensure global compliance. That gave us—and our customers—confidence.

Baseline Security Mode isn’t just a feature. It’s a shift in how we think about security, and we’re proud to have helped shape it.

Deploying Baseline Security Mode at Microsoft Digital

Rolling out Baseline Security Mode wasn’t just a technical exercise—it was a cross-team effort that demanded precision, patience, and partnership.

Microsoft Digital took the lead on deployment. We acted as Customer Zero, testing every feature in real-world conditions before it reached customers. That meant working closely with the product team to validate functionality, identify bugs, and shape the user experience.

“When we heard about Baseline Security Mode, it was still in ideation,” Gonis says. “There were no tools in the Microsoft 365 admin center yet. We had to figure out how to enable this internally while the product team built the capabilities in parallel.”

Telemetry was limited. We had only 30 days of data to work with. That made it hard to predict how changes would affect users, so we ran pilots with internal user acceptance testing cohorts and we deployed in phases.

“It was a great Customer Zero experience. Our security teams stood to benefit from Baseline Security Mode features, and we helped the product team find bugs and the issues that just hadn’t come up in early testing or at a large scale. It was a win-win situation”

John Philpott, principal product manager at Microsoft Digital

For some legacy protocols, usage was low. In these cases, the features being deployed made removing these protocols seamless. Where usage was higher or unclear, a more detailed approach was required.

First, a few thousand users. Then 50,000. Then 100,000. Eventually, the entire Microsoft tenant. We paused between each wave to monitor help desk tickets, gather feedback, and confirm that our mitigation strategies were working.

Communication was critical.

We ran targeted campaigns, sent individual emails, and published technical reports explaining what was changing, why it mattered, and how users could adapt. We even used Viva Engage to notify users directly. It was important to explain to users why longstanding functionalities were being removed. We had to explain what we were doing and how to mitigate any impact.

We did a lot of work with the product team to ensure the user experience and the IT pro experience both exceeded expectations.

“It was a great Customer Zero experience,” says John Philpott, principal product manager within Microsoft Digital. “Our security teams stood to benefit from Baseline Security Mode features, and we helped the product team find bugs and the issues that just hadn’t come up in early testing or at a large scale. It was a win-win situation.”

We flagged inconsistencies in policy syntax, pushed for better error handling, and worked with the product team to align deployment tools across workloads.

But we didn’t stop at deployment. We tracked progress, validated telemetry, and signed off on each feature before it moved into broader rollout. We even helped pave the way for the next iterations, identifying features that needed more design work or deeper telemetry before they could be deployed.

This was a true partnership. The product team built the features. We tested them, validated them, and helped make them better.

Baseline Security Mode is now live across Microsoft. And it’s ready for the world.

Capturing real benefits

Baseline Security Mode is more than a set of policies—it’s a platform for proactive defense.

The product team built it to reduce legacy risks and enforce modern security standards across Microsoft 365 workloads. Microsoft Digital validated it in production, surfacing bugs, shaping telemetry, and confirming that the features worked as intended.

We tested 22 features across Office, OneDrive & SharePoint, Substrate, Identity, and Teams. Each one targeted a specific vulnerability—like blocking ActiveX controls, disabling Exchange Web Services, or enforcing phishing-resistant authentication for admins.

We flagged critical ActiveX dependencies in third-party apps —something the product group hadn’t found—which enabled them to initiate removal. That kind of early detection helped fix issues before the features reached customers.

We found regressions in PowerShell and legacy authentication flows. The OneDrive and SharePoint team caught a high-impact bug and worked with the product team to resolve it.

That validation mattered.

We also helped shape the admin experience.

Exception handling was built into the UI. Admins could create security groups, assign users, and manage exclusions directly in the Microsoft 365 admin center.

“There’s no need to handle everything manually,” Philpott says. “Simply click here and then here to disable. It’s a much simpler process.”

Extending benefits to Microsoft customers

Baseline Security Mode is ready for enterprise.

We’ve tested it. We’ve hardened it. And we’ve made it easier to adopt.

Microsoft Digital’s deployment journey helped shape the product into something customers can trust. We didn’t just validate features—we made sure they worked in real-world environments, across diverse teams, and under the pressure of scale.

 The product team designed the features to be enterprise-ready. We ran them through our Tenant Trust Program and work council reviews to ensure compliance across global regions. That gave us confidence—and gave customers confidence too.

The benefits are clear. We’ve reduced our attack surface. We’ve improved compliance. We’ve made it easier for IT teams to enforce security without disrupting workflows. And we’ve laid the groundwork for secure-by-default computing across Microsoft.

 Customers can do the same.

Start small. Run pilots. Monitor impact. Use the tools in the Microsoft 365 admin center to deploy policies, manage exceptions, and guide users through the change. And don’t be afraid to ask for help—our journey has shown that collaboration between deployment teams and product teams makes all the difference.

Baseline Security Mode is ready, and we’re ready to help others adopt it.

Looking ahead

The first wave of Baseline Security Mode—BSM 2025—delivered 22 features across five major workloads. Microsoft Digital helped validate and deploy those features across the enterprise. And the next wave of features is already in motion.

And it’s bigger, with 46 features, more than double what we had in the first round. The product team is expanding coverage to include deeper protocol restrictions, broader app controls, and more granular authentication policies.

We’re also preparing for broader industry adoption.  

Governments, regulators, and enterprise customers are asking for secure-by-default configurations. Baseline Security Mode is our answer. And the next version will make it even easier to adopt.

We’ll continue to lead as Customer Zero. We’ll test new features, validate insights surfaced by telemetry, and share feedback with the product team. We’ll run pilots, monitor impact, and guide users through the change. And we’ll keep pushing for simplicity, scalability, and trust.

Because security isn’t a one-time project— It’s a mindset, and it’s Microsoft’s highest priority.

Key takeaways

Ready to adopt Baseline Security Mode? Here’s some actions we recommend based on our deployment experience:

• Start with a pilot: Test Baseline Security Mode with a small group of users to identify legacy dependencies and gather feedback before scaling.
• Use the Microsoft 365 admin center for deployment: Apply policies and manage exceptions directly through the UI—no scripting required.
• Identify and plan for exceptions early: Work with business units to understand where legacy formats or protocols are still needed and create security groups for exclusions.
• Communicate proactively with users: Launch campaigns to explain upcoming changes, their impact, and how users can adapt.
• Validate telemetry and error reporting: Ensure your environment captures enough data to monitor the impact of new policies and troubleshoot effectively.
• Engage your compliance and governance stakeholders: Review new policies with internal governance teams to ensure alignment with organizational and regional standards.
• Treat security as an ongoing journey: Continue to monitor, iterate, and evolve your security posture as new threats and features emerge.

Try it out

Learn more about Baseline Security Mode.

Related links

• Learn how we’re supercharging our enterprise with Windows 11 and AI.
• Find out how we’re accelerating workplace productivity at Microsoft with Windows Recall.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post Hardening our digital defenses with Microsoft Baseline Security Mode appeared first on Inside Track Blog.

In short, we’re all-in on agentic AI, and we want to help you get there, too.

“We’ve made a lot of progress deploying and driving adoption of Microsoft 365 Copilot since it was released, and we’re now doing the same when it comes to enabling our employees and our teams to build agents that make us more productive,” says Brian Fielder, vice president of Microsoft Digital, the company’s IT organization. “We’re Customer Zero at Microsoft, which means we’re the first to deploy and use the technology and services that we sell to our customers. Those learnings give us a unique perspective and story to share with you about the journey we’ve been on with AI and agents.”

We have two collections of agentic AI content that we think will be useful to you.

“When it comes to agents, we’re still at the start. We expect to learn much more as we continue, lessons we’ll share here—stay connected and we’ll continue to share our story with you.” 

Brian Fielder, vice president, Microsoft Digital

The first set of stories documents our vision and strategy for agents. They walk you through our experience deploying agentic AI, our work to create tools that enable our employees to dive in, and, through smart governance, empower everyone at Microsoft to be confident and creative with how they use agents while keeping the company safe and secure.

Our second set of stories highlights some of the most interesting and effective agents that our employees, teams, and organizations have built. These stories will not only give you examples of agents that we’ve built, they show how you can go about building  similar agents for your organization based on the collective experience of our employees and teams at Microsoft.

“We hope you find reviewing the journey we’ve been on practical and useful,” Fielder says. “When it comes to agents, we’re still at the start. We expect to learn much more as we continue, lessons we’ll share here—stay connected and we’ll continue to share our story with you.”  

November 13, 2025

Alex Fleck

The agentic future: How we’re becoming an AI-first Frontier Firm at Microsoft

January 30, 2025

Keith Boyd

AI-powered agents in action: How we’re embracing this new ‘agentic’ moment at Microsoft

Deploying agentic AI at Microsoft

May 15, 2025

Alex Fleck

Riding the wave of agents washing over Microsoft with good governance

Agentic extensibility is expanding the frontier of enterprise AI. By creating agents that surface knowledge, take actions, and even reinvent workflows, people can personalize AI’s power like never before. But how do you move into the agentic future without putting your organization and employees at risk? How do you encourage citizen developers to create agents Read More

Agents we’ve deployed internally at Microsoft

November 13, 2025

David Hirning

Accelerating employee services at Microsoft with the Employee Self-Service Agent

Microsoft is a huge and complex organization, with more than 200,000 full-time employees working in hundreds of locations around the world. Engage with our experts! Customers or Microsoft account team representatives from Fortune 500 companies are welcome to request a virtual engagement on this topic with experts from our Microsoft Digital team. Previously, when our Read More

Key takeaways

We hope that you find our agentic AI stories useful. We wanted to share a mixture of our strategy and vision around enabling our employees to deploy agents, and to share stories that feature some of the most promising agents that our employees and teams have built and deployed.

We also understand that it can feel challenging to know where to start—it was for us. Here are some things we learned along the way that should help you:

• Governing agents is complex, and dependent on the overall AI maturity of your organization. Start slowly to build that maturity before unleashing too many new agents in your environment.
• A strong policy framework is the foundation. Lean on existing app governance policies, then layer agent-specific structures on top.
• Invest in data infrastructure and AI platforms. Building robust data infrastructure ensures your organization is prepared to leverage AI, and supports scalable, innovative, and secure AI-driven solutions.
• Develop a building environment strategy. Decide what scenarios match up with specific environments and make the right environments available to the relevant employees.
• Global regulations around categories like privacy, security, and responsibility provide a good baseline for establishing governance policies. Set relevant teams to work thinking through these regulations and incorporate their insights into your agent governance.
• Foster a culture of creativity and teamwork. Champion an AI-forward culture where innovation and collaboration drive the adoption of agentic AI.
• Develop AI expertise through training and development. As agentic AI transforms workflows and business outcomes across every industry, upskilling will empower your teams to navigate the rapid advances of AI, drive innovation, and ensure your organization stays competitive.
• Align AI initiatives with strategy. Ensuring AI initiatives align with business goals maximizes their impact and positions your organization to succeed in the rapidly evolving world of agentic AI.
• Implement ethical AI practices. You can use Microsoft’s Responsible AI principles as a guide. Adopting ethical AI practices builds trust, ensures responsible innovation, and prepares your organization to navigate the evolving landscape as AI becomes central to business operations and decision-making.

Try it out

• Get started with AI agents with Microsoft 365 Copilot, Azure AI Foundry, and Copilot Studio.

Related links

• Learn how to create and publish agents with Microsoft Copilot Studio.
• Find out how to create and deploy agents with Microsoft 365 Agents SDK.
• Check out these 12 lessons to get started building AI agents.

The post Powering agentic AI adoption at Microsoft: Our ‘Customer Zero’ story appeared first on Inside Track Blog.

In the past, Julie might have interacted with different apps and websites to get help with each of those tasks. Today, thanks to the power of agentic AI and Microsoft Copilot Studio, Julie can turn to a single portal to handle all of it: the Employee Self-Service Agent.

This agentic tool, which will soon be released publicly as a free add-on for the Microsoft 365 Copilot license, has already made a big impact on the lives of our employees, saving them time, effort, and frustration. We call it the “one-stop shop” experience of employee self-service.

“Before we had the Employee Self-Service Agent, the employee-assistance experience was fragmented across mobile, websites, and physical kiosks,” says Becky West, a principal group product manager in Microsoft Digital, the company’s IT organization. “The new agent unifies all of these experiences and puts them in the same place.” Now our employees can ask questions in natural language, and it guides them through whatever campus experience they need to do—invite a guest, find dining options, create a help ticket, etc.

“Our employees rely on AI tools like Copilot to help get their work done. And the same is now true for resolving an issue related to facilities.”

Becky West, principal group product manager, Microsoft Digital

Of course, employees like Julie also need assistance with other common job-related tasks, like getting their human resources (HR) questions answered or fixing a technical issue with their device.

Those are also important categories included in the Employee Self-Service Agent, something the flexibility and extensibility of Copilot Studio makes possible.

“Our employees rely on AI tools like Copilot to help get their work done,” West says. “And the same is now true for resolving an issue related to facilities, HR, or IT support. We live in an AI-powered world, and this agent meets the moment for our people.”

In this story we share how we’re using the Employee Self-Service Agent in the real estate and facilities space, but it does much more than that. Our employees also use it to get help with IT problems and answers to their HR queries, and we expect to add other key areas soon, such as finance and legal. Available to all Microsoft employees worldwide, the full agent is already delivering a significant boost in productivity, cost savings, and user satisfaction across the company.

Everyday use cases for agentic assistance

Julie might not need IT support or help with an HR issue every day. But she’s always on the hunt for her favorite foods for lunch.

In our existing dining app, employees could look up that day’s menu for a specific building cafeteria, but they couldn’t just ask, “Hey, where can I get some good teriyaki on campus today?”

With the Employee Self-Service Agent, now they can.

“Searching on type of cuisine or dish is one of the top requests we were getting,” says Balaji Radhakrishnan, principal software engineering manager for the dining team. “It was an important feature missing from our existing apps, and we solved that with the employee-assistance agent.”

Employee Self-Service Agent screenshot

Not only can the agent help Julie locate the perfect lunch, it also connects her to the tool where she can order and pay for it. This streamlines the process for her—she doesn’t have to remember which website or app to call up to procure her teriyaki treat. (In the future, we plan to extend the functionality so the agent remembers your previous food choices, and you can order right from the agent.)

Dining is just one of the facilities-related experiences we targeted when developing the Employee Self-Service Agent. Other tasks include:  

• Lobby and visitor services – registering a campus guest
• Parking – registering a car to park on campus
• Maps – navigating around a building or a campus
• Facilities tickets – getting help with office furniture, lighting, HVAC, or other building issue
• Transportation – calling a shuttle for a ride between buildings or finding commuting help
• Finding a space – locating a place to relax, work, or connect with colleagues

“We started out by looking at the services we already offered,” West says. “We thought about what tasks would be in highest demand, where that information or transaction lived now, and how best to surface it. The more we explored the power of the agent, the wider the variety of experiences we were able to incorporate.”

Saving time and reducing frustration

Resolving employee pain points and saving time are two of the key advantages inherent to this area of agentic employee assistance. Consider the common employee task of registering a business-related campus guest (such as an interview candidate or a prospective customer).

“If we can handle 50%—600,000—of these business-related visitor registrations through the Employee Self-Service Agent, that adds up to 50,000 hours of employee time each year.”

Bhavani Paruchuri, senior product manager, Microsoft Digital

According to Bhavani Paruchuri, a senior product manager in Microsoft Digital, in 2024 Microsoft saw more than 2 million registered visitors at our buildings worldwide. Roughly 1.2 million of these were business-related guests.

Previously, employees had to email or talk to lobby hosts (front-desk staff) when they wanted to register a guest; the host would then enter visitor details into the Guest Management System. Now, the Employee Self-Service Agent provides a simple form within the chat, asking for details like guest name, email, purpose, building number, and date. Once the form is submitted, the system confirms it and sends a QR code directly to the guest via email.

“We calculated that this new process could save at least five minutes for each guest registration,” Bhavani says. “If we can handle 50%—600,000—of these business-related visitor registrations through the Employee Self-Service Agent, that adds up to 50,000 hours of employee time each year. So, just in this one area alone, the agent can have a big impact on overall productivity.”

Those savings add up, and quickly.

“Once you start using the agent for dining, you use it daily. As we added in cuisine and price filtering and other functionality that wasn’t available before, you could see it was a big differentiator from what the previous tools could do.”

Erik Downing, principal product manager, Microsoft Digital

One of the reasons we decided to include facilities-related help early on in the development of the Employee Self-Service Agent is that these common tasks would help increase usage of the new portal—building a habit with our workers that would have long-term benefits.

We have already seen employees used to finding a meal with the agent also using it to solve other challenges, including in the HR and Support spaces.

“Once you start using the agent for dining, you use it daily,” says Erik Downing, a principal product manager with Microsoft Digital. “As we added in cuisine and price filtering and other functionality that wasn’t available before, you could see it was a big differentiator from what the previous tools could do.”

West explains how this can have an outsized effect on promoting product adoption.

“If people get in the daily habit of using the agent for these routine tasks, they’ll be more comfortable going to it for other things,” West says. “Then you can really start to scale the agent up and see the larger impact across more areas.”

Filing a service request with the help of AI

Julie gets to work one morning and is dismayed to discover that her adjustable desk will no longer rise to a standing position. She needs to open a facilities ticket for help.

“The AI automatically picks out the problem class and the problem type; presents a form with the details; asks for confirmation; then kicks off the ticket right from there. It’s all in one place, AI-driven, and truly agentic in terms of task completion—and it will only get better.”

Sonaly Choudary, senior product manager, Microsoft Digital

In the past, this would have required Julie to send Facilities an email with a description of the problem, or she would have had to track down the right app or web form for the same purpose.

Now, she can simply snap a photo of the broken desk and upload it to the Employee Self-Service Agent.

The agent will open a form and use information from the photo to create the help ticket right there. This image-based technology, like natural-language chat, is something that our previous apps couldn’t do, which reflects the power of AI. 

“Whether you upload a photo or just describe your issue using natural language, we’ve really pushed this tool to be as agentic as possible,” says Sonaly Choudary, a senior product manager who works on facilities technology products for Microsoft Digital. “The AI automatically picks out the problem class and the problem type; presents a form with the details; asks for confirmation; then kicks off the ticket right from there. And then you can query the agent to get status updates on it. It’s all in one place, AI-driven, and truly agentic in terms of task completion—and it will only get better.”

How Customer Zero makes our products better

Because Microsoft employees are the first ones to use our newest products and features, we have the opportunity to roll them out gradually and test them under actual enterprise-work conditions, which enables us to gather valuable feedback and telemetry. This data is then fed back into the product development process to make key improvements. We call this our Customer Zero philosophy.

“We were pioneers as Customer Zero in showing the need for these services in an employee-assistance portal, and the product group saw that need.”

Michelle Schaefer, principal product manager in Microsoft Digital

In the case of the Employee Self-Service Agent, we began product development by tackling HR and IT support, which were key areas to capture cost savings.

But how could we get even wider usage of the product? We turned to our real estate and facilities functions.

“The facilities and real estate aspect of Microsoft Digital is unique, in that it focuses on the employee experience at the company, literally in the buildings,” says Michelle Schaefer, a principal product manager in Microsoft Digital. “All those tasks—getting lunch, parking, filing a facilities ticket, moving around the campus, inviting a guest—are universal for all our employees. We were pioneers as Customer Zero in showing the need for these services in an employee-assistance portal, and the product group saw that need. And we’re constantly gathering telemetry to learn how our workers can more easily discover the agent and have a better experience with it each time.”

Adding the facilities and real estate category to the Employee Self-Service Agent also helped our engineers learn more about building an agent that presents a “single pane of glass” to the user on the front end but incorporates so many different functions on the back end.

“Our strategy with this new natural-language agent is to augment our existing tools, which brings AI to the experience and gets the user to the right place.”

Thomas Po, senior product manager, Microsoft Digital

Each team has its own tools that compete for our employees’ attention.

“The challenge was to turn all those into a common experience for the user,” says Erik Orum Hansen, a principal engineering manager for Microsoft Digital. “That’s been a learning journey for us, as the organization pivoted to developing a single agent incorporating all these different functions.”

This single-portal approach makes it so much easier for users to explore their options and figure out the best way to accomplish the task, even as the underlying tools are still available.

We still have as many as 15 different tools that employees use today for campus related tasks, but we’re managing them more effectively—now our employees only need to use them when their use case is more challenging or detailed in nature.

“Our strategy with this new natural-language agent is to augment our existing tools, which brings AI to the experience and gets the user to the right place,” says Thomas Po, a senior product manager for Microsoft Digital. “The user may not have the specific facilities app they need on their phone, but everyone has Copilot, right? It’s about giving our employees access to information in more places and connecting them to the right tool or function.”

Employee Self-Service Agent screenshot

The Employee Self-Service Agent can also see when an employee took prior action, recognize that they might want to take the same action again, and suggest that action—for example, suggesting that they may want to reserve a shuttle ride to the same location they’ve visited previously.

“This allows users to have a more contextual, conversational experience,” says Ram Kuppaswamy, a principal software engineering manager in Microsoft Digital. “For example, for transportation needs they can just type, ‘Help me book a campus shuttle,’ and the agent can suggest options based on their previous ride history. Then it can call up a form to help complete the booking. Users really love it.”

Built on the power of Copilot Studio

We built the Employee Self-Service Agent with Microsoft Copilot Studio, a powerful platform that allows you to create and extend AI agents. The agent is designed so that our customers can customize it to fit their own business needs and integrate it with their existing technologies.

“We didn’t want a custom connector; we wanted to go with an out-of-the-box connector that worked with Dynamics,” he says. “There were some product iterations to deal with while we made sure it met Microsoft’s data-compliance standards, but ultimately it made it easier to show customers how simple it is to implement the agent—it’s a very low-code/no-code solution.”

Erik Orum Hansen, principal engineering manager, Microsoft Digital

When we built the part of the Employee Self-Service Agent that handled HR and IT Support needs, we were able to create connectors for major third-party service providers in those areas, such as Workday, SAP, and ServiceNow. (These connectors are now “out-of-the-box capabilities” that are included in the product.)

In the facilities and real estate space, we have numerous vendors that we work with to provide various campus services. Since we already used various existing internal applications to connect employee requests with these vendors, we were able to create connectors for the agent easily using Copilot Studio. More importantly, we were also able to use the out-of-the-box Dataverse connector that worked with our Dynamics 365 data, which cut down on development time.

“The agent functions as a single entry point, which then connects with the Microsoft Dynamics data,” Schaefer says. “We have numerous different facilities vendors in different parts of the world, but we didn’t have to build multiple connectors to those vendors because of the common Dynamics back end.”

Orum Hansen says this caused a small delay in the internal deployment of the product, but that it was worth it in the end.

“We didn’t want a custom connector; we wanted to go with an out-of-the-box connector that worked with Dynamics,” he says. “There were some product iterations to deal with while we made sure it met Microsoft’s data-compliance standards, but ultimately it made it easier to show customers how simple it is to implement the agent—it’s a very low-code/no-code solution.”

“We’re also previewing more multi-agent capabilities that are coming from Copilot Studio, which our customers will be able to incorporate into their own solutions. The product is just going to get richer and richer over time, as it extends into other lines of business.”

Kirk Gregersen, corporate vice president, Microsoft Viva and Microsoft 365 Copilot Experiences

The future of workplace AI

In many ways, we’re still in the early stages of the revolution that AI agents are going to bring to the workplace.

But the Employee Self-Service Agent is a significant early marker on that path.

“The first step is to develop this agent that’s optimized for the HR, IT, and facilities verticals,” says Kirk Gregersen, corporate vice president of product for Microsoft Viva and Microsoft 365 Copilot Experiences. “We’re also previewing more multi-agent capabilities that are coming from Copilot Studio, which our customers will be able to incorporate into their own solutions. The product is just going to get richer and richer over time as it extends into other lines of business.”

As employees like Julie are already finding out, this new era of agentic AI is going to be a major improvement over what came before.

“Most companies already have some kind of employee-assistance portal solution,” Orum Hansen says. “With this new agent, there’s an opportunity to really reimagine the entire experience—to shed some of the old baggage and figure out how to do things differently. It’s going to lead to a more efficient workplace, along with more satisfied employees.”

Key takeaways

Here are a few factors to remember when implementing an AI-powered employee-assistance solution at your company:

• Pick high-value targets. Consider employee needs and the most commonly used assistance functions (using data where available), then develop a solution that addresses those areas. This will drive adoption and daily use of the agent.
• Customize the solution. Take advantage of the extensibility of Copilot Studio to develop an agent that fits your organization’s specific needs.
• Augment existing tools. Your employee-assistance agent can be the front door through which users find the tool they need. Over time, you can retire legacy tools and portals as the agent is able to complete the same functions on its own.
• Go beyond information retrieval. Employees want to be able to carry out tasks right from the agent, so incorporate forms and other technologies that allow them to accomplish their goal as quickly and easily as possible.
• Think outside the box. The image-driven feature we developed for filing a facilities ticket is a great example of applying the revolutionary abilities of AI to solve problems in new and innovative ways.    

Try it out

Learn more about the Employee Self-Service Agent.

Related links

• Read about the full scope of the impact the Employee Self-Service Agent is having on our organization.
• Learn about our strategic approach to agentic AI internally at Microsoft. 
• Explore how the Employee Self-Service Agent is helping Puget Sound-based Microsoft employees with their transportation needs.
• Explore how Microsoft HR is using Viva and Copilot to empower our employees.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post Reimagining campus support at Microsoft with the Employee Self-Service Agent appeared first on Inside Track Blog.

At Microsoft Digital, the company’s IT organization, we’ve been on the front lines of this AI-powered revolution, translating vision into reality and reimagining what’s possible for the enterprise.

“We’ve learned so many lessons over the past few years building AI-powered solutions and driving an AI-forward culture. We’re excited to share them with our customers and partners so they can learn from our journey.”

Brian Fielder, vice president, Microsoft Digital

As generative AI leapt into the mainstream with the arrival of models like OpenAI’s GPT-3.5 and transformative tools such as Microsoft 365 Copilot, the stakes for IT leaders have never been higher.

The challenge isn’t just about deploying the latest AI tools—it’s about architecting a foundation for sustained, responsible, and scalable change across the enterprise.

That’s where this guide comes in. We’re opening a window into our own AI evolution—sharing our hard-won lessons, proven frameworks, and actionable steps that can help you steer your organization from AI exploration to AI acceleration. Whether you’re just beginning your journey or ready to scale enterprise-wide adoption, this guide is built to empower you to make informed decisions, sidestep common pitfalls, and unlock the full promise of AI-driven transformation.

“We’ve learned so many lessons over the past few years building AI-powered solutions and driving an AI-forward culture,” says Brian Fielder, vice president of Microsoft Digital. “We’re excited to share them with our customers and partners so they can learn from our journey.”

Read on to discover how we moved from AI vision to AI reality here in Microsoft Digital. You’ll learn how you can drive measurable business outcomes while building a culture that’s ready for what’s next.

The five stages of AI-powered transformation

We have led Microsoft through five stages of AI maturity—from initial exploration to becoming an AI-driven enterprise. This has been a three-year journey, and you and your digital leaders will need to be prepared to take time to fully experience each of these stages to truly unlock the potential of AI to transform your enterprise.

What follows is a stage-by-stage summary of how we achieved our transformation, followed by a list of empowering actions you can take to help you on your own journey.

Mapping our journey to AI maturity

Stage 1: Awareness and foundation

Set a bold vision for your AI journey, anchored in clear business outcomes—avoid implementing “AI for AI’s sake.” Engage your executive sponsors early and form an AI Center of Excellence (CoE) to foster cross-functional collaboration and empower experimentation. Establish Responsible AI principles alongside your organization’s ethics team and assess your data readiness from the start—remember, “no AI without data.” By building these foundations, you’ll position your teams to confidently launch AI initiatives and drive meaningful transformation.

Target outcomes

A foundational strategy, governance principles, and leadership buy-in to kickstart AI projects.

Learn more

Learn how we’re responding to the AI Revolution with an AI Center of Excellence.

“At the Microsoft Digital AI Center of Excellence, we’ve learned that combining strong governance, data readiness, and a continuous-improvement mindset transforms AI pilots into enterprise-scale solutions,” says Nitul Pancholi, the AI CoE lead in Microsoft Employee Experience. “This guide distills our three-year journey into clear, actionable steps to accelerate responsible AI adoption, mitigate risk, and drive measurable business impact.”

Stage 2: Active pilots and skill building

To accelerate your AI journey, start by launching targeted pilot projects across diverse areas of your organization—think automated support chatbots or network analytics. Encourage experimentation and leverage hackathons to surface a broad range of ideas. Narrow these down to your most promising initiatives by evaluating business value against implementation effort and focus resources on a select group of high impact “big bets.”

Empower your teams by investing in upskilling: offer discipline-aligned learning paths, issue digital credentials, and celebrate progress to foster a culture of continuous learning and knowledge-sharing. Establish early-stage governance by requiring all pilots to undergo Responsible AI and architectural reviews. By following these steps, you’ll create early momentum, build internal expertise, and identify the AI solutions most likely to drive meaningful impact at scale.

Target outcomes

The first tangible benefits of AI: efficiency gains, time and cost savings, and quality improvements, and an internal talent pool emerging, paving the way to scale successful solutions.

Learn more

Find out how we’re embracing AI at Microsoft with new AI certifications.

Stage 3: Operationalize and govern

To scale and integrate AI solutions across your organization, move beyond pilot projects by deploying AI solutions directly into production and embedding them within core business workflows.

Strengthen your data and AI infrastructure—consider implementing a unified data platform and robust Machine Learning Operations (MLOps) pipelines—to support this transition. Formalize enterprise governance with clearly defined steering teams: empower your AI Center of Excellence to accelerate implementation and establish a Data Council to ensure data quality and “AI-ready” assets and a Responsible AI Office to oversee ethical use and compliance. Encourage collaboration among these groups and designate domain leads to ensure your AI initiatives consistently deliver tangible business value.

By putting these practices in place, you can drive successful scaling and operationalization of AI throughout your enterprise.

Target outcomes

Multiple AI use cases running at enterprise scale under robust oversight with cross-functional alignment on AI objectives and the business value they’re delivering.

Learn more

Read our guide for tackling Microsoft 365 Copilot governance your company.

Stage 4: Enterprise-wide adoption

To consolidate your gains and achieve AI adoption across the enterprise, make AI a core consideration in every new project and process.

Ask where AI-driven intelligence can deliver real impact, whether by boosting efficiency, enhancing user experiences, or unlocking new business value. Align AI initiatives with your organization’s strategic goals by empowering business leads to synchronize efforts and continuously update your AI roadmap. Cultivate a data-driven culture through ongoing, large-scale training and make AI tools a natural part of everyday work. Establish rigorous impact tracking with clear metrics for value delivered—such as time savings, cost reduction, and quality improvements—and review these outcomes regularly at the leadership level to maintain accountability.

By integrating these practices, you can drive AI adoption throughout your organization and ensure sustained, measurable impact.

“What’s unique about our approach is that every agent is engineered for responsible action. We design agents to operate within enterprise workflows, guided by policy-aware controls, telemetry integration, and human oversight,” says Faisal Nasir, the AI CoE and Data Council lead in Microsoft Employee Experience.

Through the AI Center of Excellence and the Data Council, we ensure agents are grounded in AI-ready data and undergo comprehensive architecture and governance reviews.

“This ensures our AI solutions are not only intelligent, but also accountable, governable, and fully production-ready,” Nasir adds.

Target outcomes

AI is a pillar of your operational strategy, backed by a data-driven culture and continuous monitoring of business impact.

Learn more

Learn how we’re approaching Microsoft 365 Copilot change management at Microsoft.

Stage 5: Transform your business with agentic AI

To drive a lasting AI-powered business transformation, organizations must embed AI into every aspect of their operations and culture.

Start by leveraging the expertise of your AI CoE to foster innovation, drive continuous improvement, and keep your AI initiatives evolving. Use structured mechanisms like a Kaizen funnel to crowdsource, prioritize, and advance ideas that extend the impact of AI across the enterprise.

Strengthen governance to address the advanced challenges of agentic applications, including responsible scaling of generative AI and effective mitigation of AI hallucinations. Focus on refining human-AI collaboration so your teams are empowered to offload routine tasks to AI agents and concentrate on higher-value work.

Another tactic that’s been highly successful in Microsoft Digital is “Fix, Hack, Learn” weeks, where employees are encouraged to identify opportunities to improve our services. Multi-disciplinary teams are empowered to innovate with AI to improve our organizational effectiveness, yielding multiple AI-powered breakthroughs that are already in production.

“In Microsoft Digital, continuous improvement is a driving force behind our AI transformation,” says Don Campbell, principal product manager within Microsoft Digital and member of our AI Center of Excellence. “By embedding it and AI into every layer of our operations, we’re not only optimizing how we work today, but we are also strategically preparing our processes to become agentic tomorrow. This disciplined approach ensures that when we make a process agentic, it’s not just automated—it’s intelligent, secure, and purpose-built to scale across the enterprise.”

Target outcomes

An organization transformed by AI, achieving significant efficiency gains and innovations, and recognized as a leader in enterprise AI adoption.

Learn more

Guiding hands: take a look inside the councils steering AI projects here at Microsoft.

What our experts have to say:

“In Microsoft Digital, continuous improvement is a driving force behind our AI transformation. By embedding it and AI into every layer of our operations, we’re not only optimizing how we work today, but we are also strategically preparing our processes to become agentic tomorrow.”

Don Campbell, principal product manager and CoE member, Microsoft Digital

“At the Microsoft Digital AI Center of Excellence, we’ve learned that combining strong governance, data readiness, and a continuous-improvement mindset transforms AI pilots into enterprise-scale solutions. This guide distills our three-year journey into clear, actionable steps to accelerate responsible AI adoption, mitigate risk, and drive measurable business impact.”

Nitul Pancholi, AI Center of Excellence lead, Microsoft Employee Experience

 “What’s unique about our approach is that every agent is engineered for responsible action. We design agents to operate within enterprise workflows, guided by policy-aware controls, telemetry integration, and human oversight.”

Faisal Nasir, AI CoE and Data Council lead, Microsoft Employee Experience

Enabling success—lessons from our journey as the company’s IT organization

Achieving AI maturity is dependent on a combination of technological, organizational, and cultural factors. These enablers support the successful adoption and integration of AI within the organization.

For IT decision-makers charting the course to enterprise-scale AI, the journey is about far more than technical implementation—it’s about activating the right enablers to unlock both rapid and sustainable business impact.

Successfully scaling AI means orchestrating executive vision, robust governance, responsible innovation, resilient data foundations, and a culture of empowered talent—all working in harmony. Each of these levers is crucial not only for accelerating the path from pilot to production, but also for ensuring that every AI initiative delivers measurable outcomes, mitigates risk, and creates lasting organizational value.

By prioritizing these foundational pillars, IT leaders can fast-track value realization, embed accountability, and transform AI from a promising experiment into a strategic engine for competitive advantage. The following items explore the essential enablers that drive AI maturity at pace and why they matter now more than ever for organizations determined to lead in the age of intelligent transformation.

Seven enablers of enterprise AI transformation

Executive sponsorship and governance

To accelerate AI maturity within your organization, start by securing strong executive sponsorship and establishing clear governance structures. Appoint dedicated AI leaders and form cross-functional teams such as an AI Center of Excellence and supporting councils with well-defined roles and responsibilities. Maintain alignment with your business strategy through regular steering meetings and roadmap reviews. This approach will ensure your AI initiatives remain focused, impactful, and strategically integrated across the enterprise.

Responsible AI by design

To embed ethics and effectively manage risk in every AI project, integrate Responsible AI principles from the outset. Establish a Responsible AI Council or similar oversight group to ensure all solutions are rigorously reviewed for ethical standards before launch. By instituting mandatory Responsible AI assessments, you’ll foster trust, safeguard your organization, and address potential issues proactively—setting a strong foundation for sustainable AI adoption. This not only reduces reputational and regulatory risk, it also enables faster adoption, strengthens stakeholder confidence, and ensures AI initiatives deliver lasting value aligned with your business goals.

Data foundation, architecture reviews, and technical readiness

Treat data as a strategic asset by establishing a unified data strategy—start with a Data Council to catalogue key sources, improve data quality, and implement robust governance and access controls. Build AI-readiness across your enterprise by embedding architecture reviews and design validation into your engineering lifecycle, ensuring every solution is scalable, composable, and compliant by design. Leverage architecture forums to crowdsource feedback, align on technical standards, and promote reusable patterns that accelerate delivery. With secure cloud environments, ML Ops pipelines, and standardized AI platforms in place, your teams will be equipped to develop and scale AI solutions quickly, safely, and consistently.

Talent, skills, and culture

To build an AI-ready workforce and foster a culture of innovation, prioritize company-wide training and upskilling programs that elevate AI literacy at every level. Establish a Center of Excellence and empower “AI champions” within teams to drive adoption and celebrate meaningful impact. Encourage open collaboration—share code, best practices, and project outcomes across your organization—to accelerate learning and scale success. By breaking down silos and enabling employees to experiment with intelligent solutions, you’ll create the environment needed for sustained growth and enterprise-wide transformation. In Microsoft Digital, we are not just training our employees to use AI, we are empowering them to co-create the future of their roles. When employees are empowered to build and govern their own agents, that is when transformation truly scales.

Impact tracking and accountability

To drive meaningful business impact with AI, start by defining clear, measurable success metrics—think hours saved, cost efficiencies, and quality improvements—that can be rolled up into an organizational AI scorecard. Review these outcomes regularly at the leadership level to keep the focus on what matters. For every major AI initiative, assign an accountable owner who champions the solution, communicates the business story, and manages performance reporting.

Foster transparency by consistently comparing targets to actual results and openly sharing lessons learned when goals are missed. By embedding accountability into your rhythm of business, you’ll enable agile decision-making, concentrate your efforts where AI delivers the most value, and nurture a culture of continuous improvement. In Microsoft Digital, we’ve defined an AI value measurement framework with six dimensions of value that you can use as benchmarks to determine the impact of your own investments.

Change management and communication

To drive successful AI adoption, treat it as a people-first transformation—not just a technology deployment. Start by developing robust deployment and adoption plans for your key solutions: invest in training, craft clear communications, and establish dedicated support channels such as FAQs and help desks. Maintain a steady pulse of communication with your stakeholders—consider newsletters, interactive town halls, and a centralized library of AI success stories to celebrate impact and progress. By prioritizing transparency and providing ongoing support, you’ll smooth the path to change, encourage enthusiastic adoption, and sustain momentum throughout your organization.

Continuous improvement, innovation, and partnerships

To drive continuous improvement and innovation with AI, keep a dynamic backlog of opportunities and support each with a clear value case and refresh your pipeline regularly. Adopt structured forums such as continuous improvement and Kaizen events to identify, evaluate, and prioritize new AI use cases that deliver tangible business outcomes. Use a robust prioritization framework to ensure focus on initiatives with the greatest impact.

Identify partner teams who can serve as early adopters and provide feedback to inform your continuing journey. By building a disciplined innovation pipeline and fostering a collaborative ecosystem, you create a foundation for ongoing experimentation, accelerated learning, and sustainable AI innovation across your organization.

Advancing your organization into the frontier of AI

To embrace the next era of AI, it’s time to look beyond traditional automation and prepare your organization for agentic AI frameworks and autonomous, interoperable agents. These advanced systems aren’t just digital assistants—they’re designed to plan, act, and collaborate across workflows with minimal intervention, offering the potential to fundamentally transform how work gets done.

Start by identifying areas where agentic AI can drive real business value. Empower domain experts within your teams to become Agent Leaders—individuals who can design, oversee, and govern agent ecosystems at scale. Align your AI strategy with forward-looking industry insights and best practices—sources like the 2025 Annual Work Trend Index: The Frontier Firm Is Born offer invaluable guidance for responsible AI adoption and organizational transformation.

Recognize that the impact will be significant. Industry analysts such as Gartner predict that by 2028, about a third of enterprise applications will feature agentic AI capabilities and over 15% of daily work decisions will be handled by AI agents.

Evolving from large language models to agents

To get ahead, foster a culture of experimentation. Host hackathons, pilot agentic AI prototypes, and develop governance frameworks that ensure responsible management of these emerging technologies. Treat your AI journey as a continuous process—a growth mindset and incremental progress are key. As AI evolves, so should your practices: be ready to adapt your governance, refine human-AI collaboration, and embrace new paradigms like fully autonomous agents.

Each stage of this journey unlocks new possibilities. Ensure your organization remains at the forefront of AI maturity by committing to continuous improvement and innovation. The future of work isn’t a destination—it’s a dynamic path. Evolve your strategy, cultivate expertise, and enable your teams to thrive in the rapidly advancing digital landscape, powered by AI innovation and continuous improvement.

Key takeaways

To help your organization progress on its AI journey, consider the following strategies:

• Invest in data infrastructure and AI platforms. Building robust data infrastructure ensures your organization is prepared to leverage AI, supporting scalable, innovative, and secure AI-driven solutions.
• Foster a culture of innovation and collaboration. Champion an AI-forward culture where innovation and collaboration drive the adoption of agentic AI.
• Develop AI expertise through training and development. Upskilling your teams empowers them to navigate the rapid advances of AI, drive innovation, and ensure your organization stays competitive as agentic AI transforms workflows and business outcomes across every industry.
• Align AI initiatives with strategic business goals. Ensuring AI initiatives align with business goals maximizes impact and positions your organization to succeed in the rapidly evolving world of agentic AI.
• Implement ethical AI practices based on Microsoft’s Responsible AI Principles. Adopting ethical AI practices builds trust, ensures responsible innovation, and prepares your organization to navigate the evolving landscape as AI becomes central to business operations and decision-making.

Try it out

Read our guide for deploying and driving adoption of Microsoft 365 Copilot.

Related links

• Learn how we’re using good governance to ride the wave of agents washing over Microsoft.
• Check out how we’re embracing this new ‘agentic’ moment at Microsoft.
• Take a look inside the councils steering AI projects here at Microsoft.
• Find out how we’re unlocking enterprise AI extensibility at Microsoft with Copilot Studio.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post Enterprise AI maturity in five steps: Our guide for IT leaders appeared first on Inside Track Blog.

That’s the best way to think about the new Audio Recap feature in Microsoft Teams.

Designed to cut through the noise of information overload, it’s a new feature that transforms recorded meetings into easy to digest podcast-style summaries.

For our employees juggling scheduling conflicts, this feature is a game-changer—instead of sifting through lengthy transcripts or replaying entire recordings, they can quickly catch up by listening to concise, tailored recaps.

“It’s like putting your meetings in your earbuds,” says Lesley Montgomery, a principal product manager within Microsoft Digital, the company’s IT organization. “It’s flexible, mobile, and makes catching up on meetings unexpectedly engaging.”

Think about your favorite podcasters talking conversationally about a meeting that you need to catch up on—that’s what this is like.

Boosting meeting accessibility in the modern workplace

Our employees frequently find themselves double- or even triple-booked, forcing them to choose which meetings to attend live and which to skip. Audio Recap provides a practical solution by making missed content far more accessible. With this feature, employees can catch up on discussions while commuting, working out, or even during short breaks between tasks. No need to carve out extra time to sit down at a desk, open a transcript, and scroll through pages of text.

“With Audio Recap, any recorded Teams meeting can be rendered as an audio recap, like a podcast. Instead of reading through a transcript or replaying the entire recording, it lets you take a recorded meeting and turn it into a podcast session.”

Lesley Montgomery, principal product manager, Microsoft Digital

Audio Recap also reflects the reality and needs of today’s digital-first culture, where people expect information to be quick, available on mobile, and consumable on their own terms. Just as TikTok popularized short-form video and podcasts redefined long-form storytelling, Audio Recap is a new medium for workplace knowledge sharing—one that respects time, privacy, and attention spans.

“With Audio Recap, any recorded Teams meeting can be rendered as an audio recap, like a podcast,” Montgomery says. “Instead of reading through a transcript or replaying the entire recording, it lets you take a recorded meeting and turn it into a podcast session.”

Audio Recap allows for a high degree of customization, and users can tailor how their recap is delivered—choosing the timeframe, selecting up to eight meeting transcripts, and picking from three distinct podcast styles to match their listening preferences:

• Executive: Dual-host format highlighting strategic insights, critical decisions, and essential context
•  Newscast: Single-voice delivery focused on key facts for quick, no-frills catch-up
•  Casual: Conversational dual-host style offering lighter, more engaging summaries

This level of personalization ensures that each employee gets the version of the recap that works best for them. Some may want the highlights in five minutes; others may prefer a more narrative-style recap to catch subtle details.

“I literally just did an audio recap of some meetings this week,” says Sara Bush, a principal PM manager within Microsoft Digital. “And they were so good that I took the transcript for one and made it into a PowerPoint deck—all using AI, in minutes. I chose the newscast version, which is more succinct.”

Audio Recap also streamlines meeting reviews through consolidation. Instead of jumping between multiple meeting links or trying to track down recordings, users can view all recorded meetings in a single, unified space. By stitching together multiple recaps, Audio Recap creates a smoother experience and helps reduce friction in catching up on important discussions.

This also ensures employees don’t miss critical updates, even if their calendars are packed. Imagine a day with five overlapping meetings. Instead of toggling between recordings and transcripts, an employee can simply request audio recaps of each meeting and listen to them in sequence. It’s like having a personalized “meeting playlist” that makes the workday easier to manage.

Designed for users, built on privacy and convenience

Audio Recap was developed out of a collaboration between our product groups and our team here at Microsoft Digital, acting as Customer Zero for the company, which means testing features internally before the company rolls them out to customers. Our focus has been squarely on user benefit, not just product capability. By looking closely at how Audio Recap fits into real workflows, we’ve ensured the feature aligns with user needs. The guiding principle for us is to meet employees where they are and let them consume meeting information in ways that feel natural, intuitive, and efficient.

Privacy is another element that Audio Recap adds to the meeting replay experience. Reading transcripts or replaying video meetings can lead employees to feel exposed, especially in shared workspaces where colleagues might glance at their screen. With audio, employees can simply plug in their headphones and consume content discreetly. This not only protects sensitive information but also adds comfort and flexibility. Whether at home, in the office, or on the go, users can catch up on meetings without feeling tethered to a desk.

“You can be mobile, take it with you, and listen on the go—without worrying about someone looking over your shoulder,” Montgomery says. “It’s flexible, convenient, and makes catching up on meetings a fun and engaging experience.”

Staying current with generation TikTok

The workplace is evolving alongside cultural shifts in how people consume content.

“With this solution, we’re solving for time. We’re simplifying and democratizing communication in the ways that people take it in best, or prefer to take it in.”

Sara Bush, principal PM manager, Microsoft Digital

Quick, engaging formats on mobile devices dominate outside of work—and employees expect similar options inside the workplace.

Audio Recap taps into this trend by making meeting content consumable in the same way people enjoy podcasts or streaming audio.

By offering meetings in podcast form, Microsoft Teams continues to evolve as a modern, forward-looking platform that keeps pace with the changing expectations of a digital workforce.

“With this solution, we’re solving for time,” Bush says. “We’re simplifying and democratizing communication in the ways that people take it in best, or prefer to take it in. For example, this podcast summary for my drive to work is a perfect format for me, whereas that quick video format might be just right for somebody else.”

Audio Recap is part of the company’s broader effort to reshape how work gets done in a digital-first era. By giving employees the freedom to decide how they consume meeting information, Teams becomes not just a tool for collaboration, but a productivity amplifier.

Meetings are a necessary part of work, but how we handle the content they generate doesn’t have to feel outdated. Audio Recap makes catching up not only easier, but also more enjoyable—and where time and attention are in short supply, this shift is invaluable.

Key takeaways

If you’re interested in providing employees with a new productivity tool to streamline Teams meeting recaps, take note of these practical scenarios where Audio Recap shines:

• Overbooked calendars: Catch up on two or three meetings you couldn’t attend live without wasting extra hours.
• Long commutes: Turn drive time or train rides into productive catch-up sessions.
• Global teams: Recaps can bridge time zones, letting employees listen when it’s convenient rather than staying up for late-night calls.
• Focus time: Instead of multitasking during a live meeting, employees can skip it, then consume the recap later when they can give it full attention.

Try it out

Download Microsoft Teams today.

Related links

• Discover intelligent recap for Teams calls and meetings.
• Listen to an audio recap of your meetings in Teams.
• Read an overview of AI in Microsoft Teams for IT admins.
• Generate audio overviews with Copilot in OneDrive.
• Meet your AI Companion.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post ‘Putting your meetings in your earbuds’: How we now catch up on missed meetings with Audio Recap podcasts appeared first on Inside Track Blog.

People are using Microsoft 365 Copilot as their personal AI assistant and employing agents to power new workflows. Meanwhile, our teams are building and deploying AI-powered solutions to meet our enterprise needs.

But advancing along the AI maturity curve means more than just adoption. It’s about fundamentally reworking our daily habits to boost productivity and empower our AI assistants to help us accomplish meaningful work.

At Microsoft, we’re dedicated to helping our employees weave Copilot and other AI tools into the fabric of their workdays. To get there, we’ve used the lessons from our early skilling efforts and our experience with peer-to-peer adoption leadership as the foundation for a new learning path.

This is the story of Copilot Expo.

A new approach to skilling

Thanks to the success of our Camp Copilot adoption efforts, we learned valuable lessons about rolling AI out across a company like ours.

We took what we learned working with our champ community and turned it into a more formal Microsoft 365 Copilot adoption program that evolved into an extended company-wide event called Copilot Expo. Our change leaders within Microsoft Digital, the company’s IT organization, drove this three-week online skilling path with the support of our dedicated community of AI peer leaders, the Copilot Champs.

“We saw daily adoption move a lot more when we were presenting content that was bespoke to people’s roles and organizations.”

Stephan Kerametlian, business program management senior director, Microsoft Digital

As AI technology matured, we knew we needed to update our skilling offerings along with it. Some key lessons helped us make that a reality:

• AI adoption is about more than monthly active usage (MAU) and daily active usage (DAU). It’s about depth of engagement with the tools.
• Peer leadership is a must. Seeing people you know use a tool makes it much more accessible and attainable.
• Gamification was one of the most successful features of our early efforts, so we knew we needed to deepen those elements.
• Making content on-demand extends the life of an event like this, leading to easier knowledge discovery and further engagement.
• Company-wide initiatives are powerful, but divisions crave events tailored to their work, on their teams, in their disciplines.

“We saw daily adoption move a lot more when we were presenting content that was bespoke to people’s roles and organizations,” says Stephan Kerametlian, a business program management senior director within Microsoft Digital. “Copilot Expo was able to go a lot deeper into different roles and processes to make Copilot more real in people’s day-to-day jobs.”

Copilot Expo: Advancing along the AI maturity curve

Copilot Expo extended throughout three weeks, with plenty of opportunities for learning at different levels of AI maturity.

Our curriculum included three main sessions for the week. To accommodate different time zones with live presentations instead of recordings, each of those sessions took place three times across 12 hours. After each main session, breakouts expanded on their themes, highlighting different areas of Microsoft 365 Copilot.

Some breakouts covered day-in-the-life scenarios that resonated with a wide cross-section of employees, but we also tailored use cases to more specific disciplines and tasks. As a result, the learning path included more role-specific breakouts like “Copilot for Product Managers,” more technical topics outside Copilot like GitHub and Azure DevOps, and more advanced learning like deep dives on prompting.

To help land the lessons for the week, we offered gamified experiences on Microsoft Viva Engage. These activities typically involved a creative prompting exercise, which participants would then share with their Viva Engage communities. As an added bonus, the social aspect helped drive further groundswell for Copilot Expo.

“Peer influence can scale further and faster than policy alone. Employees show a lot more interest in content their colleagues create than material handed down from IT or adoption professionals.”

Cadie Kneip, readiness business program manager, Microsoft Digital

The sheer number of sessions meant we needed to expand the involvement of Microsoft Digital subject matter experts and change leaders, but it was absolutely essential that we involve our Copilot Champs and maintain the peer-to-peer aspect that made Camp Copilot such a success.

Why?

Because we find that our employees respond well when a respected colleague shows them how to do something or shares why they are excited to try something new.

“Peer influence can scale further and faster than policy alone,” says Cadie Kneip, a readiness business program manager within Microsoft Digital. “Employees show a lot more interest in content their colleagues create than material handed down from IT or adoption professionals.”

When participants completed the learning path, we handed out awards, shared resources, and provided opportunities for feedback. All of these elements helped employees feel a sense of accomplishment while providing our adoption team with valuable insights.

We also updated our key metrics around Copilot usage and sentiment. To make sure these metrics demonstrated meaningful change, we tracked them for comparable periods both before and after Copilot Expo.

Gamification drives deeper engagement

When we developed the plan for Copilot Expo, we knew gamification was one of the most powerful levers we could pull. Not only does it provide a fun way for participants to practice the skills they’ve learned, but it boosts retention and uptake.

Our internal research suggests that fun and gamification amplify engagement by 24% and increase productivity by 50%. They also reduce the time it takes to form habits by 40%.

“You need to think about the activities you can do to inspire your employees to recognize the value AI can hold for their work.”

Sandra Hausfelder, global adoption lead, Microsoft Digital

One of the most exciting components was a live leaderboard featuring participants’ avatars and gamertags created using Microsoft 365 Copilot. The dashboard assigned people points when they completed different components of the curriculum, and the friendly competition boosted engagement through a sense of pride.

We also increased the number of gamified activities that took place throughout the learning path. Yet again, our presenters and peer-to-peer leaders provided essential support, and we were able to crowd-source many of these gamification ideas.

Gamified activities included:

• Creating a new digital avatar by prompting Microsoft 365 Copilot.
• Building a unique superhero.
• Writing a song with Copilot’s assistance.
• Creating digital swag by designing an enamel pin.
• Going on a scavenger hunt by trying out 10 Copilot scenarios.

“You need to think about the activities you can do to inspire your employees to recognize the value AI can hold for their work,” says Sandra Hausfelder, a global adoption lead for Copilot in Microsoft Digital.

At the end of Copilot Expo, we offered MVP badges designed using Credly for everyone who completed all the necessary steps. In addition to solidifying the learning with a final motivator, providing a badge encouraged participants to share their journey with their networks, further promoting Copilot Expo as an opportunity for professional growth.

Decentralization and on-demand learning

One of the most important aspects of Copilot Expo is its capacity for extending learning opportunities beyond our centralized event series. We’re accomplishing that in two ways.

First, we make all of our Copilot Expo content available on demand as part of a persistent SharePoint page accessible to both participants and non-participants. These resources aren’t just for passive discovery. We also use them for active adoption efforts like our “Copilot Daily Discoveries” campaign on Microsoft Viva Engage.

Since the end of Copilot Expo, employees have accessed these resources thousands of times—even people who didn’t participate in the event series itself. That demonstrates a real hunger for opportunities to learn about AI.

The greatest potential impact may come from decentralizing this learning model. Company-wide events can only do so much to bridge time zones, languages, and discipline-specific scenarios.

As a result, we’ve designed a system for enabling more tailored events within individual regions and Microsoft divisions. Essentially, we’ve templatized the Copilot Expo experience, and leaders can reach out to the Microsoft Digital team to help assemble and run their own events with more customized learning paths.

Building momentum with activities

We start by conducting discovery sessions and interviews that uncover how employees might use Microsoft 365 Copilot in their roles. We also look at existing usage metrics and identify Copilot Champs who can act as advisors and ambassadors.

“We have a baseline package of material, and then we partner with organizational executives and change leaders who want to bring it to their own teams,” Kneip says. “Then we work with Copilot Champs to tailor it to their organizations.”

These focused events typically take shape as three-day learning paths. They tend to cover similar elements to the company-wide expo across the basics, leveling up, and building daily habits. The difference is that they’re highly scenario-specific.

For example, we might provide example scenarios for the Cloud + AI team, like “Give me suggestions for optimizing our next datacenter.” On engineering-heavy teams, we might focus on opportunities for AI in the software development lifecycle.

“Every mini-expo looks a little bit different because we customize it to the organization,” Hausfelder says. “We work hard to create a span of customization by looking into the details of what the organizations need us to land for their employees.”

Continuous impact through more effective adoption

Whether they’re division-based or specific to a region, these learning paths have been highly effective. In one instance, we ran a three-day event specific to Central America and the Caribbean. That led to a 15% increase in DAU and a 17% increase in week-over-week Microsoft 365 Copilot usage.

“Copilot Expo sets us up for success in the future, because it’s a delivery mechanism for employees, by employees, scaled through Copilot Champs.”

Alexandra Jones, director of business programs, Microsoft Digital

Our company-wide Copilot Expo also demonstrated substantial impact. Before-and-after tracking of key metrics over equivalent testing periods revealed substantial boosts:

• Average DAU increased substantially.
• Copilot-assisted hours climbed sharply.
• Copilot actions taken jumped significantly.
• Copilot-assisted value nearly doubled.
• The perception of the quality work done with Copilot measurably increased.

It’s a testament to the power of coordinated efforts that reach across the company as a whole and resonate with individual organizations.

“We’ve created this persistent platform as a recognizable brand for skilling, and it enables us to continue driving change,” says Alexandra Jones, a director of business programs within Microsoft Digital. “Copilot Expo sets us up for success in the future, because it’s a delivery mechanism for employees, by employees, scaled through Copilot Champs.”

Key takeaways

Adopt the lessons we’ve learned during the Microsoft Copilot Expo to successfully run your own AI skilling event.

• Listen to stakeholders: Collaborate with organizational insiders to think about the gaps they see and the content that will be relevant to their teams.
• Design your content for discovery: Evolve your offerings to be more self-serve and self-directed while maintaining crucial opportunities for connection.
• Start small and apply the lessons you learn: Begin with a pilot. Bring eager adopters together and run a small and focused expo.
• Gamification gets results: People take delight in demonstrating progress and participation. Incorporate badges, certifications, leaderboards, and other elements of fun.
• Identify your key metrics: Don’t just think about usage percentage. Focus on metrics that really demonstrate value. Examples include the number of actions, Copilot-assisted hours, and sentiment.

Try it out

Get step-by-step instructions for creating an engaging Microsoft 365 Copilot training series with our Copilot Virtual Skilling Event Framework.

Related links

• See how we made Microsoft 365 Copilot adoption fun with Camp Copilot.
• Try our 7 tips for driving Microsoft 365 Copilot adoption with a virtual skilling event.
• Learn how we’re driving Microsoft 365 Copilot adoption with our Copilot Champs Community.
• See how we’re transforming our employee experience with AI.
• Supercharge your business transformation with Microsoft Viva.
• Unleash API-powered agents at Microsoft: Our internal learnings and a step-by-step guide.
• Unlock your productivity with these Top 10 tips for using Microsoft 365 Copilot every day.

We’d like to hear from you!

• Want more information? Email us and include a link to this story and we’ll get back to you.

The post Enabling meaningful AI adoption at Microsoft with a Microsoft 365 Copilot Expo appeared first on Inside Track Blog.