Bringing AI Guidance to Cloud Workflows

As part of improving Azure’s quota management experience, I led the integration of an AI-powered solution (Copilot) into cloud workflows, enabling users to self-troubleshoot issues and providing clearer guidance and visibility into the cloud system.

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

Timeline

2024 - 2025

Role

Product Designer

Team

Research, Engineer, PM, Copilot

Responsibilities

User Research, Prototype

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

Quota issues are consistently happening: Users had no clarity on why, or how to fix them

Data and research revealed that cloud users often struggle to understand why their workflows fail, especially when the root cause relates to quota or capacity.

Many lack visibility into what went wrong, what alternatives exist, or how to proactively prevent issues.

These gaps led to repeated delays, rework, and growing dependence on support, ultimately driving up operational costs and lowering customer trust.

Opportunity

Designing Contextual AI guidance at the point of failure

Building on prior research and workshops, I uncovered a strategic opportunity to embed Copilot at failure points in the cloud workflow, moments when users were blocked, confused, and uncertain what to do next.

What users needed was real-time, in-context guidance right when and where issues happened.

Why I Integrated Copilot?

They needed help that was:

  • Immediate — not delayed by support tickets
  • Actionable — not just error messages, but next steps
  • Contextual — surfaced right when and where the issue occurred

By embedding Copilot into failure moments, we could:

  • Shows real-time explanations for failures
  • Recommends relevant actions like retrying or submitting a ticket
  • Makes users feel guided—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.

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.

03

Align & Prepare for Delivery

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

Outcome: Finalized entry points, priorities, and feasibility across teams.

Final Solutions

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

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

Empower Confident Deployment Through AI Guidance

By integrating Copilot into the pre-deployment workflow, users gain visibility into real-time capacity, avoid failure-prone configurations, and make faster, more informed decisions all without leaving the platform.

Design solution / Copilot

Help Users to Self-troubleshoot

Enable users to resolve deployment issues independently by surfacing contextual explanations and actionable guidance, reducing dependency on support and improving recovery time.

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