User541108374 posted
Hi,
depending on what you want you could make different deployment settings in your Visual Studio but as you mention CI I think it's not what you're after.
What you could do is make use of deployment slots in Web Apps
https://docs.microsoft.com/en-us/azure/app-service-web/web-sites-staged-publishing and swap after a deployment (staging to production for example).
I would like to create a second azure website that runs on the same bits with a different database and possibly some different configuration (e.g., a different header and footer, different permissions,
etc.).
This can also be interpreted as something else: multitenancy. In this case you use the same database with the same codebase but show different things / sites for different users. A good example would be SharePoint online which is the
same thing but every company / person can set up a SharePoint site and have it look different, contain different information, ...
Grz, Kris.