Bringing AI Agents for Troubleshooting

Overview

As part of improving Azure’s quota management experience, I led the integration of an AI Agents (Copilot) into cloud workflows to enable users to land on a root cause and a safe fix.

This project builds directly on the work outlined in the previous case study.

Year

2024 - 2025 at Microsoft

Role

UX/UI Design

Bringing AI Guidance to Cloud Workflows

Year

2024 - 2025

My role

Lead Designer

Team

Research, Engineer, PM

What's been done

As part of improving Azure’s quota management experience, I led the integration of an AI-powered solution (Copilot) into cloud workflows to reduce failure-related friction and better support users in real time.

Impacts

  • Uncovered key friction points and integrated AI solutions grounded in user needs
  • Increased CSAT from 25% → 75%
  • Reduced quota and capacity issues by 70%
  • Cut cloud workflow failures by 50%

Challenge

Users want to know why errors are happening and how to fix them quickly

When cloud tasks fail due to limit issues, users struggle to understand why it happened and what to do next. The current experience offers little guidance, leaving users confused, frustrated, and dependent on support.

“I need to understand why things failed and how to fix it myself”
- user interview

Opportunity

Provide real-time, in-context guidance right at the point of failure

Building on prior research, I identified a strategic opportunity to embed AI agent (Copilot) at failure points, moments when users were blocked, confused, and unsure what to do next.

Why AI?

Users need help that is:

  • Immediate. No waiting on support tickets
  • Actionable. Next steps, not just error messages
  • Contextual. Surfaced right when and where the issue occurs

What Copilot enables:

  • Real-time explanations for failures
  • Relevant actions like retrying with recommendation
  • A guided experience, users feel supported, not stuck

Design Process

Integrating Copilot into Critical User Journeys

To provide timely, in-context guidance, I embedded Copilot at moments of highest friction where quota issues disrupted workflows the most. This made support immediate, seamless, and confidence-boosting.

I facilitated a workshop with PMs, ENGs, and the Copilot UX team to review design, align feasibility, and validate technical constraints.

02

Define & Validate Opportunities

Reviewed existing solutions with PMs to understand what worked, what didn’t, and where improvements were needed.

Outcome: Confirmed Copilot would have the biggest impact in pre-deployment and post-deployment.

Final Solutions

Quota issues still happen but now users know why, and how to fix them

With Copilot embedded at failure points, users now get clear explanations, actionable next steps, and visibility into the quota system.

Learnings

Keep conversations concise and efficient. Reduce unnecessary back-and-forth by bundling related questions, helping users reach solutions faster.

Trigger Copilot in the right context. Users find AI most valuable when it appears in the right context, not as a generic option.

Offer clear next steps. Guiding users with actionable, immediate options.

Takeaways

AI integration is not just a UI layer. It requires deep understanding of backend logic, user context, and system limitations to make the guidance feel meaningful and trustworthy.

Next Steps

Pilot testing and user validation. Gather feedback from real users interacting with the Copilot integration to refine flows, messages, and timing.

Expand Copilot to other friction points. Use the same design principles to identify additional entry points where Copilot can support the user.

More work this way

Microsoft, Azure
Reshaping Cloud Quota Management UX
Microsoft, AI
Designing for Responsible AI at Scale
Microsoft, m365
Streamlining M365 Adoption Through Better Self-Guided UX
Personal project
A Minimal Scorekeeping App
Personal project
Daily UI Challenges