Skip to main content


6.3.7 Ensure that the 'contained database authentication' database flag for Cloud SQL on the SQL Server instance is set to 'off' (Automated)

Profile Applicability

• Level 1


It is recommended to set contained database authentication database flag for Cloud SQL on the SQL Server instance is set to off.


A contained database includes all database settings and metadata required to define the database and has no configuration dependencies on the instance of the Database Engine where the database is installed. Users can connect to the database without authenticating a login at the Database Engine level. Isolating the database from the Database Engine makes it possible to easily move the database to another instance of SQL Server. Contained databases have some unique threats that should be understood and mitigated by SQL Server Database Engine administrators. Most of the threats are related to the USER WITH PASSWORD authentication process, which moves the authentication boundary from the Database Engine level to the database level, hence this is recommended to disable this flag. This recommendation is applicable to SQL Server database instances.


When contained database authentication is off (0) for the instance, contained databases cannot be created, or attached to the Database Engine. Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase.Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.


From Console:

  1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting
  2. Select the instance to open its Instance Overview page
  3. Ensure the database flag contained database authentication that has been set is listed under the Database flags section.

From Command Line:

  1. Ensure the below command returns off for every Cloud SQL SQL Server database instance.
gcloud sql instances list --format=json | jq '.settings.databaseFlags[] | select(.name=="contained database authentication")|.value'


From Console:

  1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting
  2. Select the SQL Server instance for which you want to enable to database flag.
  3. Click Edit.
  4. Scroll down to the Flags section.
  5. To set a flag that has not been set on the instance before, click Add item, choose the flag contained database authentication from the drop-down menu, and set its value to off.
  6. Click Save.
  7. Confirm the changes under Flags on the Overview page.

From Command Line:

  1. Configure the contained database authentication database flag for every Cloud SQL SQL Server database instance using the below command:
gcloud sql instances patch <INSTANCE_NAME> --database-flags "contained database authentication=off"

This command will overwrite all database flags previously set. To keep those and add new ones, , include the values for all flags to be set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign ("=").


Additional Information


This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - - to see if your instance will be restarted when this patch is submitted.


Some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines.


Configuring the above flag does not restart the Cloud SQL instance.