Microsoft Azure DevOps (Team Foundation Server)

Technical requirements

The following requirements must be met to integrate Microsoft Azure DevOps with SD Elements.

  • Team Foundation Server version 2018 and later.

  • NTLM or Basic Authentication must be enabled

  • The user configured for the connection should:

    • Be a member of the project

    • Have permission to create, tag, transition and close work items.

    • Specific permissions:

      • Edit project-level information - Allow

      • Create tag definition - Allow

Default assigned fields

The following fields are set by default:

  • Title

  • Description

  • Priority


The integration supports the following:

Default Priority Mapping

SD Elements

Microsoft Azure DevOps (TFS)









Connection details

Enter the connection details for the server.


Select the protocol for the connection (HTTPS or HTTP) (Default: HTTPS)


The domain name or IP address of the server

URL changes with Azure DevOps may require the addition of a Context Root as well. For example, the URL may become, with as the Server and acme as the Context Root.

Context Root

Top-level location where Microsoft Azure DevOps is installed on a server. The value for this may be dependent on the configuration of an internal corporate proxy or where an administrator has installed Microsoft Azure DevOps.

Collection name

The name of a project collection in Microsoft Azure DevOps (Default: DefaultCollection)


Enter the credentials needed to authenticate to the server.


Username authorized to connect with the server and create/edit issues in anticipated projects.

Password/Personal Access Token (PAT)

The password or the Personal Access Token used to authenticate to the server.

Countermeasures to Synchronize

Select Countermeasures to synchronize.

Sync all Countermeasures

Synchronize all Countermeasures from SD Elements.

Sync Risk Policy Countermeasures

Synchronize only Countermeasures that fall under the risk policy.

Project details

Enter the project-level details.

Azure DevOps (TFS) Project

The name of the project where issues should be created.

Advanced Microsoft Azure DevOps configuration

Enter advanced global configuration options.

Issue Type

Type of issue that SD Elements will create when creating a Countermeasure in Azure DevOps. (Default: User Story)

Map an Azure DevOps (TFS) status to an SD Elements status

This mapping determines the status to assign an SD Elements Countermeasure based on its corresponding Azure DevOps issue status.

See Status Mapping for more information.

Map an SD Elements status to an Azure DevOps (TFS) status

This mapping determines the status to assign an Azure DevOps issue based on its corresponding SD Elements Countermeasure status. All Azure DevOps statuses in this mapping should be a single transition away from every other status in the mapping, as well as from the default status for new issues in your Azure DevOps project workflow. For example, an item in an "In Progress" state cannot be transitioned to an item in a "Completed" state. It must transition to a "Resolved" state first, then "Completed".

'Incomplete', 'Complete', and 'Not Applicable' SD Elements statuses must have a mapping. Any unmapped custom SD Elements statuses will use these mappings based on their meaning.

See Status Mapping for more information.

Unmapped Status Fallback (Optional)

The SD Elements status to map to when encountering an unmapped Azure DevOps status (Default: Incomplete)

Closed Issue Status

The name of a status in Azure DevOps to use when its corresponding SD Elements Countermeasure is removed from the project.

Enter advanced project configuration options.

Iteration Path

Name of the iteration (Example: Iteration\ABC)

If you create a new release and select the “Carry over Issue Tracker connections” option, you must manually edit the iteration path to ensure synchronization does not overwrite Countermeasures in your previous Microsoft Azure DevOps iteration.*

Area Path

Name of the Area Path (Default: Project name)


Enter settings for synchronizing SD Elements Countermeasures.

Authoritative Source

Select the tool that will be the authoritative system of record: Microsoft Azure DevOps or SD Elements. This field is used in case of conflicting statuses between the Microsoft Azure DevOps issue and the SD Elements Countermeasure. When you first synchronize a TODO Countermeasure in SD Elements with an issue in Microsoft Azure DevOps, they will have the same status. If you then change the status in one tool, for example by closing the issue in Microsoft Azure DevOps, they will have conflicting statuses. This conflict is resolved when the projects are synchronized. There are three options:

  • Issue Tracker (default): The SD Elements Countermeasure will be updated to match the status in Microsoft Azure DevOps.

  • SD Elements: The Microsoft Azure DevOps status will be updated to match the SD Elements status.

  • Last Status Change: The SD Elements and Azure DevOps states will always reflect the latest updated status. For example, if an Azure DevOps issue is most recently updated then the SD Elements Countermeasure status will be updated to reflect the Azure DevOps status. The opposite is also true.

Include code sample How-To’s in Countermeasure descriptions

Whether or not to include detailed code samples and How-To’s in the Microsoft Azure DevOps issue.

This Issue Tracker server is hosted within a private network and cannot be reached directly by SD Elements.

Select this option if SD Elements does not have direct network access to the Microsoft Azure DevOps server.

For example, if you are using a hosted SD Elements instance but you want to integrate with an internal/protected Microsoft Azure DevOps system, choose this option and run the Remote Integration Agent to perform integration.

Filter Countermeasures

Select SD Elements Countermeasures to synchronize with the Microsoft Azure DevOps project.

Countermeasures having a minimum priority

Only synchronize Countermeasures with a minimum priority, such as 7 or above. This is useful if you want to limit the amount of work for users. (Default: 1)

Countermeasures with status meaning

Only synchronize Countermeasures with certain statuses, such as TODO or DONE. (Default: TODO)

Limit to Countermeasures having these phases

Only synchronize Countermeasures in certain phases, such as Requirements or Development. (Default: none selected, meaning Countermeasures from all phases will be synchronized)

Countermeasures having all of the following tags

Only synchronize Countermeasures containing certain SD Elements Countermeasure tags. (Optional)

Countermeasures with verification status

Only synchronize Countermeasures with a specific verification status, such as Pass or Fail. (Default: none selected, meaning Countermeasures with any verification status will be synchronized)

Advanced Issue Tracker options

Enter advanced configuration options.

Issue Tracker context

Bind a set of Countermeasures using a cetain value. This is applicable only when custom titles are selected having the entry "Context"

Issue Tracker parent issue

The issue identifier of a parent issue. SD Elements Countermeasures will be created as children of this issue.

Custom Priority Mapping

If the standard Microsoft Azure DevOps priorities have been customized, you must map the customized priority names in Microsoft Azure DevOps to their corresponding SD Elements numeric priorities.

This is a common option that will need to be set.

For example, map "1" issues to priority 10 in SD Elements, "2" to priorities 7-9, and so on.

Custom Fields Mapping

In addition to the default-assigned fields, you can map additional SD Elements fields to Microsoft Azure DevOps fields.

Fields that are not required or have default values do not need to be set.

For example, you may have a required field in your Microsoft Azure DevOps project that is not set by default. Custom field mappings can be set at both the system connection and project connection levels, and the mappings set in a project connection will override mappings set in the system connection.

For more details refer to section Advanced field support.

Sync frequency

Select how frequently the SD Elements and Microsoft Azure DevOps projects are synchronized. You can choose from the following options. The more frequently you run synchronization, the greater the performance impact on both the SD Elements and Microsoft Azure DevOps servers. This is generally only a concern for large organizations running many synchronizations at once.

Hourly, Daily, Weekly, or Monthly

The projects will synchronize automatically every hour, day, week or month. Daily synchronization is typically sufficient. However, you may want to select a more frequent interval if development moves quickly in your organization.


You must click the Sync button on the Issue Tracker Integrations page in order to synchronize the projects. This is the default value.

results matching ""

    No results matching ""