Merge pull request #268205 from austinmccollum/austinmc-ccpIPs

add step for network isolation

Author: prmerger-automator[bot]

articles/sentinel/create-codeless-connector.md

@@ -4,7 +4,7 @@ description: Learn how to create a codeless connector in Microsoft Sentinel usin
 author: austinmccollum
 ms.author: austinmc
 ms.topic: how-to
-ms.date: 10/19/2023
+ms.date: 03/06/2024
 ---
 # Create a codeless connector for Microsoft Sentinel (Public preview)
 
@@ -222,13 +222,22 @@ Deploy your codeless connector as a custom template.
 1. Copy the contents of the ARM [deployment template](#create-the-deployment-template).
 1. Follow the **Edit and deploy the template** instructions from the article, [Quickstart: Create and deploy ARM templates by using the Azure portal](../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md#edit-and-deploy-the-template).
 
+### Maintain network isolation for logging source
+
+If your logging source requires network isolation, configure an allowlist of public IP addresses used by the CCP.
+
+Azure virtual networks use service tags to define network access controls. For the CCP, that service tag is [**Scuba**](/azure/virtual-network/service-tags-overview#available-service-tags).
+
+To find the current IP range associated with the **Scuba** service tag, see [Use the Service Tag Discovery API](/azure/virtual-network/service-tags-overview#use-the-service-tag-discovery-api).
+
 ## Verify the codeless connector
 
 View your codeless connector in the data connector gallery. Open the data connector and complete any authentication parameters required to connect. Once successfully connected, the DCR and custom tables are created. View the DCR resource in your resource group and any custom tables from the logs analytics workspace.
 
 >[!NOTE]
 >It may take up to 30 minutes to see data begin ingesting.
 
+
 ## Example
 
 Each step in building the codeless connector is represented in the following example sections.