Skip to main content

Create new work items with Excel for Azure DevOps

It's no secret that practicing DevOps is just as much of a business position as it is a technical position. We have a very specific job to do - ship the product and ship it fast to stay ahead of competition. To successfully do so, we must plan our work and collaborate properly. If you're using Boards in Azure DevOps to track your tickets, you may be excited to know that there's a great Excel extension called "azure devops standalone office integration" that'll actually allow you to create work items right from Excel and publish those tickets to Azure DevOps. Let's get started!

The first thing you'll need to do is have Excel (at least Office 2010) installed and the Team Foundation Server Standalone Office Integration (

After you have that let's go ahead and open up Excel and head over to the "team" tab.

Next thing we want to do is click on "New List"

Let's go ahead and click on "Servers" so we can connect to our Azure DevOps portal and click "add".

After you type in the URL to your portal you will be prompted to type in your email and password associated with your account. Once you return to the add/remove screen go ahead and click close.

Choose which Team Project you would like to connect to then click "Connect". Once you click connect you will be presented with a "New List" screen. Choose the "Input List" option.

Now that we have our list let's go ahead and create some tickets!

Now click on your "title" bar and click "Publish in the Team ribbon.

Let's head back over to our Azure DevOps portal and go to Boards > Work items.

We now have our two new tickets.

You may be asking yourself "why do this in Excel?". The primary reason why I would do this in Excel is for the convenience. I don't have to manually go into Work Items and add a bunch of new tickets in. Let's say you have 10 tickets to add. Would it make more sense to do it manually 1 by 1? Or put them in a spreadsheet all at once and simply click the "publish" button?


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…

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.

Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…