The new Powershell V2 cmdlet to Exchange Online

I saw this Knowledge base-article: https://support.oneidentity.com/identity-manager/kb/334447/connecting-exchange-online-is-not-possible

But that seems to only be for the Sync Editor/Exchange (Online) Connector.

Did your command run successfully in a normal 5.1 PowerShell? Which version of the Exchange Online CMDlets are you using?

Yes. Tried both of these:

Connect-ExchangeOnline -AppId $AppId -Certificate $Certificate -Organization $Organization
Connect-ExchangeOnline -CertificateFilePath "C:\Certificate\Certificate.pfx" -CertificatePassword $CertificatePassword -AppID $AppId -Organization $Organization

ExchangeOnlineManagement = 2.0.5
Connect-ExchangeOnline = 2.0.5

And both of them are working in PowerShell 5.1?

And in OneIM you are using the PowerShellComponentNet4?

Yes, both are working in PS 5.1

Yes, I'm using PowerShellComponentNet4.

Mmh.. the error message is weird then because OneIM 8.1 is built against .NET 4.7.2 and not against 4.6 as implied.

How can i find out which version of Powershell One Identity is running?
Does One IDentity come with a specific version of PS built-in?
Can I point/install another version of PS and force One Identity to use that specific version?

OneIM does not come with a specific version built-in. The PowerShellComponentNet4 is using PowerShell 3-5.1 (depending on what is installed) and the PowerShellComponent would default to PowerShell 2.

You cannot enforce OneIM to use a PowerShell version higher than 5.1 as they are based on a different technology than the other PowerShells.

What could be different is the architecture x86 / x64 between your test and the execution by the JobService and your profile settings (your settings from the account you have tested with vs. the profile settings from the user account the JobService is using).

The problem was with the certificate.

Here is where I found the solution: stackoverflow.com/.../34103154

Install openssl.

Convert the certificate's private key from CNG format to RSA.
Using certlm.msc export the current certificate, or if the original pfx file still exist use that.
Extract the public keys, including certificate chain:
OpenSSL pkcs12 -in "oldcertificate.pfx" -nokeys -out "intermediate.cer"
Extract the private key:
OpenSSL pkcs12 -in "oldcertificate.pfx" -nocerts -out "intermediate.pem"
Convert the key to RSA format:
OpenSSL rsa -inform PEM -in "intermediate.pem" -out "intermediate.rsa"
Merge into a new pfx file:
OpenSSL pkcs12 -export -in "intermediate.cer" -inkey "intermediate.rsa" -out "newcertificate.pfx"
All "intermediate" files can safely be deleted.
Import the newly created pfx into certlm.msc and assign the user running the scripts read privileges to the private key.

The problem was with the certificate.

Here is where I found the solution: stackoverflow.com/.../34103154

Install openssl.

Convert the certificate's private key from CNG format to RSA.
Using certlm.msc export the current certificate, or if the original pfx file still exist use that.
Extract the public keys, including certificate chain:
OpenSSL pkcs12 -in "oldcertificate.pfx" -nokeys -out "intermediate.cer"
Extract the private key:
OpenSSL pkcs12 -in "oldcertificate.pfx" -nocerts -out "intermediate.pem"
Convert the key to RSA format:
OpenSSL rsa -inform PEM -in "intermediate.pem" -out "intermediate.rsa"
Merge into a new pfx file:
OpenSSL pkcs12 -export -in "intermediate.cer" -inkey "intermediate.rsa" -out "newcertificate.pfx"
All "intermediate" files can safely be deleted.
Import the newly created pfx into certlm.msc and assign the user running the scripts read privileges to the private key.