Hey @MeaseDarrenThomas-8828 ,
Thanks for your time. I reached out to the billing team internally to be sure. Your Visual Studio Subscription grants you credits which you can spend on Azure, you cannot spend these credits on Windows 10. You need to buy your own license or select a billing model where you pay for the license with the cost of your VM.
Just about all the requests you can make on the Azure Portal are exposed as endpoints on the REST API. The REST API Docs have examples for each of the endpoints and discuss the parameters.
For example if you wanted to create a a VNET you could, hit
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/virtualNetworks/{virtualNetworkName}?api-version=2020-07-01
which would create your network, then you could hit the VM endpoint
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/virtualMachines/{vmName}/runCommands/{runCommandName}?api-version=2020-06-01
Again check the docs for the parameters, response payload, and more.
Yes you can connect the new VNet to the existing one via Virtual Network Peering. Then the resources in both networks can communicate i.e the AKS Clustor and the Virtual Nodes. There is a tutorial for setting up the peering here
If this helped please mark my original answer as accepted to help others with similar questions.
Can you share what the inner SSL exception is? You may need to open a support ticket, sounds like the root cause is the script isn't able to establish that connection so even if you try to execute it step by step your going to have trouble. Can you dump the inner ssl exception here and I'll take a look? I'd assume the connection is failing due to a networking issue with the VM, did you configure the NIC or Firewall settings against this? Also are you able to just spin up a new VM since your CD pipeline is failing anyway and retry on a fresh one?
You can see support plans here. The table describes the benefits of each support plan such as the response time. Clicking the blue button at the top for your support plan will redirect you to the Azure Portal where you can open a Ticket with Azure Technical Support.
You can still use a Service Principal as Jessica said to fetch the client id and client secret from the REST API. A service principal allows you to effectively delegate some permissions to your program i.e the permissions needed to fetch that and execute the creation of a VM.
Once you have your Service Principal you can use it to make the REST API Requests accordingly. The guide she has linked above instructs you how to create the service principal to permit this. Here's a StackOverflow post with the same information but writen a bit differently if this helps make it more clear.
@AshishJ,
Did you try to login with AD? Such as:
Lets try to log in without the token before debugging.