when i run the connect-exchangeonline to connect it it should open a authentications window but it gives the error A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles At C:\Program Files\WindowsPowerShell\Modules\Exc

Tanuj Saini 45

when i connect-exchangeonline i get this error :
A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles

At C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.7.0\netFramework\ExchangeOnlineManag

ement.psm1:751 char:21

                throw $_.Exception.InnerException;

```
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
- CategoryInfo : OperationStopped: (:) [], MsalClientException
- FullyQualifiedErrorId : A window handle must be configured. See https://aka.ms/msal-net-wam#parent-win
dow-handles

Ben Oldemeyer 5 Reputation points

2024-12-06T22:47:03.9433333+00:00

I am having this exact same issue all day today. Not to sure what to do about it but figured I'd comment and let it be known as well.
Jan Willem de Geus 10 Reputation points

2024-12-07T12:45:44.2266667+00:00

Same here too. I just found out that it only shows up in Powershell ISE
Jake Zhang-MSFT 7,925 Reputation points Microsoft Vendor

2024-12-10T02:13:12.42+00:00

This article may have information to help you, you can refer to https://zcusa.951200.xyz/en-us/answers/questions/1690217/getting-error-while-connecting-to-azure-through-po.
Johan Ekberg 10 Reputation points

2024-12-10T16:01:30.5266667+00:00

Same issue here. Works when running the plain Powershell Windowd, but not when running it in ISE
Paul Simon 0 Reputation points

2024-12-11T18:50:59.35+00:00

Same error in ISE (admin mode) and also works for me in plain powershell (admin mode).

Accepted answer

Jorge Sergio Dias Keide 135 Reputation points

2024-12-16T21:42:36.8833333+00:00

Current version is broken, uninstall all versions you've got and go back to a previous one. (mine was on 3.5.1, went back to it and now it works)

Uninstall-Module -Name ExchangeOnlineManagement -AllVersions -Force

Install-Module -Name ExchangeOnlineManagement -RequiredVersion 3.5.1 -Force
Please sign in to rate this answer.

12 people found this answer helpful.
Pedro Vervaeke 5 Reputation points

2024-12-17T12:28:36.66+00:00

Thx Jorge!

This fixed this issue for me.

Beer Helmbold 5 Reputation points

2024-12-18T10:56:33.9533333+00:00

Thank you ! Worked

Bharani Valarmathi 5 Reputation points

2024-12-19T09:53:50.4833333+00:00

Thanks.. This fixed my issue..

Aaron Wills 0 Reputation points

2024-12-27T16:31:57.06+00:00

Was happening to multiple people in our company, all running Powershell ISE in a Windows 365 environment. Thanks to Jorge for the solution, it had many at MS stumped.

Aaron Wills 0 Reputation points

2024-12-27T16:32:32.0366667+00:00

Thanks, sorted finally!

Amanda dos Santos Della Libera 0 Reputation points

2024-12-27T21:47:40.8533333+00:00

Thank you !
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

1 additional answer

James Epp 31 Reputation points

2024-12-06T19:12:31.2533333+00:00

I had the exact same issue the other day. I figured it was maybe a "just me" thing because I don't use the module very often and was using it inside a Windows 10 22H2 sandbox.

I posted about the issue on Reddit, see below:

https://old.reddit.com/r/microsoft365/comments/1h6tffz/exchangeonlinemanagement_powershell_module_bug_in/

I don't know the best way to complain about this issue to MS. The best method I figure is to "Contact Owners" in the powershell gallery: https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.0

And just now my coworker made me aware they had the same issue and shared this thread, so adding my couple cents.
Please sign in to rate this answer.

2 people found this answer helpful.
Tanuj Saini 45 Reputation points

2024-12-07T05:36:15.21+00:00

yes, James i have read your post on reddit and uninstalled the module 3.7.0 with powershell version 5. i have tried 3.7.0 preview version as well but issue still persists. then i installed 3.6.0 exchange Online management module and it worked like normal.

I installed it with the command below :

Install-Module -Name ExchangeOnlineManagement -RequiredVersion 3.6.0

i guess in 3.7.0 version it uses a different type of protocol to authenticate through MSAL which require window handles to be configured. if anybody is using the 3.7.0 version of exchange module and able to connect exchangeonline please let me know the handles that needs to be configured or the powershell version they are using.

Thanks James ! you are huge help.

Aijalon 0 Reputation points

2024-12-17T04:26:28.74+00:00

Concur this, 3.7.1 is bugged, when running Connect-ExchangeOnline -UserPrincipalName
would throw out

Error Acquiring Token: Unknown Status: Unexpected Error: 0xfffffff80070520 Context: (pii) Tag: 0x21420087 (error code -2147023584) (internal error code 557973639) OperationStopped: Unknown Status: Unexpected Error: 0xfffffff80070520 Context: (pii) Tag: 0x21420087 (error code -2147023584) (internal error code 557973639)

Once back to 3.5.1, can be connected as per usual.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

when i run the connect-exchangeonline to connect it it should open a authentications window but it gives the error A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles At C:\Program Files\WindowsPowerShell\Modules\Exc

1 additional answer

Your answer