You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The Datadog integration for [Azure Pipelines][16] works by using [service hooks][2] to send data to Datadog.
50
75
@@ -68,8 +93,6 @@ The Datadog integration for [Azure Pipelines][16] works by using [service hooks]
68
93
69
94
5. Click **Finish**.
70
95
71
-
## Advanced configuration
72
-
73
96
### Configuring multiple projects in bulk
74
97
75
98
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:
0 commit comments