HueBot - Setting Up SF Cluster

[chanheelee-thumb]

Issue Summary

Trying to setup SF cluster for HueBot deployment but stuck on New-AzServiceFabricCluster command; the command is returning a NotFound error.

Details

I'm trying to follow the instructions for the HueBot deployment but am stuck on deploying a new azure SF. I have setup an SSL certificate, installed it on my local machine, have a customer domain for my bot, and successfully ran configure_cloud.ps1.

I had to change these commands:

Connect-AzureRmAccount
Select-AzureRmSubscription -SubscriptionName $subscriptionName

Set-AzureRmKeyVaultAccessPolicy -VaultName $keyvaultName -EnabledForDeployment
New-AzureRmServiceFabricCluster -ResourceGroupName $resourceGroupName -SecretIdentifier $secretId -TemplateFile $templateFilePath -ParameterFile $parameterFilePath

To these commands:

Connect-AzAccount
Select-AzSubscription -SubscriptionName $subscriptionName

Set-AzKeyVaultAccessPolicy -VaultName $keyvaultName -EnabledForDeployment
New-AzServiceFabricCluster -ResourceGroupName $resourceGroupName -SecretIdentifier $secretId -TemplateFile $templateFilePath -ParameterFile $parameterFilePath

But I get an error saying ResourceNotFound. This is the exact error message

New-AzServiceFabricCluster : Operation returned an invalid status code 'NotFound'
At line:1 char:1
+ New-AzServiceFabricCluster -ResourceGroupName $resourceGroupName -Sec ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [New-AzServiceFabricCluster], KeyVaultErrorException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.ServiceFabric.Commands.NewAzureRmServiceFabricCluster

I have also changed region westus2 to eastus because that is where my resource group is setup

---

Question

What can I do to correctly setup the SF cluster so that I can deploy the HueBot?

I've checked that the secret identifier is correct, the key vault and resource group does exist, and it has the correct Vault Access Policy. I'm wondering if the ARM template and parameter files are outdated so I tried replacing them with the latest versions but I am still getting the same error

[InDieTasten]

Have you tried updating your AzureRm powershell module?