Legacy Workflows
This section provides information about legacy workflows that are no longer actively maintained but may still be in use in some projects. These workflows are part of the transition to a monorepo architecture and are provided for reference only.
Deprecated Content **It is strongly recommended to migrate to the
new workflows as soon as possible.** Legacy workflows will be removed in a future release and do not receive security updates or bug fixes. :::
Migration Guide
Quick Migration Steps
- Audit current workflows - Review which legacy workflows your project uses
- Choose replacement workflows - Select modern equivalents from the pipelines section
- Update configuration - Modify workflow files to use new syntax and features
- Test thoroughly - Ensure new workflows work correctly in staging
- Deploy to production - Replace legacy workflows with modern versions
Legacy → Modern Workflow Mapping
| Legacy Workflow | Modern Replacement | Benefits |
|---|---|---|
| Legacy Code Review | Code Review | Faster execution, better security scanning |
| Legacy Deploy Pipelines | App Service Deploy | Zero-downtime deployment, better rollback |
| Legacy Publish SDK | Docker Image Build | Multi-platform support, optimized caching |
Legacy Workflows
Code Quality (Deprecated)
- Legacy Code Review - Original code review
workflow for Node.js projects
- ⚠️ Use instead: Modern Code Review
- Migration effort: Low - mostly configuration changes
Deployment (Deprecated)
- Legacy Deploy Pipelines - Original
Azure deployment workflows
- ⚠️ Use instead: App Service Deploy or Container App Deploy
- Migration effort: Medium - may require application changes
Package Publishing (Deprecated)
- Legacy Publish SDK - Original package
publishing workflow
- ⚠️ Use instead: Docker Image Build
- Migration effort: Low - mainly configuration updates
Support Timeline
| Status | Description | End Date |
|---|---|---|
| 🔴 Deprecated | No new features, critical bugs only | Current |
| 🚫 End of Support | No updates, removal warnings | Q2 2024 |
| ❌ Removal | Workflows deleted from repository | Q4 2024 |
Migration Support
Getting Help
The DX team provides migration support:
- Migration checklist - Step-by-step guidance
- Direct support - Available for teams migrating from legacy workflows
- Documentation - Comprehensive guides for each modern workflow
Common Migration Issues
Authentication Changes
- Legacy workflows use service principals
- Modern workflows use OIDC authentication
- Learn about Azure Login setup
Configuration Format
- Legacy workflows use different input parameters
- Modern workflows have simplified configuration
- Check individual workflow documentation for specifics
Feature Gaps
- Some legacy features may not have direct equivalents
- Contact the DX team if you need specific functionality
Why Migrate?
Security Improvements
- OIDC Authentication - More secure than service principals
- Updated Dependencies - Latest versions with security patches
- Vulnerability Scanning - Built-in security checks
Performance Benefits
- Faster Execution - Optimized for speed and reliability
- Better Caching - Reduced build times
- Parallel Execution - Multiple jobs run simultaneously
Feature Enhancements
- Zero-Downtime Deployment - Rolling updates with health checks
- Advanced Rollback - Automatic rollback on failure
- Better Observability - Enhanced logging and monitoring
Migration Priority Focus on migrating workflows in this order:
- Security-related workflows (authentication, scanning)
- Production deployment workflows (high-risk if they fail)
- Development workflows (code review, testing) :::
Getting Started with Migration
- Review current pipelines documentation to understand modern alternatives
- Open a migration issue to get personalized guidance or to ask questions and share experiences