Skip to content

Add Azure DevOps (ADO) Integration - #7

Open
chethanshere wants to merge 10 commits into
aws-samples:mainfrom
chethanshere:feature/ado-integration
Open

Add Azure DevOps (ADO) Integration#7
chethanshere wants to merge 10 commits into
aws-samples:mainfrom
chethanshere:feature/ado-integration

Conversation

@chethanshere

Copy link
Copy Markdown

Adds Azure DevOps integration to AWS HealthCompass, enabling automated creation of ADO work items from AWS Health planned lifecycle events. This opens access to another widely-used ITSM tool for AWS customers.

What's included

  • HealthEventProcessorLambda.py — processes incoming Health events with Account, Service, and Tag routing models
  • HealthEventADOIntegration.py — creates/updates ADO work items via the ADO REST API
  • cloudformation.yaml — full CloudFormation template for deployment
  • README-ado.md — deployment and configuration documentation
  • TESTING.md — testing guide

Key features

  • Three routing models: Account-based, Service-based, Tag-based
  • Two-level work item hierarchy (Feature + Child Task)
  • Intelligent updates via comments on existing work items
  • Auto-activate and sprint alignment capabilities
  • Custom field support for ADO process templates
  • Cross-account tag discovery (Tag model)

Validation

This integration has been implemented and tested as a Proof of Concept, validated without errors.

Testing

See azuredevops/TESTING.md for testing instructions.

chethazn added 10 commits March 23, 2026 22:10
- Add ADOCustomFields CloudFormation parameter (optional, JSON-encoded)
- Parse ADO_CUSTOM_FIELDS env var in ADO Integration Lambda and append
  custom fields to Feature work item patch
- Update README-ado.md: optional params table, Feature creation example,
  troubleshooting section
- Update TESTING.md: optional params block, troubleshooting checklist
…ED status

Adds opt-in EnableAutoResolve parameter that automatically transitions
a Feature to Resolved state when all affected resources under it have
been confirmed RESOLVED by AWS Health. Resolves take precedence over
auto-activate to prevent conflicting state transitions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant