Spelling Fixes

ArieHein · ArieHein · commit 3c91ece71ef3 · 2024-12-13T23:43:53.000+01:00
diff --git a/articles/sentinel/data-connectors/1password.md b/articles/sentinel/data-connectors/1password.md
@@ -72,7 +72,7 @@ To integrate with 1Password (using Azure Functions) make sure you have:
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-This method provides an automated deployment of the 1Password connector using an ARM Tempate.
+This method provides an automated deployment of the 1Password connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/alicloud.md b/articles/sentinel/data-connectors/alicloud.md
@@ -76,7 +76,7 @@ To integrate with AliCloud (using Azure Functions) make sure you have:
 
 **Option 1 - Azure Resource Manager (ARM) Template**
 
-Use this method for automated deployment of the AliCloud data connector using an ARM Tempate.
+Use this method for automated deployment of the AliCloud data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/api-protection.md b/articles/sentinel/data-connectors/api-protection.md
@@ -72,7 +72,7 @@ Copy the values shown below and save them for configuration of the API log forwa
 
 Step 3: Install the 42Crunch protection and log forwarder
 
-The next step is to install the 42Crunch protection and log forwarder to protect your API. Both components are availabe as containers from the [42Crunch repository](https://hub.docker.com/u/42crunch). The exact installation depends on your environment, consult the [42Crunch protection documentation](https://docs.42crunch.com/latest/content/concepts/api_firewall_deployment_architecture.htm) for full details. Two common installation scenarios are described below:
+The next step is to install the 42Crunch protection and log forwarder to protect your API. Both components are available as containers from the [42Crunch repository](https://hub.docker.com/u/42crunch). The exact installation depends on your environment, consult the [42Crunch protection documentation](https://docs.42crunch.com/latest/content/concepts/api_firewall_deployment_architecture.htm) for full details. Two common installation scenarios are described below:
 
 
 Installation via Docker Compose
@@ -93,7 +93,7 @@ The sample application can be installed locally using a [Docker compose file](ht
 
 4.2 Run the sample
 
-Verfify the API protection is connected to the 42Crunch platform, and then exercise the API locally on the *localhost* at port 8080 using curl, or similar. You should see a mixture of passing and failing API calls. 
+Verify the API protection is connected to the 42Crunch platform, and then exercise the API locally on the *localhost* at port 8080 using curl, or similar. You should see a mixture of passing and failing API calls. 
 
 4.3 Verify the data ingestion on Log Analytics
 
diff --git a/articles/sentinel/data-connectors/atlassian-confluence-audit.md b/articles/sentinel/data-connectors/atlassian-confluence-audit.md
@@ -69,7 +69,7 @@ To integrate with Atlassian Confluence Audit (using Azure Functions) make sure y
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Confluence Audit data connector using an ARM Tempate.
+Use this method for automated deployment of the Confluence Audit data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/atlassian-jira-audit.md b/articles/sentinel/data-connectors/atlassian-jira-audit.md
@@ -75,7 +75,7 @@ To integrate with Atlassian Jira Audit (using Azure Functions) make sure you hav
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Jira Audit data connector using an ARM Tempate.
+Use this method for automated deployment of the Jira Audit data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/cognni.md b/articles/sentinel/data-connectors/cognni.md
@@ -62,7 +62,7 @@ Connect to Cognni
 1. Go to [Cognni integrations page](https://intelligence.cognni.ai/integrations)
 2. Click **'Connect'** on the 'Microsoft Sentinel' box
 3. Copy and paste **'workspaceId'** and **'sharedKey'** (from below) to the related fields on Cognni's integrations screen
-4. Click the **'Connect'** botton to complete the configuration.  
+4. Click the **'Connect'** button to complete the configuration.  
   Soon, all your Cognni-detected incidents will be forwarded here (into Microsoft Sentinel)
 
 Not a Cognni user? [Join us](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/shieldox.appsource_freetrial)
diff --git a/articles/sentinel/data-connectors/crowdstrike-falcon-data-replicator-v2.md b/articles/sentinel/data-connectors/crowdstrike-falcon-data-replicator-v2.md
@@ -59,7 +59,7 @@ Prerequisites
 1. Configure FDR in CrowdStrike - You must contact the [CrowdStrike support team](https://supportportal.crowdstrike.com/) to enable CrowdStrike FDR.
 	 - Once CrowdStrike FDR is enabled,  from the CrowdStrike console, navigate to Support --> API Clients and Keys. 
 	 - You need to Create new credentials to copy the AWS Access Key ID, AWS Secret Access Key, SQS Queue URL and AWS Region. 
-2.  Register AAD application - For DCR to authentiate to ingest data into log analytics, you must use AAD application. 
+2.  Register AAD application - For DCR to authenticate to ingest data into log analytics, you must use AAD application. 
 	 - [Follow the instructions here](/azure/azure-monitor/logs/tutorial-logs-ingestion-portal#create-azure-ad-application) (steps 1-5) to get **AAD Tenant Id**, **AAD Client Id** and **AAD Client Secret**. 
 	 - For **AAD Principal** Id of this application, access the AAD App through [AAD Portal](https://aad.portal.azure.com/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AppAppsPreview/menuId/) and capture Object Id from the application overview page.
 
@@ -69,7 +69,7 @@ Choose ONE from the following two deployment options to deploy the connector and
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Crowdstrike Falcon Data Replicator connector V2 using an ARM Tempate.
+Use this method for automated deployment of the Crowdstrike Falcon Data Replicator connector V2 using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -89,7 +89,7 @@ Use the following step-by-step instructions to deploy the Crowdstrike Falcon Dat
 1. Deploy the required DCE,  DCR(s) and the Custom Tables by using the [Data Collection Resource ARM template](https://aka.ms/sentinel-CrowdstrikeReplicatorV2-azuredeploy-data-resource) 
 2. After successful deployment of DCE and DCR(s), get the below information and keep it handy (required during Azure Functions app deployment).
 	 - DCE log ingestion - Follow the instructions available at [Create data collection endpoint](/azure/azure-monitor/logs/tutorial-logs-ingestion-portal#create-data-collection-endpoint) (Step 3).
-	 - Immutable Ids of one or more DCRs (as applicable) - Follow the instructions available at [Collect information from the DCR](/azure/azure-monitor/logs/tutorial-logs-ingestion-portal#collect-information-from-the-dcr) (Stpe 2).
+	 - Immutable Ids of one or more DCRs (as applicable) - Follow the instructions available at [Collect information from the DCR](/azure/azure-monitor/logs/tutorial-logs-ingestion-portal#collect-information-from-the-dcr) (Step 2).
 
 
 **2. Deploy a Function App**
diff --git a/articles/sentinel/data-connectors/crowdstrike-falcon-data-replicator.md b/articles/sentinel/data-connectors/crowdstrike-falcon-data-replicator.md
@@ -73,7 +73,7 @@ To integrate with Crowdstrike Falcon Data Replicator (using Azure Functions) mak
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Crowdstrike Falcon Data Replicator connector using an ARM Tempate.
+Use this method for automated deployment of the Crowdstrike Falcon Data Replicator connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/cybersixgill-actionable-alerts.md b/articles/sentinel/data-connectors/cybersixgill-actionable-alerts.md
@@ -56,7 +56,7 @@ To integrate with Cybersixgill Actionable Alerts (using Azure Functions) make su
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Cybersixgill Actionable Alerts data connector using an ARM Tempate.
+Use this method for automated deployment of the Cybersixgill Actionable Alerts data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/dataminr-pulse-alerts-data-connector.md b/articles/sentinel/data-connectors/dataminr-pulse-alerts-data-connector.md
@@ -226,7 +226,7 @@ If you're already signed in, go to the next step.
 1. Open any API request tool.
 2. Click on '+' to create a new request.
 3. Select HTTP request method as **'POST'**.
-4. Enter the url prepapred in **point 1)**, in the request URL part.
+4. Enter the url prepared in **point 1)**, in the request URL part.
 5. In Body, select raw JSON and provide request body as below(case-sensitive): 
 		{ 
 		 "integration-settings": "ADD", 
diff --git a/articles/sentinel/data-connectors/github-using-webhooks.md b/articles/sentinel/data-connectors/github-using-webhooks.md
@@ -70,7 +70,7 @@ To integrate with GitHub (using Webhooks) (using Azure Functions) make sure you
 
 
 
-*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".*
+*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 delay 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".*
 
  For more details, Click [here](https://aka.ms/sentinel-gitHubwebhooksteps)
 
diff --git a/articles/sentinel/data-connectors/google-cloud-platform-iam.md b/articles/sentinel/data-connectors/google-cloud-platform-iam.md
@@ -77,7 +77,7 @@ To integrate with Google Cloud Platform IAM (using Azure Functions) make sure yo
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the data connector using an ARM Tempate.
+Use this method for automated deployment of the data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/hackerview-intergration.md b/articles/sentinel/data-connectors/hackerview-intergration.md
@@ -1,6 +1,6 @@
 ---
-title: "HackerView Intergration (using Azure Functions) connector for Microsoft Sentinel"
-description: "Learn how to install the connector HackerView Intergration (using Azure Functions) to connect your data source to Microsoft Sentinel."
+title: "HackerView Integration (using Azure Functions) connector for Microsoft Sentinel"
+description: "Learn how to install the connector HackerView Integration (using Azure Functions) to connect your data source to Microsoft Sentinel."
 author: cwatson-cat
 ms.topic: how-to
 ms.date: 10/15/2024
@@ -9,7 +9,7 @@ ms.author: cwatson
 ms.collection: sentinel-data-connector
 ---
 
-# HackerView Intergration (using Azure Functions) connector for Microsoft Sentinel
+# HackerView Integration (using Azure Functions) connector for Microsoft Sentinel
 
 Through the API integration, you have the capability to retrieve all the issues related to your HackerView organizations via a RESTful interface.
 
@@ -38,7 +38,7 @@ HackerViewLog_Azure_1_CL
 
 ## Prerequisites
 
-To integrate with HackerView Intergration (using Azure Functions) make sure you have: 
+To integrate with HackerView Integration (using Azure Functions) make sure you have: 
 
 - **Microsoft.Web/sites permissions**: Read and write permissions to Azure Functions to create a Function App is required. [See the documentation to learn more about Azure Functions](/azure/azure-functions/).
 
diff --git a/articles/sentinel/data-connectors/illumio-saas.md b/articles/sentinel/data-connectors/illumio-saas.md
@@ -68,7 +68,7 @@ To integrate with Illumio SaaS (using Azure Functions) make sure you have:
 Prerequisites
 
 1. Ensure AWS SQS is configured for the s3 bucket from which flow and auditable event logs are going to be pulled. In case, Illumio provides bucket, please contact Illumio support for sqs url, s3 bucket name and aws credentials. 
- 2. Register AAD application - For DCR (Data collection rule) to authentiate to ingest data into log analytics, you must use Entra application. 1. [Follow the instructions here](/azure/azure-monitor/logs/tutorial-logs-ingestion-portal#create-azure-ad-application) (steps 1-5) to get **AAD Tenant Id**, **AAD Client Id** and **AAD Client Secret**. 
+ 2. Register AAD application - For DCR (Data collection rule) to authenticate to ingest data into log analytics, you must use Entra application. 1. [Follow the instructions here](/azure/azure-monitor/logs/tutorial-logs-ingestion-portal#create-azure-ad-application) (steps 1-5) to get **AAD Tenant Id**, **AAD Client Id** and **AAD Client Secret**. 
  2. Ensure you have created a log analytics workspace. 
 Please keep note of the name and region where it has been deployed.
 
@@ -78,7 +78,7 @@ Choose one of the approaches from below options. Either use the below ARM templa
 
 1. Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of Azure resources using an ARM Tempate.
+Use this method for automated deployment of Azure resources using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -90,7 +90,7 @@ Use this method for automated deployment of Azure resources using an ARM Tempate
 
 2. Deploy additional function apps to handle scale
 
-Use this method for automated deployment of additional function apps using an ARM Tempate.
+Use this method for automated deployment of additional function apps using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/lookout-cloud-security-for-microsoft-sentinel-using-azure-function.md b/articles/sentinel/data-connectors/lookout-cloud-security-for-microsoft-sentinel-using-azure-function.md
@@ -92,7 +92,7 @@ To integrate with Lookout Cloud Security for Microsoft Sentinel (using Azure Fun
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the data connector using an ARM Tempate.
+Use this method for automated deployment of the data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/microsoft-active-directory-domain-controllers-security-event-logs.md b/articles/sentinel/data-connectors/microsoft-active-directory-domain-controllers-security-event-logs.md
@@ -39,14 +39,14 @@ SecurityEvent
 To integrate with Microsoft Active-Directory Domain Controllers Security Event Logs make sure you have: 
 
 - ****: Azure Log Analytics will be deprecated, to collect data from non-Azure VMs, Azure Arc is recommended. [Learn more](/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
-- **Detailled documentation**: >**NOTE:** Detailled documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
+- **Detailed documentation**: >**NOTE:** Detailed documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
 
 
 ## Vendor installation instructions
 
 
 > [!NOTE]
-   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independant for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
+   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independent for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
 
 >This Data Connector is the **option 3 and 4** of the wiki.
 
diff --git a/articles/sentinel/data-connectors/microsoft-exchange-admin-audit-logs-by-event-logs.md b/articles/sentinel/data-connectors/microsoft-exchange-admin-audit-logs-by-event-logs.md
@@ -40,14 +40,14 @@ Event
 To integrate with Microsoft Exchange Admin Audit Logs by Event Logs make sure you have: 
 
 - ****: Azure Log Analytics will be deprecated, to collect data from non-Azure VMs, Azure Arc is recommended. [Learn more](/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
-- **Detailled documentation**: >**NOTE:** Detailled documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
+- **Detailed documentation**: >**NOTE:** Detailed documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
 
 
 ## Vendor installation instructions
 
 
 > [!NOTE]
-   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independant for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
+   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independent for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
 
 >This Data Connector is the **option 1** of the wiki.
 
diff --git a/articles/sentinel/data-connectors/microsoft-exchange-http-proxy-logs.md b/articles/sentinel/data-connectors/microsoft-exchange-http-proxy-logs.md
@@ -39,14 +39,14 @@ ExchangeHttpProxy_CL
 To integrate with Microsoft Exchange HTTP Proxy Logs make sure you have: 
 
 - **Azure Log Analytics will be deprecated**: Azure Log Analytics will be deprecated, to collect data from non-Azure VMs, Azure Arc is recommended. [Learn more](/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
-- **Detailled documentation**: >**NOTE:** Detailled documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
+- **Detailed documentation**: >**NOTE:** Detailed documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
 
 
 ## Vendor installation instructions
 
 
 > [!NOTE]
-   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independant for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
+   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independent for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
 
 >This Data Connector is the **option 7** of the wiki.
 
diff --git a/articles/sentinel/data-connectors/microsoft-exchange-logs-and-events.md b/articles/sentinel/data-connectors/microsoft-exchange-logs-and-events.md
@@ -51,14 +51,14 @@ To integrate with Microsoft Exchange Logs and Events make sure you have:
 
 
 > [!NOTE]
-   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independant for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
+   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independent for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
 
 1.  Download and install the agents needed to collect logs for Microsoft Sentinel
 
 Type of servers (Exchange Servers, Domain Controllers linked to Exchange Servers or all Domain Controllers) depends on the option you want to deploy.
 
 
-2.  Deploy log injestion following choosed options
+2.  Deploy log ingestion following chosen options
 
 
 

Original file line number	Diff line number	Diff line change
`@@ -226,7 +226,7 @@ If you're already signed in, go to the next step.`
`226`	`226`	`1. Open any API request tool.`
`227`	`227`	`2. Click on '+' to create a new request.`
`228`	`228`	`3. Select HTTP request method as 'POST'.`
`229`		`-4. Enter the url prepapred in point 1), in the request URL part.`
	`229`	`+4. Enter the url prepared in point 1), in the request URL part.`
`230`	`230`	`5. In Body, select raw JSON and provide request body as below(case-sensitive):`
`231`	`231`	`{`
`232`	`232`	`"integration-settings": "ADD",`