Forum Discussion
Solved
Error when trying to modify or create Exchange Online connectors
Hi All, Getting this error when trying to update an existing EXO transport connector or creating a new. Sounds like backend and License SKU specific to me. Anyone else experiencing the same? ...
- Latest (31-01-2023 | 6.30 PM)
We had requested Microsoft to add the changes required to the connector and they have completed the request after about 24 hours. We had to use Premier support service to get this escalated to the appropriate team in a timely manner.
This is surely some relief for us until they apply a permanent fix to the SKUs.
I am facing the same issue from last 2 to 3 weeks. Can anyone got a fix>?
As per Microsoft support team after 1st Week of March only it will work as the fix deployment is still in progress.
As per Microsoft support team after 1st Week of March only it will work as the fix deployment is still in progress.
21/02/2023 and still facing this issue. Reported to Product Support under SR35182562. Similarly, cannot create 'OnPremise' type connectors either via the UI or PowerShell. Can create 'Partner' types both using the UI and PowerShell (New-InboundConnector -ContectorType Partner) but have found the resulting connector to be non-functional i.e. the MX always replies with the same error:
[21-Feb-2023 13:36:55 UTC] SMTP ERROR: DATA END command failed: 550 5.7.64 TenantAttribution; Relay Access Denied [LO2GBR01FT040.eop-gbr01.prod.protection.outlook.com 2023-02-21T13:36:55.529Z 08DB13AAF0562144]