Continuous Deployment with VSTS

[lgmorand]

Hi, thanks for the document, it's pretty clear and fluent until...CD

• The task "Powershell" does not seem to exists anymore, you have to choose between "Azure Powershell" or "Powershell to Remote machine", which do not have the same fields to fill.

• If I use a "Azure Powershell", I just need to configure the azure endpoint and everything seems ok, until I try a deployment. Then I get an error (which is truncated by VSTS/powershell..)

2017-01-25T15:27:47.3856706Z` ##[command]Import-Module -Name C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ResourceManager\AzureResourceManager\AzureRM.Profile\AzureRM.Profile.psd1 -Global

2017-01-25T15:27:48.5958861Z ##[command]Add-AzureRMAccount -ServicePrincipal -Tenant ******** -Credential System.Management.Automation.PSCredential

2017-01-25T15:27:50.4787406Z ##[command]Select-AzureRMSubscription -SubscriptionId 6c9dc160-dca4-47cb-9e76-ed16a4b4edb1 -TenantId ********

2017-01-25T15:27:51.7085035Z ##[command]& 'D:\a\r1\a\PartsUnlimitedMRP.CI\deploy\SSH-MRP-Artifacts.ps1' -sshUser azureuser -sshPassword Microsoft01! -sshTarget mrpdemo.westeurope.cloudapp.azure.com

2017-01-25T15:27:54.1979768Z ##[error]The server's host key is not cached in the registry. You

I think, it's related to this wellknown error

The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.

So i'm still looking why it does not seem to connect to the VM

[pavankumar9491]

@andreajeka I am facing the same issue which u had faced. Have you found the solution on how to fix it ?