updates

Author: bwren

articles/azure-monitor/essentials/data-collection-endpoint-overview.md

@@ -15,13 +15,13 @@ ms.reviwer: nikeist
 A data collection endpoint (DCE) is a connection where data sources send collected data for processing and ingestion into Azure Monitor. This article provides an overview of data collection endpoints and explains how to create and set them up based on your deployment.
 
 ## When is a DCE required?
-Prior to March 31, 2024, a DCE was required for all data collection scenarios using a DCR that required an endpoint. Any DCR created after this date includes its own endpoints for logs and metrics. The URL for these endpoints can be found in the [`logsIngestion` and `metricsIngestion`](./data-collection-rule-structure.md#endpoints) properties of the DCR. These endpoints can be used instead of a DCE for most scenarios.
+Prior to March 31, 2024, a DCE was required for all data collection scenarios using a DCR that required an endpoint. Any DCR created after this date includes its own endpoints for logs and metrics. The URL for these endpoints can be found in the [`logsIngestion` and `metricsIngestion`](./data-collection-rule-structure.md#endpoints) properties of the DCR. These endpoints can be used instead of a DCE for any direct ingestion scenarios.
 
 Endpoints cannot be added to an existing DCR, but you can keep using any existing DCRs with existing DCEs. If you want to move to a DCR endpoint, then you must create a new DCR to replace the existing one. A DCR with endpoints can also use a DCE. In this case, you can choose whether to use the DCE or the DCR endpoints for each of the clients that use the DCR.
 
-The following scenarios can't use the DCR endpoints and require a DCE:
+The following scenarios can currently use DCR endpoints.  A DCE required if private link is used.
 
-- [Private link](../logs/private-link-security.md)
+- [Logs ingestion API](../logs/logs-ingestion-api-overview.md).
 
 
 ## Components of a DCE
@@ -129,7 +129,6 @@ The sample data collection endpoint (DCE) below is for virtual machines with Azu
 
 - Data collection endpoints only support Log Analytics workspaces as a destination for collected data. [Custom metrics (preview)](../essentials/metrics-custom-overview.md) collected and uploaded via Azure Monitor Agent aren't currently controlled by DCEs.
 
-- Data collection endpoints are where [Logs ingestion API ingestion limits](../service-limits.md#logs-ingestion-api) are applied.
 
 ## Next steps
 - [Associate endpoints to machines](../agents/data-collection-rule-azure-monitor-agent.md#create-a-data-collection-rule)

articles/azure-monitor/essentials/data-collection-rule-samples.md

@@ -286,6 +286,8 @@ The sample [data collection rule](../essentials/data-collection-rule-overview.md
 - Sends data to a table called MyTable_CL in a workspace called my-workspace.
 - Applies a [transformation](../essentials//data-collection-transformations.md) to the incoming data.
 
+> [!NOTE]
+> Logs ingestion API requires the [logsIngestion](../essentials/data-collection-rule-structure.md#endpoints) property which includes the URL of the endpoint. This property is added to the DCR after it's created.
 
 ```json
 {

articles/azure-monitor/essentials/data-collection-rule-structure.md

@@ -36,9 +36,7 @@ Contains the URLs of the endpoints for the DCR. This section and its properties
 | `metricsIngestion` | URL for ingestion endpoint for metric data.  |
 
 **Scenarios**
-- Azure Monitor agent
 - Logs ingestion API
-- Events Hubs
 
 ## `dataCollectionEndpointId` 
 Specifies the [data collection endpoint (DCE)](data-collection-endpoint-overview.md) used by the DCR.

articles/azure-monitor/logs/tutorial-logs-ingestion-api.md

@@ -248,7 +248,7 @@ The [DCR](../essentials/data-collection-rule-overview.md) defines how the data w
 
     :::image type="content" source="media/tutorial-workspace-transformations-api/data-collection-rule-details.png" lightbox="media/tutorial-workspace-transformations-api/data-collection-rule-details.png" alt-text="Screenshot that shows DCR details.":::
 
-1. Copy the **Immutable ID** and **Logs ingestion URI** for the DCR. You'll use these in a later step when you send sample data using the API.
+1. Copy the **Immutable ID** and **Logs ingestion URI** for the DCR. You'll use these when you [send data to Azure Monitor using the API](./tutorial-logs-ingestion-code.md).
 
     :::image type="content" source="media/tutorial-logs-ingestion-api/data-collection-rule-json-view.png" lightbox="media/tutorial-logs-ingestion-api/data-collection-rule-json-view.png" alt-text="Screenshot that shows DCR JSON view.":::
 

articles/azure-monitor/logs/tutorial-logs-ingestion-code.md

@@ -12,6 +12,10 @@ This article provides sample code using the [Logs ingestion API](logs-ingestion-
 - Custom table in a Log Analytics workspace
 - Data collection rule (DCR) to direct the data to the target table
 - Microsoft Entra application with access to the DCR
+- Data collection endpoint (DCE) if you're using private link. Otherwise, use the DCR logs endpoint.
+
+
+
 
 ## Sample code