Skip to content
PYD ENTERPRISES
Start free trial

Source control · Ingest and export

PYD ENTERPRISES and Azure DevOps

Scan Azure Repos Git repositories and TFVC snapshots from Azure DevOps Server or Services, run scans from self-hosted pipeline agents, and export specs as pull requests.

Book technical walkthroughAll integrations
Azure DevOps logo

Azure DevOps

Source control

Ingest and export
azure-pipelines.ymlYAML
1stages:
2  - stage: SpecExtraction
3    pool: { name: OnPremAgents }
4    jobs:
5      - job: PYD ENTERPRISESScan
6        container: registry.internal/pyd/cli:2026.11
7        steps:
8          - script: pyd scan --system underwriting --ref $(Build.SourceVersion) --wait
9          - script: pyd diff --against baseline --fail-on new-unresolved

VB6, WebForms and WCF often live here

Microsoft shops that started on Visual SourceSafe and moved to Team Foundation Server tend to hold their VB6 components, classic ASP.NET WebForms applications and WCF services in Azure DevOps Server today, sometimes still in TFVC rather than Git. PYD ENTERPRISES' .NET and VB6 front end reads .vbp, .cls, .bas, .frm, .aspx, .aspx.cs, .svc and web.config files directly, so the job of this integration is simply to get the right snapshot onto the PYD ENTERPRISES volume.

For Git repositories in Azure Repos, PYD ENTERPRISES clones with a personal access token or service account credential that has Code (Read) scope and pins the scan to the commit SHA. For TFVC, PYD ENTERPRISES does not talk to the version control server itself: you check out the path at a known changeset into a working folder (or export it on a build agent), and PYD ENTERPRISES scans that folder with the changeset number recorded as the scan reference.

Pipelines on self-hosted agents

A pipeline stage on a self-hosted agent inside your network can run the PYD ENTERPRISES CLI container, start a scan for the commit or changeset that triggered it, and fail the stage when the diff against the approved baseline contains new unresolved COM references or new rules awaiting review. Microsoft-hosted agents run outside your perimeter and should not be used for scans of source you cannot share.

  • VB6 projects that reference registered COM components resolve against the type libraries you supply; missing ones are listed as unresolved, never inferred.
  • WebForms pages are parsed together with their code-behind so event handlers and ViewState reads map back to the markup controls that raise them.

Exports

Specification bundles go to a separate Azure Repos Git repository as a branch and pull request, where branch policies decide required reviewers. WCF services become OpenAPI 3.1 operations with JSON Schema components derived from their DataContracts, and calculation logic lifted from VB6 modules is exported as DMN 1.5. Each artifact records the commit or changeset it was extracted from.

FAQ

Azure DevOps questions.

Can PYD ENTERPRISES scan TFVC directly?

PYD ENTERPRISES scans a checked-out snapshot of a TFVC path rather than connecting to TFVC itself. Record the changeset number as the scan reference so every artifact points to it.

Do we need the original VB6 IDE or registered COM components?

No IDE is needed. Supplying type libraries for referenced COM components improves resolution; without them, calls are recorded as unresolved external boundaries.

Does this work with Azure DevOps Services as well as Server?

Yes for Git repositories. With Services, scan workers need egress to the clone endpoint through your proxy; analysis still happens entirely inside your environment.

RELATED INTEGRATIONS

GitHub logoGitHubMirror GitHub or GitHub Enterprise Server repositories inside your VPC, scan a pinned commit, and return specifications to a review repository as pull requests.GitLab logoGitLabClone self-managed GitLab projects inside your network, run PYD ENTERPRISES as a CI job on your own runners, and publish specs back as merge requests.Bitbucket logoBitbucketIngest legacy repositories from Bitbucket Data Center or Bitbucket Cloud with read-only credentials, and return specification bundles as pull requests for review.Broadcom Endevor logoBroadcom EndevorIngest exported Endevor element libraries (COBOL, copybooks, JCL, PROCs and BMS maps) with their environment, system, subsystem, type and stage metadata intact.

See the Azure DevOps flow on your own code.

Run PYD ENTERPRISES on 100,000 lines of COBOL or Java in your private VPC and review OpenAPI specs and DMN tables tomorrow.

Start 14-day trialBook technical walkthrough