You could try to host the WSDL somewhere and reference it from there. Otherwise it can be easily imported.
https://docs.microsoft.com/en-us/azure/api-management/import-soap-api
https://docs.microsoft.com/en-us/biztalk/core/connect-to-azure-api-management
However, if you are importing an API, you might come across some restrictions or identify issues that need to be rectified before you can successfully perform the import.
For WSDL below are the points we need :
- WSDL files are used to create SOAP pass-through and SOAP-to-REST
APIs.
- SOAP bindings -Only SOAP bindings of style ”document” and “literal”
encoding are supported. There is no support for “rpc” style or
SOAP-Encoding. WSDL:Import - This attribute isn't supported.
Customers should merge the imports into one document.
- Messages with multiple parts - These types of messages aren't
supported. WCF wsHttpBinding - SOAP services created with Windows
Communication Foundation should use basicHttpBinding - wsHttpBinding
isn't supported.
- MTOM - Services using MTOM may work. Official support isn't offered
at this time. Recursion - Types that are defined recursively (for
example, refer to an array of themselves) are not supported by APIM.
- Multiple Namespaces - Multiple namespaces can be used in a schema,
but only the target namespace can be used to define message parts.
Namespaces other than the target, which are used to define other
input or output elements, are not preserved. Although such a WSDL
document can be imported, on export all message parts will have the
target namespace of the WSDL.
For more info, follow this :
https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions
