The "Getting data" freeze that affects some users but not others, with SQL as the only data source, usually points to one of these causes:
1. SQL connection timeout or throttling: Azure SQL has DTU/vCore limits. If the app queries large tables without delegation (pulling all rows and filtering client-side), heavy users or simultaneous sessions can hit SQL connection limits causing it to hang. Check Azure SQL metrics in the Azure portal (CPU, DTU percentage, connection counts) during a freeze event.
2. Per-user connection issue: you mentioned some users are fine and some aren't. Check if affected users have their own SQL connection or are sharing one. If sharing, and the connection owner's account has an issue (expired password, MFA prompt), it breaks for all users sharing that connection.
3. Delegation limits: if any gallery or data call isn't delegable to SQL, Power Apps pulls the first 2000 rows and filters locally. For users with larger datasets in scope, this causes the "Getting data" delay. Check for delegation warnings (blue underlines) in your formulas.
4. Network/firewall: Azure SQL has firewall rules. If some users are on a different network segment than others, they may be hitting firewall blocks that cause the connection to hang rather than fail immediately.
In Live Monitor (while running from Dev), filter for Errors and Network calls from the affected user. The failing SQL call will show the exact error and query time, which narrows this down fast.
Best regards,
Valantis
✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.
❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).
🏷️ For follow-ups @Valantis.
📝 https://valantisond365.com/
