Azure Remote app | Error | DNS server could not be reached

I have created Remote app Hybrid configurations in Azure, My remote app environment connecting with the azure VM network. So I have implemented VNET to VNET connection with my azure virtual network and remote app virtual network. And I have uploaded my Customize Template image to the remote app.

But the issue comes when I’m trying to create the remote app collection. It giving the following error.

ERROR – Could not provision the RemoteApp collection. Error: DNS server could not be reached.

Featured image

This is a common error to many remote app users, and there are many blogs saying to add google DNS to the Virtual network of remote app. I have tried this, and it make me to recreate the VNET to VNET. But it didn’t helped me.

So I started troubleshooting and found this Remote app machine is added to the Active directory, I used that computer account name and remote desktop to that using my DC in azure VM. After connected to this VM, I have added google DNS ( to this remote app VM by changing the network adapter properties.

Then went back to azure portal – Remote app – Remote app collection – Update

And it worked 🙂

Use this method if you got in to this trouble.

Hope this was useful

Azure Automation | Start | Stop | Virtual machines.

Azure automation is a cool feature that can use to automate the creation, monitoring, deployment and management of cloud resources in your Microsoft Azure subscription using a highly-available workflow execution engine.

It’s a really cool feature, but when it’s first released, all the PowerShell run books have to use the certificate based authentication. And there should be a separate run book required to publish to access this certificate based authentication. But with new updated azure automation, its support PowerShell credential based authentication, which will enable to write PowerShell run books much easier.

This article describe how to automate the VM start and stop (deallocation) using PowerShell run books by credential level authentication.


  1. Create an Azure Administrator account in the Azure active directory to run Azure automation run books.
    1. Create a Azure Active Directory User
      1. Select Active Directory on right side panel
      2. Select the Azure active directory
      3. Create new user (Automation user)
    2. Make this user as a Co-Administrator
      1. Select Settings from panel
      2. Select administrators
      3. Click ADD user and give the email address of the user account that created. (Automation user)


  2. Create Automation Account
    1. Click the automation tab
    2. Click the plus sign to create a new automation account.


  3. Define credential for azure automation account
    1. Click the newly created automation account
    2. Go to assets tab
    3. Click add settings and select ADD credentials.
    4. In define credentials page select PowerShell credentials for credential type


  4. Create VM start Run Book.
    1. Click the run book tab
    2. Click new (plus sign)
    3. Automation – runbook – quick create, give the runbook name as VM start.
    4. Click edit runbook or click on the Run book – Autor – Draft
    5. Type the following powershell script

      workflow Get-VMStart


      $Cred = Get-AutomationPSCredential –Name

      Add-AzureAccount -Credential $Cred

      Select-AzureSubscription -SubscriptionName “Visual Studio Premium with MSDN”

      Start-AzureVM -ServiceName “VM01” -Name “VM01” -force



      • In automation ps credential name, type the account name that defined earlier.
      • Subscription name, you can find out from the portal – settings – subscription
      • AzureVM – Service name, is the cloud service name for the VM
      • AzureVM – name , is the VM name.
  5. Create a VM Stop runbook
    1. Use the same steps with the following script (use a new runbook)
      workflow Get-VMStop


      $Cred = Get-AutomationPSCredential –Name

      Add-AzureAccount -Credential $Cred

      Select-AzureSubscription -SubscriptionName “Visual Studio Premium with MSDN”

      Stop-AzureVM -ServiceName “VM01” -Name “VM01”


  6. Click Test to run the Runbook.

you can schedule this runbooks to run any preferred time

Hope this is helpful