Skip to content

Commit bcdcd6a

Browse files
SCI Datadog integration section in Azure pipelines (#33013)
* SCI Datadog integration section in Azure pipelines Added instructions for configuring Datadog integration and enabling CI Visibility in Azure DevOps. * SDCI-1902 / Fix pr Comments * SDCI-1902 / Fix links in tabs * SDCI-1902 / FIx Links * SDCI-1902 / Fix spelling * fix link in Service Hook Subscriptions tab --------- Co-authored-by: Joe Peeples <[email protected]>
1 parent 90c5968 commit bcdcd6a

File tree

1 file changed

+36
-8
lines changed
  • content/en/continuous_integration/pipelines

1 file changed

+36
-8
lines changed

content/en/continuous_integration/pipelines/azure.md

Lines changed: 36 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,31 @@ This table shows the mapping of concepts between Datadog CI Visibility and Azure
4545
| _Not available in Datadog_ | Step |
4646

4747
## Configure the Datadog integration
48+
{{< tabs >}} {{% tab "Datadog Integration (recommended)" %}}
49+
50+
### Enable CI Visibility in Datadog
51+
52+
After the Azure App is created and installed, enable CI Visibility for the organizations and projects you want Datadog to monitor.
53+
54+
1. Verify that your Azure DevOps organization is linked to a **Microsoft Entra tenant**. See the [Azure source code setup instructions][1] for guidance on connecting Azure DevOps projects to Datadog.
55+
56+
2. In Datadog, navigate to [**Software Delivery → CI Visibility → Add a Pipeline Provider → Azure Pipelines**][2].
57+
58+
3. Click **Configure** next to the Azure DevOps organization you want to enable.
59+
60+
4. To enable CI Visibility for the entire organization, toggle **Enable CI Visibility**. Future projects detected by the Azure app will automatically be enabled.
61+
62+
5. To enable CI Visibility for individual projects:
63+
- Scroll through the projects list.
64+
- Toggle **Enable CI Visibility** for each project you want to monitor.
65+
66+
Pipelines appear in Datadog immediately after CI Visibility is enabled for an organization or project.
67+
68+
[1]: /integrations/azure-devops-source-code/#setup
69+
[2]: https://app.datadoghq.com/ci/setup/pipeline?provider=azurepipelines
70+
71+
{{% /tab %}}
72+
{{% tab "Service Hook Subscriptions" %}}
4873

4974
The Datadog integration for [Azure Pipelines][16] works by using [service hooks][2] to send data to Datadog.
5075

@@ -68,8 +93,6 @@ The Datadog integration for [Azure Pipelines][16] works by using [service hooks]
6893

6994
5. Click **Finish**.
7095

71-
## Advanced configuration
72-
7396
### Configuring multiple projects in bulk
7497

7598
Datadog offers a [script][12] to help you enable service hooks across multiple or all of your Azure projects using the Azure API. The script requires Python 3 and the `requests` package.
@@ -114,7 +137,18 @@ Example for enabling the hooks in specified projects:
114137
--az-org datadoghq \
115138
projectName1 projectName2
116139
```
140+
[2]: https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/webhooks?view=azure-devops
141+
[3]: https://app.datadoghq.com/organization-settings/api-keys
142+
[8]: https://marketplace.visualstudio.com/items?itemName=Datadog.ci-visibility
143+
[12]: https://raw.githubusercontent.com/DataDog/ci-visibility-azure-pipelines/main/service_hooks.py
144+
[13]: https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows#create-a-pat
145+
[16]: /integrations/azure_devops/
117146

147+
{{% /tab %}}
148+
{{< /tabs >}}
149+
150+
151+
## Advanced configuration
118152

119153
### Set custom tags
120154

@@ -157,20 +191,14 @@ The **CI Pipeline List** page shows data for only the default branch of each rep
157191
{{< partial name="whats-next/whats-next.html" >}}
158192

159193
[1]: https://azure.microsoft.com/en-us/products/devops/pipelines
160-
[2]: https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/webhooks?view=azure-devops
161-
[3]: https://app.datadoghq.com/organization-settings/api-keys
162194
[4]: https://app.datadoghq.com/ci/pipelines
163195
[5]: https://app.datadoghq.com/ci/pipeline-executions
164196
[6]: /continuous_integration/pipelines/custom_tags_and_measures/?tab=linux
165-
[8]: https://marketplace.visualstudio.com/items?itemName=Datadog.ci-visibility
166197
[9]: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/approvals?view=azure-devops&tabs=check-pass#approvals
167198
[10]: /glossary/#custom-tag
168199
[11]: /glossary/#custom-measure
169-
[12]: https://raw.githubusercontent.com/DataDog/ci-visibility-azure-pipelines/main/service_hooks.py
170-
[13]: https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows#create-a-pat
171200
[14]: https://app.datadoghq.com/integrations/azure
172201
[15]: /glossary/#custom-span
173-
[16]: /integrations/azure_devops/
174202
[17]: /continuous_integration/search/#search-for-pipelines
175203
[18]: /logs/guide/best-practices-for-log-management/
176204
[19]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/

0 commit comments

Comments
 (0)