Just a heads up, the CI might not be triggered due to a known issue Azure side: https://status.dev.azure.com/_event/179641421 It seems that today they're releasing the fix; there's a workaround for it but it would require rebasing all the PRs, because it's a change in the YAML file. I think we can wait tomorrow and see if it's still there, in that case opt to do the workaround.