Fabric gateway autoscaling reduces pressure on report refreshes
Reviewed by Helen Jones
Microsoft announced a preview of autoscaling for Virtual Network Data Gateway on July 14, 2026. Fabric admins can configure minimum and maximum gateway nodes so refreshes, DirectQuery workloads, and copy jobs can scale during demand spikes.
Before this, report refresh reliability often depended on sizing gateway capacity for the busiest part of the day. That can leave teams paying for spare capacity most of the time, or dealing with refresh failures when reporting jobs pile up. Autoscaling gives report builders a more flexible way to protect important refresh windows. The practical question is not whether to switch it on everywhere, but which gateways have predictable spikes, failed jobs, or queues that justify a controlled preview test.
Analysis
Pick one gateway with recurring refresh pressure and test autoscaling with a narrow min/max range. Track refresh failures, queue time, and gateway cost before widening the rollout.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Fabric gateway autoscaling tackles report refresh spikes", Collab365 Spaces. 1 source referenced.