Exchange Online
A Microsoft email and calendaring hosted service.
6,171 questions
That's pretty much what should happen. Have you tried running any cmdlet, say Get-Mailbox?
Unable to connect to Exchange Online Powershell
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 80%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMO%3C/text%3E%3C/svg%3E)
Micael Ondoa
20
Reputation points
Hello,
I am unable to login to Exchange Online Powershell using the following steps. I am a global admin and the Powershell is opened in elevated mode.
I enter the code below
Connect-ExchangeOnline -UserPrincipalName <mylogin>
Then the login opens and I select my user
It loads for some time then closes and I get the following message in Powershell
This V3 EXO PowerShell module contains new REST API backed Exchange Online cmdlets which doesn't require WinRM for Client-Server communication. You can now run these cmdlets after turning off WinRM Basic Auth in your client machine thus making it more secure. Unlike the EXO* prefixed cmdlets, the cmdlets in this module support full functional parity with the RPS (V1) cmdlets. V3 cmdlets in the downloaded module are resilient to transient failures, handling retries and throttling errors inherently. REST backed EOP and SCC cmdlets are also available in the V3 module. Similar to EXO, the cmdlets can be run without WinRM basic auth enabled. For more information check https://aka.ms/exov3-module
Exchange Online
Windows for business Windows Server User experience PowerShell
{count} votes
-
Vasil Michev 119.5K Reputation points MVP Volunteer Moderator2023-10-27T15:18:51.1966667+00:00 That's the standard "banner" message, you can ignore it. What happens after? Are you getting any error messages? Can you run cmdlets?
-
Micael Ondoa 20 Reputation points
2023-10-27T16:06:41.03+00:00 Hi Vasil, nothing happens. The window closes and it comes back to the prompt in Powershell.
Sign in to comment
Accepted answer
-
Vasil Michev 119.5K Reputation points MVP Volunteer Moderator
2023-10-27T16:21:05.8866667+00:00 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Kael Yao 37,746 Reputation points Moderator2023-10-30T01:30:04.18+00:00 This should be the normal behavior after you connected to Exchange Online Powershell.
Please have a check if you can run Exchange Online cmdlets and get result as suggested.
-
Micael Ondoa 20 Reputation points
2023-10-30T09:36:18.6666667+00:00 Sorry for my late reply. Now the login screen only flashes, I don't get to enter my credentials. Then I get this message.
-
Micael Ondoa 20 Reputation points
2023-10-30T11:22:47.64+00:00 I am able to run cmdlets now. I tried the get-mailbox and it worked. Thanks.
Sign in to comment -