# Legacy Team Foundation Server Integration Reference **Last reviewed:** September 30, 2026 This page is retained as a legacy reference for teams that still maintain AIQ integrations with Team Foundation Server or Azure DevOps Server-era workflows. ## What changed in this article - Marked TFS integration as legacy because many teams have moved from Team Foundation Server to Azure DevOps Services or newer CI/CD integrations. - Added checks for repository URL, credentials/token handling, branch/path mapping, build triggers, artifact ownership, and migration planning. - Warned against storing passwords in integration configuration and recommended maintained token-based access where supported. ## Validation workflow 1. Confirm whether the environment still uses TFS/Azure DevOps Server or should migrate to a current integration path. 2. Validate repository access, token scope, branch/path settings, and artifact retrieval with a controlled test. 3. Document ownership and migration status so legacy TFS dependencies are not expanded accidentally. **Review note:** This page is now clearly labeled as legacy rather than current default integration guidance. --- Last updated: September 30, 2026 If you have feedback on this topic, contact .