Error when running AKS cluster creation test

Thank you for your contribution and feedback! Help us review faster by providing the following information:

This issue is a: (mark with an x)

• bug report
• request for new sample
• documentation issue or request
• regression (a behavior that used to work and stopped in a new release)

None of the above. This is a new-user issue.

Steps to reproduce:

1. Git clone the repo
2. Setup the needed AZURE env variables
3. Run the AKS cluster creation test

Errors and log messages:

$ go test -v ./compute/
=== RUN ExampleCreateAKS
2019/03/05 16:12:59 creating resource group 'azure-samples-go-CreateAKS-yImO0' on location: westus2
2019/03/05 16:15:09 cannot get the AKS cluster create or update future response: Code="NotFound" Message="resources.DeploymentsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="DeploymentNotFound" Message="Deployment '018a8773-902c-4912-941f-3173d2dd0ca7' could not be found.""
2019/03/05 16:15:09 created AKS cluster
2019/03/05 16:15:09 cannot get AKS managed cluster gosdk-aks-w20XVKVUAI from resource group azure-go-samples: containerservice.ManagedClustersClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'azure-go-samples' could not be found."
2019/03/05 16:15:09 retrieved AKS cluster
2019/03/05 16:15:09 containerservice.ManagedClustersClient#Delete: Failure sending request: StatusCode=404 -- Original Error: Code="ResourceGroupNotFound" Message="Resource group 'azure-go-samples' could not be found."
2019/03/05 16:15:09 deleted AKS cluster
2019/03/05 16:15:09 deleting resources
--- FAIL: ExampleCreateAKS (129.93s)

Expected behavior:

An AKS cluster will be created followed by a deletion of the same cluster.

OS and Go versions:

$ go version
go version go1.11.5 darwin/amd64

Mac OS version 10.13.6

Further info:

Start by running go test -v ./compute/ and inspect the ExampleCreateAKS test referenced in the failure. Trace the AKS creation, retrieval, and deletion steps and compare them with the logged Azure 404 errors; done means the example creates and deletes the same cluster successfully.