WebSites: Multiple hostname bindings/aliases per shared site
Currently, all shared websites must end with *.azurewebsites.net
Think even shared websites should support multiple bindings per site. The current implementation restriction *.azurewebsites.net is ridiculous and this way this all shared service is just "demoware" - no real sites will use this.
Dotnetnuke for example, is multi-tenant by design. but in this service it is just interesting for testing.
Jose Antonio Silva
shared this idea
10 comments
-
Nir Mashkowski
commented
Just released the paid shared feature this morning http://www.windowsazure.com/en-us/pricing/details/
-
Rasmus Nielsen commented
Agreed. We need this feature also.
-
Brian U
commented
Hope this is coming soon... I'm really looking forward to moving my site over to Azure, but lacking this is simply a deal breaker for my company and I really don't want to go through the hassle of setting my site up to use a Web Role when this is (hopefully) right around the corner.
Even an extra small reserved option would be great. I have no problem paying for my hosting, but the jump from $0 to $70 is simply not realistic (I don't need as much muscle as the small instance provides anyway).
Is there any news? Thanks!
-
Nir Mashkowski
commented
Still working on it :-) will report the dates as soon as I am allowed....
-
Matthew Thepc commented
@Nir Mashkowski - soon but when? I'm ready & waiting to move my site onto Azure, but I'm not going to do it until you support custom domains for shared sites. Is there a timeline that we could see for this?
-
Max
commented
SSL and ADFS need to be baked into Azure. The idea that you have to manually set up authentication is directly contrary to the idea that this is a platform.
-
smallbizguy
commented
While I love the new Azure, I find it is absurd that we can't use custom domains when in shared mode. I agree with with Jose that this make every site out there look like demoware. Bring custom domain support quickly please, if you want to lock in lots of new small business.
-
Pete Lopez
commented
Yes, being able to use custom DNS would allow me to bring all my domains over and develop new domains for clients before moving them to their own accounts.
-
Rafael Leonhardt
commented
I would like to migrate my blog to Azure Website (Shared mode), but I want to use my own domain, not *.azurewebsite.net.
I gave up to bring my blog to Azure because I can´t use my domain and because the reserved instance is too expensive to my little blog.
-
Nir Mashkowski
commented
Thanks for the feedback, we are looking into an appropriate solution here and will update everyone soon!
