Skip to main content

Executing commands and scripts on a VM within the Azure portal

At times you may need to run a script or a command to retrieve resources or create new resources. Rather than having to SSH or RDP into your server, you can easily run these commands or scripts right from the Azure Portal.

1) An Azure account
2) A Linux VM, Windows VM, or preferably both.
3) Knowledge of Bash and PowerShell (I will explain the cmdlets and shell scripts that I'm running)

First thing you want to do is go to your Resource Group within Azure and head over to your VMs.

(For the Linux portion) Click on your Linux and in the left pane scroll down to "Run command".

Once you click on "Run command", you'll see two options. RunShellScript and ifconfig. Choose RunShellScript.

Once you're there, you can run whatever script or bash line you'd like.

Similarly, we can do the same on a Windows machine. If you set up a Windows Server, head over to your Windows Server and find the "Run command" option in the same place as the Linux VM.

We'll see a few more options here then we saw in the Linux VM. Let's choose "RunPowerShellScript".

This is quite useful if you need to run a script or a line of code against one machine to ensure something exists or you know you need to install something one time. I wouldn't recommend using this for something like running a script on 5 different machines. This is more for one-off checks/installs.


Popular posts from this blog

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …