This is a consequence of the support for Azure SQL Database - as you can use it as a data tier now, you can also upgrade your existing Team Foundation Server instance to Azure DevOps in a lift and shift fashion.
First of all -- *this works on my machine* (lab) and *I bear no responsibilities* 😁 it is highly experimental and only with Azure DevOps Server 2019 RC1 - although I am sure it is going to be polished in the next releases. Let's review the pre-requisites:
It is likely that you need to remove all the Windows users, and the table and stored procedures used for the scheduled backups. Remember that as of now it is still an experimental process - no support whatsoever for this, especially because you are modifying the database manually!
Once the database are imported (S3 tier or above!) you need to run this query on the Azure DevOps databases:
First of all -- *this works on my machine* (lab) and *I bear no responsibilities* 😁 it is highly experimental and only with Azure DevOps Server 2019 RC1 - although I am sure it is going to be polished in the next releases. Let's review the pre-requisites:
- You need to run domain-joined VM(s)
- The(se) VM(s) must have a Managed Identity in order to access Azure SQL Database
It is likely that you need to remove all the Windows users, and the table and stored procedures used for the scheduled backups. Remember that as of now it is still an experimental process - no support whatsoever for this, especially because you are modifying the database manually!
Once the database are imported (S3 tier or above!) you need to run this query on the Azure DevOps databases:
CREATE USER <vmname> FROM EXTERNAL PROVIDER
ALTER ROLE db_owner ADD MEMBER <vmname>
ALTER USER <vmname> WITH DEFAULT_SCHEMA=dbo
Followed by this query in the master database:
CREATE USER <vmname> FROM EXTERNAL PROVIDER
ALTER ROLE dbmanager ADD MEMBER <vmname>
This is it really - then you can launch your Azure DevOps Server Configuration Wizard and proceed to an upgrade. Yes, even if you already installed Azure DevOps Server! Of course there are changes to perform here, so it makes sense to call it as such: