Unable to authenticate in self-hosted Azure DevOps repo with different domain

Version

2.5.0+d34930736e131ad80e5690e5634ced1808aff3e2

Operating system

Windows

OS version or distribution

Windows 11 Pro

Git hosting provider(s)

Azure DevOps Server (TFS/on-prem)

Other hosting provider

Azure DevOps on dev.{my_domain}.ru:1443

(Azure DevOps only) What format is your remote URL?

None

Can you access the remote repository directly in the browser?

Yes, I can access the repository

Expected behavior

I was expecting whenever I call git fetch\get pull\get pull I would not receive error:

> git fetch
fatal: Authentication failed for 'https://dev.mydomain.ru:1443/org/project/_git/repo/'

Actual behavior

All that was OK yesterday, but smth happened today and so I can't interact with my remote.

I was thinking that the problem was in incorrect provider - it was generic however it is an Azure DevOps.
My remote URL is https://dev.{domain}.ru:1443/{org}/{project}/_git/{repo}/, so I guess GCM can't recognize it.

I was trying to set git config --global credential.https://dev.multisoft.ru:1443.provider azure-repos and try it, but response on EVERY command was:

> git fetch
fatal: Host is not Azure DevOps.
fatal: Host is not Azure DevOps.
Username for 'https://dev.{domain}.ru:1443': {login}
Password for 'https://{login}@dev.{domain}.ru:1443':
fatal: Host is not Azure DevOps.
fatal: Host is not Azure DevOps.

It doesn't matter whether credentials are correct or not - it's still being requested for every command.

Also I'm interested how can I git credential-manager azure-repos bind account for my domain with PAT.

Logs

git credential-manager diagnose

Running diagnostics...

[ OK ] Environment
[ OK ] File system
[ OK ] Networking
[ OK ] Git
[ OK ] Credential storage
[ OK ] Microsoft authentication (AAD/MSA)
[ OK ] GitHub API

Diagnostic summary: 7 passed, 0 skipped, 0 failed.
Log files:
C:\Users*****\gcm-diagnose.log

Caution: Log files may include sensitive information - redact before sharing.

Start by reproducing authentication against the self-hosted Azure DevOps URL shown in the report, including the configured azure-repos provider and the git credential-manager azure-repos bind command. Compare host recognition and credential persistence for the custom domain; done means fetch succeeds without repeated prompts and the credentials are reused.