The container is configured by providing Environment Variables to the runtime.
The following parameters are available:
- license (required)
- storageaccount (required)
- delete (required, if quarantinecontainer is not provided)
- quarantinecontainer (required, if delete is not provided)
- skiptestblob (optional)
- startwithfullscan (optional)
license
The license key that you get after purchasing the product.
Example: eyJUZXJtcyI6eyJTdGFydERh…
storageaccount
The Connection String to the Azure Storage Account.
Can be copied from ‘Access keys’ in the Azure Portal:
Example: DefaultEndpointsProtocol=https;AccountName=mevitcofcme;AccountKey=Dd/N4ce34s6kQ==;EndpointSuffix=core.windows.net
delete
If any value is provided, infected blobs are deleted automatically.
Example: true
quarantinecontainer
The container name of the quarantine container. If an infected blob is detected, it will be moved to this container. If the container does not exist, it will be created. Please use simple names for the container, naming convention is very strict: Naming and Referencing Containers
Example: quarantine
skiptestblob
When the container is started, a test blob (0 bytes) is created on the first container on the Azure Storage Account to trigger the creation of the Change Feed. If you provide any value for this parameter, the test blob will be skipped.
startwithfullscan
If any value is provided, the Azure Storage Account will be scanned based on the available Change Feed. The Change Feed can be configured to store events only for a given time period but also to keep all logs.
Example: true