> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/azure-devops/introduction.md).

# Introduction

## Introduction

StepSecurity supports Azure DevOps in two areas: runtime security for pipeline runs, and governance over the identities and tokens that hold access to your Azure DevOps organization.

#### Capabilities

| Area                                                                          | What it does                                                                                                                                                                       | Where to configure it                               |
| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| [Harden-Runner](/azure-devops/harden-runner.md)                               | Network and runtime security monitoring for Azure Pipelines jobs, including outbound traffic monitoring, file integrity checks, and detections for anomalous behavior during a run | Add the `HardenRunner@1` task to your pipeline YAML |
| [PAT Governance](/azure-devops/identities-and-pats.md#personal-access-tokens) | Continuous evaluation of Personal Access Tokens in your Azure DevOps organization against four security controls, with per-token remediation                                       | Settings > Control Evaluation                       |
| [Identity inventory](/azure-devops/identities-and-pats.md)                    | Visibility into Personal Access Tokens, service connections, and Entra service principals with access to your organization                                                         | Identities & PATs                                   |

Harden-Runner currently supports Microsoft-hosted agents.

#### Getting started

1. Connect your Azure DevOps organization to StepSecurity from the [Admin Console](/azure-devops/admin-console.md). This installs the StepSecurity app in your Azure tenant.
2. Add the Harden-Runner task as the first task in each pipeline job to start collecting runtime telemetry. See[ Harden-Runner](/azure-devops/harden-runner.md).
3. Enable the Personal Access Token controls you want under Settings > Control Evaluation, and set their thresholds.
4. Configure notification channels and events under Settings > Notifications so violations reach your team.

#### Documentation

* [Overview](/azure-devops/overview.md): the All Controls dashboard and the PAT Governance controls
* [Harden-Runner](/azure-devops/harden-runner.md): runtime security for Azure Pipelines
* [Identities & PATs](/azure-devops/identities-and-pats.md): token, service connection, and service principal inventory
* [Settings](/azure-devops/settings.md): notifications, control evaluation, and API access
* [Admin Console](/azure-devops/admin-console.md): connecting and managing Azure DevOps organizations


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stepsecurity.io/azure-devops/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.