If your source control repository is cloud-hosted, you can configure an organization to use OAuth authentication instead of personal access tokens to provide access to the repository. Configure OAuth authentication on the Settings page.
If you use a GitHub repository, you must have a GitHub access application installed on your repository that allows IDMC to perform source control operations on the organization's GitHub repository. If you don't have this application installed on your repository, you can install it from the Settings page.
GitHub repositories with more than 500 assets in a single project or folder require that you accept additional permissions to prevent check-in failures. For more information, see the Checking in large repositories in source control Knowledge article.
Note:
Microsoft plans to drop support of Azure DevOps OAuth. If the organization uses Azure DevOps OAuth to access the source control repository, you can change to using Microsoft Entra ID OAuth on the Settings page. This change is permanent. You can't revert to Azure DevOps OAuth after you change to Microsoft Entra ID OAuth.
After you change the organization's repository access to Microsoft Entra ID OAuth, each user needs to re-authenticate to avoid interruption in source control access. To re-authenticate, click the User icon on the toolbar and select Settings. In the Source Code Control Credentials section, click Drop Authentication and then reconfigure OAuth authentication.