Forum Discussion
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? ...
- 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.
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.
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.
