Scripted installation of Chef Habitat on Windows

I spotted this week that we have made a subtle change to the Chef Habitat installation instructions on Windows and added a new scripted install option via PowerShell.

In general, we recommend using Chocolatey to install the latest version of Chef Habitat on your Windows-based workstations. If you have Chocolatey installed, this can be as simple as running:

choco install habitat -y

If you have a CI system (such as Azure Pipelines or Jenkins) or just want to stay on the bleeding edge rather than the stable builds pushed to Chocolatey, then you might want a more direct route to installing the latest version and we now provide a PowerShell script that can be used to install and configure specific versions of Habitat.

Assuming you have a modern (Windows 10, Windows Server 2016 or higher) Windows installation then installation can now be as short as running the following PowerShell command:

iex "& { $(irm }"

If you need to specify the version you can use the following example:

iex "& { $(irm } -Version 0.75.0"

If you are using Azure Pipelines, you can simply include this PowerShell step in your azure-pipelines.yml file:

- master

  vmImage: 'windows-2019'

- task: [email protected]
    targetType: 'inline'
    script: 'iex "& { $(irm }"'

When running the job in your pipeline, you should see output as follows:

Azure Pipelines showing a PowerShell step installing Habitat on a build agent

Source: official Habitat installation docs for Windows

Microsoft MVP status renewed for 2019-2020 and rebooting the blog!

I’m very pleased to announce I have been re-awarded Microsoft MVP status in Azure for the 4th consecutive year! I am humbled and grateful for the support!

When reviewing my contributions over the last year, one area that was sorely lacking compared to the year before was blogging. In retrospect this came naturally from trying to avoid having multiple presences (I also have been known to blog at but these are mostly product announcements that are orchestrated by Chef’s marketing team) so I will try a different approach and post smaller updates that are more relevant to the technical audience here (and maybe some outside-of-work stuff, who knows! YHBW).

It’s the start of a new “Fiscal Year” at Microsoft (FY2020) and typically that means rotations in the product teams and some new ways of working and objectives.

Hopefully I will get to talk to you about some of the new things we have been building at the WinOps London conference and Microsoft Ignite later this year – hoping to see some of you there and I look forward to sharing and amplifying the knowledge in this great community.