Thanks Kranthi
We found the issue: our firewall was configured to allow a specific process to access the SQL Server, but when scanning the SHIR uses a different process (Microsoft.DataMap.Agent.Connectors.Azure.DataFactory.ServiceHost.exe) which was blocked. I’m not sure which process was allowed beforehand.
When that process was allowed, the scan completed successfully.