Ocp-Apim-Subscription-Key for Service to Service calls

Not applicable

I want to require a Ocp-Apim-Subscription-Key when calling an API that is managed using Azure API Management. If I am calling the API from another API, what Ocp-Apim-Subscription-Key should I use? Do I need to set up a "User" in Azure API Management that represents the calling API and add that User to a Product that has access to my API? Seems silly to have to add a fake user that represents an unattended call to my API.

4 Replies

That is a decent option, however I'd prefer not to go that route. We have the services already setup with AAD authentication and I am moving them to APIM. I want to make the change as seamless as possible.

if you have already setup AD as an identity i believe you should be able to use AD auth on the api. 


we use google here and have that as an option. I haven't tried on AD. 

I can certainly not require the Subscription Key, but from my understanding, if a SK is not used you will lose all of your analytics with regards to that user's use of the API.