Merge pull request #242185 from pritamso/Broken-link-fix-cwatson

American-Dipper · web-flow · commit 673bf7f5fb84 · 2023-06-25T15:21:51.000-07:00
Broken link fixed
diff --git a/articles/sentinel/data-connectors/atlassian-jira-audit-using-azure-function.md b/articles/sentinel/data-connectors/atlassian-jira-audit-using-azure-function.md
@@ -78,7 +78,7 @@ Use this method for automated deployment of the Jira Audit data connector using
 	[![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentineljiraauditazuredeploy)
 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 
 > **NOTE:** Within the same resource group, you can't mix Windows and Linux apps in the same region. Select existing resource group without Windows apps in it or create new resource group.
-3. Enter the **JiraAccessToken**, **JiraUsername**, **JiraHomeSiteName** (short site name part, as example HOMESITENAME from https://HOMESITENAME.atlassian.net) and deploy. 
+3. Enter the **JiraAccessToken**, **JiraUsername**, **JiraHomeSiteName** (short site name part, as example HOMESITENAME from `https://HOMESITENAME.atlassian.net`) and deploy. 
 4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 
 5. Click **Purchase** to deploy.
 
diff --git a/articles/sentinel/data-connectors/braodcom-symantec-dlp.md b/articles/sentinel/data-connectors/braodcom-symantec-dlp.md
@@ -72,7 +72,7 @@ Install the Microsoft Monitoring Agent on your Linux machine and configure the m
 2. Forward Symantec DLP logs to a Syslog agent
 
 Configure Symantec DLP to forward Syslog messages in CEF format to your Microsoft Sentinel workspace via the Syslog agent.
-1. [Follow these instructions](https://help.symantec.com/cs/DLP15.7/DLP/v27591174_v133697641/Configuring-the-Log-to-a-Syslog-Server-action?locale=EN_US) to configure the Symantec DLP to forward syslog
+1. [Follow these instructions](https://techdocs.broadcom.com/content/dam/broadcom/techdocs/symantec-security-software/information-security/data-loss-prevention/generated-pdfs/Symantec_DLP_15.7_Whats_New.pdf) to configure the Symantec DLP to forward syslog
 2. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address.
 
 3. Validate connection
diff --git a/articles/sentinel/data-connectors/cisco-firepower-estreamer.md b/articles/sentinel/data-connectors/cisco-firepower-estreamer.md
@@ -122,9 +122,3 @@ Make sure to configure the machine's security according to your organization's s
 
 
 [Learn more >](https://aka.ms/SecureCEF)
-
-
-
-## Next steps
-
-For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/cisco.cisco-firepower-estreamer?tab=Overview) in the Azure Marketplace.
diff --git a/articles/sentinel/data-connectors/claroty.md b/articles/sentinel/data-connectors/claroty.md
@@ -10,7 +10,7 @@ ms.author: cwatson
 
 # Claroty connector for Microsoft Sentinel
 
-The [Claroty](https://claroty.com/) data connector provides the capability to ingest [Continuous Threat Detection](https://claroty.com/continuous-threat-detection/) and [Secure Remote Access](https://claroty.com/secure-remote-access/) events into Microsoft Sentinel.
+The [Claroty](https://claroty.com/) data connector provides the capability to ingest [Continuous Threat Detection](https://claroty.com/resources/datasheets/continuous-threat-detection) and [Secure Remote Access](https://claroty.com/secure-remote-access/) events into Microsoft Sentinel.
 
 ## Connector attributes
 
diff --git a/articles/sentinel/data-connectors/morphisec-utpp.md b/articles/sentinel/data-connectors/morphisec-utpp.md
@@ -19,7 +19,7 @@ Integrate vital insights from your security products with the Morphisec Data Con
 | **Kusto function url** | https://aka.ms/sentinel-morphisecutpp-parser |
 | **Log Analytics table(s)** | CommonSecurityLog (Morphisec)<br/> |
 | **Data collection rules support** | [Workspace transform DCR](/azure/azure-monitor/logs/tutorial-workspace-transformations-portal) |
-| **Supported by** | [Morphisec](https://support.morphisec.com/support/home) |
+| **Supported by** | [Morphisec](https://support.morphisec.com/hc) |
 
 ## Query samples
 
diff --git a/articles/sentinel/data-connectors/netskope-using-azure-function.md b/articles/sentinel/data-connectors/netskope-using-azure-function.md
@@ -51,7 +51,7 @@ Netskope
 To integrate with Netskope (using Azure Function) 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/).
-- **Netskope API Token**: A Netskope API Token is required. [See the documentation to learn more about Netskope API](https://innovatechcloud.goskope.com/docs/Netskope_Help/en/rest-api-v1-overview.html). **Note:** A Netskope account is required
+- **Netskope API Token**: A Netskope API Token is required. [See the documentation to learn more about Netskope API](https://docs.netskope.com/en/rest-api-v1-overview.html). **Note:** A Netskope account is required
 
 
 ## Vendor installation instructions
diff --git a/articles/sentinel/data-connectors/nxlog-aix-audit.md b/articles/sentinel/data-connectors/nxlog-aix-audit.md
@@ -18,7 +18,7 @@ The NXLog [AIX Audit](https://nxlog.co/documentation/nxlog-user-guide/im_aixaudi
 | --- | --- |
 | **Log Analytics table(s)** | AIX_Audit_CL<br/> |
 | **Data collection rules support** | Not currently supported |
-| **Supported by** | [NXLog](https://nxlog.co/user?destination=node/add/support-ticket) |
+| **Supported by** | [NXLog](https://nxlog.co/community-forum/t/819-support-tickets) |
 
 ## Query samples
 
diff --git a/articles/sentinel/data-connectors/nxlog-bsm-macos.md b/articles/sentinel/data-connectors/nxlog-bsm-macos.md
@@ -18,7 +18,7 @@ The NXLog [BSM](https://nxlog.co/documentation/nxlog-user-guide/im_bsm.html) mac
 | --- | --- |
 | **Log Analytics table(s)** | BSMmacOS_CL<br/> |
 | **Data collection rules support** | Not currently supported |
-| **Supported by** | [NXLog](https://nxlog.co/user?destination=node/add/support-ticket) |
+| **Supported by** | [NXLog](https://nxlog.co/community-forum/t/819-support-tickets) |
 
 ## Query samples
 
diff --git a/articles/sentinel/data-connectors/nxlog-dns-logs.md b/articles/sentinel/data-connectors/nxlog-dns-logs.md
@@ -18,7 +18,7 @@ The NXLog DNS Logs data connector uses Event Tracing for Windows ([ETW](/windows
 | --- | --- |
 | **Log Analytics table(s)** | NXLog_DNS_Server_CL<br/> |
 | **Data collection rules support** | Not currently supported |
-| **Supported by** | [NXLog](https://nxlog.co/user?destination=node/add/support-ticket) |
+| **Supported by** | [NXLog](https://nxlog.co/community-forum/t/819-support-tickets) |
 
 ## Query samples
 
diff --git a/articles/sentinel/data-connectors/tenable-io-vulnerability-management-using-azure-function.md b/articles/sentinel/data-connectors/tenable-io-vulnerability-management-using-azure-function.md
@@ -61,7 +61,7 @@ Tenable_IO_Assets_CL
 To integrate with Tenable.io Vulnerability Management (using Azure Function) 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**: Both a **TenableAccessKey** and a **TenableSecretKey** is required to access the Tenable REST API. [See the documentation to learn more about API](https://developer.tenable.com/reference#vulnerability-management). Check all [requirements and follow  the instructions](https://docs.tenable.com/tenableio/vulnerabilitymanagement/Content/Settings/GenerateAPIKey.htm) for obtaining credentials.
+- **REST API Credentials/permissions**: Both a **TenableAccessKey** and a **TenableSecretKey** is required to access the Tenable REST API. [See the documentation to learn more about API](https://developer.tenable.com/reference#vulnerability-management). Check all [requirements and follow  the instructions](https://docs.tenable.com/tenableio/Content/Platform/Settings/MyAccount/GenerateAPIKey.htm) for obtaining credentials.
 
 
 ## Vendor installation instructions
@@ -80,7 +80,7 @@ To integrate with Tenable.io Vulnerability Management (using Azure Function) mak
 
 **STEP 1 - Configuration steps for Tenable.io**
 
- [Follow the instructions](https://docs.tenable.com/tenableio/vulnerabilitymanagement/Content/Settings/GenerateAPIKey.htm) to obtain the required API credentials. 
+ [Follow the instructions](https://docs.tenable.com/tenableio/Content/Platform/Settings/MyAccount/GenerateAPIKey.htm) to obtain the required API credentials. 
 
 
 
diff --git a/articles/sentinel/data-connectors/vmware-vcenter.md b/articles/sentinel/data-connectors/vmware-vcenter.md
@@ -46,7 +46,7 @@ vCenter
 
 
 **NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias VMware vCenter and load the function code or click [here](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/VMware%20vCenter/Parsers/vCenter.txt), on the second line of the query, enter the hostname(s) of your VMware vCenter device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update. 
-> 1. If you have not installed the vCenter solution from ContentHub then [Follow the steps](https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/VCenter/Parsers/vCenter.txt) to use the Kusto function alias, **vCenter**
+> 1. If you have not installed the vCenter solution from ContentHub then [Follow the steps](https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/VMware%20vCenter/Parsers/vCenter.txt) to use the Kusto function alias, **vCenter**
 
 1. Install and onboard the agent for Linux
 
diff --git a/articles/sentinel/data-connectors/zoom-reports-using-azure-function.md b/articles/sentinel/data-connectors/zoom-reports-using-azure-function.md
@@ -10,7 +10,7 @@ ms.author: cwatson
 
 # Zoom Reports (using Azure Function) connector for Microsoft Sentinel
 
-The [Zoom](https://zoom.us/) Reports data connector provides the capability to ingest [Zoom Reports](https://marketplace.zoom.us/docs/api-reference/zoom-api/reports/) events into Microsoft Sentinel through the REST API. Refer to [API documentation](https://marketplace.zoom.us/docs/api-reference/introduction) for more information. The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
+The [Zoom](https://zoom.us/) Reports data connector provides the capability to ingest [Zoom Reports](https://developers.zoom.us/docs/api/) events into Microsoft Sentinel through the REST API. Refer to [API documentation](https://developers.zoom.us/docs/api/) for more information. The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
 
 ## Connector attributes
 
@@ -40,7 +40,7 @@ Zoom
 To integrate with Zoom Reports (using Azure Function) 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**: **ZoomApiKey** and **ZoomApiSecret** are required for Zoom API. [See the documentation to learn more about API](https://marketplace.zoom.us/docs/guides/auth/jwt). Check all [requirements and follow  the instructions](https://marketplace.zoom.us/docs/guides/auth/jwt) for obtaining credentials.
+- **REST API Credentials/permissions**: **ZoomApiKey** and **ZoomApiSecret** are required for Zoom API. [See the documentation to learn more about API](https://developers.zoom.us/docs/internal-apps/jwt/). Check all [requirements and follow  the instructions](https://developers.zoom.us/docs/internal-apps/jwt/) for obtaining credentials.
 
 
 ## Vendor installation instructions
@@ -59,7 +59,7 @@ To integrate with Zoom Reports (using Azure Function) make sure you have:
 
 **STEP 1 - Configuration steps for the Zoom API**
 
- [Follow the instructions](https://marketplace.zoom.us/docs/guides/auth/jwt) to obtain the credentials. 
+ [Follow the instructions](https://developers.zoom.us/docs/internal-apps/jwt/) to obtain the credentials. 
 
 
 
