Fact-checked by Grok 2 weeks ago

Azure DevOps

Azure DevOps is a cloud-based platform developed by that provides integrated tools and services for teams to manage the entire application lifecycle, including , , building, testing, and deployment. Launched on September 10, 2018, as a and evolution of Team Services (VSTS), it builds on over 15 years of 's investments in developer tools and has been adopted by thousands of organizations worldwide. The platform emphasizes collaboration, agility, and scalability, supporting both cloud-hosted (Azure DevOps Services) and on-premises deployments (). At its core, Azure DevOps comprises five primary services: Azure Boards for work tracking and agile planning with tools like Kanban boards and backlogs; Azure Repos for version control using Git or Team Foundation Version Control (TFVC); Azure Pipelines for continuous integration and continuous delivery (CI/CD) across various languages and platforms; Azure Test Plans for manual, exploratory, and automated testing; and Azure Artifacts for managing software packages and dependencies. These services integrate seamlessly to enable end-to-end DevOps practices, fostering faster delivery cycles and improved team productivity. Pricing is flexible, offering free access for up to five users per organization, with paid tiers based on subscriptions or pay-as-you-go usage for larger teams. Azure DevOps also supports extensibility through a marketplace of add-ons, integrations with third-party tools like GitHub and Slack, and advanced features such as AI-assisted workflows, including GitHub Copilot integration and agentic DevOps AI agents introduced in 2025 updates. Its on-premises counterpart, Azure DevOps Server (formerly Team Foundation Server), allows organizations to maintain data sovereignty while accessing similar functionalities, with the latest release being the Azure DevOps Server RC on October 7, 2025. Overall, the platform has become a cornerstone for modern software development, powering everything from small startups to enterprise-scale projects by promoting automation, security, and collaboration.

Overview

Definition and Purpose

Azure DevOps is a suite of integrated services offered by designed to support the full software development lifecycle, encompassing planning, development, testing, and delivery of applications. It provides a comprehensive set of tools that enable teams to manage projects from inception through deployment, fostering collaboration among stakeholders while accommodating both cloud-hosted and on-premises deployments. The primary purpose of Azure DevOps is to implement practices by unifying workflows for agile planning, version control, and (CI/CD) pipelines, testing, and package management, thereby streamlining end-to-end processes and reducing time to market. This integration helps organizations automate repetitive tasks, enhance code quality, and ensure reliable releases across diverse environments. Evolving from earlier Microsoft offerings like Team Services (VSTS) and Team Foundation Server (TFS), Azure DevOps builds on these foundations to deliver modern, scalable solutions for collaborative development. Azure DevOps targets a wide range of users, including developers, project managers, and operations teams within organizations of all sizes, from startups to large enterprises, and it extends support to open-source projects through free tiers for public repositories and unlimited private storage for small teams. Its high-level architecture is primarily cloud-based, leveraging the platform for scalability and accessibility via interfaces, while offering extensibility to setups through on-premises servers that integrate seamlessly with cloud services. This flexible model allows teams to choose deployment options that align with their security, compliance, and infrastructure needs.

Key Components

Azure DevOps comprises five core services that provide end-to-end support for software development and deployment processes. These services—Azure Boards, Azure Repos, Azure Pipelines, Azure Test Plans, and Azure Artifacts—enable teams to plan, code, build, test, and package applications collaboratively. Azure Boards facilitates work tracking and planning using Agile methodologies such as Kanban boards, Scrum backlogs, and customizable dashboards to manage work items like user stories, bugs, and tasks. Azure Repos offers source control through unlimited private Git repositories or Team Foundation Version Control (TFVC), supporting features like branch policies and pull requests for code collaboration. Azure Pipelines automates continuous integration and continuous delivery (CI/CD) with multi-stage pipelines that handle builds, tests, and deployments across platforms, including support for containers like Docker and orchestration tools like Kubernetes. Azure Test Plans manages testing activities, encompassing manual, exploratory, and automated tests through organized test suites and integrated reporting. Azure Artifacts provides universal package management for feeds such as NuGet, npm, and Maven, enabling secure sharing and versioning of dependencies within builds. These services interconnect within shared organizations and projects, allowing seamless data flow across the development lifecycle—for instance, work items from can link directly to code changes in , which trigger automated pipelines in for testing via and packaging through . This integration fosters visibility and efficiency, with dashboards aggregating insights from all services to monitor progress holistically.

History

Origins in TFS and VSTS

Team Foundation Server (TFS) was released on March 29, 2006, as part of the Visual Studio 2005 Team System, marking Microsoft's initial foray into an integrated on-premises application lifecycle management (ALM) platform. This platform combined centralized version control via Team Foundation Version Control (TFVC), work item tracking for project management, reporting capabilities, and automated build services to support team collaboration in software development. Initially tailored for .NET-centric development within Windows environments, TFS provided a unified repository for source code, requirements, tasks, and bugs, emphasizing traceability and process guidance through customizable process templates. Over the subsequent years, TFS underwent iterative enhancements across multiple versions, including TFS 2008, which improved scalability and reporting; TFS 2010, which introduced advanced agile planning tools such as hierarchical work items, velocity tracking, and integrated storyboarding to better support and agile methodologies; and further releases up to TFS 2018, which refined build orchestration and multi-device testing. These evolutions addressed early criticisms of setup complexity and expanded language support beyond .NET, incorporating tools for and other ecosystems while maintaining TFVC as the core centralized system. The shift toward cloud-based delivery began in September 2012 with the preview launch of the Team Foundation Service, a hosted evolution of TFS designed for accessibility and reduced infrastructure management. Renamed Online in 2013, this service mirrored TFS features in the cloud, initially emphasizing integration for —introduced on January 30, 2013—to complement TFVC and facilitate open-source workflows. Online achieved general availability in 2013, with public previews of advanced features like CodeLens for code analytics following in 2014 and reaching general availability in 2015. In November 2015, Visual Studio Online was rebranded as Team Services (VSTS), solidifying its role as a scalable, multi-tenant counterpart to TFS and broadening support for cross-platform, multi-language development teams. This transition highlighted the move from on-premises rigidity to flexible, subscription-based ALM, while TFS continued as the self-hosted option through 2018.

Rebranding to Azure DevOps

In September 2018, Microsoft rebranded Visual Studio Team Services (VSTS) to Azure DevOps Services for its cloud-based offering, positioning it as a comprehensive platform for DevOps practices accessible to developers beyond the Visual Studio ecosystem. Simultaneously, the on-premises Team Foundation Server (TFS) was renamed Azure DevOps Server starting with version 2019, maintaining compatibility for enterprise environments while emphasizing a unified branding across cloud and self-hosted deployments. This rebranding aimed to promote broader adoption of DevOps methodologies by decoupling the tools from specific IDEs and highlighting five core services—Azure Boards, Azure Repos, Azure Pipelines, Azure Test Plans, and the newly introduced Azure Artifacts for package management. Following the rebranding, expanded DevOps capabilities to address evolving development needs. Artifacts was launched in September 2018 as a dedicated service for hosting and sharing packages across formats like , , and , enabling seamless integration into build pipelines without external dependencies. By 2020, Pipelines received significant enhancements for container orchestration and deployment, including improved tasks for building images and deploying to clusters via YAML-based configurations, supporting hybrid cloud workflows. AI-driven features emerged in 2025 with private previews of integration, such as sending work items from Boards to the Copilot coding agent, allowing code suggestions and task automation to accelerate pull request reviews and branch creation. Key milestones post-rebranding underscored Azure DevOps' evolution toward ecosystem integration and modernization. In 2019, Microsoft unified its services under the Azure DevOps brand, completing the migration of VSTS users and standardizing access across organizational projects for consistent tooling. The 2021 focus on GitHub convergence built on Microsoft's 2018 acquisition, with general availability of Azure Boards integration to GitHub repositories, enabling automatic linking of commits, pull requests, and issues to work items for streamlined collaboration. Recent updates in 2024 and 2025 enhanced multi-cloud support in Azure Pipelines, allowing deployments to non-Azure providers like AWS and Google Cloud through extensible agents and tasks. In 2025, Azure DevOps continued to evolve with Q4 updates focusing on enhanced GitHub integrations, scale improvements for connecting repositories, and support for work item integration with the GitHub Copilot coding agent. The hybrid model remains a , with ongoing support for providing on-premises control while incorporating cloud sync features like repository mirroring and pipeline synchronization to bridge local and Azure DevOps Services environments.

Core Services

Azure Boards

Azure Boards is a web-based service within Azure DevOps designed for planning, tracking, and discussing work across teams during the software development lifecycle. It provides tools for managing work items such as issues, bugs, user stories, and tasks, enabling collaboration through customizable workflows that support agile methodologies. Teams can visualize progress, prioritize backlogs, and monitor metrics to ensure alignment with project goals. The core functionalities of Azure Boards revolve around flexible planning and tracking tools. Kanban boards allow teams to visualize work items as cards in columns representing workflow stages, such as "To Do," "In Progress," and "Done," with drag-and-drop updates for status changes. These boards support swimlanes for categorizing work by priority or type and work-in-progress (WIP) limits to prevent bottlenecks. Backlogs serve as prioritized lists for organizing work hierarchically, including product backlogs for features and requirements, and portfolio backlogs for epics and initiatives. Sprint planning is facilitated through taskboards, which focus on iteration-specific work, allowing teams to assign tasks and track daily progress. Work item types are customizable, encompassing epics for high-level initiatives, features for deliverable groupings, user stories or product backlog items for customer requirements, tasks for granular efforts, and bugs for defects. Azure Boards offers robust support for Agile and Scrum methodologies through built-in templates and reporting tools. The service includes predefined process templates—Agile for general agile practices with user stories and tasks; for sprint-focused teams using product backlog items and impediments; and CMMI for formal processes emphasizing requirements, risks, and reviews. These templates define default work item types, workflows, and fields to streamline adoption. For progress tracking, velocity charts measure team capacity over sprints by summing story points or effort, helping forecast future iterations. Burndown charts display remaining work against time, highlighting trends like scope changes to identify deviations early. Customization in Azure Boards allows teams to tailor the tool to specific needs via process templates and extensions. Administrators can inherit from system processes like Agile, Scrum, or CMMI to create custom versions, adding or modifying work item types, fields, and workflow states without affecting other projects. Custom fields, such as picklists or numeric values for effort tracking, can be added to capture project-specific data, with rules enforcing dependencies—like making a field required based on state changes. Extensions from the Azure DevOps Marketplace enable further enhancements, such as custom rules for automated field updates or integrations for advanced workflows. These customizations apply at the level, ensuring consistency while allowing team-specific configurations like board column mappings. Practical usage of Boards includes linking work items to development artifacts for and using queries for reporting. Work items can be associated with commits or pull requests in Azure Repos, automatically updating status upon completion and providing end-to-end visibility from planning to deployment. The Work Item Query Language (WIQL), a SQL-like syntax, enables complex reporting by selecting fields, applying filters (e.g., by state or assigned user), and ordering results; for instance, queries can generate lists of overdue tasks or trend analyses for dashboards. These features support efficient workflows, such as bulk updates from query results or sharing reports via .

Azure Repos

Azure Repos provides capabilities within Azure DevOps, enabling teams to manage and collaborate on code using or Team Foundation Version Control (TFVC). As the primary source control service, it supports unlimited private repositories at no additional cost for basic usage, allowing developers to store, track changes, and collaborate on codebases securely in the . , the default and recommended option, offers for flexible branching and merging, while TFVC serves as a legacy centralized system primarily for existing projects transitioning from on-premises setups. Key features include branch policies and pull request workflows, which enforce code quality by requiring reviews, successful builds, and minimum approvals before merging changes into protected branches such as the . Permissions can be configured at the , , or levels to control read, write, and administrative access for users or groups, ensuring granular security. Additional capabilities encompass code search via an optional extension for querying across repositories, integration to publish repository files as pages, and tools that display and relationships in the web interface. Repositories can also link commits or pull requests to work items in Boards for traceability. Migration tools facilitate importing repositories from external providers like or directly through the Azure DevOps portal, preserving history and branches during the process. For TFVC users, built-in utilities convert centralized repositories to , enabling a shift to modern distributed workflows while maintaining version history. Best practices for Repos emphasize adopting a Git branching , such as the Gitflow model, where feature branches are created for isolated development and merged via pull requests to maintain a stable main branch. Forking is recommended for open-source contributions or external collaborators, allowing changes to be proposed through pull requests for review before integration. Merge strategies like squash or rebase help keep commit history clean, while processes in pull requests promote peer feedback, automated checks, and required approvals to uphold quality standards.

Azure Pipelines

Azure Pipelines is a cloud-based continuous integration and (CI/CD) service within DevOps that automates the building, testing, and deployment of software applications across various platforms and languages. It enables teams to define workflows as code using files, supporting both simple builds and complex multi-environment deployments. Azure Pipelines integrates seamlessly with repositories, allowing pipelines to trigger automatically on code changes for efficient automation. The service's capabilities rely on build agents to execute pipeline tasks. Microsoft-hosted agents provide pre-configured machines in the cloud, supporting Windows, , and macOS environments with common tools like , Java, and .NET pre-installed, eliminating the need for infrastructure management. Self-hosted agents allow users to run on their own or machines, offering greater over , access, and compliance requirements. Pipelines support multi-stage configurations, where workflows are defined in a single YAML file with stages for building, testing, and deploying, promoting principles and integration. jobs enable multiple tasks to run concurrently on available agents, optimizing resource use, while matrix strategies allow a single job to execute multiple times with varying parameters, such as testing across different operating systems or configurations. For deployments, Azure Pipelines facilitates integration with services like App Service and Functions, as well as external targets such as Kubernetes clusters and virtual machines. Deployment jobs run steps sequentially against defined environments, supporting strategies like or rolling updates. Release gates introduce automated checks, such as querying external systems for health status, while approvals require manual intervention from designated approvers to proceed, ensuring compliance in production environments. These features allow controlled rollouts to multi-environment setups, including on-premises infrastructure. Extensibility is achieved through the , which offers thousands of pre-built tasks for custom steps, such as integrating with third-party tools like or AWS. Variable groups centralize the storage of reusable values and secrets across pipelines, linked via library management for secure access. Service connections provide authenticated endpoints to external services, such as subscriptions or repositories, enabling secure task execution without embedding credentials in files. Scalability in Pipelines accommodates varying workloads through tiered . Open-source (public) projects receive up to 10 free Microsoft-hosted parallel jobs with unlimited minutes per month (each up to 360 minutes) and 1 free self-hosted job with unlimited minutes. For private projects under the plan ($6 per user per month), users get 1 free Microsoft-hosted parallel job with 1,800 total minutes per month (each up to 60 minutes) and 1 free self-hosted job with unlimited minutes; additional parallel jobs are available for purchase ($40 per month for Microsoft-hosted, $15 for self-hosted). Higher access levels like + Test Plans ($52 per user per month) do not alter job limits but provide expanded feature access.

Azure Test Plans

Azure Test Plans is a component of Azure DevOps designed to facilitate manual, exploratory, and planned testing activities within projects. It enables teams to create, manage, and execute test cases, organize them into suites and plans, and track testing progress to ensure throughout the development lifecycle. This service supports both structured testing approaches, where predefined test cases are followed, and ad-hoc exploratory sessions that allow testers to investigate issues dynamically. By integrating with other Azure DevOps services, Test Plans helps bridge the gap between testing efforts and overall , providing tools to log defects directly as work items for resolution. As of 2025, recent updates include the New Test Run experience in public preview (Q4 2025) for improved test execution and reporting on the latest test outcomes for requirements. Key testing tools in Azure Test Plans include test suites, plans, and cases, which form the foundational structure for organizing testing activities. Test cases are individual, reusable units that describe steps, expected results, and preconditions for verifying specific functionalities, such as user interface interactions or data validation scenarios. These can be grouped into test suites—logical collections like static suites for fixed sets of cases or requirements-based suites linked to user stories—to streamline execution. Test plans, in turn, represent high-level containers that encompass multiple suites, defining the scope, schedule, and assignment of testing for a release or iteration, allowing teams to assign testers and track completion rates. For exploratory testing, Azure Test Plans offers session-based tools, including a session recorder that captures screenshots, annotations, and step-by-step actions during unstructured sessions, enabling testers to document findings in real-time without rigid scripts. Integration with automation enhances the capabilities of Azure Test Plans by allowing manual tests to coexist with automated ones run through Azure Pipelines. Teams can link test cases to automated tests, where builds from Pipelines provide test data or environments, ensuring seamless validation across manual and processes. Defect tracking is tightly coupled with work items in Azure Boards; during test execution, failures can be logged as bugs with direct to the associated , requirements, or code changes, facilitating quick and resolution by development teams. This linkage supports end-to-end , where test results inform sprint retrospectives and release decisions. Reporting features in Azure Test Plans provide insights into testing effectiveness through analytics, coverage metrics, and progress visualizations. Test analytics dashboards offer configurable views of pass/fail rates, test run history, and trends over time, helping identify bottlenecks in the testing . Coverage metrics quantify how well requirements or are tested, such as percentage of user stories covered by executed tests, while progress charts display completion status via burndown or cumulative flow diagrams tailored to testing milestones. These reports can be shared or exported to support reviews and continuous improvement. Access to advanced features in Azure Test Plans requires the Basic + Test Plans access level ($52 per user per month) to unlock full authoring and functionalities for creating and managing test plans, suites, and exploratory sessions. Basic access ($6 per user per month) allows viewing and running existing tests, but not full management. This tiered model ensures scalability for organizations with intensive testing needs.

Azure Artifacts

Azure Artifacts is a package service within Azure DevOps that enables teams to create, host, and share software packages across multiple formats from a centralized feed, facilitating and in development workflows. It supports universal package by allowing a single feed to store diverse package types without restrictions on mixing formats, promoting efficient consumption and distribution for build processes. The service accommodates key package formats including for .NET assemblies, for / modules, for dependencies, for libraries, and universal packages for arbitrary file sets or custom formats not covered by the others. Feeds serve as the core organizational unit, functioning as repositories that can be configured as public—limited to project-scoped access in public Azure DevOps projects and shareable online—or private, which are the default and restrict access to specific users or teams within the organization or project scope. Public feeds support publishing but not downloading universal packages, ensuring controlled sharing. Feed permissions are managed through , with roles such as Feed Owner (full management including deletion and restoration), Contributor (publish and read access), and Reader (view and download only), allowing granular control over who can interact with packages. Retention policies provide a 30-day recovery window for deleted feeds, after which they are permanently removed and the feed name becomes available again after 15 minutes, helping maintain without indefinite . Upstream sources enhance functionality by connecting feeds to external public registries, such as nuget.org for packages or npmjs.com for modules, enabling proxying and automatic saving of requested packages into the feed. In Azure Pipelines, Azure Artifacts integrates seamlessly for publishing packages generated during builds—such as using dedicated tasks for , , , or PyPI—and consuming them in subsequent stages or projects, streamlining and delivery. It also offers a server feature that hosts symbol files, allowing tools like or to automatically retrieve them for stepping through optimized code without manual file management. Symbols are published via pipeline tasks like "Index sources and publish symbols," supporting efficient post-build . Upstream sources provide built-in caching by automatically storing copies of packages pulled from external registries, ensuring availability even if the source becomes unavailable and reducing network latency for repeated restores. Packages are immutable once published or saved, preventing alterations to versions and maintaining version integrity across the . For compliance, Artifacts integrates with vulnerability scanning tools through Pipelines, such as the Microsoft Security DevOps extension for or npm audit for JavaScript dependencies, enabling detection of known vulnerabilities in packages during the build process.

Integrations and Extensions

Microsoft Ecosystem Integration

Azure DevOps provides seamless native integrations with various services, enabling end-to-end development and deployment workflows within the Microsoft ecosystem. These integrations leverage shared , , and deployment capabilities to streamline , automate processes, and ensure across and environments. By connecting with services, , and tools like Office 365 and Power BI, Azure DevOps enhances visibility, traceability, and efficiency for teams managing software lifecycles. A core aspect of this integration involves services for deployment, identity, and monitoring. Pipelines supports and () to key targets, including App Service for web apps and APIs, Kubernetes Service (AKS) for containerized applications, and Virtual Machines (VMs) for custom infrastructure needs, using built-in tasks for scripting and configuration. Identity management is handled through (formerly AD), allowing organizations to connect their DevOps instance for unified , where users sign in with the same credentials across services and manage access via Entra ID groups and policies. For monitoring, Application Insights integrates directly with DevOps, enabling the creation of work items such as bugs or tasks from telemetry data like exceptions or issues, using Kusto (KQL) templates to populate details automatically and link them to pipelines or boards. GitHub integration, deepened following Microsoft's 2018 acquisition, allows synchronization of repositories and artifacts between platforms to support hybrid workflows. Users can connect repositories to Azure Boards to automatically link commits, pull requests (s), branches, and issues to work items, providing traceability without manual updates. Azure Pipelines can build and deploy code from repos, while GitHub Actions can complement Pipelines for specific automation tasks, such as PR validations or releases, with features like GitHub Checks for status updates. This convergence facilitates a unified developer experience, where teams can use Azure DevOps for planning and for code hosting. As of 2025, integrations have expanded to support GitHub Enterprise Cloud organizations with data residency enabled (August 2025), Azure Boards integration with for AI-assisted work item management (private preview September 2025, general availability Q4 2025), linking work items to GitHub Advanced Security alerts (Q4 2025), expanded GitHub Advanced Security features including improved login and domain-based scoping (November 2025), and scale improvements for connecting repositories. Additional Microsoft tools extend Azure DevOps functionality for collaboration and analytics. Office 365 integrations include notifications pushed to Office 365 Groups or channels for events like build completions or work item updates, configurable via service hooks. Power BI connects to Azure DevOps views via the Power BI Data Connector, allowing custom dashboards for metrics like velocity, bug trends, or deployment success rates, with OData feeds for real-time data import. IDE extensions, such as Team Explorer, enable direct connectivity for source control, work item tracking, and build management within the IDE, supporting Git and TFVC workflows. For hybrid scenarios, Azure Arc extends Azure DevOps management to on-premises and multi-cloud resources. Azure Arc-enabled servers and Kubernetes clusters can be onboarded to Azure, allowing Azure Pipelines to deploy applications, apply policies, and monitor hybrid infrastructure consistently with cloud resources, using service principals for secure access at scale. This enables unified governance, where DevOps teams treat on-premises VMs or Kubernetes as native Azure assets for CI/CD pipelines.

Third-Party Extensions and Marketplace

The Azure DevOps Marketplace, integrated within the Visual Studio Marketplace, serves as a central hub for discovering, installing, and managing extensions that customize and extend the functionality of Azure DevOps services such as Boards, Pipelines, Repos, Test Plans, and Artifacts. These extensions are available in both free and paid models, with the majority being free and maintained by the community, while paid options often include advanced features like premium support or enterprise integrations. Extensions are categorized by functionality, including build and release tasks for automating pipelines, reporting tools for enhanced dashboards and analytics, and security extensions for code scanning and vulnerability management. Popular third-party integrations available through the enable seamless connectivity with external tools, enhancing notification workflows, code quality analysis, and infrastructure management. For instance, the Jenkins Integration extension facilitates by triggering Jenkins builds from Pipelines or syncing job statuses. The extension integrates static code analysis directly into build pipelines, allowing automated quality gates and detection of bugs, vulnerabilities, and code smells. Similarly, the extension provides tasks to install and execute commands for (IaC) provisioning across clouds like , AWS, and GCP, supporting plan, apply, and destroy operations within pipelines. For notifications, extensions like those for enable service hooks to post updates on build completions, pull requests, or work item changes directly to channels. Extensions are installed and managed at the organization level in Azure DevOps, ensuring deployment-specific control without affecting other tenants. Users access the via the shopping bag icon in their organization settings, search for extensions, and select "Get it free" or purchase paid versions, with permissions reviewed during to grant necessary scopes like read/write to repos or builds. Management includes assigning extensions to specific projects, disabling or uninstalling them organization-wide, and handling updates through automatic deployment of new versions upon publication, as defined in the extension's for versioning. The REST supports programmatic updates, such as enabling or disabling installed extensions, to maintain compliance and performance. As of Q4 2025, enhancements include improved management of high-privilege scopes, decorators, and unpublished extensions to . Community contributions form the backbone of the Marketplace, with developers worldwide publishing open-source extensions via GitHub repositories to address specific needs like custom widgets or tasks. To ensure quality, extensions undergo a rigorous certification process before public availability: publishers share extensions privately first, followed by Microsoft's validation including virus scans, , and potential demo requests to verify and . Certified extensions must be actively maintained, adhere to privacy policies, and meet install thresholds for badges like "Top Publisher," fostering trust through user ratings, reviews, and responsive support from contributors.

Security and Compliance

Built-in Security Features

Azure DevOps provides a suite of built-in security features designed to safeguard data, control access, and mitigate risks within development workflows. These mechanisms emphasize defense-in-depth, integrating , monitoring, secret protection, and automated threat detection directly into the platform's core services. By leveraging these features, organizations can enforce least-privilege access, track activities for , and proactively identify vulnerabilities in dependencies. Access management in Azure DevOps relies on (RBAC), where permissions are assigned through predefined groups such as Project Administrators, which allow members to configure project settings, teams, and processes. These groups operate at organization, project, or collection levels, with inheritance from enabling seamless synchronization of user identities and group memberships across Azure services. Deny permissions override allows, ensuring granular control, while access levels like Basic and Basic + Test Plans determine feature availability without altering underlying RBAC. Administrators can manage these via the platform's interface, supporting custom groups for tailored access. Auditing and logging capture all significant actions in Azure DevOps, including permission modifications, resource deletions, and branch policy updates, storing events in activity logs for 90 days. These logs detail actors, timestamps, IP addresses, and categories, allowing administrators to filter, export in or formats, and review for anomalies. Integration with Azure Sentinel streams data for real-time threat detection, enabling automated alerts and incident response workflows. This feature requires Entra ID-backed organizations and Project Collection Administrator permissions to access. Secrets management utilizes variable groups to store and share sensitive values across pipelines, with at rest and in transit to prevent exposure in logs or outputs. These groups link directly to Azure Key Vault for centralized , automatic rotation, and role-based , reducing the risk of hardcoding credentials. secure files further support this by allowing upload and decryption of confidential documents, such as certificates, exclusively within authorized builds, governed by library security policies. Pipelines must explicitly authorize variable group usage to enforce isolation. Vulnerability scanning is embedded in Artifacts and Pipelines to inspect dependencies for known issues during builds and package management. In Artifacts, tools like npm audit automatically scan projects for security flaws in public and private packages, reporting severity levels and suggesting fixes via updates to package files. For broader coverage, Advanced Security integration in Repos and Pipelines performs dependency analysis on ecosystems like , , and , generating alerts for CVEs tied to the Advisory Database and closing them upon resolution. Scans trigger on pipeline runs or graph changes, with results viewable in the Advanced Security tab for .

Compliance Standards and Certifications

Azure DevOps adheres to several key industry standards and certifications to support for organizations using its services. It holds certifications including ISO/IEC 27001:2022 for , ISO/IEC 27018:2019 for protection of personally identifiable information in public clouds, ISO 26262:2018 (ASIL D) for functional safety in automotive applications, C5, IRAP, and ENS-Spain. Additionally, Azure DevOps complies with SOC 1 Type 2 and SOC 2 Type 2 reports, which cover controls for , , , and confidentiality, with annual audits conducted by independent third parties. These reports are accessible through the Service Trust Portal. For data privacy and protection, Azure DevOps supports compliance with the General Data Protection Regulation (GDPR) in the , enabling organizations to manage processing in line with requirements. It also achieves HIPAA compliance, including eligibility for a Business Associate Agreement (BAA) that outlines responsibilities for handling in the United States. These certifications ensure that Azure DevOps meets stringent requirements for sectors like healthcare and data-intensive industries. Azure DevOps provides data residency options to address sovereignty needs, allowing customers to select from eight geographic regions: , , , , , , , and . Within these regions, customer data is geo-replicated for high availability, except in where it replicates to South Central US; this setup helps organizations maintain control over data location to meet local regulations. In 2023, enhanced Azure's EU Data Boundary commitments, which apply to Azure DevOps by ensuring customer data for EU customers is stored and processed within EU boundaries where configured, supporting sovereignty controls.

Pricing and Licensing

Subscription Models

Azure DevOps offers subscription models designed to accommodate teams of varying sizes and needs, primarily through cloud-based services and on-premises deployments. Organizations can set up a free tier that supports up to five Basic users, providing access to core features such as Azure Boards, Repos, Pipelines, and 2 GiB of Artifacts storage without any cost. Beyond the initial five users, the Basic plan is available at $6 per user per month, enabling unlimited users with full access to these foundational services. Stakeholder access is included at no additional charge for unlimited users, offering read-only capabilities like viewing work items, dashboards, and providing feedback, but excluding advanced tools such as code repositories or test case creation. Visual Studio subscriptions integrate seamlessly with Azure DevOps, granting subscribers complimentary access that does not count toward the five-user free limit. Professional-level subscriptions provide access, while subscriptions include Basic plus Test Plans features, allowing unlimited organizations and comprehensive usage for development and testing workflows. This model supports individual developers and teams by bundling Azure DevOps licensing with broader productivity tools, such as enhancements and cloud credits. For on-premises deployments, requires licensing along with Client Access Licenses () for each user. Professional subscriptions cover one license and one at $45 per user per month, whereas subscriptions do so at $250 per user per month; additional users can be licensed via the plan at $6 per month or + Test Plans at $52 per month. Classic licensing options are also available through resellers for a three-year commitment, ensuring flexibility for organizations preferring self-hosted environments. Feature access varies by subscription level to align with user roles and requirements. The access level unlocks most capabilities, including agile planning in Boards, in Repos, and in Pipelines, but excludes specialized testing tools. Advanced features like Test Plans, which support management and execution, necessitate the Basic + Test Plans subscription or equivalent licensing, such as Test Professional or Enterprise editions. This tiered structure ensures that organizations pay only for the functionalities essential to their practices.

Usage-Based Billing

Azure DevOps employs a usage-based billing model for certain resources, allowing organizations to pay only for consumption beyond included free tiers, primarily through an associated Azure subscription. This pay-as-you-go approach covers compute resources in pipelines and storage for artifacts, enabling scalable costs without fixed commitments for variable workloads. Billing is managed at the organization level, with charges accruing for additional parallel jobs and data retention as usage exceeds limits. For Pipelines, usage-based s apply to parallel using s. Microsoft-hosted parallel include one free job limited to 1,800 minutes per month per ; additional $40 each and provide unlimited minutes. Self-hosted parallel include one free job with unlimited minutes, while extra $15 each, also with unlimited minutes. These rates support flexible scaling, with no charges for self-hosted maintained by the user. Azure Artifacts storage follows a tiered pay-as-you-go structure after the initial 2 GiB free allowance per organization. Storage beyond 2 GiB is billed at $2 per GiB for 2–10 GiB, $1 per GiB for 10–100 GiB, $0.50 per GiB for 100–1,000 GiB, and $0.25 per GiB for over 1,000 GiB, charged monthly based on average usage. This model accommodates package management needs without upfront costs for low-volume teams. Public open-source projects benefit from enhanced free usage, including up to 10 parallel jobs with unlimited minutes in Pipelines, eliminating compute costs for community-driven development. Overall, usage-based billing integrates with Azure Cost Management tools via the linked subscription, providing dashboards for tracking, forecasting, and optimizing expenses across resources.

References

  1. [1]
    What is Azure DevOps? - Azure DevOps - Microsoft Learn
    Jul 18, 2025 · Azure DevOps is a cloud-based platform that provides integrated tools for software development teams. It includes everything you need to plan ...Core services · Dashboards
  2. [2]
    Introducing Azure DevOps | Microsoft Azure Blog
    Sep 10, 2018 · Azure DevOps captures over 15 years of investment and learnings in providing tools to support software development teams.
  3. [3]
    Azure DevOps
    Optimize your development process with Azure DevOps Services. Plan smarter, collaborate better, and ship faster using agile tools, CI/CD, agentic AI, ...
  4. [4]
    Azure DevOps Server 2022 Release Notes - Microsoft Learn
    Azure DevOps Server 2022 Release Date: December 6, 2022​​ Azure DevOps Server 2022 is a roll up of bug fixes. It includes all features in the Azure DevOps Server ...
  5. [5]
    Azure DevOps Services Pricing
    Explore the different Azure DevOps pricing options for open source projects, small teams, and teams of all sizes.
  6. [6]
    What is Azure Boards - Azure Boards | Microsoft Learn
    Sep 29, 2025 · Azure Boards is a web-based service that teams use to plan, track, and discuss work throughout the development lifecycle. It supports agile ...
  7. [7]
    Collaborate on code - Azure Repos - Microsoft Learn
    Jan 13, 2024 · Azure Repos is a set of version control tools that you can use to manage your code. Whether your software project is large or small, using version control as ...<|control11|><|separator|>
  8. [8]
    What is Azure Pipelines? - Azure Pipelines | Microsoft Learn
    Jul 28, 2025 · Azure DevOps grants a free tier of parallel jobs to every organization for both Microsoft-hosted and self-hosted private and public projects.Continuous Integration · Continuous Delivery · Azure Pipelines Pricing
  9. [9]
    What is Azure Test Plans? Manual, exploratory, and automated test ...
    Jul 17, 2025 · This browser-based test management solution supports planned manual testing, user acceptance testing, exploratory testing, and stakeholder feedback.
  10. [10]
    Tenth anniversary of Team Foundation Server - Buck Hodges
    Mar 17, 2016 · Today marks the tenth anniversary of shipping TFS 2005, which was our first version. We shipped nearly six months late – VS 2005 shipped in ...
  11. [11]
    Visual Studio 2013 - Introducing Visual Studio Online - Microsoft Learn
    TFS was introduced eight years ago, and began the move to a cloud-hosted application lifecycle management (ALM) service in 2012 with the launch of Team ...
  12. [12]
    Agile Development - Make Agile Work for You in TFS 2010
    TFS 2010 provides out-of-the-box integration to leverage a new Windows SharePoint Service (WSS) or an existing one. The creation of an MSF Agile project ...
  13. [13]
    Team Foundation Service updates - Jan 30 | Microsoft Learn
    Jan 30, 2013 · This Git support does not replace the existing centralized TFS version control system – which many teams will still find matches their needs, ...Missing: shift | Show results with:shift
  14. [14]
    General Availability of CodeLens in Visual Studio Online
    Apr 17, 2015 · To use CodeLens in Visual Studio Online you must : Be using Visual Studio Ultimate 2013 Update 4, or Visual Studio 2015 (Preview or later ...
  15. [15]
    Microsoft empowers developers with new and updated tools ...
    Nov 18, 2015 · The company today introduced Visual Studio Team Services, an enhanced and rebranded version of the Visual Studio Online service with 3.6 million ...
  16. [16]
    TFS rebrand to Azure DevOps Server - Microsoft Learn
    Oct 7, 2025 · Microsoft rebranded Visual Studio Team Foundation Server (TFS) as Azure DevOps Server 2019 and up. This new release brings many of the newest features.Missing: evolution | Show results with:evolution
  17. [17]
    Getting started with package management using Azure Artifacts
    Sep 10, 2018 · In this video, we will show you some initial steps to help you get started, by creating a feed for an npm package to use in your Azure Pipeline.Missing: date | Show results with:date<|control11|><|separator|>
  18. [18]
    Introducing Azure DevOps | Microsoft Learn
    Sep 10, 2018 · The single service that was Visual Studio Team Services (VSTS) is now becoming our new set of Azure DevOps Services.<|control11|><|separator|>
  19. [19]
  20. [20]
    About Kanban Boards - Azure Boards
    ### Summary of Kanban Boards in Azure Boards
  21. [21]
    Use backlogs to manage projects - Azure Boards
    ### Summary of Backlogs in Azure Boards
  22. [22]
  23. [23]
    About work items and work item types - Azure Boards - Microsoft Learn
    Oct 8, 2025 · Your backlog items might appear as User Stories (Agile), Issues (Basic), Product Backlog Items (Scrum), or Requirements (CMMI). All these work ...
  24. [24]
    Default processes and process templates - Azure Boards
    Jul 29, 2025 · Scrum: Is the next most lightweight. Agile: Supports many Agile method terms. CMMI: Provides the most support for formal processes and change ...Understand CMMI process... · Agile process work item types
  25. [25]
    Use Agile Process Template Artifacts - Azure Boards | Microsoft Learn
    Oct 9, 2025 · Monitor progress. All processes, including Agile, Scrum, and CMMI, support building charts and dashboards to show status and trends. Azure ...
  26. [26]
    Manage Scrum process template objects - Azure Boards
    Oct 8, 2025 · Learn how to use Scrum process objects to plan and track work and monitor progress and trends when you're connected to Azure DevOps.
  27. [27]
    Understand CMMI process template artifacts - Azure - Microsoft Learn
    Oct 8, 2025 · The following table maps template versions used by Azure DevOps on-premises releases; Azure Boards (cloud) always uses the latest template.
  28. [28]
  29. [29]
  30. [30]
  31. [31]
    List work item fields and attributes in Azure Boards - Microsoft Learn
    Nov 3, 2025 · Learn about work item fields, their attributes, and how to modify them in Azure Boards.
  32. [32]
    Add a Custom Rule to a Work Item Type - Azure DevOps Services
    Aug 21, 2025 · Add fields to a selected work item type. Select the work item type (WIT) to which you want to add a rule, choose Rules, and then choose New rule ...
  33. [33]
    Configure and Customize Azure Boards - Microsoft Learn
    Sep 30, 2025 · Custom fields let you capture project-specific data. They can power rollups and reports but apply across the process. Recommendations: ... You can ...
  34. [34]
    Link work items to objects - Azure Boards | Microsoft Learn
    Oct 18, 2025 · In the Work items to link field, enter the ID of the work item you want to link to, or select from the dropdown menu, and then select Add link.
  35. [35]
    Define a work item query in Azure Boards - Microsoft Learn
    Jul 17, 2025 · Work item queries in Azure Boards generate lists of work items based on filter criteria, defined by one or more clauses, and can be saved and ...
  36. [36]
    Work Item Query Language (WIQL) reference syntax - Azure Boards
    WIQL syntax is used to execute the Query By Wiql REST API. The API only returns work item IDs, regardless of which fields you include in the SELECT statement.Prerequisites · Query language overview
  37. [37]
    Guide for getting started with Azure Repos - Microsoft Learn
    Feb 1, 2024 · Azure Repos offers free unlimited private Git repositories, making it easy to try. Git is the most commonly used version control system today.
  38. [38]
    Git and TFVC version control - Azure Repos - Microsoft Learn
    Jul 24, 2024 · Git is the default version control provider for new projects. You should use Git for version control in your projects and begin to move your existing TFVC ...Missing: shift | Show results with:shift
  39. [39]
    Git branch policies and settings - Azure Repos - Microsoft Learn
    Mar 25, 2025 · Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management standards.
  40. [40]
    Set Git branch security and permissions - Azure Repos
    Jul 28, 2025 · Bypass policies when completing pull requests, Users with this permission are exempt from the branch policy set for the branch when completing ...
  41. [41]
    Set Git repository permissions - Azure Repos - Microsoft Learn
    Sep 4, 2025 · Set Git repository permissions in Project Settings>Repositories>Security. You can set permissions for security groups or specific users.
  42. [42]
    Functional code search - Azure Repos - Microsoft Learn
    Jul 17, 2025 · This article explains how to refine your search across repositories using code types and other functions with the Code Search Marketplace extension for Azure ...Prerequisites · Code search best practices
  43. [43]
    Publish Git Repository Files to Team Wiki - Azure DevOps
    Jun 4, 2025 · This article describes how to add and edit content published to a wiki by using the Azure DevOps web portal and the Azure DevOps CLI.
  44. [44]
    Manage branches in your Git repo - Azure DevOps - Microsoft Learn
    Feb 18, 2025 · Manage the work in your team's Git repo from the Branches view on the web. Customize the view to track the branches you care most about.Prerequisites · Organize your branches
  45. [45]
    Drive Git development from work items - Azure Boards
    Jul 17, 2025 · This article covers how to create new branches, add links to commits, and manage pull requests in a Git repository hosted on Azure DevOps.<|control11|><|separator|>
  46. [46]
    Import a Git repository into a project - Azure Repos | Microsoft Learn
    Jul 15, 2025 · This article shows you how to import an existing Git repo from GitHub, Bitbucket, GitLab, or other location into a new or empty existing repo in your Azure ...Prerequisites · Import into a new repo
  47. [47]
    Import and migrate repositories from TFVC to Git - Azure Repos
    Feb 18, 2025 · You can migrate code from an existing Team Foundation Version Control (TFVC) repository to a new Git repository within the same organization.Requirements · Steps to migrate · Convert version control...
  48. [48]
    Adopt a Git branching strategy - Azure Repos - Microsoft Learn
    Mar 25, 2024 · Adopt a branching strategy for your team. You can collaborate better and spend less time managing version control and more time developing code.Branch policies · Create a new Git branch · What is continuous delivery?Missing: visualization | Show results with:visualization
  49. [49]
    Fork your repository - Azure Repos | Microsoft Learn
    Feb 18, 2025 · If you want to merge your codebase changes into the original repo, you must create a pull request (PR) to request review and approval of those ...Missing: best | Show results with:best
  50. [50]
    Create a pull request to review and merge code - Azure Repos
    Sep 4, 2025 · To link work items, open the PR in your browser, and then make your updates on the PR's Overview page. You can link Azure Boards work items ...About pull requests · Review pull requests · Complete the PR · Microsoft Ignite
  51. [51]
    Azure Pipelines Agents - Microsoft Learn
    Sep 11, 2025 · Learn how you can build code and deploy software by using agents in Azure Pipelines.Self-hosted Windows agents · Self-hosted Linux agents · Microsoft-hosted agents
  52. [52]
    YAML schema reference for Azure Pipelines - Microsoft Learn
    The YAML schema reference for Azure Pipelines is a detailed reference for YAML pipelines that lists all supported YAML syntax and their available options.Pipeline definition · Resources.pipelines.pipeline · Jobs definition · Trigger definition
  53. [53]
    Jobs in Azure Pipelines - Microsoft Learn
    Jun 6, 2025 · The matrix strategy enables a job to be dispatched multiple times, with different variable sets. The maxParallel tag restricts the amount of ...Define container jobs · Deployment jobs · Add stages, dependencies...
  54. [54]
    jobs.job.strategy definition - Azure Pipelines - Microsoft Learn
    The parallel job strategy is useful for slicing up a large test matrix. The Visual Studio Test task understands how to divide the test load across the number of ...Implementations · Remarks
  55. [55]
    Azure Pipelines
    Build and deploy faster with Azure Pipelines. Get cloud-hosted pipelines for Linux, macOS, and Windows. Build web, desktop, and mobile applications.
  56. [56]
    Deployment jobs - Azure Pipelines | Microsoft Learn
    Jul 17, 2025 · A deployment job is a collection of steps that are run sequentially against the environment. A deployment job and a traditional job can exist in the same stage.Missing: integrations | Show results with:integrations
  57. [57]
    Understand release gates, checks, and approvals - Azure Pipelines
    Mar 25, 2024 · By using gates, approvals, and manual intervention you can take full control of your releases to meet a wide range of deployment requirements.Microsoft Ignite · Deployment gates concepts · Define approvals and checks
  58. [58]
    Deployment gates concepts - Azure Pipelines | Microsoft Learn
    May 20, 2025 · Gates work with approvals to ensure that the right stakeholders approve the release and the release meets the necessary quality and compliance ...
  59. [59]
    Manage variable groups - Azure Pipelines - Microsoft Learn
    Jul 15, 2025 · This article explains how to create and use variable groups in Azure Pipelines. Variable groups store values and secrets that you can pass into a YAML pipeline.
  60. [60]
    Service connections - Azure Pipelines | Microsoft Learn
    Nov 3, 2025 · Learn how to manage Azure Pipelines service connections and get a reference to service connection types.
  61. [61]
    Announcing Azure Pipelines with unlimited CI/CD minutes for open ...
    Sep 10, 2018 · Our free offer for private projects includes a cloud-hosted job with 1,800 minutes of CI/CD a month or you can run unlimited minutes of CI/CD on ...Missing: enterprise limits
  62. [62]
    What is Azure Artifacts? - Azure Artifacts | Microsoft Learn
    Sep 22, 2025 · Azure Artifacts provides 2 GiB of free storage for each organization. This free tier is designed to help you evaluate if Azure Artifacts fits your workflow.Missing: date | Show results with:date
  63. [63]
    What are Azure Artifacts feeds? - Azure Artifacts
    ### Summary of Azure Artifacts Feeds
  64. [64]
    What are upstream sources? - Azure Artifacts - Microsoft Learn
    Sep 29, 2025 · Package versions are immutable. Saved packages remain in the feed even if the upstream source is disabled or removed. Upstream sources ...Missing: scanning | Show results with:scanning
  65. [65]
    Publish npm packages with Azure Pipelines - Microsoft Learn
    Jun 23, 2025 · This article will guide you through publishing your npm packages to internal and external feeds using YAML and Classic pipelines.Missing: integration | Show results with:integration<|separator|>
  66. [66]
    Debug with symbols in Visual Studio - Azure Artifacts | Microsoft Learn
    Aug 15, 2025 · From Visual Studio, select Tools > Options > Debugging. Select Symbols from the list, and then select the + sign to add a new Azure DevOps ...Add Azure Artifacts symbol... · Debug optimized modules
  67. [67]
    Publish symbols for debugging - Azure Pipelines - Microsoft Learn
    May 28, 2025 · With Azure Pipelines, you can publish your symbols to Azure Artifacts symbol server using the Index sources and publish symbols task.
  68. [68]
    Configure the Microsoft Security DevOps Azure DevOps extension
    Nov 5, 2025 · Microsoft Security DevOps is a command-line application that integrates static analysis into your development lifecycle.
  69. [69]
    Enhance project security with npm audit - Azure Artifacts
    Feb 8, 2024 · The npm audit command performs a thorough scan of your project, identifying potential security vulnerabilities and generating a detailed report ...Missing: integration | Show results with:integration
  70. [70]
    Build secure applications with Azure DevOps - Microsoft Learn
    Jul 16, 2025 · Learn how to build secure, scalable applications that integrate with Azure DevOps using modern authentication and best practices.Why integrate with Azure... · Getting started: Choose your...
  71. [71]
    Deploy to Azure services - Azure Pipelines | Microsoft Learn
    Jul 15, 2024 · Azure Pipelines combines continuous integration (CI) and continuous delivery (CD) to test and build your code and ship it to any target.
  72. [72]
    Connect organization to Microsoft Entra ID - Azure DevOps Services
    Jan 8, 2025 · This article shows how to connect your Azure DevOps organization to Microsoft Entra ID. You can sign in with the same credentials that you use with Microsoft ...Prerequisites · Connect your organization to...
  73. [73]
    Work item integration with Application Insights - Azure Monitor
    Nov 5, 2025 · Work item integration lets you create issues, bugs, or tasks in GitHub or Azure DevOps directly from Application Insights experiences.Permissions · Create and configure a work...
  74. [74]
    GitHub integration overview - Azure DevOps | Microsoft Learn
    Jul 17, 2025 · Azure Boards and Azure Pipelines offer multiple integration points with GitHub and GitHub Enterprise. These integrations enable seamless collaboration.
  75. [75]
    Build GitHub repositories - Azure Pipelines | Microsoft Learn
    Dec 11, 2024 · Azure Pipelines can automatically build and validate every pull request and commit to your GitHub repository.
  76. [76]
    Azure Boards Integration With GitHub - Microsoft Learn
    Aug 7, 2025 · Take advantage of the integration between GitHub and Azure Boards, manage code in GitHub and link to GitHub commits, pull requests, ...Install the Azure Boards App... · Microsoft Ignite · ConnectMissing: date | Show results with:date
  77. [77]
    Azure DevOps integration with Microsoft Teams
    Oct 21, 2025 · This article describes how you can integrate your Azure DevOps project activities directly into your Microsoft Teams channels.<|control11|><|separator|>
  78. [78]
    About Power BI integration - Azure DevOps - Microsoft Learn
    Mar 25, 2025 · Learn about how to access Analytics for Azure DevOps and the different integration options you can use to connect to Power BI.Microsoft Ignite · Sample reports · Requirements tracking
  79. [79]
    Tools and Clients that Connect to Azure DevOps - Microsoft Learn
    Jul 16, 2025 · Review tools that support connecting to Azure DevOps, including browser and command-line tools, tools for developers and Office integration, ...Missing: 2021 | Show results with:2021
  80. [80]
    Connect hybrid machines to Azure at scale - Microsoft Learn
    Oct 16, 2025 · In this article, you learn how to connect machines to Azure using Azure Arc-enabled servers using a service principal.Automatic connection for SQL... · Create a service principal for...
  81. [81]
    Manage and Deploy Kubernetes in Azure Arc - Microsoft Learn
    Learn how Azure Arc extends Kubernetes cluster management and configuration across customer data centers, edge locations, and multiple cloud environments.Cluster Registration · Azure Arc Agents For... · Use Azure Policy To Enable...
  82. [82]
    Extensions overview - Azure DevOps | Microsoft Learn
    Jul 17, 2025 · Extensions are add-ons that you can use to customize and extend your experience with Azure DevOps. They're written using standard technologies such as HTML, ...<|control11|><|separator|>
  83. [83]
    Extensions for Azure DevOps - Visual Studio Marketplace
    One place for all extensions for Visual Studio, Azure DevOps Services, Azure DevOps Server and Visual Studio Code. Discover and install extensions and ...Missing: categories | Show results with:categories
  84. [84]
    Extension Manifest Reference - Azure DevOps | Microsoft Learn
    May 7, 2025 · Every extension has a JSON manifest file that defines basic information about the extension. The file also defines how it can extend and enhance the experience.
  85. [85]
    Extensibility Points - Azure DevOps - Microsoft Learn
    Oct 3, 2025 · Browse through the places where your extension can extend Azure DevOps capabilities.
  86. [86]
    Add a Custom Build or Release Task in an Extension - Azure DevOps
    Aug 5, 2025 · This guide walks you through creating, testing, and publishing custom build or release tasks as Azure DevOps extensions. Custom pipeline tasks ...
  87. [87]
    Infrastructure-as-Code Scanning Tasks Extension
    Sep 8, 2025 · An extension that contributes custom tasks to install the following infrastructure-as-code scanning tools, analyze an infrastructure-as-code repository with ...
  88. [88]
    Jenkins Integration - Visual Studio Marketplace
    Extension for Azure DevOps - Jenkins is an award-winning, cross-platform, continuous integration and continuous delivery application that increases your ...
  89. [89]
    Azure DevOps Extension | SonarQube Server - Sonar Documentation
    Oct 13, 2025 · The Azure DevOps extension for SonarQube Server makes it easy to integrate analysis into your Azure build pipeline. The extension allows the ...<|separator|>
  90. [90]
    Terraform - Visual Studio Marketplace
    May 27, 2025 · Extension for Azure DevOps - Install terraform and run terraform commands to manage resources on Azure, AWS, GCP and OCI.
  91. [91]
    Create a service hook for Azure DevOps with Slack - Microsoft Learn
    Jul 15, 2025 · In this article, learn how to post messages to Slack in response to events in your Azure DevOps organization, such as completed builds, code changes, pull ...Prerequisites · Create a custom app in Slack
  92. [92]
    Azure Pipelines | Slack Marketplace
    Azure Pipelines enables you to continuously build, test, and deploy to any platform or cloud. It has native container support, flexible workflows, ...
  93. [93]
    Install extensions - Azure DevOps | Microsoft Learn
    Install, assign, disable, and uninstall extensions, which add new features and capabilities for Azure DevOps. For more information about extensions, see the ...Prerequisites · Install an extension
  94. [94]
    Package, publish extensions - Azure DevOps - Microsoft Learn
    Jul 17, 2025 · An overview of how to package, publish, unpublish, publicize, and share an extension for Azure DevOps.
  95. [95]
    Update - REST API (Azure DevOps Extension Management)
    Learn more about Extension Management service - Update an installed extension. Typically this API is used to enable or disable an extension.
  96. [96]
    microsoft/azure-pipelines-terraform - GitHub
    The goal of this extension is to guide the user in the process of using Terraform to deploy infrastructure within Azure, Amazon Web Services(AWS) and Google ...
  97. [97]
    Make your Azure DevOps secure - Microsoft Learn
    Oct 16, 2025 · This article provides an overview of necessary security-related configurations to protect your Azure DevOps environment against threats and vulnerabilities.Protect your network and data · Implement Zero Trust
  98. [98]
    About permissions and security groups - Azure DevOps
    Jul 17, 2025 · In this article, learn about access levels and permissions via inheritance, security groups, roles, and more in Azure DevOps.
  99. [99]
    Security groups, service accounts, and permissions reference
    Jul 17, 2025 · This article provides a comprehensive reference for each built-in user, group, and permission. For a quick reference to default assignments, see Default ...
  100. [100]
  101. [101]
    Link a variable group to secrets in Azure Key Vault - Microsoft Learn
    Sep 10, 2025 · In your Azure DevOps project, select Pipelines > Library > + Variable group. · On the Variable groups page, enter a name and optional description ...
  102. [102]
    Secrets in Azure Pipelines - Microsoft Learn
    Sep 11, 2025 · It's best to securely manage secret variables in Azure Key Vault. You can also set secret variables in the pipeline definition UI or in a ...
  103. [103]
    Set up dependency scanning - Azure Repos - Microsoft Learn
    Feb 20, 2025 · Dependency scanning generates an alert for any open-source component, direct or transitive, found to be vulnerable that your code depends upon.Prerequisites · About dependency scanningMissing: integration | Show results with:integration
  104. [104]
    Data protection overview - Azure DevOps Services - Microsoft Learn
    Jun 20, 2025 · Azure DevOps uses Azure Storage as the primary repository for service metadata and customer data. Depending on the type of data and the storage ...
  105. [105]
    ISO/IEC 27001:2022 - Azure Compliance - Microsoft Learn
    May 26, 2023 · The Azure DevOps ISO/IEC 27001 certificate is available separately from the Service Trust Portal ISO reports section. Frequently asked questions.ISO 27001:2013 · Azure Policy · Microsoft Ignite · ISOIEC pageMissing: HIPAA FedRAMP
  106. [106]
    ISO/IEC 27018:2019 - Azure Compliance - Microsoft Learn
    Apr 4, 2023 · The Azure DevOps ISO/IEC 27018 certificate is available separately from the Service Trust Portal ISO reports section. Frequently asked questions.Iso/iec 27018:2019 Overview · Azure And Iso/iec 27018 · Frequently Asked Questions
  107. [107]
  108. [108]
    HIPAA - Azure Compliance | Microsoft Learn
    Apr 5, 2023 · Azure has enabled the physical, technical, and administrative safeguards required by HIPAA and the HITECH Act inside the in-scope Azure services.Hipaa Overview · Azure And Hipaa · Frequently Asked QuestionsMissing: SOC | Show results with:SOC
  109. [109]
  110. [110]
    What is the EU Data Boundary? - Microsoft Privacy
    The EU Data Boundary is a geographically defined boundary within which Microsoft has committed to store and process Customer Data and personal data.Missing: 2023 | Show results with:2023
  111. [111]
    About access levels - Azure DevOps | Microsoft Learn
    Supported access levels · Basic: Provides access to most features. · Basic + Test Plans: Provides access to all features included in Basic and Azure Test Plans.Get started as a Stakeholder · Add users to an organization
  112. [112]
    Visual Studio Pricing: Compare Subscription Plans & Costs
    ### Summary of Azure DevOps Access in Visual Studio Subscriptions
  113. [113]
    Azure DevOps Server Pricing
    Azure DevOps Server can be priced at $45/user/month (Visual Studio Professional) or $250/user/month (Visual Studio Enterprise) through Azure, or $6/user/month ...Azure DevOps Services · Pricing for Azure DevOps · DevOps
  114. [114]
    Billing overview - Azure DevOps | Microsoft Learn
    Jul 17, 2025 · Azure Boards: Work item tracking and boards; Azure Repos: Unlimited private Git repos; Azure Artifacts: Two GiB free per organization. All ...