SigParser

If you don't want to use the local storage on your server where the On Premise engine is deployed you can instead use Azure Storage. Be careful the storage account is not public. 

The Azure Storage option has pros and cons. The pro is the storage can grow forever but you are unlikely to need that much storage because the storage is only used when the SigParser API is unreachable which isn't often. The con is that it is harder to setup and managing connection strings becomes an additional burden.

Create an Azure Storage Account (optional)

In Azure Portal, search for Storage accounts

1. Choose the appropriate subscription &amp; resource group
2. Specify the storage account name, something like sigparserstorage
3. Choose Standardperformance
4. Choose StorageV2 (general purpose v2)
5. Choose Locally-redundant storage (LRS)
6. Choose Next to proceed to Networking
7. Choose Public endpoint(all network) 
 1. The storage account's contents should not be made public. This settings just controls the endpoint for this storage account. 
 2. You can make a private endpoint but it requires a private DNS and a network interface (NIC). See this <a href="https://learn.microsoft.com/en-us/azure/storage/files/storage-files-networking-endpoints?tabs=azure-portal#create-a-private-endpoint" target="_blank" rel="nofollow noopener noreferrer">page for details</a>.
8. Click Review + create
9. Click Create
10. Give it a minute to deploy
11. Click Go to resource

Confirm public access to the storage account is disabled. 

1. Go to Settings -&gt; Configuration and verify Allow Blob public access is Disabled

On the left menu bar, click File shares

1. Click + File share
2. Choose some name, like sigparsershare
3. Save this name into the EmailFetcher appsettings.json config file as azurestoragesharename
4. Choose the Hot tier
5. Click Create

On the left menu bar, click Access keys

1. Click Show keys at the top of the page.
2. Copy key1’s Connection string

Under Settings, click Secrets

1. Click Generate/Import
2. Enter AzureStorageConnectionString as the name
3. Paste the connection string from the previous step as the value
4. Click Create

1. In Azure Portal, search for Storage accounts
2. Click New
 1. Choose the appropriate subscription &amp; resource group
 2. Specify the storage account name, something like sigparserstorage
 3. Choose Standardperformance
 4. Choose StorageV2 (general purpose v2)
 5. Choose Locally-redundant storage (LRS)
 6. Choose Next to proceed to Networking
 7. Choose Public endpoint(all network) 
 1. The storage account's contents should not be made public. This settings just controls the endpoint for this storage account. 
 2. You can make a private endpoint but it requires a private DNS and a network interface (NIC). See this <a href="https://learn.microsoft.com/en-us/azure/storage/files/storage-files-networking-endpoints?tabs=azure-portal#create-a-private-endpoint" target="_blank" rel="nofollow noopener noreferrer">page for details</a>.
 8. Click Review + create
 9. Click Create
 10. Give it a minute to deploy
 11. Click Go to resource
3. Confirm public access to the storage account is disabled. 
 1. Go to Settings -&gt; Configuration and verify Allow Blob public access is Disabled 
4. On the left menu bar, click File shares
 1. Click + File share
 2. Choose some name, like sigparsershare
 3. Save this name into the EmailFetcher appsettings.json config file as azurestoragesharename
 4. Choose the Hot tier
 5. Click Create
5. On the left menu bar, click Access keys
 1. Click Show keys at the top of the page.
 2. Copy key1’s Connection string
6. Go back to the Azure Vault page
7. Under Settings, click Secrets
 1. Click Generate/Import
 2. Enter AzureStorageConnectionString as the name
 3. Paste the connection string from the previous step as the value
 4. Click Create