Merge pull request #290625 from Daidihuang/2024_11-Monthly-broken-links-fix-cwatson-cat

2024_11-Monthly-broken-links-fix-cwatson-cat

Author: v-ccolin

articles/sentinel/data-connectors/hyas-protect.md

@@ -13,7 +13,7 @@ ms.collection: sentinel-data-connector
 
 HYAS Protect provide logs based on reputation values - Blocked, Malicious, Permitted, Suspicious.
 
-This is autogenerated content. For changes, contact the solution provider.
+It's autogenerated content. For changes, contact the solution provider.
 
 ## Connector attributes
 
@@ -36,7 +36,7 @@ HYASProtectDnsSecurityLogs_CL
 
 ## Prerequisites
 
-To integrate with HYAS Protect (using Azure Functions) make sure you have: 
+To integrate with HYAS Protect (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/).
 - **REST API Credentials/permissions**: **HYAS API Key** is required for making API calls.
@@ -56,7 +56,7 @@ To integrate with HYAS Protect (using Azure Functions) make sure you have:
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the HYAS Protect data connector using an ARM Tempate.
+Use this method for automated deployment of the HYAS Protect data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -89,14 +89,14 @@ If you're already signed in, go to the next step.
 
 	c. Select **Create new Function App in Azure** (Don't choose the Advanced option)
 
-	d. **Enter a globally unique name for the function app:** Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. HyasProtectLogsXXX).
+	d. **Enter a globally unique name for the function app:** Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (for example, HyasProtectLogsXXX).
 
 	e. **Select a runtime:** Choose Python 3.8.
 
-	f. Select a location for new resources. For better performance and lower costs choose the same [region](https://azure.microsoft.com/regions/) where Microsoft sentinel is located.
+	f. Select a location for new resources. For better performance and lower costs, choose the same [region](https://azure.microsoft.com/regions/) where Microsoft Sentinel is located.
 
-6. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
-7. Go to Azure Portal for the Function App configuration.
+6. Deployment begins. A notification is displayed after your function app is created and the deployment package is applied.
+7. Go to Azure portal for the Function App configuration.
 
 
 **2. Configure the Function App**
@@ -111,7 +111,3 @@ If you're already signed in, go to the next step.
 . Once all application settings have been entered, click **Save**.
 
 
-
-## Next steps
-
-For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/hyas.microsoft-sentinel-solution-hyas-protect?tab=Overview) in the Azure Marketplace.

articles/sentinel/unified-connector-cef-device.md

@@ -129,7 +129,7 @@ Set your security solution to send syslog messages in CEF format to the proxy ma
 
 Set your security solution to send syslog messages in CEF format to the proxy machine. Make sure to send the logs to port 514 TCP on the machine IP address.
 
-1. Follow the directions to install the [ExtraHop Detection SIEM Connector bundle](https://learn.extrahop.com/extrahop-detection-siem-connector-bundle) on your Reveal(x) system. The **SIEM Connector** is required for this integration.
+1. Follow the directions to install the [ExtraHop Detection SIEM Connector bundle](https://learn.extrahop.com/) on your Reveal(x) system. The **SIEM Connector** is required for this integration.
 1. Enable the trigger for **ExtraHop Detection SIEM Connector - CEF**.
 1. Update the trigger with the ODS syslog targets you created. 
 

articles/sentinel/unified-connector-syslog-device.md

@@ -321,7 +321,6 @@ This data connector was developed using RSA SecurID Authentication Manager versi
 
 1. Follow these instructions to configure the VMware ESXi to forward syslog:
 
-   - [VMware ESXi 3.5 and 4.x](https://kb.vmware.com/s/article/1016621)
    - [VMware ESXi 5.0+](https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.monitoring.doc/GUID-9F67DB52-F469-451F-B6C8-DAE8D95976E7.html)
 
 1. Use the IP address or hostname for the Linux device with the Linux agent installed as the **Destination IP** address.