You’re not doing anything wrong – this dialog is actually telling you the fix, the problem is just that the doc links behind it have recently moved (hence the 404s).

What’s happening here:

• Lakeflow Connect created a set of SQL Server utility stored procedures in your source DB (v12demo), e.g.
  lakeflowFixPermissions, lakeflowSetupChangeTracking, lakeflowSetupChangeDataCapture, lakeflowDetectPlatform, lakeflowUtilityVersion_1_1.

• The ingestion user svc_databricks doesn’t have EXECUTE permission on those procedures.

• The validation step picks that up and generates the “fix script” you see in the screenshot.

So the fix is simply to run that script in the source SQL database, as a user with db_owner (or equivalent) privileges.

Sharing a likely doc that should help: https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/sql-server-utility

@Advika Thank you. My reason for this post was to alert the SQL server ingestion team to this bug in the interface. I will file a report about this (didn't know I could do that) and a few other issues with the feature that I've found recently.