Connect-ExchangeOnline fails because System.Windows.Forms objects are used

[baldieavenger]

Hi,
When updating to the latest ExchangeOnlineManagement module, i'm unable to get the pop out to sign in. This works fine with 2.0.3 and in ISE / PowerShell.
Running 5.1 Powershell, 1.56.2 (system setup) Code.
Attached Diagnostic logs when both versions for comparison and a screenshot of the creds pop up Im expecting.
Thanks!
John

CodeLogs20210604.zip

[andyleejordan]

Hi, could you also open an issue with the module's repo too?

[baldieavenger]

Hi Andrew,
Anything more you need from me to dig into this?
Thanks!
John

[dariomws]

Hi @baldieavenger, thank you for your feedback.

I've tested it and it's working for me.

VS Code:

ISE:

[baldieavenger]

Looks like its due to "System.Windows.Forms"
#3394 (comment)

[andyleejordan]

@baldieavenger your profile and script aside, is this issue alone resolved by the dev preview I had you try? That is, can you run Connect-ExchangeOnline in the integrated terminal?

[andyleejordan]

@baldieavenger With the stable extension, I can reproduce the issue where the authentication prompt doesn't open at all from Connect-ExchangeOnline. With the dev build and Windows PowerShell, the authentication prompt does open for me in the integrated console. After authenticating, the module takes a looong time to finish, but eventually drops me back at a prompt, presumably having connected. With the dev build and PowerShell 7, instead of a GUI prompt, the module opens the browser for authentication; this still works correctly and then it sits loading for a while but eventually finishes.

So I believe my patch to OmniSharp has resolved the issue with Connect-ExchangeOnline in the integrated terminal.

[andyleejordan]

That fix is merged and will be in the next release!

[ghost]

This issue has been marked as fixed. It has been automatically closed for housekeeping purposes.