It should be possible to connect to your companies WLAN network using the
.pfx certificate. You have given all needed information. The information to use them you can find with:
rpi ~$ man wpa_supplicant.conf
The important part is at the end. You are using EAP-TLS so you should have a client certificate and a server side certifcate included in the
.pfx file, that must converted:
Some EAP authentication methods require use of certificates. EAP-TLS uses both server side and client certificates whereas EAP-PEAP and EAP-TTLS only require the server side certificate. When client certificate is used, a matching private key file has to also be included in configuration. If the private key uses a passphrase, this has to be configured in wpa_supplicant.conf ("private_key_passwd").
wpa_supplicant supports X.509 certificates in PEM and DER formats. User certificate and private key can be included in the same file.
If the user certificate and private key is received in PKCS#12/PFX format, they need to be converted to suitable PEM/DER format for wpa_supplicant. This can be done, e.g., with following commands:
# convert client certificate and private key to PEM format
openssl pkcs12 -in example.pfx -out user.pem -clcerts
# convert CA certificate (if included in PFX file) to PEM format
openssl pkcs12 -in example.pfx -out ca.pem -cacerts -nokeys
It seems that you do not need option
private_key_passwd because they told you there is no protection of the client certificate with an additional password.
To setup wpa_supplicant.conf you should start with the example given with:
# work network; use EAP-TLS with WPA; allow only CCMP and TKIP ciphers
Maybe you will need some try and error but it should do.