Microsoft 365 Integration issues

Status
Not open for further replies.

FisheyeAdmin

Free User
Joined
Mar 30, 2022
Messages
1
Reaction score
0
Hi Guys,

We've tried to integrate Microsoft 365 with 3CX, but ran into issues. We got the below error

"Real Time Notifications to Microsoft 365 changes will not work because it seems that HTTPS port forwarding is not configured. This means that when changes occur, they will not be updated real time. A synchronization will still occur every night. Code: InvalidRequest Message: Subscription validation request timed out. Inner error: AdditionalData: date: 2022-03-30T20:12:51 request-id: 279bdcad-9ceb-4688-bce3-c4eb82f97e2b client-request-id: 279bdcad-9ceb-4688-bce3-c4eb82f97e2b ClientRequestId: 279bdcad-9ceb-4688-bce3-c4eb82f97e2b"

Any help would be really appreciated.

Regards,
Fisheye
 
Hi Fisheye,

This message means that the HTTPS port you have used is not accessible from the Internet.

The default HTTPS port is 5001, but during the installation you may have changed it to something else.

Once you open this port and you can access the Management Console login screen from outside the LAN, then this message will go away.
 
We found one more scenario that causes this scenario: attempting to test too fast?

We enrolled O365 integration and got the same error message. We confirmed that the confirmed HTTPS port (443) and the default (5001) were open TCP on both IPv4 and IPv6. 3CX server hosted in cloud and accessible. We ran 3CX firewall test and it came back no issues. But the error persisted.

What happened before the error message cleared:
1.
We went to users->M365 and enabled following:
  • Sync Microsoft Users
  • Enable SSO
  • Sync Photo
  • Sync Only (specific users)
    • When clicked "Add" first time no users showed up. I think we saved on the page, and reloaded it, and clicked "Add" and users started showed up. Not huge tenant (less than 250 users) so unlikely timeout but who knows.

2. 15 to 30 minutes passed.

Next time I pulled up the Integrations-M365 page the error was replaced with "Status OK. Real Time Notifications from 3CX to Microsoft 365 are working and in sync."
 
Status
Not open for further replies.