Forum Discussion
A problem has occurred accessing your storage account or content
- 2 years ago
Hi amolt !
Could you please share your ticket ID / service request ID with me so I can take a closer look at your case? You can post it here or send it privately to me over a direct message. I wonder what could be consuming so much and if perhaps there are opportunities of improvements at the query level.
I will be marking this as resolved as the underlying issue is related to capacity and just resource consumption. Such resource consumptions depend on a number of factors beyond just the capacity as it also relies on your data source, the connector in use and the overall query or dataflow that was created. There are techniques in which you could stage the data first and perform the transformations afterwards, so we could privately explore those options that would work best for your specific case.
Best!
Hi everyone,
After MANY hours with MS support working through the issue(s), I have confirmed that the issue is related to the capacity itself.
First test I did was to move my worspaces back to the Trial Capacity, which resolved all issues (took about 2 minutes and I was able to load and see everything again).
Then, through the Azure Portal, I created a NEW capacity (F8 like my old capacity) and I switched all my workspaces to use this new capacity, and everything is now working as expected. (Make sure to Pause your old capacity to not be charged for it).
The support person acknoledged that MS is working hard to fix some performance issues with the Fabric capacities, and this was a functional workaround (considering that the product is still in "Preview").
Hope this helps others.
I just paused my fabric element on Azure, switched it back on and viola. All working again.
Thanks!