Forum Discussion
Error when trying to modify or create Exchange Online connectors
- 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 have managed to get Microsoft Support to create my connector for me, but it was misconfigured! Groan. I've since learned that the back-end engineering teams are asking the front-end support agents to send them a fully configured PowerShell command, so in my case, the support agent configured it incorrectly. We worked on that today and came up with a correctly configured command.
When contacting Microsoft Support to request that they either create a new or update an existing connector, I recommend that you provide them with the exact PowerShell command. Something like this for a new connector:
Tenant ID: <GUID>
New-InboundConnector -Name "Your Connector Name" -Comment "Connector to allow incoming mail relay from domain.com and sub.domain.com websites (Originating IP: 99.99.99.99)" -ConnectorType OnPremises -SenderIPAddresses 99.99.99.99 -SenderDomains *.domain.com -CloudServicesMailEnabled $true -Enabled $true
Or if a connector already exists:
Tenant ID: <GUID>
Set-InboundConnector -Identity "Your Connector Name" -Name "Your New Connector Name" -Comment "Connector to allow incoming mail relay from domain.com and sub.domain.com websites (Originating IP: 99.99.99.99)" -ConnectorType OnPremises -SenderIPAddresses 99.99.99.99 -SenderDomains *.domain.com -CloudServicesMailEnabled $true -Enabled $true
No, you shouldn't have to do this.
Yes, it will speed the creation/update of your connector.
Yes, this whole palaver is a cluster-****
Notes:
1. The -Comment parameter will end up being the "Description" in the EAC GUI
2. The -CloudServicesMailEnabled parameter affects the "Retain internal Exchange email headers (recommended)" option.
... the other parameters are described https://learn.microsoft.com/en-us/powershell/module/exchange/new-inboundconnector?view=exchange-ps.
I hope this helps.
- Thank you heaps tictag for the detailed info. Very useful indeed.
Thanks for the format.
They've rolled out a "fix", you should no be able to create the inbound connector. However.. when trying to enable it, you should see something like this:
Error executing request. For this service offering, you can't enable an inbound connector. Please contact Support to enable it. Organization 'xxxxxx-xxxxx-xxxx-xxxxxxxxxxxx', Service Offering: 'O365_BUSINESS_ESSENTIALS'.
This way we shouldn't have to provide the PowerShell command anymore but will have to contact Microsoft to enable the connector for us..
- I have your same issue, I have contacted Microsoft last week to enable the connector but the issue is still ongoing without any significant feedback frome their side (we are checking, we will contact you soon, etc.).
Is there any way to escalate and fix it?
Thank you.
