#General Settings

You can configure the following settings in general settings. Click the tile to access the corresponding settings page.

• Database Settings – Choose to use the default Cosmos database or your own Cosmos database to store the Insights data.

• Visibility Settings – Choose whether to hide IP addresses from exported activity reports.

#Database Settings

The Database settings page displays the Azure Cosmos database selection for your tenant. You can edit the database that is used to store scan results on this page. Select Default Cosmos database to use the Cosmos database provided by AvePoint, or select My own Cosmos database to use your own Cosmos database.

If you use your own Cosmos database, all your Insights data stored in the default Cosmos database will be migrated into your own Cosmos database, and you can select the Customize the email recipients for the completion of data migration checkbox and define the email recipients to notify the configured users when the data migration completes. The data stored in the default Cosmos database will be automatically removed 30 days after the data migration.

Complete the following database settings when My own Cosmos database is selected:

• Connection string – Enter the primary or secondary connection string of your Azure Cosmos database. To find the connection string, refer to the following steps:

  1. Log in to Azure portal.

  2. Select the Azure Cosmos database that you want to use to store scan results.

  3. Navigate to Settings > Keys > Read-write Keys, and you can find the primary and secondary connection strings.

• Database name – The database name is automatically filled in. You can also change it to use an existing Cosmos database.

• Container name – The container name is automatically filled in.

  If you have already created a container with the same name in your database, make sure the partition key configured is /scopeid.

• Throughput – The throughput – Request Units per second (RU/s) – required for the workload. Refer to Throughput Recommendation to estimate your required RU/s.

  To change the throughput setting for your container, refer to the following steps:

  1. Log in to Azure portal.

  2. Navigate to your Azure Cosmos DB account and open the Data Explorer tab.

  3. Under SQL API, click the Cosmos database that you configured in the database settings to load all containers.

  4. Click the container that you configured in the database settings and click Scale & Settings.

  5. In the Settings tab, you can configure the throughput settings for the container under Scale.

#Throughput Recommendation

The cost of all database operations is normalized by the Azure Cosmos database and is expressed by Request Units (or RUs, for short). A Request Unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by the Azure Cosmos database.

The throughput of a newly created container is 4,000 RU/s. This is also recommended if you use an existing container.

To estimate your required RU/s, refer to the following table.

User seat (n)	RU recommendation	Cost
0-2,000	4,000 RU/s	$35.04-$350.40 Monthly
2,000-10,000	2n RU/s(The maximum RU/s is 20,000)2n indicates that the number of user seats is multiplied by 2.	For details, refer to Capacity Calculator.
>10,000	30,000 RU/s	$262.80-$2628.00 Monthly

#Visibility Settings

Visibility settings controls the visibility of IP addresses in exported activity reports.

To conform to your organization regulations, you can enable this setting to hide IP addresses from the exported activity reports.