Forum Discussion
Working with Microsoft Fabric Support - A Collaborative Approach
Hi krlitt
This is a really helpful guide. The checklist for "Issue Details + Error Info + Environment Info" will definitely reduce back-and-forth with support.
One suggestion: Could we also get a downloadable template with all these fields? That way users can fill it before raising a ticket and it speeds things up even more.
Thanks for sharing this collaborative approach!
Hey Gautam_Kumar01, Thank you for the feedback!
One challenge with a downloadable template is that the information we need can vary depending on the specific Fabric Service involved.
Example, an Eventhouse issue may require an EventhouseID, while an Activator issue may require an ActivatorID.
Our goal with this post was to highlight the key details that help the Fabric Support team start troubleshooting quickly. At a minimum, including the following can significantly accelerate investigations:
+ WorkspaceID (key item)
EventhouseID / ActivatorID / EventstreamID
Capacity Name
+ Region (key)
+ Error Message (key)
+ Approximate Timeframe (UTC) (key)
That said, service-specific templates are a great idea, and we'll definitely keep that in mind for future guidance.
Thanks again for the suggestion!