[FND-2245] Add ADO integration to tiering documentation

content/en/Platform Deep Dive/Credits/ptaas-tiers.md

@@ -31,7 +31,7 @@ The availability of some features in the Cobalt platform depends on the {{% ptaa
 | Start pentest within | 3 business days | 2 business days | 1 business day | The pentest start time is based on your PtaaS tier and depends on when you've submitted all the required information for your pentest. We move the pentest to [Planned](/penteststates/), allocate pentesters—and they start testing your asset within the following timeframes:<ul><li>Standard tier: 3 business days</li><li>Premium tier: 2 business days</li><li>Enterprise tier: 1 business day</li></ul> |
 | Free retesting duration | 6 months | 12 months | 12 months | [Free retesting duration](/platform-deep-dive/pentests/findings/remediate-findings/#free-retesting-duration) for your pentest [findings](/platform-deep-dive/pentests/findings/) depends on your PtaaS tier:<ul><li>Standard tier: 6 months</li><li>Premium and Enterprise tiers: 12 months</li></ul>The timeline for retesting starts after your pentest end date within an active contract. Mark your findings as Ready for Retest at least 10 days before your contract ends. |
 | Customer Success Team | Pool | Named CSM | Named CSM | Our Customer Success Team includes a Customer Success Manager (CSM) and a Pentest Architect. We'll onboard you to the Cobalt platform and support you during the pentest process.<ul><li>Standard tier: A pool of CSMs provide support through email when you need help.</li><li>Premium and Enterprise tiers: You get a named CSM.</li></ul> |
-| Native integrations (Jira, GitHub) | — | ✓ | ✓ | <ul><li>[Jira](/integrations/jira/): Synchronize Cobalt findings with Jira tickets bi-directionally (Cloud and Server).</li><li>[GitHub](/integrations/github/): Push Cobalt findings as issues to GitHub (Cloud only).</li></ul> |
+| Native integrations (Jira, GitHub, Azure DevOps) | — | ✓ | ✓ | <ul><li>[Jira](/integrations/jira/): Synchronize Cobalt findings with Jira tickets bi-directionally (Cloud and Server).</li><li>[GitHub](/integrations/github/): Push Cobalt findings as issues to GitHub (Cloud only).</li><li>[Azure DevOps](/integrations/azure-devops/): Push Cobalt findings as work items to Azure DevOps Boards.</li></ul> |
 | Customizable reports | — | ✓ | ✓ | [Customize](/platform-deep-dive/pentests/reports/customize-report/) the contents of pentest reports. |
 | Onboarding | — | Security + 1 dev team | All teams | Onboarding includes CSM-led calls in which your team and Cobalt align on the primary points of contact, success plans, and an inventory of your assets. In addition, a Cobalt Sales Engineer provides a comprehensive demo of the Cobalt platform, along with technical guidance on how to set up your first pentest.<ul><li>Premium tier: onboarding for up to 2 teams</li><li>Enterprise tier: onboarding for all teams</li></ul> |
 | Strategic planning | — | Annual | Quarterly |  We help you build and plan a test strategy for your assets on a regular basis:<ul><li>Premium tier: annually</li><li>Enterprise tier: quarterly</li></ul>Your CSM arranges a meeting to better understand your security needs and asset criticality and draft an appropriate pentest schedule. |