Is there a reason azure-api-management doesn't allow the expose SOAP services?
<p>I am benchmarking different API management solutions and Azure API Management is one of them. One of my criterion is to be able to import a soap web service and to "restify" it.</p>

<p>After some researches in the msdn doc it seems that it is not possible to import a SOAP service whereas it has been asked by the community almost two years ago: <a href="https://feedback.azure.com/forums/248703-api-management/suggestions/5782547-soap-support" rel="nofollow noreferrer">This thread</a> has been marked as "under review" for almost 2 years.</p>

<p>I am pretty surprised to see that this is not possible whereas SOAP web services are still pretty common and I think it would be useful to a lot of people to be able to manage them in Azure.</p>

<p>So I have two questions:</p>

<ul>
<li>Is it really still impossible to manage SOAP web services in Azure or has this feature been added and I didn't look at the right place for a documentation?</li>
<li>If it is still not possible, why? What explains that Microsoft still doesn't allow to do that?</li>
</ul>

<p><strong>Note</strong> That I have read <a href="https://stackoverflow.com/questions/26637002/azure-api-management-and-asmx-wsdl-soap-endpoint/28299153#28299153">this question</a> two things motivated my question: the other one hasn't been active for more than one year and it doesn't explain the reason why SOAP endpoint are not available.</p>