This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 67%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
We're having intermittent issue with ADO repositories. Sometimes when performing Git operations i.e. fetch, etc, we'll receive 429 errors. After waiting for some time or rerunning the process, it will work okay.
Hello @Durga Reshma Malthi , does this mean that even if we use different token from a different under the same tenant, it still won't work?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 64%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Hi LD Magpantay
Just checking in to see if you had a chance to review the response provided to your question.
Feel free to reach out if you have any further queries.
Hi LD Magpantay
Just checking in to see if you had a chance to review the response provided to your question.
Feel free to reach out if you have any further queries.
Hi LD Magpantay
Even if you're using different personal access tokens (PATs) or service principals under the same Azure AD tenant, the rate limiting is typically scoped at the organization or tenant level, not just per token.
So, using another token under the same tenant won’t bypass throttling if the combined Git traffic from your org is what’s triggering it.
Hope this helps!
Please Let me know if you have any queries.
Hi LD Magpantay
A 429 error from Azure DevOps Git operations means you're hitting a rate limit or throttling by the Azure DevOps service.
This is not necessarily a bug, but Azure DevOps way of protecting service availability when too many requests are made in a short time window.
It resolves after a delay or retry, it's likely a throttling mechanism kicking in to protect the service.
Additional References:
https://developercommunity.visualstudio.com/t/429-error-whoa-thats-a-lot-of-requests/1102240
https://learn.microsoft.com/en-us/azure/devops/repos/git/limits?view=azure-devops
Hope this helps!
Please Let me know if you have any queries.