| title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Restrictions and known issues in Azure API Management API import | Microsoft Docs |
Details of known issues and restrictions on import into Azure API Management using the Open API, WSDL or WADL formats. |
api-management |
vladvino |
vlvinogr |
7a5a63f0-3e72-49d3-a28c-1bb23ab495e2 |
api-management |
mobile |
na |
na |
article |
02/08/2017 |
apipm |
While every effort is made to ensure that importing your API into Azure API Management is as seamless and problem-free as possible, we do occasionally impose restrictions or identify issues that will need to be rectified before you can successfully import. This article documents these, organised by the import format of the API.
In general, if you are receiving errors importing your Open API document, please ensure you have validated it - either using the designer in the new Azure Portal (Design - Front End - Open API Specification Editor), or with a 3rd party tool such as Swagger Editor.
- Host Name we require a host name attribute.
- Base Path we require a base path attribute.
- Schemes we require a scheme array.
WSDL files are used to generate SOAP Pass-through APIs, or serve as the backend of a SOAP-to-REST API.
- WSDL:Import we do not currently support APIs using this attribute. Customers should merge the imported elements into one document.
- Messages with multiple parts are currently not supported.
- WCF wsHttpBinding SOAP services created with Windows Communication Foundation should use basicHttpBinding - wsHttpBinding is not supported.
- MTOM Services using MTOM may work. Official support is not offered at this time.
- Recursion types that are defined recursively (e.g. refer to an array of themselves) are not supported.
There are no known WADL import issues currently.