> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/troubleshooting-analysis.md).

# Troubleshooting analysis with Azure

Troubleshooting various Azure pipeline and integration issues in SonarQube Server 2026.2.

See also [Troubleshooting the analysis](/sonarqube-server/2026.2/analyzing-source-code/troubleshooting-the-analysis.md).

## Azure build pipeline fails <a href="#azure-pipeline-fails" id="azure-pipeline-fails"></a>

If your Azure build pipeline fails on the analysis stage, check that you correctly set the integration at the global level. In particular, check the PAT failure points. See [Binding to Azure DevOps](/sonarqube-server/2026.2/instance-administration/devops-platforms/azure-devops.md#preparing) for more information.

## Missing blame information or Could not find ref error <a href="#missing-blame-info-error" id="missing-blame-info-error"></a>

The errors "*Missing blame information…*" and "*Could not find ref…*" can be caused by checking out with a partial or shallow clone, or when using Git submodules. You should disable git shallow clone to make sure the scanner has access to all of your history when running analysis with Azure DevOps.

For more information, see the MS article on [Shallow fetch](https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/azure-repos-git?view=azure-devops\&tabs=yaml#shallow-fetch).

## Self-signed certificate error on Prepare Analysis Configuration task <a href="#self-signed-certificate-error" id="self-signed-certificate-error"></a>

Try to add the server self-signed certificate as described in [TLS certificates on client side](/sonarqube-server/2026.2/analyzing-source-code/scanners/scanner-environment/manage-tls-certificates.md#azure-pipelines).

### Related pages

* [Adding analysis to your Azure pipeline](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/introduction.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/troubleshooting-analysis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.