Migration from devops onprem to azure devops onclound

[markchan-langan]

Can this tool do the from migration from onprem to cloud? I tried using the MS migration tool and its giving me an error that i can't connect to the sql vm, reason is we have a large tfs db and the recommended approach was to restore data to the azure sql vm, then on the import.json replace the connectionstring to it.. i did that and still its saying cant connect, even use the external ip of the sql vm still no luck, it is also saying that white list a certain ip for the datamigration tool services and according to our network team they already whitelisted it.. i know my user and pass is correct on the connectionstring because i tried connecting to the azure sql vmu using ssms and it works.. so im stuck now.. maybe this tool can do the same and i can do the migration using this tool instead. Any response will be highly appreciated.

[MrHinsh]

@markchan-langan, yes, this tool can do that, but the correct way is to use the Microsoft Azure DevOps Data Import Tool. This tool is a tool of last resort and does not do what the import tool does.

What you are experiancing is a configuration issue of either the config, the connections string, or the credentials.

I offer Azure DevOps Migration Services and can help out if you need.

[markchan-langan]

seems like the configuration on the azure sql vm, because i tried telnetting to it and i cant connect to it.. credentials are correct and according to network they have already implemented service tags on the azure sql vm and white listed all required ips from the devops server on prem.

[MrHinsh]

Did you use a standard Azure SQL VM image, or was it configured by one of your corporate DBAs?

I recommend avoiding involvement from corporate DBAs in TFS or Azure DevOps data environments. They often apply colloquial, company-specific enterprise database conventions rather than following Microsoft’s documented standards for Azure DevOps and TFS data tiers, which can lead to instability and support issues.

The environment must be configured exclusively according to Microsoft’s documentation for Azure DevOps Data Import and Azure DevOps Data Tier. Deviations are not supported and introduce unnecessary risk.

[markchan-langan]

they are the network team, i believe they just use the standard azure sql vm image, we dont have a resident dba and normally it just me as the senior dev to do thing like like setting up stuff. I got the vm with sql server on it then i restored tfs_configuration and tfs_defaultcollection and followed the steps on the migration tool on what to do with the database. We have over 200gb of data so i did this, then i created a user account with admin privileged and owner access which i know is really working cause i use my ssms on my dev maching to connect to it.

i could still verify with the network team if they did use the standard azure sql vm image

[markchan-langan]

Now i remember, i did replace the sql server on it, because i cant connect to it and the network persons who created that image didnt know what to since they dont do stuff like that.. might that be the cause of it? i mean i cant connect to the db using ssms even when im inside the vm so i decided to replace the whole sql server