Fix broken link in Monitor Ingestion README (Azure#25939)

Author: scottaddie

sdk/monitor/azure-monitor-ingestion/README.md

@@ -2,8 +2,7 @@
 
 The Azure Monitor Ingestion client library is used to send custom logs to [Azure Monitor][azure_monitor_overview].
 
-This library allows you to send data from virtually any source to supported built-in tables or to custom tables 
-that you create in Log Analytics workspace. You can even extend the schema of built-in tables with custom columns.
+This library allows you to send data from virtually any source to supported built-in tables or to custom tables that you create in Log Analytics workspace. You can even extend the schema of built-in tables with custom columns.
 
 **Resources:**
 
@@ -24,7 +23,7 @@ _Azure SDK Python packages support for Python 2.7 has ended on 01 January 2022.
 
 - Python 3.6 or later
 - An [Azure subscription][azure_subscription]
-- An [Azure Log Analytics workspace][azure_monitor_create_using_portal].
+- An [Azure Log Analytics workspace][azure_monitor_create_using_portal]
 - A [Data Collection Endpoint][data_collection_endpoint]
 - A [Data Collection Rule][data_collection_rule]
 
@@ -36,7 +35,6 @@ Install the Azure Monitor Ingestion client library for Python with [pip][pip]:
 pip install azure-monitor-ingestion
 ```
 
-
 ### Create the client
 
 An authenticated client is required to upload Logs to Azure Monitor. The library includes both synchronous and asynchronous forms of the clients. To authenticate, create an instance of a token credential. Use that instance when creating a `LogsIngestionClient`. The following examples use `DefaultAzureCredential` from the [azure-identity](https://pypi.org/project/azure-identity/) package.
@@ -73,26 +71,19 @@ logs_client = LogsIngestionClient(endpoint, credential)
 
 ### Data Collection Endpoint
 
-Data Collection Endpoints (DCEs) allow you to uniquely configure ingestion settings for Azure Monitor. [This 
-article][data_collection_endpoint] provides an overview of data collection endpoints including their contents and 
-structure and how you can create and work with them.
+Data Collection Endpoints (DCEs) allow you to uniquely configure ingestion settings for Azure Monitor. [This article][data_collection_endpoint] provides an overview of data collection endpoints including their contents and structure and how you can create and work with them.
 
 ### Data Collection Rule
 
-Data collection rules (DCR) define data collected by Azure Monitor and specify how and where that data should be sent or
-stored. The REST API call must specify a DCR to use. A single DCE can support multiple DCRs, so you can specify a
-different DCR for different sources and target tables.
+Data collection rules (DCR) define data collected by Azure Monitor and specify how and where that data should be sent or stored. The REST API call must specify a DCR to use. A single DCE can support multiple DCRs, so you can specify a different DCR for different sources and target tables.
 
-The DCR must understand the structure of the input data and the structure of the target table. If the two don't match,
-it can use a transformation to convert the source data to match the target table. You may also use the transform to
-filter source data and perform any other calculations or conversions.
+The DCR must understand the structure of the input data and the structure of the target table. If the two don't match, it can use a transformation to convert the source data to match the target table. You may also use the transform to filter source data and perform any other calculations or conversions.
 
 For more details, refer to [Data collection rules in Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/essentials/data-collection-rule-overview).
 
 ### Log Analytics Workspace Tables
 
-Custom logs can send data to any custom table that you create and to certain built-in tables in your Log Analytics 
-workspace. The target table must exist before you can send data to it. The following built-in tables are currently supported:
+Custom logs can send data to any custom table that you create and to certain built-in tables in your Log Analytics workspace. The target table must exist before you can send data to it. The following built-in tables are currently supported:
 
 - [CommonSecurityLog](https://docs.microsoft.com/azure/azure-monitor/reference/tables/commonsecuritylog)
 - [SecurityEvents](https://docs.microsoft.com/azure/azure-monitor/reference/tables/securityevent)
@@ -105,7 +96,7 @@ workspace. The target table must exist before you can send data to it. The follo
 
 ### Upload custom logs
 
-This example shows uploading logs to Azure monitor.
+This example shows uploading logs to Azure Monitor.
 
 ```python
 import os
@@ -177,6 +168,7 @@ This project has adopted the [Microsoft Open Source Code of Conduct][code_of_con
 
 [azure_core_exceptions]: https://aka.ms/azsdk/python/core/docs#module-azure.core.exceptions
 [azure_core_ref_docs]: https://aka.ms/azsdk/python/core/docs
+[azure_monitor_create_using_portal]: https://docs.microsoft.com/azure/azure-monitor/logs/quick-create-workspace
 [azure_monitor_overview]: https://docs.microsoft.com/azure/azure-monitor/
 [azure_subscription]: https://azure.microsoft.com/free/python/
 [changelog]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/monitor/azure-monitor-ingestion/CHANGELOG.md