我们最终做的是：
在构建端，我们生成一个幂等数据库创建脚本：

dotnet ef migrations script --idempotent --output migrations.sql  --context  ApplicationContext

其中ApplicationContext是EF上下文的名称，migrations.sql是sql脚本文件名。
然后在部署端，我们有一个小的powershell脚本，它可以有效地运行migrations.sql脚本

param(
[Parameter(Mandatory)]
[string]$server,
[Parameter(Mandatory)]
[string]$dbname,
[Parameter(Mandatory)]
[string]$dbadmin,
[Parameter(Mandatory)]
[string]$dbpassword,
[Parameter(Mandatory)]
[string]$migrationPath
)

function Deploy-Migrations ($migrationPath,$DBSettings)
{
   #Setting up database connection
   $connection = New-Object System.Data.SqlClient.SqlConnection
   $connection.ConnectionString = [string]::Format("Data Source=tcp:{0}.database.windows.net,1433;Initial Catalog={1};User Id={2}@{0};Password={3};MultipleActiveResultSets=True", $DBsettings['sqlServerName'], $DBsettings['databasename'],$DBsettings['adminAccount'], $DBsettings['adminPassword']) 

    try
    {
        $connection.Open();

         $SqlCmd = New-Object System.Data.SqlClient.SqlCommand
         $SqlCmd.Connection = $connection
         $query = Get-Content $migrationPath
         $sqlCmd.CommandText = $query.Replace("GO","") # This is required to prevent "syntax" complaints
         $sqlCmd.ExecuteNonQuery()

         Write-Host "Migration Deployed" 
    }
    Catch
    {

        Write-Error "oops ... PAnic ... $($_.Exception.Message) on $($_.Exception.ItemName)"
        break
    }
    Finally
    {
        $connection.Close()
    }  
 }

$DBSettings = @{"sqlServerName"=$server; "databasename"=$dbname;    "adminAccount"=$dbadmin; "adminPassword"=$dbpassword }

Deploy-Migrations $migrationPath $DBSettings

从.Net 6.0（可能还有.Net Core 3.x）开始...
您可以让ARM模板中的deployScript为您执行迁移。下面是设计为Azure Marketplace部署的an example。该示例假定您已预生成script.sql，该script.sql保存在Marketplace应用部署“bundle”的artifacts文件夹中。然后，deployScript只需运行一个Invoke-Sqlcmd来运行script.sql文件。