Forum Discussion
Teams is unable to access your calendar
I started the below error on a lot of computers today. My co-worker did not get the error UNTIL he updated to the same version of Teams as me
You have Microsoft Teams version 25072.1609.3541.7814.
You've got the latest version. It was last checked on 4/7/2025.
The issue is with multiple windows 11 users and their local teams installation. Brand new issue and trust me I'm the admin there were no changes by me. (in Exchange or Teams)
I've run the Exchange connectivity test (ok)
The MS remote connectivity test fails with this error
Make sure user has Exchange Web Services EWS and REST API protocols enabled. The Microsoft 365 Teams Calendar App diagnostics referenced in the link requires a Microsoft 365 admin account to be executed
This worked Friday, it does this today. What changed?
Folks, for me it was the EWS (exchange web services) being set to ON for the user but OFF for the org. The whole KB article pointed out they REVERSED THE BEHAVIOR of the setting.
i.e.last week disabled for ORG and ON for user would work.
This week it won't work. You have to use EWS Enabled TRUE for org AND user
It's not instant gratification when you make the change it may take more than a few hours.
FYI, this appears to have been a known change with a notification being sent out Feb 25, 2025 but I guess we ignored it in the noise. Not sure if it is the same issue as everyone else but posting just in case.
Your Tenant Might Be Impacted by the way to control EWS usage in Exchange Online is changing
MC1015906 · Published Feb 25, 2025
https://admin.microsoft.com/AdminPortal/home?ref=MessageCenter/:/messages/MC1015906That's the problem, the noise! If the message center had a simple option to filter only by "We're making a change that will break your tenant" it would be so much simpler than wading through the piles of garbage of mindless tweaks and features notices...
In this day and age there's no reason they can't determine which tenants are currently using something they're about to nuke...
Same issue, whole organization is affected. I have a ticket open and they haven't been able to figure it out.
Check your EWS for the whole org setting. I'll be it's set to false. See above in the thread. It took about 6 hours for it to kick in.
We ran into this same issue around the same time. After MANY hours of scratching our heads, we fixed it by re-enabling EWS. Problem is why it got set to disabled in the first place? Did Microsoft do something?, probably.
Just set the EwsEnabled to True and everything is working again but it is taking a while to propagate out to our users.
Set-OrganizationConfig -EwsEnabled $True
Same issue here. Did you find a solution?
Having this issue as well. No recent changes suddenly just reported.
Being ignored by Microsoft my tickets been open over a calendar day.
