I uploaded an App Service in Azure, already with working API (with JWT Token system). It's all fine and working with <mywebapp>.azurewebsites.net (Web Service URL) for the front-end website, and <mywebapp>.azurewebsites.net/<api-route> for API access.
And then I've read about API Management Services so I registered my web app though there. Now I can use the portal to test my API, it even has its own token system, but my JWT token system is still in effect, so now I would need to do 2 authorization methods to use this API? I've also got a new domain: <mywebapp>.azure-api.net/<api-route> (Gateway URL) which now created the confusion.
My question is, is it okay to just use the same web app as front-end and API, like what I did in the App Service example? Or is it more pretty to create a separate web app to use in API Management Services (and use the default token system)?
I created my front-end with Razor using this tutorial: https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/?view=aspnetcore-5.0
And then I added the API on top of it using this tutorial: https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?view=aspnetcore-5.0&tabs=visual-studio