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
Fred_Weinmann Thank you very much for entering this conversation! RobertCrane there you go 😉
MicrosoftChristianBergstrom actually, I really need to thank Robert and the MVP network here 🙂
I got roped into this because Robert asked an MVP friend for ideas who happened to know me.
Thus connected, we were able to narrow this down a lot due to the call Robert had with me, allowing me to hands on troubleshoot this together with him. Before that, the temporary nature of things was a real issue, making it difficult to track, when you can't reproduce an error.
Fred_Weinmann Thanks for the info anyway. I am not experiencing the issue with V2, I was just trying to help Robert out.
- Fred_Weinmann
ChristianBergstrom and much appreciated that, truly 🙂
The community lives by the people that are part of it trying to help each other. Just wanted to make sure Roberts active and helpful interaction was also out there and not just something that silently happened in the background. Wouldn't have felt comfortable to "take all the glory" myself here (for values of glory in a tech disruption, anyway ^^).
Fred_Weinmann We're also seeing this for one user in our tenant, but not another user, if that help or confuses things.
