Skip to content

Commit 977716d

Browse files
authored
Merge pull request #123649 from changeworld/patch-3
Fix typo
2 parents 58ed3ae + 6c195a9 commit 977716d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.collection: sentinel-data-connector
1313

1414
The [GitHub](https://www.github.com) webhook data connector provides the capability to ingest GitHub subscribed events into Microsoft Sentinel using [GitHub webhook events](https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads). The connector provides ability to get events into Microsoft Sentinel which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
1515

16-
**Note:** If you are intended to ingest Github Audit logs, Please refer to GitHub Enterprise Audit Log Connector from "**Data Connectors**" gallery.
16+
**Note:** If you are intended to ingest GitHub Audit logs, Please refer to GitHub Enterprise Audit Log Connector from "**Data Connectors**" gallery.
1717

1818
This is autogenerated content. For changes, contact the solution provider.
1919

@@ -56,7 +56,7 @@ To integrate with GitHub (using Webhooks) (using Azure Functions) make sure you
5656

5757
**Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function**
5858

59-
>**IMPORTANT:** Before deploying the Github Webhook connector, have the Workspace ID and Workspace Primary Key (can be copied from the following).
59+
>**IMPORTANT:** Before deploying the GitHub Webhook connector, have the Workspace ID and Workspace Primary Key (can be copied from the following).
6060
6161

6262

@@ -70,7 +70,7 @@ To integrate with GitHub (using Webhooks) (using Azure Functions) make sure you
7070

7171

7272

73-
*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".*
73+
*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".*
7474

7575
For more details, Click [here](https://aka.ms/sentinel-gitHubwebhooksteps)
7676

0 commit comments

Comments
 (0)