Send Azure DevOps logs to LogPulse

The Azure DevOps organization audit log, pipeline logs and real-time service hook events.

In short
To send Azure DevOps logs to LogPulse, add Azure DevOps under Configure → Sources → Cloud. LogPulse reads the Azure DevOps Audit API and service hooks itself, without an agent. Events land in the audit, cicd indexes with source azure_devops and fill the CI/CD Pipeline, Security Event data models.

Overview

How Azure DevOps data reaches LogPulse
Vendor
Azure DevOps Audit API and service hooks
Collect
Integration pollerreads new events, maps the fields
Store
index=audit
index=cicd
  1. Azure DevOps Audit API and service hooks to Integration poller
  2. Integration poller to index=audit
  3. Integration poller to index=cicd

LogPulse signs in to Azure DevOps with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • Azure DevOps Personal Access Token (PAT)
  • Required scope: Audit Log: Read
  • Organization Admin or Project Admin role
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in Azure DevOps

Field in LogPulseWhere you find it
Azure DevOps URLThe address of your organization: https://dev.azure.com/your-organization, or a *.visualstudio.com address.
Personal Access Token (PAT)A PAT with the scope Audit Log: Read, from an Organization Admin or Project Admin. Stored encrypted and never shown again.
Specific project (optional)Leave empty to collect from all projects. The name is case-sensitive.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose Azure DevOps. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Service Hooks is not polled but sent to LogPulse by Azure DevOps. After you save, LogPulse shows the address and the key to set on the Azure DevOps side.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Audit Logsauditazure_devopsazure:devops:auditOrganization audit trail: permission changes, PAT creation, user management, git policy changes.
Service Hookscicdazure_devopsazure:devops:webhookReal-time events: build completions, PR activity, code pushes, work item changes, security alerts.
Pipeline Logs (off by default)cicdazure_devopsazure:devops:pipeline:logCI/CD pipeline run logs, stage results, job output, and build artifacts metadata.

The index is the kind of data and the source is the product, so detection rules for that kind of data find Azure DevOps without changes.

Note: Service hook events come in through a webhook: after you save, LogPulse shows the webhook address and secret once.
Note: The Audit API is not available on every Azure DevOps organization tier; the connection test tells you when it is not.

Fields and data models

Data modelWhat you get
CI/CD PipelineBuild and release pipeline events with status, duration, trigger and stage information.
Security EventPermission changes, PAT management, user access modifications and policy changes from the audit log.

Events are mapped to the data models above, with the same field names as other sources of the same kind. See field names.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (audit, cicd) source IN (azure_devops)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
PAT does not have "Audit Log: Read" scope. Add this permission to your token in Azure DevOps.Edit the PAT and add the scope Audit Log: Read.
Organization not found. Double-check the URL: it should look like https://dev.azure.com/your-org.Use the address of the organization, without a project behind it.
Audit API returned HTTP 4xx. The Audit service may not be available for your organization tier.Auditing must be turned on in the organization settings, and the organization must be connected to Microsoft Entra ID.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Azure DevOps may also simply have had nothing new.

Frequently asked questions

How do I send Azure DevOps logs to LogPulse?
Add the Azure DevOps cloud integration under Configure, Sources, Cloud in LogPulse and fill in Azure DevOps URL, Personal Access Token (PAT). LogPulse reads the Azure DevOps Audit API and service hooks itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in Azure DevOps?
Azure DevOps Personal Access Token (PAT). Required scope: Audit Log: Read. Organization Admin or Project Admin role. Read access is enough for collecting logs.
Which index does Azure DevOps data go to?
The index is the kind of data: audit, cicd. The source is the product: azure_devops. Each data source has its own sourcetype, listed on this page.
Which data models does Azure DevOps fill?
CI/CD Pipeline, Security Event. Detection rules and dashboards written for a data model work on Azure DevOps without changes.
Why is Pipeline Logs off by default?
To keep your daily ingest down until you need it: Pipeline Logs is high volume or of use to fewer teams. Tick the data source in the integration to switch it on.