Changing to Powershell 5 solved this.Īfter executing this code we have successfully deployed our model! When I was testing this code I ran into errors using Powershell 6 as the sqlserver module was not correctly importing the Invoke-ASCmd cmdlet. This will initiate the interactive sign in flow. If you wanted to test this code locally and didn’t want to use a Service Principal, you could use your own e-mail assuming you have permissions to set yourself as an admin on the AAS instance. Service Principal is the chosen authentication method, since it works non-interactively within Azure Pipelines.If you don’t have this setup, you need to ensure that there is a call Connect-AzAccount so that you are authenticated. Because this is being deployed in Azure Pipelines we are using Service Connections to ensure that our Azure Powershell tasks are already instantiated in the correct context, saving us from having to specify this in our code. We have made a couple of key assumptions with the code above, namely:
0 Comments
Leave a Reply. |