Incorp changes from public PR 112459 / ansereb

Author: cwatson-cat

articles/sentinel/data-connectors/github-using-webhooks-using-azure-function.md

@@ -108,11 +108,14 @@ If you're already signed in, go to the next step.
 
 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 application settings individually, with their respective string values (case-sensitive): 
-		WorkspaceID
-		WorkspaceKey
-		logAnalyticsUri (optional) - 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**.
+3. Add each of the following application settings individually, with their respective string values (case-sensitive):
+
+   - WorkspaceID
+   - WorkspaceKey
+   - logAnalyticsUri (optional) - 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`.
+   - GithubWebhookSecret (optional) - To enable webhook authentication generate a secret value and store it in this setting.
+
+1. Once all application settings have been entered, click **Save**.
 
 
 **Post Deployment steps**
@@ -133,7 +136,8 @@ If you're already signed in, go to the next step.
  2. Click on Settings.
  3. Click on "Webhooks" and enter the function app url which was copied from above STEP 1 under payload URL textbox. 
  4. Choose content type as "application/json". 
- 5. Subscribe for events and Click on "Add Webhook"
+ 1. (Optional) To enable webhook authentication, add to the "Secret" field value you saved to GithubWebhookSecret from Function App settings.
+ 1. Subscribe for events and click on "Add Webhook"
 
 
 *Now we are done with the GitHub Webhook configuration. Once the GitHub events triggered and after the delay of 20 to 30 mins (As there will be a dealy for LogAnalytics to spin up the resources for the first time), you should be able to see all the transactional events from the GitHub into LogAnalytics workspace table called "githubscanaudit_CL".*