Verified with: 4.4.0-0.nightly-2020-05-22-051026

I confirmed the following probes are in use on my working Azure cluster:

public-lb:

~~~
    "name": "api-internal-probe",
    "numberOfProbes": 3,
    "port": 6443,
    "protocol": "Https",
    "provisioningState": "Succeeded",
    "requestPath": "/readyz",
    "resourceGroup": "qe-cluster-kdrvz-rg",
    "type": "Microsoft.Network/loadBalancers/probes"
~~~

internal-lb:

~~~

    "name": "sint-probe",
    "numberOfProbes": 3,
    "port": 22623,
    "protocol": "Https",
    "provisioningState": "Succeeded",
    "requestPath": "/healthz",
    "resourceGroup": ""qe-cluster-kdrvz-rg",
    "type": "Microsoft.Network/loadBalancers/probes",

    "name": "api-internal-probe",
    "numberOfProbes": 3,
    "port": 6443,
    "protocol": "Https",
    "provisioningState": "Succeeded",
    "requestPath": "/readyz",
    "resourceGroup": "qe-cluster-kdrvz-rg",
    "type": "Microsoft.Network/loadBalancers/probes"
~~~

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2310