Merge pull request #235401 from cwatson-cat/4-21-23-dc-fix-lnks5

v-shils · web-flow · commit 8740703de83c · 2023-04-21T12:47:31.000-07:00
Sentinel auto-gen data connectors - fx lnks abs 5
diff --git a/articles/sentinel/data-connectors/ai-vectra-stream.md b/articles/sentinel/data-connectors/ai-vectra-stream.md
@@ -92,7 +92,7 @@ Install the Linux agent on sperate Linux instance.
 
 2. Configure the logs to be collected
 
-Follow the configuration steps below to get Vectra Stream metadata into Microsoft Sentinel. The Log Analytics agent is leveraged to send custom JSON into Azure Monitor, enabling the storage of the metadata into a custom table. For more information, refer to the [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-json).
+Follow the configuration steps below to get Vectra Stream metadata into Microsoft Sentinel. The Log Analytics agent is leveraged to send custom JSON into Azure Monitor, enabling the storage of the metadata into a custom table. For more information, refer to the [Azure Monitor Documentation](/azure/azure-monitor/agents/data-sources-json).
 1. Download config file for the log analytics agent: VectraStream.conf (located in the Connector folder within the Vectra solution: https://aka.ms/sentinel-aivectrastream-conf).
 2. Login to the server where you have installed Azure Log Analytics agent.
 3. Copy VectraStream.conf to the /etc/opt/microsoft/omsagent/**workspace_id**/conf/omsagent.d/ folder.
diff --git a/articles/sentinel/data-connectors/automated-logic-webctrl.md b/articles/sentinel/data-connectors/automated-logic-webctrl.md
@@ -37,7 +37,7 @@ Event
 
 1. Install and onboard the Microsoft agent for Windows.
 
-Learn about [agent setup](https://learn.microsoft.com/services-hub/health/mma-setup) and [windows events onboarding](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-windows-events). 
+Learn about [agent setup](/services-hub/health/mma-setup) and [windows events onboarding](/azure/azure-monitor/agents/data-sources-windows-events). 
 
  You can skip this step if you have already installed the Microsoft agent for Windows
 
diff --git a/articles/sentinel/data-connectors/cisco-asa-ftd-via-ama.md b/articles/sentinel/data-connectors/cisco-asa-ftd-via-ama.md
@@ -39,7 +39,7 @@ CommonSecurityLog
 
 To integrate with Cisco ASA/FTD via AMA (Preview) make sure you have: 
 
-- ****: To collect data from non-Azure VMs, they must have Azure Arc installed and enabled. [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
+- ****: To collect data from non-Azure VMs, they must have Azure Arc installed and enabled. [Learn more](/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
 
 
 ## Vendor installation instructions
diff --git a/articles/sentinel/data-connectors/cisco-meraki.md b/articles/sentinel/data-connectors/cisco-meraki.md
@@ -65,7 +65,7 @@ Typically, you should install the agent on a different computer from the one on
 
 2. Configure the logs to be collected
 
-Follow the configuration steps below to get Cisco Meraki device logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
+Follow the configuration steps below to get Cisco Meraki device logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
  For Cisco Meraki logs, we have issues while parsing the data by OMS agent data using default settings. 
 So we advice to capture the logs into custom table **meraki_CL** using below instructions. 
 1. Login to the server where you have installed OMS agent.
diff --git a/articles/sentinel/data-connectors/cloudflare-using-azure-function.md b/articles/sentinel/data-connectors/cloudflare-using-azure-function.md
@@ -37,7 +37,7 @@ Cloudflare_CL
 To integrate with Cloudflare (Preview) (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).
-- **Azure Blob Storage connection string and container name**: Azure Blob Storage connection string and container name where the logs are pushed to by Cloudflare Logpush. [See the documentation to learn more about creating Azure Blob Storage container.](https://learn.microsoft.com/azure/storage/blobs/storage-quickstart-blobs-portal)
+- **Azure Blob Storage connection string and container name**: Azure Blob Storage connection string and container name where the logs are pushed to by Cloudflare Logpush. [See the documentation to learn more about creating Azure Blob Storage container.](/azure/storage/blobs/storage-quickstart-blobs-portal)
 
 
 ## Vendor installation instructions
diff --git a/articles/sentinel/data-connectors/cohesity-using-azure-function.md b/articles/sentinel/data-connectors/cohesity-using-azure-function.md
@@ -52,7 +52,7 @@ To integrate with Cohesity (using Azure Functions) make sure you have:
 **STEP 1 - Get a Cohesity DataHawk API key (see troubleshooting [instruction 1](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/CohesitySecurity/Data%20Connectors/Helios2Sentinel/IncidentProducer))**
 
 
-**STEP 2 - Register Azure app ([link](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps)) and save Application (client) ID, Directory (tenant) ID, and Secret Value ([instructions](https://learn.microsoft.com/azure/healthcare-apis/register-application)). Grant it Azure Storage (user_impersonation) permission. Also, assign the 'Microsoft Sentinel Contributor' role to the application in the appropriate subscription.**
+**STEP 2 - Register Azure app ([link](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps)) and save Application (client) ID, Directory (tenant) ID, and Secret Value ([instructions](/azure/healthcare-apis/register-application)). Grant it Azure Storage (user_impersonation) permission. Also, assign the 'Microsoft Sentinel Contributor' role to the application in the appropriate subscription.**
 
 
 **STEP 3 - Deploy the connector and the associated Azure Functions**.
diff --git a/articles/sentinel/data-connectors/corelight.md b/articles/sentinel/data-connectors/corelight.md
@@ -50,7 +50,7 @@ Install the agent on the Server where the Corelight logs are generated.
 
 2. Configure the logs to be collected
 
-Follow the configuration steps below to get Corelight logs into Microsoft Sentinel. This configuration enriches events generated by Corelight module to provide visibility on log source information for Corelight logs. Refer to the [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
+Follow the configuration steps below to get Corelight logs into Microsoft Sentinel. This configuration enriches events generated by Corelight module to provide visibility on log source information for Corelight logs. Refer to the [Azure Monitor Documentation](/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
 1. Download config file: [corelight.conf](https://aka.ms/sentinel-Corelight-conf/).
 2. Login to the server where you have installed Azure Log Analytics agent.
 3. Copy corelight.conf to the /etc/opt/microsoft/omsagent/**workspace_id**/conf/omsagent.d/ folder.
diff --git a/articles/sentinel/data-connectors/darktrace-connector-for-microsoft-sentinel-rest-api.md b/articles/sentinel/data-connectors/darktrace-connector-for-microsoft-sentinel-rest-api.md
@@ -104,7 +104,7 @@ darktrace_model_alerts_CL
 To integrate with Darktrace Connector for Microsoft Sentinel REST API make sure you have: 
 
 - **Darktrace Prerequisites**: To use this Data Connector a Darktrace master running v5.2+ is required.
- Data is sent to the [Azure Monitor HTTP Data Collector API](https://learn.microsoft.com/azure/azure-monitor/logs/data-collector-api) over HTTPs from Darktrace masters, therefore outbound connectivity from the Darktrace master to Microsoft Sentinel REST API is required.
+ Data is sent to the [Azure Monitor HTTP Data Collector API](/azure/azure-monitor/logs/data-collector-api) over HTTPs from Darktrace masters, therefore outbound connectivity from the Darktrace master to Microsoft Sentinel REST API is required.
 - **Filter Darktrace Data**: During configuration it is possible to set up additional filtering on the Darktrace System Configuration page to constrain the amount or types of data sent.
 - **Try the Darktrace Sentinel Solution**: You can get the most out of this connector by installing the Darktrace Solution for Microsoft Sentinel. This will provide workbooks to visualise alert data and analytics rules to automatically create alerts and incidents from Darktrace Model Breaches and AI Analyst incidents.
 
diff --git a/articles/sentinel/data-connectors/flare.md b/articles/sentinel/data-connectors/flare.md
@@ -47,7 +47,7 @@ As an organization administrator, authenticate on [Flare](https://app.flare.syst
 
 
 Click on 'Create a new alert channel' and select 'Microsoft Sentinel'. Enter your Shared Key And WorkspaceID. Save the Alert Channel. 
- For more help and details, see our [Azure configuration documentation](https://learn.microsoft.com/azure/sentinel/connect-data-sources).
+ For more help and details, see our [Azure configuration documentation](/azure/sentinel/connect-data-sources).
 
 
    {0}
diff --git a/articles/sentinel/data-connectors/juniper-idp.md b/articles/sentinel/data-connectors/juniper-idp.md
@@ -52,7 +52,7 @@ Install the agent on the Server.
 
 2. Configure the logs to be collected
 
-Follow the configuration steps below to get Juniper IDP logs into Microsoft Sentinel. This configuration enriches events generated by Juniper IDP module to provide visibility on log source information for Juniper IDP logs. Refer to the [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
+Follow the configuration steps below to get Juniper IDP logs into Microsoft Sentinel. This configuration enriches events generated by Juniper IDP module to provide visibility on log source information for Juniper IDP logs. Refer to the [Azure Monitor Documentation](/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
 1. Download config file [juniper_idp.conf](https://aka.ms/sentinel-JuniperIDP-conf).
 2. Login to the server where you have installed Azure Log Analytics agent.
 3. Copy juniper_idp.conf to the /etc/opt/microsoft/omsagent/**workspace_id**/conf/omsagent.d/ folder.
diff --git a/articles/sentinel/data-connectors/qualys-vulnerability-management-using-azure-function.md b/articles/sentinel/data-connectors/qualys-vulnerability-management-using-azure-function.md
@@ -157,7 +157,7 @@ Due to the potentially large amount of Qualys host detection data being ingested
 3. Add the line `"functionTimeout": "00:10:00",` above the `managedDependancy` line 
 4. Ensure **SAVED** appears on the top right corner of the editor, then exit the editor.
 
-> NOTE: If a longer timeout duration is required, consider upgrading to an [App Service Plan](https://learn.microsoft.com/azure/azure-functions/functions-scale#timeout)
+> NOTE: If a longer timeout duration is required, consider upgrading to an [App Service Plan](/azure/azure-functions/functions-scale#timeout)
 
 
 
diff --git a/articles/sentinel/data-connectors/senservapro.md b/articles/sentinel/data-connectors/senservapro.md
@@ -199,7 +199,7 @@ let timeframe = 14d;
 
 1. Setup the data connection
 
-Visit [Senserva Setup](https://www.senserva.com/senserva-setup/) for information on setting up the Senserva data connection, support, or any other questions. The Senserva installation will configure a Log Analytics Workspace for output. Deploy Microsoft Sentinel onto the configured Log Analytics Workspace to finish the data connection setup by following [this onboarding guide.](https://learn.microsoft.com/azure/sentinel/quickstart-onboard)
+Visit [Senserva Setup](https://www.senserva.com/senserva-setup/) for information on setting up the Senserva data connection, support, or any other questions. The Senserva installation will configure a Log Analytics Workspace for output. Deploy Microsoft Sentinel onto the configured Log Analytics Workspace to finish the data connection setup by following [this onboarding guide.](/azure/sentinel/quickstart-onboard)
 
 
 
diff --git a/articles/sentinel/data-connectors/ubiquiti-unifi.md b/articles/sentinel/data-connectors/ubiquiti-unifi.md
@@ -54,7 +54,7 @@ Install the agent on the Server to which the Ubiquiti logs are forwarder from Ub
 
 2. Configure the logs to be collected
 
-Follow the configuration steps below to get Ubiquiti logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
+Follow the configuration steps below to get Ubiquiti logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
 1. Configure log forwarding on your Ubiquiti controller: 
 
 	 i. Go to Settings > System Setting > Controller Configuration > Remote Logging and enable the Syslog and Debugging (optional) logs (Refer to [User Guide](https://dl.ui.com/guides/UniFi/UniFi_Controller_V5_UG.pdf) for detailed instructions).
diff --git a/articles/sentinel/data-connectors/vmware-vcenter.md b/articles/sentinel/data-connectors/vmware-vcenter.md
@@ -57,7 +57,7 @@ Typically, you should install the agent on a different computer from the one on
 
 2. Configure the logs to be collected
 
-Follow the configuration steps below to get vCenter server logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
+Follow the configuration steps below to get vCenter server logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
  For vCenter Server logs, we have issues while parsing the data by OMS agent data using default settings. 
 So we advice to capture the logs into custom table **vCenter_CL** using below instructions. 
 1. Login to the server where you have installed OMS agent.
diff --git a/articles/sentinel/data-connectors/windows-firewall-events-via-ama.md b/articles/sentinel/data-connectors/windows-firewall-events-via-ama.md
@@ -37,7 +37,7 @@ ASimNetworkSessionLogs
 
 To integrate with Windows Firewall Events via AMA (Preview) make sure you have: 
 
-- ****: To collect data from non-Azure VMs, they must have Azure Arc installed and enabled. [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
+- ****: To collect data from non-Azure VMs, they must have Azure Arc installed and enabled. [Learn more](/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
 
 
 ## Vendor installation instructions
diff --git a/articles/sentinel/data-connectors/zero-networks-segment-audit-function-using-azure-function.md b/articles/sentinel/data-connectors/zero-networks-segment-audit-function-using-azure-function.md
@@ -83,7 +83,7 @@ Use the following step-by-step instructions to deploy the Zero Networks Segment
 
 **1. Deploy a Function App**
 
-> **NOTE:** You will need to [prepare VS code](https://learn.microsoft.com/azure/azure-functions/functions-create-first-function-powershell#prerequisites) for Azure function development.
+> **NOTE:** You will need to [prepare VS code](/azure/azure-functions/functions-create-first-function-powershell#prerequisites) for Azure function development.
 
 1. Download the [Azure Function App](https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/ZeroNetworks/SegmentFunctionConnector/AzureFunction_ZeroNetworks_Segment_Audit.zip) file. Extract archive to your local development computer.
 2. Start VS Code. Choose File in the main menu and select Open Folder.
diff --git a/articles/sentinel/data-connectors/zscaler-private-access.md b/articles/sentinel/data-connectors/zscaler-private-access.md
@@ -55,7 +55,7 @@ Install the agent on the Server where the Zscaler Private Access logs are forwar
 
 2. Configure the logs to be collected
 
-Follow the configuration steps below to get Zscaler Private Access logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
+Follow the configuration steps below to get Zscaler Private Access logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](/azure/azure-monitor/agents/data-sources-json) for more details on these steps.
 Zscaler Private Access logs are delivered via Log Streaming Service (LSS). Refer to [LSS documentation](https://help.zscaler.com/zpa/about-log-streaming-service) for detailed information
 1. Configure [Log Receivers](https://help.zscaler.com/zpa/configuring-log-receiver). While configuring a Log Receiver, choose **JSON** as **Log Template**.
 2. Download config file [zpa.conf](https://aka.ms/sentinel-ZscalerPrivateAccess-conf) 
