Forum Discussion
manojviduranga
Jan 30, 2023Iron Contributor
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?
Error executing request. For this service offering, you can’t create or update inbound connectors in your organization
I've tried the following with no success.
1. Change existing connetcor/Create a new using PowerShell - Same error returned
2. Use different Admin accounts with GA role assigned
3. Use different browsers
- 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.
- flodashlabsCopper ContributorWe'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. - tictagBrass Contributor
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 here.
I hope this helps.
- manojvidurangaIron ContributorThank you heaps tictag for the detailed info. Very useful indeed.
- Billy_BoumanCopper Contributor
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..
- chmod777Copper ContributorI 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.
- tictagBrass Contributor
I found this article which seems to describe what's going on with this issue:
https://office365itpros.com/2023/02/22/inbound-connector-restriction/
Undocumented change, no thought to updating learn docs, new operational process for Microsoft Support without telling them, no thought to ISVs ...
All seems like a right cluster-***, like some bod in the engineering team just decided to wing it!
- BenLangersCopper Contributor
tictagOh boy... Sure reads like 100% authentic Microsoft
- donvnCopper Contributor
Hi all,
I got this error when to Enabling Hybrid Modern Authentication by run Hybrid Configuration wizard
HCW0 - PowerShell failed to invoke 'New-InboundConnector': For this service offering, you can’t create or update inbound connectors in your organization ‘myOrg’. {CategoryInfo={Activity=[System.String] New-InboundConnector,Category=[System.Management.Automation.ErrorCategory] InvalidOperation,Reason=[System.String] OrganizationInboundConnectorProhibitedException,TargetName=[System.String] ,TargetType=[System.String] },ErrorDetails=,Exception=[System.Management.Automation.RemoteException] For this service offering, you can’t create or update inbound connectors in your organization ‘myOrg’., F36658B3,Microsoft.Exchange.Management.SystemConfigurationTasks.NewInboundConnector}
Do you have any ideas to fix that?
Thanks.
- BenLangersCopper ContributorSame issue here today on a fresh trial subscription (Business Standard). The error message is available in the auto-responses when creating a new service request, suggesting to open a new ticket to request the required changes until a fix is available to enable management from the portal and powershell again.
- BenLangersCopper Contributor
After 3 days of wasting my time
- Can you send a screenshot of the error message?
was included in the original request
- Have you tried as a global admin
Duh. Was also in the request
- We really need to call for additional information
Takes them 2 days to call me. No information requested, just some more lies!
Now they claim it is a new issue known about for two days and a fix is being rolled out as we speak. In the mean time, even product support cannot even create new connectors.
A bare minimum of honesty is opbviously not a job requirement at Microsoft?
You cannot possibly be taking this joke serious as a business solution?- flodashlabsCopper Contributor
Yep. It's absolutly a mess to handle inbound connectors like this. Since years microsoft doesnt really "shine" with the customer support and now they decide to increase the effort of processing tickets that way? I don't know man...
Now everytime the inbound connector doesnt work we need to create a ticket to generate a new one. Sucks pretty hard. I tell you what it is...
- Chris_TarnerCopper ContributorAnyone got a fix yet? Still same issue with me trying to run the HCW.
- donvnCopper Contributor
- Info_Masison_LGHCopper ContributorI 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.- tictagBrass Contributor
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]
- flodashlabsCopper Contributor
Issue still exists to me and Microsoft seems to ignore it.
Super fun...!
"For this service offering, you can’t create or update inbound connectors in your organization..."
Since 3 weeks we are not able to configure a mail signature service just because of this issue.
Very annoying.
- BerbegalCopper ContributorHello all.
We received confirmation from Microsoft that the connectors incident has been resolved.
I have test it and I've been able to create both inbound and outboun connectors with no problems.
It's working OK, now !!!- RayKimCopper Contributor
I was also finally able to create a connector as well.
- janvisionnetCopper ContributorHey, is there any update on this, I just rolled up a new tenant with 4 users, Business Standard licensing and I am still unable to create an incoming connector?
- Blocon1998Copper ContributorNot at the moment the connector type onpremise still can not be created I have a godaddy office 365 subscription. and it been like this for 2 weeks now, no update from microsoft.
- RayKimCopper ContributorSame issue here since Jan 31 2023. Still can't add a connector.
- MikeSkiCopper ContributorI also have this issue, and have confirmed this across multiple tenancies. Has anyone had any further feedback from MS on when this will be resolved or a work around?
- manojvidurangaIron ContributorIssue remains intact and we haven't heard from Microsoft yet. As we were in urgency, the only option was to raise a Premier support ticket so that could do the amendments to the connector required for us.
- MarcKoenemanCopper Contributor
manojviduranga
Same issue still here. Even though MSoft published the 7th of Feb that is was resolved, I still have the issue (13th Feb 2023, 11:40hrs)
- Maikel185Copper Contributor
Same problem here no response from microosft yet