Forum Discussion
Exchange Online: Connector creation failed
- from Microsoft Exchange Online team:
"Dev tenants were used to relay phish emails through EXO using Inbound connector. Because of this misuse, we had to other way but to restrict that. "
Pity.
"Dev tenants were used to relay phish emails through EXO using Inbound connector. Because of this misuse, we had to other way but to restrict that. "
Pity.
vand3rlinden We had the same issue. we used 2 dev tenants to test very complex scenarios, we were in the middle of doing a very complex migration. Microsoft by turning off this feature with no notice not only pushed our project back with huge costs but also literally leaves no options for consultants like us to test different scenarios. hard to believe that a tech giant like Microsoft had to resort to this option to resolve 'SPAM' issues, and had no other smart technical solution.
Rana_BanerjeeI completely agree with you, a dev tenant should contain all possibilities. Unfortunately, Microsoft will not change this. They mentioned this in their documentation:
In Exchange Online, inbound connectors for mailflow are not supported. If you try to create an inbound connector, you will get the following error: "Error executing request. For this service offering, you can't create or update inbound connectors in your organization."
