Forum Discussion
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.
My tenant is mixed with kiosk, Std, basic and premium, my admin user is premium, but the error is the same.
We're experiencing the same issue in at least one customer environment. Hope there's a fix for it soon!
- Microsoft Service Incident: EX505293 – Unable to create new email transport connectors
User impact: Admins are unable to create new email transport connectors in some circumstances.
More info: Admins with the following SKUs will be unable to create new email transport connectors:
Microsoft 365 Business Standard
Microsoft 365 Business Basic
Exchange Online Essentials
Existing connectors are not impacted by this event and will work as expected.
Current status: We’ve identified an issue in which admins are unable to create new email transport connectors. We’re reviewing potential mitigation solutions and will provide a timeline for resolution when it becomes available.
Scope of impact: Any admin with the affected SKU(s) listed in the More info section will be unable to create new email transport connectors.
Start time: Saturday, January 21, 2023, 12:00 AM (12:00 AM UTC)
Next update by: Friday, February 3, 2023, 10:00 PM (10:00 PM UTC)I have just had this issue with a customers tenant ( I work for an MSP in the UK)
I managed to amend it using Powershell here is the command I used
Set-InboundConnector "Name of Connector" -SenderIPAddresses 1.1.1.1,1.1.1.2-SenderIPAddress is a comma seperated list of IP's to add
markrj66 Annoyingly still doesn't accept a New-InboundConnector though
HI Rikardz we are still having the same error
- From how I understand this the roll-out of the fix will not be complete until tuesday next week. In my environment the problem is now resolved, but according to Microsoft only 25% of the tenants have beed deployed.
