![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 76%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 50%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
Getting your nameservers back to Azure DNS
You can do this without the Azure resource. Your App Service Domains are registered through GoDaddy behind the scenes, and there's an account under the email on your Azure subscription even though Azure never shows it to you. Run a password recovery at GoDaddy's Domain Control Center against that address. If you get in, repoint the nameservers to your Azure DNS zone from there.
Getting the resource back into your resource group
That one is a support ticket. When the Azure resource goes but the registration survives, the domain management object stays orphaned against your subscription, and only Microsoft can clear it so the resource can be recreated. It isn't a portal action. Worth raising it as a migration issue rather than a deletion, since that's what actually happened and it points them at the right thing.
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.