Azure should be its own domain registrar
Windows Azure should offer domain registrar services so users don't have to maintain our domain names with a separate company. This also has the potential to greatly streamline the process of setting up a website on Azure.
Domain registration is being evaluated and remains on our long term road-map. However, it is not planned for CY 2019.
Awais Jameel commented
Yes absolutely Microsoft should hove to make azure registered domain more manageable. By making there Own domain registrar services.
Ben @ Bloxxi commented
ou can currently purchase domains in Azure Websites > Custom Domains > Buy Domain.
Looks like the registrar is GoDaddy & only a limited amount of TLD's are supported (.com, .net, .org, .biz)
Something competing with AWS Route53 (large list of supported TLDs and in/out transfer), not an ugly parody that App Service has!!!
And all that for a reasonable price, of course!!!
Azure DNS should support purchasing and transferring a domain name! And not an ugly parody, that App Service currently has, but something valuable (like AWS Route53 currently has)!
I totally agree with this post!!!
Azure should provide an ability to register a new domain name in place, otherwise it's a half-featured service!!!
Daniel Grenemark commented
Allowing domain registrar functionality with turn-key features for ie, Azure Websites, AAD. Would greatly reduce complexity and reduce deployment time.
Even is Microsoft is not the actual registrar these should at least be a resource provider for third parties to offer domain registration.
If Visual Studio can provide me everything i need to create a new website in Azure, i surely want it to provide me some options on DNS as well.
+10 if I can. Please don't let google eat the pie first
Bart Sipes commented
This is a must now that Google is attempting to do the same. Http://domains.google.com
+1 for DNS hosting as the more important feature.
Not sure about become a domain registrar - you will also have to support country level TLDs and all have different procedures. There are pretty good alternatives that offer a lot TLDs for competitive prices. May be interesting if MSFT can at least match the prices and can service many TLDs - but rather see the teams focussing their efforts on other services.
As Astaykov mentioned, DNS hosting would very much streamline setup across Azure services. The Azure control panel provides a nice overview of services, having the ability to manage domains within would very much provide a seamless management experience.
Azure's main benefit is it's very clean environment, solely concentrating on the services vs. add-on...ads...etc. Therefore managing domains in general would be much more intuitive.
A proper DNS hosting solution will be just fine. As long as anyone can point their domain to MSFT DNS Servers. Microsoft already provides such service for O365 P-plan subscribers, so you should consider extending this support across all Microsoft online customers.
Akash Kava commented
Along with powerful DNS Cloud ...