---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/it-business-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Default map configuration for Azure DevOps integration with Agile Development 2.0

# Default map configuration for Azure DevOps integration with Agile Development 2.0 {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Understand the default field map configuration, of different process types, between Azure DevOps and Agile Development 2.0.
By looking at the default map configuration for different process types, you can see how work item types in Azure DevOps are mapped in Agile Development. You can also see how fields are mapped between the two applications.

When you import available epics, stories, and issues from Azure DevOps, this data is stored in tables as defined in the process map configuration.  
Nota:  
When you upgrade to version 1.3 of the application, map
configuration is generated at the process level per process type and not at the instance
level. You must update any custom maps that you previously configured to ensure that the
import and export of work items is not impacted.

Here's how you can view the default map configuration for different process types.  
1. Navigate to Agile Azure DevOps IntegrationAzure DevOps Instances.
2. Open your Azure DevOps instance record.
3. From the Process Mappings related list, open the record for a process map.
{#default-agile-azure-mapping__ol_xmd_3vr_bkb}

You can add or update the configuration for field, table, and choice maps between Azure DevOps and Agile Development 2.0. For details, see [Customizing your map configuration for Azure DevOps integration](https://servicenow-prod.fluidtopics.net/KWpt5EQHlReoAO3Wfp4XCw "Customize the table, field, or state map configuration between Azure DevOps and Agile Development 2.0 according to your organizational preferences.").

The following are the details of the default map configuration for various process types in Azure DevOps.

## Default mapping for Agile process {#default-agile-azure-mapping__section_fw3_bzg_h2c}

{#default-agile-azure-mapping__table_bt3_fzg_h2c__entry__2}

| Table in Azure DevOps | Table in Agile Development 2.0 |
|-|-|
| User Story | Story \[rm_story\] |
| Epic | Epic \[rm_epic\] |
| Feature | Feature \[ sn_safe_feature\] |
[Tabela 1. Default mapping configuration for Agile Process]

{#default-agile-azure-mapping__table_bt3_fzg_h2c}

## Default mapping for Basic process {#default-agile-azure-mapping__section_sck_czg_h2c}

{#default-agile-azure-mapping__table_kgx_nzg_h2c__entry__2}

| Table in Azure DevOps | Table in Agile Development 2.0 |
|-|-|
| Issue | Story \[rm_story\] |
| Epic | Epic \[rm_epic\] |
[Tabela 2. Default mapping configuration for Basic process]

{#default-agile-azure-mapping__table_kgx_nzg_h2c}

## Default mapping for CMMI process {#default-agile-azure-mapping__section_qmx_czg_h2c}

{#default-agile-azure-mapping__table_isy_yzg_h2c__entry__2}

| Table in Azure DevOps | Table in Agile Development 2.0 |
|-|-|
| Epic | Epic \[rm_epic\] |
| Requirement | Story \[rm_story\] |
[Tabela 3. Default mapping configuration for CMMI process]

{#default-agile-azure-mapping__table_isy_yzg_h2c}

## Default mapping for Scrum process {#default-agile-azure-mapping__section_dhl_dzg_h2c}

{#default-agile-azure-mapping__table_r3d_b1h_h2c__entry__2}

| Table in Azure DevOps | Table in Agile Development 2.0 |
|-|-|
| Product Backlog Item | Story \[rm_story\] |
| Epic | Epic \[rm_epic\] |
[Tabela 4. Default mapping configuration for Scrum process]

{#default-agile-azure-mapping__table_r3d_b1h_h2c}