OAuth2.0 Authentication and Communication to Excha...

Community

On April 16, between 2:25 P.M. ET and 4:12 P.M. ET, the domain zoom.us was not available due to a server block by GoDaddy Registry. This block was the result of a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry, which resulted in GoDaddy Registry mistakenly shutting down zoom.us domain. Zoom, Markmonitor, and GoDaddy worked quickly to identify and remove the block, which restored service to the domain zoom.us. There was no product, security or network failure at Zoom during the outage. GoDaddy and Markmonitor are working together to prevent this from happening again.

I have a question about OAuth 2.0 authentication and communication to Exchange for Zoom Rooms calendar integration.
If you know the answer to this question, please respond.

■Question
In the past, when we used EWS authentication (legacy authentication) for Zoom Rooms calendar integration, communication from Zoom to Exchange occurred irregularly on the M365 side.
However, after changing from EWS authentication to OAuth2.0 authentication, communication to Exchange has not been confirmed.

We were aware that the communication to Exchange was polled from Zoom (AWS), but with OAuth2.0 authentication, is it OK without polling?
(Is polling no longer required?).

I apologize for not understanding, but could you please tell us what polling is for and what is the reason for the communication that occurs in the first place?

0 REPLIES 0

Communication

Productivity

Apps & Integration

Spaces

Employee Engagement