How can you move Azure Devops organisations to a different tenancy - azure-devops

We currently have an Azure organisation, containing several projects and related boards etc, linked to a specific Azure Active directory and tenant id.
Does anyone know if there is a way I can move the organisation and all child objects to a new tenancy/Azure Active directory?
We need to do this as we wish to decommission the original active directory.
I've googled for solutions and can see that other people were waiting for Microsoft to provide a solution.

I've done the same using the following instructions: https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/change-azure-ad-connection?view=azure-devops
Trick here is not to use a Work or School Account.

Related

Ways to provide read only views of subsets of DevOps work items

I use Azure DevOps to track work items and bugs for a project. I'd like to grant certain people external to the project a read-only view of work items that are related to them (eg. tagged Person X), but without having to grant them access to DevOps. I have been toying with the idea of setting up a flow in Power Apps to continuously update a shared excel spreadsheet based on work items in DevOps, but I fear I might be missing easier/better options. How would you provide a limited read-only view of a backlog to externals?
I'd like to grant certain people external to the project a read-only
view of work items that are related to them (eg. tagged Person X), but
without having to grant them access to DevOps.
For this issue , I am afraid that this is unachievable in azure devops. At present, there is no such permission setting in azure devops to restrict external people can only read work items with specified tag.
You could add your request for this feature on our UserVoice site , which is our main forum for product suggestions.After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it. Thank you for helping us build a better Azure DevOps.

Is it possible to move project collection between two organizations?

We are currently having a project collection with backlogs, sprints, etc. in an Azure DevOps account. There is another organization with completely different credentials to log in that we'd like to transfer this project collection to the other organization. I could not find any features or approaches to complete this transfer. Is there a way to be able to achieve this goal?
There is no way to migrate a project between organisations. This may become possible in the future, but the feature suggestion is 8 years old and hasn't seen progress, yet.
However, depending on your requirements, you might be able to create your own tools/scripts to "re-create" your project in the new organisation using the REST API.

Is there a way to create an organization dashboard in Azure DevOps?

Our team is currently using DevOps and are very pleased with how everything is working. We've setup Dashboards in each project that tracks work items and sprints and would like to do the same at the Organization Level. Is there a way to create a master overview of multiple projects in an organization?
Unfortunately we cannot create an organization level dashboard, it's not supported.
We can only create the Team Project level dashboards for teams, please see Add and manage dashboards for details.
However there's already a user voice submitted here to suggest the feature and it's in planned, but based on the response seems no plans to store a dashboard on organization overview. So you can vote it up and add your comments on the existing user voice or submit a new one to suggest the feature...
In our VSTS Feature
Timeline(https://learn.microsoft.com/en-us/vsts/release-notes/), you
see a feature called “Dashboards – Create dashboard separate from a
team” under “Reporting”
This feature will allow you to create a Dashboard that has no
association with the team. This means you don’t need to create a team,
to make a Dashboard. You can create any number of these Dashboards and
share them with who you want.
However, Dashboards will still be stored with a Team Project. So to
address your scenario (cross-team-project Dashboard), you’ll just have
to pick a team project to store the dashboard.
We don’t have immediate plans to store a dashboard outside a team
project.
Our team was dealing with the same problem as yours, and we decided to develop our own dashboard solution at the end.
After using it as an internal tool for several months, we recently made it available as a SaaS.
You may check it out on meercode.io for more information.
Your feedback will be greatly appreciated.
Behind the dashboard widgets are queries, and it is possible to execute those queries across multiple projects.
When you open the query editor, there is a checkbox:
"Query across projects" checkbox (imgur)
This way we created a project in Devops that only contains a dashboard that shows all work items in any project, assigned to or followed by the current user.
That and some nifty colored tiles =)

Ops Hub User Matching

Can you please tell me where OPSHub Visual Studio Online Migration Utility pulls the user data from when doing a match, both on-prem and online? I am trying to match users for just one project, which has 41 users, however the utility wants me to match 119 users, many of which are not even associated with any project on my on-Prem TFS server. Additionally, where is the online user information pulled from? I have some that are displayed as email address, others seem to be usernames. Obviously I need to straighten this out so I can map to the correct users. Also, some users exist on Prem that will never map to any online user, so how can I get rid of them?
Project Collection Valid Users are pulled from both the end points. This is done to make the user mapping explicit. In some cases, a user might have done some changes in a project but is now no longer a part of the project. If such user is not mapped then, loss of information is observed when such data is migrated.
For users of on-prem who are not going to be in VSTS. You can map them as default to any other user. (Or maybe create a dedicated user for) Basically, all changes done by those users in your on-prem TFS would be shown as done by the user with which they would be mapped.

Move resources from one resource group to another

I was searching the Steps to Move resources from one resource group to another on Azure and found this - saying work in progress to achieve it through Azure portal since May 04, 2015
Just wanted to know if we have any other way (SDKs, Azure Powershell etc) to achieve the same?
Much appreciated if you could share the steps in an eloborated way, so that I think it would useful for the future referrers.
Now you can move resources from one resource group to another in the same or other subscription though there are some restrictions on what all resource types can be moved and what all resource types can be moved across subscription. You can do it through Azure Portal, PowerShell as well as using Azure Resource Manager REST API. Please see this blog post for more details on how to do this: https://azure.microsoft.com/en-in/documentation/articles/resource-group-move-resources/