Forum Discussion

manojviduranga's avatar
manojviduranga
MCT
Jan 30, 2023
Solved

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?   ...
admin
exchange online
office 365
  • manojviduranga's avatar
    manojviduranga
    Jan 31, 2023
    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.
BenLangers's avatar
BenLangers
Copper Contributor
Feb 26, 2023
Same 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.
  • BenLangers's avatar
    BenLangers
    Copper Contributor
    Mar 01, 2023

    BenLangers 

    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?

    • flodashlabs's avatar
      flodashlabs
      Copper Contributor
      Mar 01, 2023

      BenLangers 

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

      • BenLangers's avatar
        BenLangers
        Copper Contributor
        Mar 29, 2023

        flodashlabsI have finally got an enabled inbound connector. Spent 3 sessions on the phone with some so-called second line 'engineer' who was equally ignorant about the actual issue and persisted in arguing we should setup a contact form on the website using a partner connector to the Office 365 tenant of the person why was filling in the form...

        After another two, three times trying to explain the situation *again* everything went silent for another two weeks and suddenly, without any news or confirmation, the connector changed to 'enabled'.
        Now I've got some teamlead sending apologies and all kinds of stuff that I have to understand.

        I understand one thing.

        I've been a Microsoft Partner and passionate advocate of Microsoft solutions for my entire professional career. I have sold boxes, Open License, Open License Subscription, managed Enterprise Agreements and have been doing CSP. This was the last license or subscription for their crap I have EVER sold. I will never recommend anyone to have to go through this nonsense and will be offering other solutions to my customers. This ordeal has been too much.

         

        Bey bey Microsoft!

        I'd say "it's been fun", but I hate to lie.

Resources