This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 42%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHP%3C/text%3E%3C/svg%3E)
I trying to use the same app service for both my web application and the supporting web api.
I successfully publish my web applicate to "{mywebsite}.azurewebsites.net", but when I publish my web api and specify the target destination to be "{mywebsite}.azurewebsites.net/api" folder (in my publish configuration) it publishes the api to "{mywebsite}.azurewebsites.net" and overwrites my web application.
@Henry Petersen Thank you for reaching out to Microsoft Q&A. Before publishing your web api to the App service have you created a separate folder for that webapi in the portal under path mappings (Go to portal > demo-site App Service > Configuration > Path Mappings > Virtual applications and directories) as suggested in this article Deploying Multiple virtual directories to a single Azure website.
Thanks for the response. I ended up publishing to a separate App Service, which seems to work fine, but not sure if it is a best practice.
@Henry Petersen Keeping your app application and the web api in two different app services will ensure better isolation in terms of security, monitoring and scaling.
For example, if you host your web application and web api in one app service together, there will a single backend to serve the requests from both of them. During peak load time, huge number of incoming requests may result in backend performance degradation(due to high resource consumption). Separation of backend may assist in independent scaling decisions thus improving elasticity and availability.
Feel free to reach back to me if you have any further queries on this.
I have manage to figure out all of the proper settings to publish the webapi to the separate folder within the app service. Now I'm moving on to decide if I should store the access token or use api management to control access to my web api.