Azure DevOps vs Github Enterprise for Copilot

[zaffaste]

Hello everyone and thanks in advance for your help,
we currently use Azure DevOps with git code repository fully integrated into Visual Studio and Visual Studio Code. Now we want to add the new Github Copilot functionality and as far as I know we have to pay for a Github enterprise subscription (whose features, as far as I know, are completely covered by Azure DevOps) and then we have to join the waitlist before paying to use Github co-pilot. Are these considerations correct?
If my considerations above are correct, what might be the features we would have with Github Enterprise that we didn't actually have with Azure DevOps?

Thank you so much,
Stefano

[DarrenChochian]

To use GitHub Copilot, you don't need a separate GitHub Enterprise subscription; it's included in GitHub Team or GitHub Enterprise Cloud subscriptions. GitHub Enterprise offers additional enterprise-specific features, but Azure DevOps already covers most development lifecycle needs. To get GitHub Copilot, make sure you have a GitHub Team or GitHub Enterprise Cloud subscription, and there's no need to join a separate waitlist, it's available once you have the right subscription.

[DonShrout]

@DarrenChochian Our company also has our entire codebase in Azure DevOps git repositorys. If we want to use GitHub Copilot Enterprise, we will have to purchase GitHub Enterprise Cloud subscriptions. Will that give Copilot access to our git repositories in Azure DevOps?

[DuckScapePhilip]

This is also a concern of mine. Is there a way to pay for GitHub CoPilot Enterprise and have it access our code base and wiki inside of Azure DevOps?