The only workaround is to enable TLS 1.0 on SQL server temporarily, using IIS Crypto for example, then process the SQL server and disable TLS 1.0 right after that.
Enhancement Request MMAD-124 has been created for the issue.
Update: the issue is rectified starting in MMAD 8.15 Hotfix 20201112.
Note: please also run IIS Crypto on QMM machine, where SQL Processing Wizard is executed, to make sure that TLS client protocols are enabled as well
