Forum Discussion
Error when connecting to Exchange online vis PowerShell
Hi folks,
a quick update from engineering:
This is a known issue with only some of the service endpoints, which is why some of you are affected, some not, and why it can go away after some time.
Engineering is working on a fix for this and will patch this as soon as possible (Since we are still narrowing it down, I can't give you a solid ETA yet, sorry), at which point everything should be back to normal. Once the problem has been resolved, I will most definitely post an update here.
In the meantime, there is a workaround to get you unblocked:
You can update the connection Uri to explicitly include the "SerializationLevel=Full" parameter.
For example:
Connect-ExchangeOnline
would become:
Connect-ExchangeOnline -ConnectionUri "https://outlook.office365.com/powershell-liveid?SerializationLevel=Full"
While this will keep working indefinitely, it increases the bandwidth use, potentially slowing execution at scale. I would recommend to not use this as a permanent update to your code and undo it once the issue has been resolved.
Note: We have received reports of this workaround not working for everybody. We are investigating this, whether it is the same problem or an entirely new one.
I'll try to keep you updated on this once I have any news on the issue 🙂
If you are affected by this and want to help us troubleshoot this, please fill out this quick survey. It helps us with developing a pattern and tracking down affected sessions.
Update: Fixed typo in workaround
ChristianBergstrom wrote:
RobertCrane Hey, you should report it https://docs.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#report-bugs-and-issues
But I have also followed this thread, maybe this works for you as well?
"UPDATE - Added "-delegatedorganization xxx.onmicrosoft.com" and now it connects to V2"
Thanks, but it doesn't tell you where to send those logs unfortunately!
RobertCrane At the bottom on the same page, it will take you here
https://github.com/MicrosoftDocs/office-docs-powershell/issues
Or just attach the logs in a ticket to the MS support.
ChristianBergstrom Ah yes, good old GitHub. Thanks.
MS Support via the standard logging a ticket process has proved remarkable unhelpful in all respects unfortunately. We are well beyond going back there due to lack of inaction.
RobertCrane I'm afraid I know exactly what you mean. Anyway, hope it gets sorted!
ChristianBergstrom Appreciate the assist. I'll report back if there is progress. Seems that:
Connect-ExchangeOnline -DelegatedOrganization '<tenant>.onmicrosoft.com'will also work BUT that's a pain if you have a script that runs across many tenants, every day! Some of which need this and others that don't!
