Hi,

We are using an Azure SQL DB which which is geo replicated to meet our DR requirements. As part of this configuration Azure adds two additional schemas to the DB (DSS and TaskHosting) presumably to keep track of the internal replication state.
However this does cause the Octopus Integrity check to fail as it is not expecting to find these tables on the DB.

I have also noticed that during upgrades (from 3.X to 4.x) it tries and fails to remove these tables which isn't causing any issues we can see at the moment but could cause issues down the line if the update does actually manage to modify one of these tables. Also it's not great seeing lots of red errors when performing updates. :)

Would it be possible for Octopus to limit this check to just the dbo schema or some way of white-listing known differences on a DB to the expected Octopus schema.

See https://help.octopusdeploy.com/discussions/problems/67806-check-system-integrity-fails-with-azure-sql-replicated-dbs for further details.