PROVIDER NAME APPLIANCE NAME

>**NOTE:** This connector uses Azure Functions to connect to a 'PROVIDER NAME APPLIANCE NAME' to pull its logs into Azure Sentinel. This might result in additional data ingestion costs. Check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) for details.

>**(Optional Step)** Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. [Follow these instructions](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) to use Azure Key Vault with an Azure Function App.

**STEP 1 - Configuration steps for the 'PROVIDER NAME APPLIANCE NAME' API** The provider should provide or link to detailed steps to configure the 'PROVIDER NAME APPLICATION NAME' API endpoint so that the Azure Function can authenticate to it successfully, get its authorization key or token, and pull the appliance's logs into Azure Sentinel.

**STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function** >**IMPORTANT:** Before deploying the 'PROVIDER NAME APPLIANCE NAME' connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the 'PROVIDER NAME APPLIANCE NAME' API authorization key(s) or Token, readily available.

Workspace ID

Primary Key

**Option 1 - Azure Resource Manager (ARM) Template** Use this method for automated deployment of the 'PROVIDER NAME APPLIANCE NAME' connector. 1. Click the **Deploy to Azure** button below. [](<Add Link to ARM Template on https://aka.ms/threathunter GitHub repo, name template as azuredeploy_Connector_PROVIDER_NAME_APPLIANCE_NAME_AzureFunction.json>) 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 3. Enter the **Workspace ID**, **Workspace Key**, **API Username**, **API Password**, 'and/or Other required fields'. >Note: If using Azure Key Vault secrets for any of the values above, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) for further details. 4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 5. Click **Purchase** to deploy.

**Option 2 - Manual Deployment of Azure Functions** Use the following step-by-step instructions to deploy the 'PROVIDER NAME APPLIANCE NAME' connector manually with Azure Functions.

1. Create a Function App

1. From the Azure Portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp). 2. Click **+ Add** at the top. 3. In the **Basics** tab, ensure Runtime stack is set to **'Add Required Language'**. 4. In the **Hosting** tab, ensure **Plan type** is set to **'Add Plan Type'**. 5. 'Add other required configurations'. 5. 'Make other preferable configuration changes', if needed, then click **Create**.

2. Import Function App Code

1. In the newly created Function App, select **Functions** from the navigation menu and click **+ Add**. 2. Select **Timer Trigger**. 3. Enter a unique Function **Name** in the New Function field and leave the default cron schedule of every 5 minutes, then click **Create Function**. 4. Click on the function name and click **Code + Test** from the left pane. 5. Copy the [Function App Code](<Add GitHub link to Function App code>) and paste into the Function App `run.ps1` editor. 6. Click **Save**.

3. Configure the Function App

1. In the Function App screen, click the Function App name and select **Configuration**. 2. In the **Application settings** tab, select **+ New application setting**. 3. Add each of the following 'x (number of)' application settings individually, under Name, with their respective string values (case-sensitive) under Value: apiUsername apipassword apiToken workspaceID workspaceKey uri logAnalyticsUri (optional) (add any other settings required by the Function App) Set the `uri` value to: `<add uri value>` >Note: If using Azure Key Vault secrets for any of the values above, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Azure Key Vault references documentation](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) for further details. - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: https://<CustomerId>.ods.opinsights.azure.us. 4. Once all application settings have been entered, click **Save**.