Error when trying to modify or create Exchange Online connectors

[manojviduranga]

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 

[#2]

Same problem here no response from microosft yet

[#3]

@Maikel185  

Same issue here, causing major disruption. How does Microsoft have no update on this a week later? 

[#4]

Same issue here since Jan 31 2023. Still can't add a connector.

[#5]

@MegaVolt - thanks for commenting on this! After several days of trying to set up connectors, the "Set-OutboundConnector" and "Set-InboundConnector" commands worked. I still can't create new connectors, but this worked for existing connectors at least.

[#6]

Microsoft begun the deployment of a fix, which has reached around 25 percent of the affected environment as of Wednesday, February 1, 2023, 11:00 PM (11:00 PM UTC) .  

Microsoft  anticipate the fix will fully roll out by Tuesday, February 7, 2023, 12:00 AM (12:00 AM UTC) .

Previously impacted customers may be able to create or modify connectors as users will experience relief as the fix saturates within their environment.

[#7]

HI @Rikardz   we are still having the same error 

[#8]

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.

[#9]

Hey, 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?

[#10]

Not 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.

[#11]

Hello 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 !!!

[#12]

I was also finally able to create a connector as well.

[#13]

Issue 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.

[#14]

@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)

[#15]

i have same issue from 3 weeks to now

[#16]

We have th same issue, we opened a ticket by Microsoft

[#17]

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.

[#18]

Anyone got a fix yet? Still same issue with me trying to run the HCW.

[#19]

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.

[#20]

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]

[#21]

@eltito2395  I opens a support case a week ago, they are aware it is still an issue. Still waiting for fix, but there is serous attention with MSoft.