Summary

Some Jira Align (JA) instances may be connected to one or more Azure DevOps (ADO) instances and one or more Jira instances (using relevant Connectors) simultaneously. This article covers limitations on such a configuration

Solution

A JA instance can support both ADO and Jira connectors working at the same time with the limitation that each connector must use different JA Programs

• Once a JA Program has been used by a connector (either Jira or ADO) then that Program will be greyed-out (not selectable) when attempting to use the same Program in the configuration of any other connectors
• There is no restriction on Portfolios being used, meaning the separate Programs can be in the same Portfolio or different Portfolios (with the choice possibly depending on if there is a requirement to span between the Programs with Portfolio Epics or Capabilities) 
• Work Items (Stories, Features etc)  that were integrated to Jira Align using different connectors cannot be handled in the same JA Programs

Workaround:

If there is a requirement to integrate ADO work items into the same JA Program as Jira work items, then consider integrating ADO with Jira and not using the ADO Connector. The same Jira Connector can then be used to integrate the Jira Projects and the ADO data (that is now in a Jira Project) into Jira Align using just the one Jira Connector. A solution using this configuration is discussed in this community article:

Need Jira and ADO in one Team-of-Teams / Program?