Skip to main content

Azure DevOps Server –Mermaid support improvements

Azure DevOps (Server) had Mermaid support for a long time. Unfortunately that support was limited to the Wiki functionality.

This means that if you had markdown files somewhere else in your repo; for example as part of your readme.md file or an architecture decision record(ADR), any mermaid diagram inside these files was not rendered.

Some extensions exists in the Visual Studio marketplace that tried to solve this,  but when using these extensions I noticed that none of these extensions were bug free and all had limitations or caused problems with other features inside Azure DevOps.

With the December 2025 release of Azure DevOps, you no longer need a 3th party solution as this feature is finally available.

Create a mermaid diagram in any .md file:

And the preview tab will now nicely render your diagram:

Nice!

More information

Markdown Syntax for Files, Widgets, Wikis - Azure DevOps | Microsoft Learn

Azure DevOps Server Release Notes - Azure DevOps Server & TFS | Microsoft Learn

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...