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.
We've got additional news... -.-'
After we've sent all informations, powershell command included, to microsoft, they created the needed connector for us.
But the mails got blocked by microsoft caused by an error "451 4.4.62 Mail sent to the wrong Office 365 region."
So we informed CodeTwo about this behaviour and they told us, we could try to recreate the inbound connector.
By the fact that I just freaking can't "just" recreate a new connector within 20 seconds. I had to create a new ticket which takes some DAYS for the recreation. *Im close to freaking out cause' of Microsoft, sorry for that*
After some time of waiting, I got this feedback by microsoft:
"Taking into consideration what customer informed about the error message received: 451 4.4.62 Mail sent to the wrong Office 365 region. ATTR35, recreating the connector with the same settings will probably not help. Can we get the SMTP logs from Code Two to check what may cause the issue? I see the customer uses a certificate for this connector. Is this certificate unique and used only for his organization? Thank you!"
Now I have to talk to the CodeTwo support again which also need to contact microsoft for this informations. Its so.... nvm
So... still waiting for an solution.
After we've sent all informations, powershell command included, to microsoft, they created the needed connector for us.
But the mails got blocked by microsoft caused by an error "451 4.4.62 Mail sent to the wrong Office 365 region."
So we informed CodeTwo about this behaviour and they told us, we could try to recreate the inbound connector.
By the fact that I just freaking can't "just" recreate a new connector within 20 seconds. I had to create a new ticket which takes some DAYS for the recreation. *Im close to freaking out cause' of Microsoft, sorry for that*
After some time of waiting, I got this feedback by microsoft:
"Taking into consideration what customer informed about the error message received: 451 4.4.62 Mail sent to the wrong Office 365 region. ATTR35, recreating the connector with the same settings will probably not help. Can we get the SMTP logs from Code Two to check what may cause the issue? I see the customer uses a certificate for this connector. Is this certificate unique and used only for his organization? Thank you!"
Now I have to talk to the CodeTwo support again which also need to contact microsoft for this informations. Its so.... nvm
So... still waiting for an solution.