Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a site running on Azure built in ASP.NET MVC. Part of the site is effectively a marketing site with mostly static pages, the rest is the dashboard that our users log into to use the product.

Currently it's all ASP.NET MVC tucked away in a Visual Studio solution, and effectively unreachable by anyone without access to the code. I'd like to expose the marketing pages so they can be edited without access to the code, also allowing them to be changed without compiling the solution and publishing it.

So, I'd like to figure out how to split our site into two, one that continues to run the dashboard site (could be and another that's driven by Wordpress ( for all of the "about us" and marketing chatter. Currently we have 1 web site in Azure. How can I run a second site in Azure while sharing the domain? Any thoughts on a cost effective way to approach this?

share|improve this question
up vote 0 down vote accepted

I've just done something similar to what you're asking about, using Azure Websites - I have a public facing website, call it (not real) and I have an API I wanted published on the same domain. the web site and the api each have their own Azure Website ( and respectively)

I manage my domain with 123-reg so in their advanced DNS settings I've added the awverify records

I have the following three records for the public website - one CNAME to drive internet traffic and two to support verification of both naked domain and full domain

awverify CNAME
awverify.www CNAME

I then added the following for the API - again - one for the verification and one for actual traffic

awverify.api CNAME

As you can see in my DNS records I simply needed to add another set for the subdomain - one for verification and one for traffic and I got two separate websites as part of the same domain.

I then went to both Azure websites on the Azure Management Portal, made sure they are both Shared or Standard instances, to ensure support for custom domains and then in the configure tab I added the custom domains. (without the correct verification records this would fail, but will show which verification entries in the DNS need adding)

Worth noting that DNS takes a while to update, so you will need to wait a little bit between updating the DNS records and successfully updating the custom domain in Azure.

share|improve this answer
Thanks for your answer! – Chris Stewart Dec 27 '13 at 1:48
With pleasure, glad I could help – Yossi Dahan Dec 27 '13 at 7:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.