I have asked our Azure team to reply to your issue

---

Ken Grierson
DotNetNuke Corporation
Test Lead

I have the same issue, on a vanilla-site deployed directly from the Azure control panel, and with no change at all to configuration options (not even a skin change - through I later tried that).

Assuming I did something wrong myself, I delete the site and redeployed from the beginning using a new name for the resources. The result was the same. There is no Host menu when deploying to Azure.

The issue is not new. I attempted to deploy a test-site in November last year, and had the same issue, though at the time I did not completely understand what was goin on (I simply couldn't locate the SMTP settings). Back then I gave up and used another CMS. This time I'd like the opportunity to actually use DNN. And I am using a different Azure subscription this time, so I am pretty sure the issue is not directly related to the Region/Datacenter/Account used in Azure.

Let's stop assuming users are doing something wrong when installing, and realize that there is a potential issue with either DNN or with the current deployment scripts used in Azure. The issue is reproducable, and occurs even when no settings, skins or changes have been applied to the site. The symptom is simple: The Host menu item is absent.

The site only has a single user account, which is the Host account created during deployment. Perhaps the new Host account created during deployment has wrong data or insufficient rights?

In any case: Please look into this issue. A DNN portal without the Host configuration option is sort of like a hamburger without the beef... it's eatable, but something important is missing!