Scheduled Refresh - Azure SQL connection timeout

[MatsElmsater]

As of 12/16/2019, our scheduled refreshes to Azure SQL database are failing with error:

Microsoft SQL: Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. This failure occurred while attempting to connect to the routing destination. The duration spent while attempting to connect to the original server was - [Pre-Login] initialization=6; handshake=22; [Login] initialization=0; authentication=0; [Post-Login] complete=5; The duration spent while attempting to connect to this server was - [Pre-Login] initialization=32673; handshake=0;

These seems to be isolated to Power BI service as we can connect via other tools.

Anyone else experience this?

Thanks,

Mats

[MatsElmsater]

It looks like all our credentials were reset to use Ouath2 authentication instead of Basic (with username and password specificed). I changed it back and was able to refresh our datasets. 

I wonder if this had anything to do with the scheduled maintenance on 12/15: 

PLANNED MAINTENANCE - COMPLETED

Clusters:
US-East
West-US

Starting December 15, 2019 20:00 UTC.
Ending December 15, 2019 23:00 UTC.

Power BI service may be unavailable for a short period of time (10 to 30 Minutes) as part of planned maintenance, During this time users located near to the listed clusters or with tenants located in this clusters may experience issues accessing Power BI service and background operations may not complete successfully. After the maintenance window is complete, to refresh cached DNS values, all users should restart open browser windows, Power BI Mobile app users will need to verify they are using the most recent app, sign out and sign back in to the app. Once maintenance is complete and required actions are taken we expect the service to operate normally.

[v-chuncz-msft]

@MatsElmsater 

Glad to hear that you've solved this problem. You may keep an eye on the Awareness and create a support ticket for assistance if necessary.

[Anonymous]

I'm experiencing this issue on the east Canada server for one of our clients. We choose to use azure AD logins though, don't want to use standard database login if we can prevent it...