Forum Discussion
Jan 30, 2023
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? ...
- Jan 31, 2023Latest (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.
tictag
Feb 27, 2023Brass Contributor
I found https://office365itpros.com/2023/02/22/inbound-connector-restriction/ 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!
BenLangers
Feb 27, 2023Copper Contributor
tictagOh boy... Sure reads like 100% authentic Microsoft
- donvnFeb 27, 2023Copper 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.