> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/configuration-guide/integrations/azure/defaults.md).

# Defaults

Configure default synchronization and work item behavior for the Azure DevOps integration.

The Defaults page controls how Pharos synchronizes data between Azure DevOps work items and Pharos issues/logs. Settings are split into two tabs — **Logs** and **Issues** — each governing different aspects of the integration behavior.

{% hint style="info" %}
For work item template configuration (project, work item type, description, merge fields), see [Ticketing Actions](https://docs.pharos.ai/configuration-guide/ticketing/actions.md). Defaults controls synchronization behavior, not template content.
{% endhint %}

***

## Accessing Defaults Settings

1. Open the **Pharos** app
2. Navigate to **Pharos Admin** → **Integrations** → **Azure**
3. Select the **Defaults** sub-section

***

## Logs Tab

The Logs tab controls how Pharos handles Azure DevOps work items created from log-level ticketing rules.

![Azure Defaults — Logs tab showing three controls: Auto Generate Similarity Labels, Auto Relate Work Items With Similar Errors, Create Unique Work Items by Org](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-ccace2b687a01ebda60bd34e1a785ab7e4908b60%2Fazure-defaults-logs-tab.png?alt=media)

| Control                                                 | Description                                                                                                                                                                                                                                                                                      |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Auto Generate Similarity Labels in Azure Work Items** | When enabled, Pharos adds generated labels (tags) to new work items that can be used to search for same or similar issues. New labels are appended to your existing labels or any defaults defined in the ticketing action.                                                                      |
| **Auto Relate Work Items With Similar Errors**          | When enabled, Pharos automatically relates similar issues via an Azure DevOps link. The links point to the earliest created unresolved similar issue.                                                                                                                                            |
| **Create Unique Work Items by Org**                     | When enabled, Pharos always creates a new work item even if an open work item for the same error from a different org already exists. Useful for multi-org ([Connected Orgs](https://docs.pharos.ai/configuration-guide/connected-orgs.md)) setups where each org should have its own work item. |

{% hint style="info" %}
These controls are most relevant for organizations using **log-level ticketing rules** or **Connected Orgs**. If you only create work items at the issue level, the Issues tab is more important.
{% endhint %}

***

## Issues Tab

The Issues tab controls bidirectional synchronization between Azure DevOps work items and Pharos issues.

![Azure Defaults — Issues tab showing five synchronization controls: related work items, duplicate work items, work item priority, issue priority, and completed status](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-53898857f23e3b901808232d7e75cc539774064f%2Fazure-defaults-issues-tab.png?alt=media)

### Relationship Sync

| Control                                         | Description                                                                                                                                                                                                    |
| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Synchronize related Work Items and Issues**   | When enabled, Pharos automatically relates Azure DevOps work items corresponding to related issues, and vice versa — will relate issues when work items are linked in Azure DevOps.                            |
| **Synchronize duplicate Work Items and Issues** | When enabled, Pharos automatically creates a duplicate link for work items corresponding to duplicate issues, and vice versa — will duplicate issues when work items are linked as duplicates in Azure DevOps. |

In Azure DevOps, these relationships appear as **Related** and **Duplicate** link types on the work item's Links tab.

### Priority Sync

| Control                                     | Description                                                                                                                                                                                                               |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Automatically update Work Item priority** | When enabled, Pharos updates the Azure DevOps work item priority based on the corresponding issue priority. Changes in Pharos flow to Azure DevOps.                                                                       |
| **Automatically update Issue priority**     | When enabled, Pharos updates the issue priority based on the corresponding work item priority. Once updated, Pharos always synchronizes priority from the work item, overriding any direct priority updates on the issue. |

Azure DevOps uses numeric priorities (1 = Critical, 2 = High, 3 = Medium, 4 = Low). Pharos maps its priority values to these numbers automatically.

{% hint style="warning" %}
Enabling both priority sync directions creates a bidirectional sync. Be aware that the Azure DevOps → Pharos direction takes precedence once a sync has occurred.
{% endhint %}

### Status Sync

| Control                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                   |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Synchronize completed status** | When enabled, resolving or closing a work item in Azure DevOps (e.g., setting State to Done, Closed, or Resolved) automatically updates the corresponding Pharos issue to Completed status. This is the foundation of the [reoccurrence handling](https://docs.pharos.ai/configuration-guide/ticketing.md#reoccurrence-handling) — if a completed issue reoccurs, Pharos creates a new work item and links it to the old one. |

***

## Recommended Settings

For most organizations starting with Azure DevOps integration:

| Control                                         | Recommended               | Why                                                                  |
| ----------------------------------------------- | ------------------------- | -------------------------------------------------------------------- |
| **Synchronize related Work Items and Issues**   | Enabled                   | Keeps Azure DevOps relationships in sync with Pharos                 |
| **Synchronize duplicate Work Items and Issues** | Enabled                   | Prevents duplicate work items from cluttering the backlog            |
| **Automatically update Work Item priority**     | Enabled                   | Triage in Pharos → priority flows to Azure DevOps                    |
| **Automatically update Issue priority**         | Enabled                   | Priority changes in Azure DevOps reflect in Pharos                   |
| **Synchronize completed status**                | Enabled                   | Closing work items in Azure DevOps completes issues in Pharos        |
| **Auto Generate Similarity Labels**             | Disabled initially        | Enable once you understand how tags affect your Azure DevOps queries |
| **Auto Relate Work Items With Similar Errors**  | Disabled initially        | Enable after establishing log-level ticketing rules                  |
| **Create Unique Work Items by Org**             | Disabled unless multi-org | Only needed with Connected Orgs                                      |

***

## Environment-Specific Defaults

Each org (production, sandbox) has its own defaults configuration. After a sandbox refresh:

* Review whether sync settings should match production or differ
* Consider disabling **Synchronize completed status** in sandbox if you don't want sandbox work item closures affecting issue status
* Use the [Quick Start](https://docs.pharos.ai/configuration-guide/quick-start.md) wizard **Sandbox Refresh** option to reset integration state

***

## Related

* [Authentication](https://docs.pharos.ai/configuration-guide/integrations/azure/authentication.md) — Connect Pharos to Azure DevOps
* [Ticketing Actions](https://docs.pharos.ai/configuration-guide/ticketing/actions.md) — Template configuration (project, work item type, merge fields)
* [Ticketing Rules](https://docs.pharos.ai/configuration-guide/ticketing/rules.md) — Automated work item creation criteria
* [Ticketing Overview](https://docs.pharos.ai/configuration-guide/ticketing.md) — Manual creation, sync behavior, best practices

{% hint style="success" %}
**Next Step:** Create [Ticketing Actions](https://docs.pharos.ai/configuration-guide/ticketing/actions.md) to define your work item templates, then set up [Ticketing Rules](https://docs.pharos.ai/configuration-guide/ticketing/rules.md) to automate work item creation.
{% endhint %}
