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

Question

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

Anonymous

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 15 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 15 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
Anonymous

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

This article may have information to help you, you can refer to https://learn.microsoft.com/en-us/answers/questions/1690217/getting-error-while-connecting-to-azure-through-po.
Johan Ekberg 15 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).
Pete Mantai 0 Reputation points

2025-01-28T19:09:23.4833333+00:00

I get the same error as Travis:

"WARNING: The version '1.4.8.1' of module 'PackageManagement' is currently in use. Retry the operation after closing the applications."

There are no other PowerShell windows open.
Jose J. Rivera 5 Reputation points

2025-02-25T16:27:34.2066667+00:00

Getting same error after installing latest EXO version 3.7.
I am used to use only the connect-exchangeonline command and wait for the credential windows to Pop-up.
On this version that seems to be broken. However saving credentials to a variable $cred = get-credential . then use Connect-ExchangeOnline with the -credential parameter worked. Connect-ExchangeOnline -Credential $cred. to avoid prompting for that window. Update: it worked for a few days closing out ISE and reopening, using credential parameter. but not anymore, downgraded to EXO 3.6.0
茂南王 0 Reputation points

2025-03-12T09:01:43.8333333+00:00
upgrade the powershell with follow command can resolve the issue.

winget install --id Microsoft.PowerShell --source winget
Torrey Garcia 0 Reputation points

2025-06-17T17:30:02.86+00:00

In PS 7 run:

Connect-ExchangeOnline -disablewam

Answer accepted by question author

9 additional answers

Your answer

Ben Oldemeyer 15 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 15 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
Anonymous

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

This article may have information to help you, you can refer to https://learn.microsoft.com/en-us/answers/questions/1690217/getting-error-while-connecting-to-azure-through-po.
Johan Ekberg 15 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).
Pete Mantai 0 Reputation points

2025-01-28T19:09:23.4833333+00:00

I get the same error as Travis:

"WARNING: The version '1.4.8.1' of module 'PackageManagement' is currently in use. Retry the operation after closing the applications."

There are no other PowerShell windows open.
Jose J. Rivera 5 Reputation points

2025-02-25T16:27:34.2066667+00:00

Getting same error after installing latest EXO version 3.7.
I am used to use only the connect-exchangeonline command and wait for the credential windows to Pop-up.
On this version that seems to be broken. However saving credentials to a variable $cred = get-credential . then use Connect-ExchangeOnline with the -credential parameter worked. Connect-ExchangeOnline -Credential $cred. to avoid prompting for that window. Update: it worked for a few days closing out ISE and reopening, using credential parameter. but not anymore, downgraded to EXO 3.6.0
茂南王 0 Reputation points

2025-03-12T09:01:43.8333333+00:00

upgrade the powershell with follow command can resolve the issue.

winget install --id Microsoft.PowerShell --source winget
Torrey Garcia 0 Reputation points

2025-06-17T17:30:02.86+00:00

In PS 7 run:

Connect-ExchangeOnline -disablewam

Answer 1

Jorge Sergio Dias Keide 365

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

Pedro Vervaeke 5 Reputation points

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

Thx Jorge!

This fixed this issue for me.
Renier 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 10 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 10 Reputation points

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

Thanks, sorted finally!
amandadlibera 5 Reputation points

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

Thank you !
Sébastien GOUVERNEUR 5 Reputation points

2024-12-30T08:36:08.7333333+00:00

Perfect it work ! thank you.
Tomasz Gryglicki 5 Reputation points

2024-12-31T08:57:17.6333333+00:00
this fix is ok, thanks!
Thomas Nielsen 146 Reputation points

2025-01-03T11:37:28.1466667+00:00

Thank you very much. That fixed my issue.

I installed version 3.6.0 and that version works too.
Travis Bird 15 Reputation points

2025-01-03T17:57:49.38+00:00

I get this error when trying to force install 3.5.1 "WARNING: The version '1.4.8.1' of module 'PackageManagement' is currently in use. Retry the operation after closing the applications." Anyone have any ideas?
Thomas Nielsen 146 Reputation points

2025-01-04T14:32:55.1833333+00:00

Hi Travis

Make sure you close all your PowerShell Windows and only have the one with the Instal-Module command open on your computer.

Best Regards

Thomas

https://www.techthatworks.net/
Cote, Don 5 Reputation points

2025-01-08T00:11:49.9366667+00:00

I had to add -AllowClobber to the install before it worked for me, but I appreciate the solution!

Install-Module -Name ExchangeOnlineManagement -RequiredVersion 3.5.1 -Force -AllowClobber
Alan McLaughlin 0 Reputation points

2025-01-14T18:36:38.7066667+00:00

I feel silly for not suspecting a recent update to the EXO module... Everything broke right after that. Thanks for sharing! Regressing to a previous EXO posh module resolved.
Tristan Buckley 0 Reputation points

2025-01-17T11:07:22.41+00:00

Thanks, I can confirm this is working again after applying the work around
Jahidul Kabir MSFT 0 Reputation points

2025-01-20T05:50:29.1066667+00:00

Seems this is happening WW. MS team confirmed this is a bug which got introduced in the latest version of the module.

Hopefully it will be there in the next preview or GA. current workaround is to downgrade or use the prev version.
David Homer 20 Reputation points

2025-01-23T13:55:35.1733333+00:00

This seems to be a problem in 3.7.0 and 3.7.1? Does anyone have the bug tracking link?
Helmut Gary Perez 0 Reputation points

2025-01-24T23:19:19.1+00:00

Worked for me! Thank you.
Vkantamneni 1 Reputation point

2025-02-05T14:06:09.6133333+00:00

Thank You Jorge. It's resolved my issue.
Jimmy Fierens 0 Reputation points

2025-02-05T14:07:17.41+00:00

Thanks,

I ran into this issue today, and fixed pretty fast
Peter Arisz | Advisie 0 Reputation points

2025-02-07T09:54:26.0466667+00:00

Got the WARNING: The version '1.4.8.1' of module 'PackageManagement' is currently in use. Retry the operation after closing the applications.

Didn't find a fix
David Homer 20 Reputation points

2025-02-07T10:08:06.6433333+00:00

For people who can't downgrade I've updated the blog with workaround 3 which means you can do the MSAL authentication yourself and bypass the Microsoft bug
https://david-homer.blogspot.com/2025/01/exchange-online-management-powershell.html
Derek M 20 Reputation points

2025-02-28T17:39:57.23+00:00

True fix is updating your Powershell, run below in your ISE. Kudos to Michael Kronschnabl. winget install --id Microsoft.PowerShell --source winget
茂南王 0 Reputation points

2025-03-12T09:02:57.8666667+00:00
Update the powershell can truly resolve the issue without downgrade EXOM

winget install --id Microsoft.PowerShell --source winget
-M 15 Reputation points

2025-03-14T13:41:20.92+00:00

3.7.1 was causing severe authentication issues for EOL... like 3-5 minutes after MFA. downgrade to 3.5.1 and BOOM, works like its supposed to.
Zach Olsen 0 Reputation points

2025-03-26T21:42:47.5566667+00:00

That worked, thanks!
Michael Thompson 0 Reputation points

2025-04-08T22:26:26.0133333+00:00

i dont know what you people did but it doesnt work for me
Derek M 20 Reputation points

2025-04-09T12:12:00.49+00:00

You have to run the below command every time you start a new EXO session even though it may already be updated and installed, seems silly, but that's Microsoft for you. Likely due to PowerShell ISE not being supported anymore. I added this to the bottom of my install, update, import, commands and it works every time.
winget install --id Microsoft.PowerShell --source winget

Answer 2

Michael Kronschnabl 120

Got it up an running again. Just go in your ISE and install the new PowerShell 7.5:

winget install --id Microsoft.PowerShell --source winget

after that, you are able to connect to exchangeonline again.

Jim Nairn 0 Reputation points

2025-02-04T14:12:30.6833333+00:00

I had to find out first how to add winget (apparently, mine had never seen it), but after that, the above line worked, and i was able to connect with no error
Nick M. Kulkarni 26 Reputation points

2025-02-26T10:35:59.76+00:00

Thanks Michael, that fixed it for me.
Mason Mitchell 15 Reputation points

2025-02-28T17:19:43.55+00:00

This is the proper solution rather than going back to a previous version... this version is not broken.

Thank you for posting this!
Derek M 20 Reputation points

2025-02-28T17:28:08.2533333+00:00

Thank you for this! This is the true solution! Not going back to version Exchange module 3.6.0.
Mason Mitchell 15 Reputation points

2025-02-28T21:27:05.01+00:00

...ran into a problem with this... thanks to @James Epp here is a work around until MS fixes their code:

Preface any code you're trying to run in ISE with this (works like a charm but not sure for how long SMH):

$msalPath = [System.IO.Path]::GetDirectoryName((Get-Module ExchangeOnlineManagement).Path); Add-Type -Path "$msalPath\Microsoft.IdentityModel.Abstractions.dll"; Add-Type -Path "$msalPath\Microsoft.Identity.Client.dll"; [Microsoft.Identity.Client.IPublicClientApplication] $application = [Microsoft.Identity.Client.PublicClientApplicationBuilder]::Create("fb78d390-0c51-40cd-8e17-fdbfab77341b").WithDefaultRedirectUri().Build(); $result = $application.AcquireTokenInteractive([string[]]"https://outlook.office365.com/.default").ExecuteAsync().Result; Connect-ExchangeOnline -AccessToken $result.AccessToken -UserPrincipalName $result.Account.Username;
Derek M 20 Reputation points

2025-02-28T21:29:45.1133333+00:00

Haven't had any issues since updating to the new PowerShell.
WillW 0 Reputation points

2025-03-17T13:30:51.83+00:00

The 'winget install --id Microsoft.PowerShell --source winget' does work for PowerShell ISE, but weirdly enough only for the current session. If I exit ISE and reopen it, I get the window handle error again. Re-running the winget command again returns "no available upgrade found", but it does "fix" the issue again ... until next time.

It seems like there should be a way to import/load whichever component winget adds to the ISE session, but I haven't figured out what that is yet. I'd like to put something in my profile.ps1 other than "winget install ... " because I generally don't run ISE admin elevated and the winget command fails in a non-elevated session. Any ideas?
swey 11 Reputation points

2025-03-23T12:36:07.26+00:00

Not sure why, but it solved it

Found an existing package already installed. Trying to upgrade the installed package...
No available upgrade found.
No newer package versions are available from the configured sources.
Anthony Charles 0 Reputation points

2025-04-30T15:10:36.5+00:00

This fixed it for me too, thank you
Kash 0 Reputation points

2025-05-12T09:30:50.43+00:00

Absolutely this is the FIX - This works.

We always move forward and adapt - Not backwards
Peter Akaneme 0 Reputation points

2025-06-01T16:55:43.2266667+00:00

Thank you, @Michael Kronschnabl the piece was very beneficial and simple to follow. I had to let my coursemates know about it.
Tom Schmidt 0 Reputation points

2025-08-19T09:57:48.15+00:00

This solved my problem as well, thank you
Jorge Sergio Dias Keide 365 Reputation points

2025-10-09T20:01:13.95+00:00

Michael Kronschnabl , this approach didn’t seem to work for me. As far as I understand, ISE always runs on PowerShell 5.1, so I’m not sure how upgrading a completely separate version would resolve the issue. Could you clarify how this would help?

Answer 3

Hello, I've had the same problem and looked into this - I've written everything I found here.
https://david-homer.blogspot.com/2025/01/exchange-online-management-powershell.html

Looks like Microsoft makes it that interactive login windows need a parent window now (so they don't disappear behind your application). They have however used some archaic method to get the console window handle. Therefore if you're not in a console application (for example a .NET or other Windows application, or PowerShell ISE etc etc) there is no console window therefore it crashes. I've reported it on the PowerShell gallery.

Answer 4

Derek M 20

Better fix is updating your Powershell, run below in your ISE. Kudos to Michael Kronschnabl.
winget install --id Microsoft.PowerShell --source winget

Answer 5

James Epp 31

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.

Anonymous

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

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.

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

9 additional answers

Your answer