Skip to content

Commit

Permalink
🔧 chore(integrations): Updated Azure DevOps Dev Docs (#12231)
Browse files Browse the repository at this point in the history
Co-authored-by: Alex Krawiec <[email protected]>
  • Loading branch information
iamrajjoshi and coolguyzone authored Jan 2, 2025
1 parent 042f43e commit 211f61b
Show file tree
Hide file tree
Showing 7 changed files with 75 additions and 27 deletions.
27 changes: 0 additions & 27 deletions develop-docs/integrations/azuredevops.mdx

This file was deleted.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added develop-docs/integrations/azuredevops/app-id.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
75 changes: 75 additions & 0 deletions develop-docs/integrations/azuredevops/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
---
title: Azure DevOps Integration
sidebar_title: Azure DevOps
---

## Create an Azure Application

Log into your Azure DevOps account or create a new one, and ensure you have a project set up.

Make sure the organization has third-party access via OAuth enabled in the organization settings.
![3p-oauth](./3p-oauth.png)


To use the Azure DevOps integration you'll need to create an application.

To start, you will need access to a [Microsoft Entra Admin Portal](https://entra.microsoft.com/#home)

![Register App](./register-app.png)


When configuring the app, use the following values:

| Setting | Value |
| ------------------------------- | -------------------------------------------------------------------------------------------------- |
| Supported account types | Accounts in any organizational directory |
| Redirect URI | `{YOUR_DOMAIN}/extensions/vsts/setup` |

<Note>

Take note of your App ID as we'll need it later.
![App ID](./app-id.png)

</Note>

Next go to Manager -> API Permissions to add the following permissions:
* Azure DevOps (`vso.code`, `vso.graph`, `vso.work_item`, `vso.service_endpoint`)
* Microsoft Graph (`User.Read`) (This should be added by default)

![Permissions](./perms.png)

Go to the "Certificates & secrets" tab and create a new client secret. Make sure you copy the secret as we'll need it later.

![Client Secret](./client-secret.png)

Add the App ID and Client Secret to `devlocal.py` like this:

```python
# Azure DevOps #
SENTRY_OPTIONS["vsts_new.client-id"] = your-app-id
SENTRY_OPTIONS["vsts_new.client-secret"] = your-client-secret
```

You can also add the App ID and Client Secret to `config.yml` like this:

```yml
# Azure DevOps #
vsts_new.client-id: your-app-id
vsts_new.client-secret: your-client-secret
```
You will also need to enable the feature flag to use the new Azure DevOps integration.
Enable the `migrate-azure-devops-integration` feature flag in your organization.
Add the following to your `devlocal.py` file:

```python
SENTRY_FEATURES["organizations:migrate-azure-devops-integration"] = True
```

<Alert title="Feature Flag" level="info">

This is a temporary measure until we fully migrate to the new Azure DevOps integration and remove references to the old one.

</Alert>

Follow our [documentation on installing and configuring the Azure DevOps integration](https://docs.sentry.io/organization/integrations/source-code-mgmt/azure-devops/) to finish installation and use the integration.
Binary file added develop-docs/integrations/azuredevops/perms.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 211f61b

Please sign in to comment.