Forum Discussion
Error when trying to modify or create Exchange Online connectors
Hi All,
- 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.
52 Replies
- 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. We are also facing exactly the same issue. Outbound connectors and Rules are created, but not the inbound connectors.
- Latest-----
In terms of SKU changing, I thought of replicating this scenario in my test lab just for the sake of verification.
1. Obtained a trial of ‘M365 Business Basic’
2. Didn’t assign any licenses to users
3. Simply tried to modify a connector/create a connector
4. Exact error was reproduced
This means, you don’t necessarily need to allocate licenses to the users to face the issue. Having the SKU itself in the tenancy is what causing the issue, it appears. Complete removal of an SKU takes months and usually happens in stages (due to compliance reasons) which means even if you change the license allocation, the error will remain intact.
Considering the above, I believe the SKU changing is not an option for us and this is eventually turns us back to rely on Microsoft support. There's no positive updates yet from Microsoft. We are considering of changing the licenses (although this discouraged due to side-effects it may cause, the customer is desperate to get back online) from Business to E3 and observe if that makes any difference. The incident doesn't specify whether the issue is when the SKU presents in the tenant or when allocated to users so it's going be interesting to find out.
- The service incident indicates it's related to M365 business Std and Basic as well as Exchange Online Essentials SKU's. I wonder if a trial of another higher SKU was added to your tenants would that provide a short term fix?
- 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!
- I tried it on another tanent with at least one bus. premium and got the same error
- Same problem here,
unfortunatelly there are no new updates yet on issue EX505293 manojviduranga Yes I am getting the same issue from this morning and the relay is not currently working. Anyone has a solution, please share it with us.
- We have the same Issue as well.
- alangdale Thanks for posting your status.
There' s also an ongoing service incident relating to this.
o EX505293, Last updated: January 28, 2023 10:15 AM
I raised this with Microsoft support and they're escalating to relevant engineering teams. Will keep this thread updated as I hear from them.- We have the same problem since January 27th. If Microsoft support gives you a solution, do not hesitate to share it with us.
Yes I am getting the same issue from this morning and the relay is not currently working
