All our SOAP services files use external XSD files that are imported into the WSDL. To import these in API Management, we need to merge the files into one big WSDL.
It would be nice if we could import the WSDL and the imported XSD files without the need to create a "merged" WSDL46 votes
Would be nice to have the option to define a different endpoint to different products. This will allow to define a 'test' and 'live' products that works with different environments. While at the same time the developers keys, examples, etc are all in one place.43 votes
Currently consumption plan services are not discoverable via resource explorer this will impact the ability to automate the deployment of apis between API Management instances
This is important if the consumption plan is to be used a lead into higher level SKUs especially as there is no upgrade option from consumption to higher level skus.20 votes
Thank you for the feedback! We added this suggestion to the backlog and will update the item when we prioritize it for implementation.
I'm not sure why the operation's display name needs to be unique but if it does then it should include the operation verb in the uniqueness check.
Having these two operations:
Should not cause an error that the Display Name is not unique. Both of the operations should be allowed to be named "\users".16 votes
API Management supports the Type parameter property and standard JSON types as its values but doesn't support the optional modifier Format property - Format property translates to a description and doesn't round trip on export. Format property is used by some code generators and it's important to have it represented in the model and supported in OpenAPI import and export.4 votes
- Don't see your idea?