(AzureCXP) fixes MicrosoftDocs/azure-docs#110036

Updates the discrepancy in the regionality of the DCE with respect to Workspace. For this particular scenario, the DCR, DCR and Workspace need to be in the same region as verified from the portal.

Author: AnuragSingh-MSFT

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

@@ -62,7 +62,7 @@ Start by registering an Azure Active Directory application to authenticate again
     :::image type="content" source="media/tutorial-logs-ingestion-portal/new-app-secret-value.png" lightbox="media/tutorial-logs-ingestion-portal/new-app-secret-value.png" alt-text="Screenshot that shows the secret value for the new app.":::
 
 ## Create data collection endpoint
-A [data collection endpoint](../essentials/data-collection-endpoint-overview.md) is required to accept the data from the script. After you configure the DCE and link it to a DCR, you can send data over HTTP from your application. The DCE does not need to be in the same region as the Log Analytics workspace where the data will be sent or the data collection rule being used.
+A [data collection endpoint](../essentials/data-collection-endpoint-overview.md) is required to accept the data from the script. After you configure the DCE and link it to a DCR, you can send data over HTTP from your application. The DCE needs to be in the same region as the Log Analytics workspace where the data will be sent or the data collection rule being used.
 
 1. To create a new DCE, go to the **Monitor** menu in the Azure portal. Select **Data Collection Endpoints** and then select **Create**.