Azure DevOps
Learn how to connect Azure DevOps to ZigiOps. Step-by-step Personal Access Token setup, connected system configuration, and supported integration templates.
What is Azure DevOps integration in ZigiOps?
Azure DevOps is a cloud-based DevOps platform providing work item tracking, repositories, pipelines, and release management. ZigiOps enables secure, agentless, bi-directional integrations between Azure DevOps and ITSM, DevOps, and monitoring systems.
With ZigiOps, Azure DevOps can:
Receive incidents and tickets from ITSM platforms
Synchronize work items with external systems
Participate in end-to-end DevOps and IT operations workflows
Maintain traceability across tools without custom scripting
Which Azure DevOps versions are supported?
Using a supported version is mandatory.
Azure DevOps
All
All
Are there any environmental prerequisites for Azure DevOps?
Before proceeding, always confirm the prerequisites of the specific integration template you plan to use. Some integration templates may not require all environmental prerequisites described below.
See the Related Templates section at the end of this page.
How do I create a Personal Access Token (PAT) in Azure DevOps?
A Personal Access Token (PAT) is required for authenticating Azure DevOps with ZigiOps.
Sign in to your Azure DevOps organization
Example: https://dev.azure.com/{yourOrganization}. Choose the correct organization from the menu on the left.
Open User Settings and select Personal Access Tokens
Click + New Token
Configure the token
Name - a descriptive name for the integration
Organization - select the organization where the token will be used
Expiration - choose a lifespan for the token
Select the required Scopes, depending on the integration use case:
For build and release agents: Agent Pools (Read and Manage)
For audit log access: Read Audit Log
Click Create
Copy the token and store it securely
The token is shown only once and will not be displayed again.
How do I connect Azure DevOps to ZigiOps?
Connected System Configuration
Follow the steps below to add Azure DevOps as a connected system.
Log in to your ZigiOps instance
Navigate to Connected Systems - Add New System - Azure DevOps
Configure the following parameters
Server URL - Enter the Azure DevOps service URL.
For Azure DevOps Cloud (most commonly used): Use the standard Microsoft cloud endpoint:
https://dev.azure.comThis is the default and official Azure DevOps Services URL. It must be entered exactly as shown above - do not add organization names, paths, or additional segments.For Azure DevOps On-Premises (TFS / Azure DevOps Server): Use the specific server URL provided by your Azure DevOps Server installation. For example:
http://yourserver:8080/tfs. On-premises deployments are significantly less common than cloud deployments.Instance Type - Select the type of your Azure DevOps instance:
Cloud (Azure DevOps Services)
On-Premises (Azure DevOps Server / TFS)
The selected instance type determines how ZigiOps handles the connection and naming conventions internally.
Organization / Collection - Enter the name of your Azure DevOps organization (Cloud) or collection (On-Premises).
Although the concept is technically the same, Microsoft uses different terminology:
In Azure DevOps Cloud, it is called an Organization
In Azure DevOps Server (On-Premises), it is called a Collection
ZigiOps automatically adjusts the label based on the selected Instance Type, so there is no confusion during configuration.
Username - Enter your Azure DevOps username.
Private Access Token - Enter the previously generated Personal Access Token (PAT). Ensure the PAT has the required permissions for the integration scenario (for example: Work Items - Read/Write, Project and Team - Read).
Proxy Settings (optional) - Enable this option only if your environment requires communication through a proxy server.
Review the configuration
Click Save to store the connected system
Common Configuration Mistakes
Below are the most frequent issues encountered when connecting Azure DevOps to ZigiOps.
1. Incorrect Server URL
For Azure DevOps Cloud, the Server URL must be: https://dev.azure.com
Do not add organization names, project paths, or any additional segments.
Example of incorrect format: https://dev.azure.com/ventsi0957/Ventsi%20Basic
For On-Premises deployments, ensure the full server URL (including port if applicable) matches your Azure DevOps Server configuration.
2. Organization / Collection Name Mismatch
Ensure the Organization (Cloud) or Collection (On-Premises) name is entered exactly as defined in Azure DevOps. It is case-sensitive. Do not include URL prefixes, slashes, or extra spaces.
Correct example (Cloud): organization-name
Incorrect: https://dev.azure.com/organization-name
3. Insufficient PAT Permissions
The Personal Access Token (PAT) must have adequate permissions for the integration scenario.
Typical required scopes include:
Work Items - Read and Write
Project and Team - Read
Build / Release - if CI/CD synchronization is required
If permissions are insufficient, authentication may succeed but synchronization actions will fail.
4. Expired or Revoked PAT
If the integration stops working after a period of time, verify that the PAT:
Has not expired
Has not been manually revoked
Has not been regenerated
If necessary, generate a new PAT and update it in the Connected System configuration.
5. Proxy Misconfiguration
If a proxy is required in your environment:
Ensure proxy settings are enabled in ZigiOps
Verify proxy credentials (if authentication is required)
Confirm outbound HTTPS connectivity to Azure DevOps
If issues persist after reviewing the above checks, consult the Troubleshooting section or contact ZigiWave Support with the relevant logs from the ZigiOps instance.
What are the most common Azure DevOps integration use cases?
Use Case 1: Synchronizing ITSM incidents with Azure DevOps work items
When incidents are created in ITSM platforms such as ServiceNow, ZigiOps can automatically create corresponding work items in Azure DevOps. Incident details such as priority, description, attachments, and comments are mapped directly to Azure DevOps work items. As developers update or resolve the work item, the changes are synchronized back to the ITSM system, ensuring consistent status tracking across teams.
Use Case 2: Bridging development teams working in Jira and Azure DevOps
In environments where different teams use different DevOps tools, ZigiOps enables seamless collaboration between Jira and Azure DevOps. Tasks, bugs, or user stories created in one system can be automatically created or updated in the other. This allows organizations to maintain tool flexibility while preserving traceability, visibility, and synchronized workflows across platforms.
Use Case 3: Centralizing operational work from ITSM into Azure DevOps
Azure DevOps is often used as the primary platform for development and operational execution. ZigiOps enables incidents, problems, or service requests from ITSM systems to be funneled into Azure DevOps as structured work items. This ensures that development teams receive actionable, well-contextualized tasks while IT operations teams retain governance and lifecycle control in their native systems.
What integration templates are available for Azure DevOps?
ZigiOps provides a set of predefined Azure DevOps integration templates, covering common ITSM and DevOps scenarios.
Related Azure DevOps Templates
Azure DevOps tasks - Jira tasks
Bi-directional
Azure DevOps work items - Remedy incidents
Bi-directional
Azure DevOps work items - ServiceNow incidents
Bi-directional
Cherwell incidents - Azure DevOps issues
Bi-directional
Remedy problems - Azure DevOps work items
Bi-directional
ServiceNow incidents - Azure DevOps issues
Bi-directional
Each template includes predefined entity mappings, direction of synchronization, and field-level configuration logic.
For detailed information about available templates for Azure DevOps integrations, please contact:
Email: [email protected]
Summary
The Azure DevOps integration in ZigiOps provides:
Secure, PAT-based authentication
Agentless connectivity
Support for all Azure DevOps versions and deployment types
Bi-directional synchronization with ITSM and DevOps tools
Ready-to-use integration templates
Last updated
Was this helpful?