Hi,

Over the portal, there is an option to link Function App with API Management. This seamlessly imports function app into APIM. However to achieve the same in Azure CLI, lot of work to be done using az apim api commands (create api, create operations etc.). Instead, provide an import capable commands which does the same we do over portal.

Related discussion is captured here:
https://docs.microsoft.com/en-us/answers/questions/226573/link-existing-function-app-with-apim-using-azure-c.html

Hi,

Over the portal, there is an option to link Function App with API Management. This seamlessly imports function app into APIM. However to achieve the same in Azure CLI, lot of work to be done using az apim api commands (create api, create operations etc.). Instead, provide an import capable commands which does the same we do over portal.

Related discussion is captured here:
https://docs.microsoft.com/en-us/answers/questions/226573/link-existing-function-app-with-apim-using-azure-c.html

We need to download the APIM analytics table data to spreadsheet file, but it seems currently it is not supported.

Can we add feature to export APIM analytics table data (refer to attached image file) to spreadsheet file?

Thanks

As per currently known API importing issues, $ref pointers from the OpenAPI specification can't reference external files. However, it could be a crucial feature to standardize APIs across an organization. As is we can certainly make it a local reference but it enforces duplication and becomes difficult to manage length OpenAPI documents. Hence please allow to import OpenAPI documents with remote references.

Known import issue reference: https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions

As per currently known API importing issues, $ref pointers from the OpenAPI specification can't reference external files. However, it could be a crucial feature to standardize APIs across an organization. As is we can certainly make it a local reference but it enforces duplication and becomes difficult to manage length OpenAPI documents. Hence please allow to import OpenAPI documents with remote references.

Known import issue reference: https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions

As per currently known API importing issues, $ref pointers from the OpenAPI specification can't reference external files. However, it could be a crucial feature to standardize APIs across an organization. As is we can certainly make it a local reference but it enforces duplication and becomes difficult to manage length OpenAPI documents. Hence please allow to import OpenAPI documents with remote references.

Known import issue reference: https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions

As per currently known API importing issues, $ref pointers from the OpenAPI specification can't reference external files. However, it could be a crucial feature to standardize APIs across an organization. As is we can certainly make it a local reference but it enforces duplication and becomes difficult to manage length OpenAPI documents. Hence please allow to import OpenAPI documents with remote references.

Known import issue reference: https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions

In a service like APIM, it's important do a proactive check after APIM upgrade to trigger a rollback if neccesary

in the upgrade of Oct 23, 2020 we have impact in our API's for 3 day until the rollback was done.

When using APIM API URL Suffix Validation (".well-known") through Portal, a generic error is thrown.

Universal Links is common to Apple Mobile development, and you MUST host the file at <domain name>/.well-known/apple-app-site-association. It cannot be nested under further paths.

If the 2019-01-01 Azure RM API is called directly, ".well-known" works fine as the Path, so this is only an issue today with the portal and also in terraform. This may be a regression in the latest 2019-12-01 API.

Currently, WCF client is able to access backend SOAP API.

However, APIM currently does not have any built-in support for WCF based mutual authentication/message security. APIM has the ability to attach a client certificate to the HTTP request that is sent to the backend, but WCF clients add some additional body elements that the WCF backend expects, which APIM does not do.

Hope the WCF based mutual authentication could be integrated better in the APIM.

I am using REST API to get a list of users who signed up on the developer portal.

I implemented this logic by using ARM-based REST API, I found this document for archive this,
https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-12-01/user/listbyservice

But, by using this API it does not return the password of the registered user, so If I want to use these users in my other application then without a password I cannot use, please provide a password as well with user properties in response.

I would like to set Ocp-Apim-Subscription-Key at inbound policy level to be able to retrieve Ocp-Apim-Trace-Location without sending Ocp-Apim-Subscription-Key from the client.

we are using jwt token authentication so we don´t have Ocp-Apim-Subscription-Key as mandatory, actually we would like to return Ocp-Apim-Trace-Location for our dev and qa environments, that´s why I want to add Ocp-Apim-Subscription-Key header at policy level and not modify our existing apis.

I am trying to hit API which is in hostgroup using powershell and in the response you are able to see the resource group name in upper case but I have defined it in lower case. How can I get the response with the defined one.

APIM Developer Tier has limitation on 1000 entities, we suggest to remove this limitation.

APIM is a really good product, however, it could be heavily enhanced with out of the box integration with payment processors such as paypal subscriptions.
This would allow anyone to easily create monetizable APIs

These five rules are by no means the final say on API management, but they do provide context for the overall market:
1. Design. Make the APIs accessible to different classes of developers and partners. ...
2. Documentation. To make APIs accessible, offer documentation and communication tools to make it easy to create and manage the applications built on the API itself. ...
3. Analytics. ...
4. Universal Access. ...
5. Uptime.

What do you think? What are some other principles to follow when managing APIs?

https://www.justcerts.com/

If developer portal can be self-hosted that it can be and this is a really good experience, so default developer portals should be set as disabled.