Forum Discussion
Microsoft/Google Interop problem - Outlook Server error occurred message
Situation:
We have two tenants, one Microsoft 365 and one Google Workspace. We connected the two-tenants using Googles Interop Documentation (https://support.google.com/a/answer/7441020?hl=en), so that users on both tenants can see the Free/Busy calendar availability of each other.
Problem:
This setup worked well for 6 months + but currently the Microsoft user can’t see the calendar availability of the google users (Google users can see the calendar availability of the Microsoft users). Problem started out of nowhere and we don’t think anything was done from our site that could have caused the problem.
The availability is not working in the Desktop Apps (New and Old one), as well as not working in Outlook Web.
In the old Outlook version, a Server error can be seen - See screenshot
Steps taken so far:
- Completely repeated the steps for “Exchange can see Google” but problem persists
- We used the Connectivity tester from Google for the interop setup, but we can only confirm the google view on exchange, not the Exchange view on Google.
Question:
- How do i get more information on that "server error" in Outlook?
- Any ideas on what causes the problem in general?
- Update: We have been in contact with the MS Support and the topic got raised in Microsofts Internal Engineering Team: "it is a known issue as the connectivity with the 3rd party calendar to google is under review and a workaround from the engineering team is being looked into. However, an ETA is yet unknown."
Luckily for us it just started working again two days ago. So hopefully this will not come back in the future due to an improved support by Microsoft.
- Let me know if you hear of any solutions. We are experiencing the same issue
- Update: We have been in contact with the MS Support and the topic got raised in Microsofts Internal Engineering Team: "it is a known issue as the connectivity with the 3rd party calendar to google is under review and a workaround from the engineering team is being looked into. However, an ETA is yet unknown."
Luckily for us it just started working again two days ago. So hopefully this will not come back in the future due to an improved support by Microsoft.
