It would be very helpful to have a way to throttle users in the capacity rather than a workspace. Giving user their own workspace is not an acceptable workaround. For example, if there are 500+ users but 3 are frequent problem users, and we have advised on best practices and re-trained them yet they still spike, we need a way to protect the 500 from being impacted by the 3. Taking away their access is unfortunately not an option and they are using the same models as the bulk audience. Once they make the naughty list, throttling them at the capacity level would be extremely helpful.
No CommentsBe the first to comment
Recent ideas
Access Variable Library in Semantic Models
Enable the Variable Library as a centralized location for storing all environment‑specific variables, allowing us to adjust them for promotion scenarios (e.g., from dev to prod) without relying on de...FreddyH2 hours agoAdvocate IINew910Views31likes2CommentsEnhance Fabric Pipeline Monitoring with Parent-Child Pipeline Lineage and Parameter Visibility
Currently, Microsoft Fabric Pipeline monitoring lacks several capabilities that are available in Azure Data Factory, making troubleshooting and operational support challenging in enterprise environme...dwramreddy3 hours agoRegular VisitorNew2Views0likes0CommentsDynamic ADLS-Gen2 path input for Spark Jobs Main definition file
I would like the ability to add a dynamic input box on a spark job definition's "Main Definition File" "ADLS-Gen2 path". this would be useful to set base and variable paths across all spark jobs...mfink_db7 hours agoNew MemberNew238Views2likes2CommentsReintroduce Tenant/Capacity Switch to Control "Users can create Plan items" Post-GA
During the Preview phase of Fabric Plan items, administrators had access to a dedicated tenant/capacity setting: "Users can create Plan items". With General Availability (GA), this granular administr...Sri-Surendra_Ku10 hours agoNew MemberNew106Views14likes1Comment