By default, Azure Devops (ADO) usually works like all GitClear git integrations: you log in to your ADO account from the GitClear "Sign Up" page, then you are redirected to a page that lists all of your company's organizations, and the repos in each organization that can be selected for processing.
As the most "enterprise-y" git provider supported by GitClear, Azure offers a plethora of configuration options, some of which can inhibit your ability to connect to your Azure repos. This page collects all known settings that may need to be changed/enabled in order to successfully connect GitClear to Azure Devops repos.
linkEnsuring Oauth login enabled
Industry-standard Oauth login is used to connect GitClear to an Azure Devops account. Most customers find that their organization automatically allows login via Oauth, but if you are not provided a list of repos to import after logging in via Azure, one debugging step we recommend is to confirm that third-party Oauth access was not disabled in your organization.
You can check your organization's setting by visiting the "Organization Settings" after logging in, then clicking "Policies" tab under "Security."
