You have a GitHub Actions workflow that builds and deploys an Azure SQL database. The schema is stored in a GitHub repository as an SDK-style SQL…

The SqlPackage.exe command-line utility includes the DriftReport action specifically for this purpose. This action compares the schema of a registered database against its baseline registration (typically the last deployed .dacpac) and generates an XML report detailing any changes or "drift" that has occurred directly on the production database, outside of the source-controlled deployment process.

B. The DeployReport action generates a report of changes that would be made by a deployment, not a report of drift that has already occurred.

C. The Extract action creates a .dacpac file from a live database. While this .dacpac could be used in a comparison, this action alone does not generate the drift report.

D. The Script action generates a T-SQL deployment script to update a target database. It does not produce a drift report.

1. Microsoft Docs, "SqlPackage DriftReport action". States: "The SqlPackage DriftReport action creates an XML report of the changes that have been made to a registered database since it was last registered."

2. Microsoft Docs, "SqlPackage command-line reference". Provides the syntax and parameters for all actions, clearly distinguishing the purpose of DriftReport from other actions like DeployReport and Script.