MCAS Activity(Preview)

>**NOTE:** This connector uses Azure Functions to connect to MCAS 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 API Token** [Follow these instructions](https://docs.microsoft.com/cloud-app-security/api-authentication) to create an API Token.

**STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function** >**IMPORTANT:** Before deploying the MCAS Activity Data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the API Token and MCAS URL, readily available.

Workspace ID

Primary Key

Option 1 - Azure Resource Manager (ARM) Template

This method provides an automated deployment of the MCAS Activity data connector using an ARM Tempate. 1. Click the **Deploy to Azure** button below. [](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FDataConnectors%2FMCASActivityFunction%2Fazuredeploy.json) 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 3. Enter the **Workspace ID**, **Workspace Key**, **API Token**, **MCAS URL**, **Lookback** > - The default **Time Interval** is set to pull the last five (5) minutes of data. If the time interval needs to be modified, it is recommended to change the Function App Timer Trigger accordingly (in the function.json file, post deployment) to prevent overlapping data ingestion. > - 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 MCAS Activity Data 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), and select **+ Add**. 2. In the **Basics** tab, ensure Runtime stack is set to **Powershell Core**. 3. In the **Hosting** tab, ensure the **Consumption (Serverless)** plan type is selected. 4. Make other preferrable configuration changes, if needed, then click **Create**.

**2. Import Function App Code** 1. In the newly created Function App, select **Functions** on the left pane and click **+ Add**. 2. Select **Timer Trigger**. 3. Enter a unique Function **Name** and leave the default cron schedule of every 5 minutes, then click **Create**. 4. Click on **Code + Test** on the left pane. 5. Copy the [Function App Code](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fazure%2FAzure-Sentinel%2FDataConnectors%2FMCASActivityFunction%2Fazuredeploy.json) and paste into the Function App `run.ps1` editor. 5. Click **Save**.

**3. Configure the Function App** 1. In the Function App, select the Function App Name and select **Configuration**. 2. In the **Application settings** tab, select **+ New application setting**. 3. Add each of the following five (5) application settings individually, with their respective string values (case-sensitive): APIToken MCASURL Lookback TimeInterval WorkspaceID WorkspaceKey - Set the `timeInterval` (in minutes) to the default value of `5` to correspond to the default Timer Trigger of every `5` minutes. Note that modifying time interval will require modifying the Function App Timer Trigger accordingly to prevent overlapping data. - 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. Once all application settings have been entered, click **Save**.