Apr 08 2019 09:12 AM
Nov 13 2019 11:11 PM
Nov 13 2019 11:42 PM
Nov 17 2019 06:47 PM
The answer, technically, is that no out-of-box solution exists for archiving (or even doing on-demand backups for that matter) of your ADO Service data. If you're using ADO Server then you have the power to do whatever you want. As the goal, in your case, is to hide older data, however, the answer begs a few questions: (1) what data do you need to keep (2) how are your teams structured, (3) what repos are you using, and (4) how often does the process need to run? Keep in mind, Microsoft's written guidance is to create a single Team Project per business unit, organization with some exceptions (https://docs.microsoft.com/en-us/azure/devops/organizations/projects/about-projects?view=azure-devop... Therefore, a simple answer may be to create a separate Team Project for archiving and move all repos to that project through the use of automation or manually (https://docs.microsoft.com/en-us/azure/devops/repos/git/import-git-repository?view=azure-devops). Our organization? We don't care much about the Work Item history so we grab the data and store it in Azure files once it becomes no longer necessary. There is a User Voice around backups but it doesn't have a lot of traffic. (https://developercommunity.visualstudio.com/content/idea/365441/provide-a-backup-service-for-visual-...)
Nov 18 2019 05:08 AM
Thank you for your answer. I will look into the option you mentioned which does not sound bad for now. Our way of functioning is the creation of a project entry per product, so we do have a lot of projects going on.
Thank you all for your support.
Jan 15 2020 08:49 PM
If you go to
Jul 21 2020 01:42 PM
Any update on this feature? We are growing our adoption of Azure, and have some inactive projects that we would like to hide, but not delete.
Sep 25 2020 01:33 PM
I would also like to know if archiving is possible. For Audit purposes we need to keep the data just not allow everyone to view it.
Oct 01 2020 03:02 AM
Hi @gresdawg ,
Have you considered the following workaround?
1. Create a special identity (e.g. DevOps Archive Admin) in AAD.
2. Modify permissions of those old projects by setting that identity as the only Project Administrator and remove other members and groups. In this way they can become invisible to regular users.
3. In case of an audit, login to AzDO with this identity to show auditors all those "hidden" projects.
I'm curious if you see any issues for using this approach.