Microsoft Fabric
Redefining onboarding and AI integration for Microsoftโs data analytics ecosystem
Case Study
6 minute read
Macbook Pro

Role
Product Design Intern
Team
5 Consultants
2 Project Managers
1 Senior Product Designer
1 Creative Director
Timeline
Jan 2025 - May 2026
Skills
Product Design
Prototyping
AI UX
Data Systems
01
TLDR
Fabric is Microsoft's unified data analytics platform, used by 31,000+ organizations to move, engineer, and report on data in one place. It's powerful, but it shows you the data and nothing about where to go next or who is behind it: new users got lost across six overlapping workloads, and teams broke each other's reports without knowing who owned what.
In Spring 2025, I found the blocker was clarity, not complexity, which became three design principles and [your 2025 prototypes]. Microsoft brought us back in Spring 2026 to close the second gap: I designed three Copilot features, an agent change-approval flow, a dependency risk heat map, and workspace memories, that make ownership visible while keeping the human in control, validated in 7 interviews and 2 usability tests. [Result: what Microsoft took forward, or the strongest feedback you got.]
02
Context
What is Microsoft Fabric?
A unified data analytics platform that brings together data movement, data engineering, data science, and business intelligence all in one place










Mapping every path a user could take
outlining user flows and feature journeys across Fabric's workloads
powerbi
warehouse
science
engineering
factory
real time intelligence
05
Reflection
In 2025 I learned users weren't overwhelmed by Fabric's power, just lost in its structure. In 2026 I saw they were also losing track of each other. Both years came down to one job: make the invisible legible, and leave people in charge.
Big thanks to the Microsoft Fabric team, especially Gresshaa Mehta and Brent Sandifer for their guidance, collaboration, and trust throughout this project!
Automate the work, not the judgment.
Designing for and with agents changed my question from โwhat can AI do?โ to โwhat should a person still decide?โ Routine edits can run in the background while you focus elsewhere. I worked the same way: Copilot helps me explore, and I made the calls.
Feasibility is a design material.
Every concept faced one question: is this buildable in Fabric's real architecture? Naming the constraints made the work more credible, not less ambitious












