I am exploring a possibility to implement Managed Identities for REST API hosted in Azure App Service. This Api consumes multiple third party APIs which are outside our control and secured by AAD.
Currently, we store AAD ApplicationId / Secret in the configuration. Whenever we need to consume any of the third party API, we follow below process -
- Use ApplicationId & Secret to generate a Token
- Call third party API with the token in header
- During a call clientId in token is checked for authorization
Can I we use Managed Identities in this scenario? Does this require code changes for any of thes APIs? Can I be able to access ClientIds which I can onboard to third party APIs for authorization?