revert more changes for DCs that were introducting broken links

Author: cwatson-cat

articles/sentinel/data-connectors/netskope-using-azure-functions.md

@@ -3,7 +3,7 @@ title: "Netskope (using Azure Functions) connector for Microsoft Sentinel"
 description: "Learn how to install the connector Netskope (using Azure Functions) to connect your data source to Microsoft Sentinel."
 author: cwatson-cat
 ms.topic: how-to
-ms.date: 01/06/2024
+ms.date: 10/23/2023
 ms.service: microsoft-sentinel
 ms.author: cwatson
 ---
@@ -49,14 +49,14 @@ Netskope
 To integrate with Netskope (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/).
-- **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://www.netskope.com/resources). **Note:** A Netskope account is required
 
 
 ## Vendor installation instructions
 
 > [!NOTE]
 >  - This connector uses Azure Functions to connect to Netskope to pull logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) for details.
-> -  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 Netskope and load the function code or click [here](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Netskope/Parsers/Netskope.txt), on the second line of the query, enter the hostname(s) of your Netskope device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.
+>  - 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 Netskope and load the function code or click [here](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Netskope/Parsers/Netskope.txt), on the second line of the query, enter the hostname(s) of your Netskope device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.
 
 **(Optional Step)** Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. [Follow these instructions](/azure/app-service/app-service-key-vault-references) to use Azure Key Vault with an Azure Function App.
 
@@ -91,7 +91,6 @@ Option 2 - Manual Deployment of Azure Functions
 
 This method provides the step-by-step instructions to deploy the Netskope connector manually with Azure Function.
 
-
 **1. Create a Function App**
 
 1.  From the Azure portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp), and select **+ Add**.

articles/sentinel/data-connectors/senservapro.md

@@ -3,7 +3,7 @@ title: "SenservaPro (Preview) connector for Microsoft Sentinel"
 description: "Learn how to install the connector SenservaPro (Preview) to connect your data source to Microsoft Sentinel."
 author: cwatson-cat
 ms.topic: how-to
-ms.date: 01/06/2024
+ms.date: 02/23/2023
 ms.service: microsoft-sentinel
 ms.author: cwatson
 ---
@@ -18,7 +18,7 @@ The SenservaPro data connector provides a viewing experience for your SenservaPr
 | --- | --- |
 | **Log Analytics table(s)** | SenservaPro_CL<br/> |
 | **Data collection rules support** | Not currently supported |
-| **Supported by** | [Senserva](https://www.senserva.com/contact/) |
+| **Supported by** | [Senserva](https://www.senserva.com/support/) |
 
 ## Query samples
 
@@ -199,8 +199,7 @@ let timeframe = 14d;
 
 1. Setup the data connection
 
-Visit [Senserva Setup](https://www.senserva.com/senserva-microsoft-sentinel-edition-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)
-
+Visit [Senserva Setup](https://www.senserva.com/portal/) 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)
 
 
 

articles/sentinel/data-connectors/tenable-io-vulnerability-management-using-azure-function.md

@@ -3,7 +3,7 @@ title: "Tenable.io Vulnerability Management (using Azure Functions) connector fo
 description: "Learn how to install the connector Tenable.io Vulnerability Management (using Azure Function) to connect your data source to Microsoft Sentinel."
 author: cwatson-cat
 ms.topic: how-to
-ms.date: 01/06/2024
+ms.date: 11/29/2023
 ms.service: microsoft-sentinel
 ms.author: cwatson
 ---
@@ -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/nessus/Content/Credentials.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/integrations/BeyondTrust/Nessus/Content/API%20Configuration.htm) to obtain the required API credentials.