Merge pull request #264103 from TimShererWithAquent/01242024OPBR

TimShererWithAquent · web-flow · commit 0d68c440ef7d · 2024-01-24T21:57:20.000Z
Address build issues.
diff --git a/articles/ai-services/LUIS/includes/sdk-python.md b/articles/ai-services/LUIS/includes/sdk-python.md
@@ -118,7 +118,7 @@ Create two sets of variables: the first set you change, the second set leave as
 
 ## Authenticate the client
 
-Create an [CognitiveServicesCredentials](/python/api/msrest/msrest.authentication.cognitiveservicescredentials) object with your key, and use it with your endpoint to create an [LUISAuthoringClient](/python/api/azure-cognitiveservices-language-luis/azure.cognitiveservices.language.luis.authoring.luisauthoringclient) object.
+Create an CognitiveServicesCredentials object with your key, and use it with your endpoint to create an [LUISAuthoringClient](/python/api/azure-cognitiveservices-language-luis/azure.cognitiveservices.language.luis.authoring.luisauthoringclient) object.
 
 [!code-python[Authenticate the client](~/cognitive-services-quickstart-code/python/LUIS/sdk-3x/authoring_and_predict.py?name=AuthoringCreateClient)]
 
diff --git a/articles/ai-services/content-moderator/includes/quickstarts/python-sdk.md b/articles/ai-services/content-moderator/includes/quickstarts/python-sdk.md
@@ -86,7 +86,7 @@ These code snippets show you how to do the following tasks with the Content Mode
 
 ## Authenticate the client
 
-Instantiate a client with your endpoint and key. Create a [CognitiveServicesCredentials](/python/api/msrest/msrest.authentication.cognitiveservicescredentials) object with your key, and use it with your endpoint to create an [ContentModeratorClient](/python/api/azure-cognitiveservices-vision-contentmoderator/azure.cognitiveservices.vision.contentmoderator.content_moderator_client.contentmoderatorclient) object.
+Instantiate a client with your endpoint and key. Create a CognitiveServicesCredentials](/python/api/msrest/msrest.authentication.cognitiveservicescredentials object with your key, and use it with your endpoint to create an [ContentModeratorClient](/python/api/azure-cognitiveservices-vision-contentmoderator/azure.cognitiveservices.vision.contentmoderator.content_moderator_client.contentmoderatorclient) object.
 
 [!code-python[](~/cognitive-services-quickstart-code/python/ContentModerator/ContentModeratorQuickstart.py?name=snippet_client)]
 
diff --git a/articles/aks/app-routing-nginx-prometheus.md b/articles/aks/app-routing-nginx-prometheus.md
@@ -21,7 +21,7 @@ The application routing add-on exposes the Prometheus metrics endpoint at `/metr
 ## Prerequisites
 
 - An Azure Kubernetes Service (AKS) cluster with the [application routing add-on enabled][app-routing].
-- A Prometheus instance, such as [Azure Monitor managed service for Prometheus][managed-prometheus-configure].
+- A Prometheus instance, such as Azure Monitor managed service for Prometheus.
 - A Grafana instance, such as [Azure Managed Grafana][managed-grafana].
 
 ## Validating the metrics endpoint
@@ -58,7 +58,7 @@ You can now terminate the `port-forward` process to close the forwarding.
 
 ## Configuring Azure Monitor managed service for Prometheus and Azure Managed Grafana using Container Insights
 
-Azure Monitor managed service for Prometheus is a fully managed Prometheus-compatible service that supports industry standard features such as PromQL, Grafana dashboards, and Prometheus alerts. This service requires configuring the metrics addon for the Azure Monitor agent, which sends data to Prometheus. If your cluster isn't configured with the add-on, you can follow this article to [configure your Azure Kubernetes Service (AKS) cluster to send data to Azure Monitor managed service for Prometheus][managed-prometheus-configure] and send the collected metrics to [an Azure Managed Grafana instance][create-grafana].
+Azure Monitor managed service for Prometheus is a fully managed Prometheus-compatible service that supports industry standard features such as PromQL, Grafana dashboards, and Prometheus alerts. This service requires configuring the metrics addon for the Azure Monitor agent, which sends data to Prometheus. If your cluster isn't configured with the add-on, you can follow this article to configure your Azure Kubernetes Service (AKS) cluster to send data to Azure Monitor managed service for Prometheus and send the collected metrics to [an Azure Managed Grafana instance][create-grafana].
 
 ### Enable pod annotation based scraping
 
diff --git a/articles/azure-maps/how-to-dev-guide-js-sdk.md b/articles/azure-maps/how-to-dev-guide-js-sdk.md
@@ -205,7 +205,7 @@ main().catch((err) => {
 
 ```
 
-This code snippet shows how to use the `MapsSearch` method from the Azure Maps Search client library to create a `client` object with your Azure credentials. You can use either your Azure Maps subscription key or the [Microsoft Entra credential](#using-a-microsoft-entra-credential) from the previous section. The `path` parameter specifies the API endpoint, which is "/search/fuzzy/{format}" in this case. The `get` method sends an HTTP GET request with the query parameters, such as `query`, `coordinates`, and `countryFilter`. The query searches for Starbucks locations near Seattle in the US. The SDK returns the results as a [FuzzySearchResult] object and writes them to the console. For more information, see the [FuzzySearchRequest] documentation.
+This code snippet shows how to use the `MapsSearch` method from the Azure Maps Search client library to create a `client` object with your Azure credentials. You can use either your Azure Maps subscription key or the [Microsoft Entra credential](#using-a-microsoft-entra-credential) from the previous section. The `path` parameter specifies the API endpoint, which is "/search/fuzzy/{format}" in this case. The `get` method sends an HTTP GET request with the query parameters, such as `query`, `coordinates`, and `countryFilter`. The query searches for Starbucks locations near Seattle in the US. The SDK returns the results as a FuzzySearchResult object and writes them to the console. For more information, see the FuzzySearchRequest documentation.
 
 Run `search.js` with Node.js:
 
@@ -215,7 +215,7 @@ node search.js
 
 ## Search an Address
 
-The [searchAddress] query can be used to get the coordinates of an address. Modify the `search.js` from the sample as follows:
+The searchAddress query can be used to get the coordinates of an address. Modify the `search.js` from the sample as follows:
 
 ```JavaScript
 const MapsSearch = require("@azure-rest/maps-search").default;
diff --git a/articles/azure-maps/weather-services-faq.yml b/articles/azure-maps/weather-services-faq.yml
@@ -100,7 +100,7 @@ sections:
       - question: |
           Can I create radar and satellite tile animations? 
         answer: |
-          Yes. In addition to real-time radar and satellite tiles, Azure Maps customers can request past and future tiles to enhance data visualizations with map overlays. Customers can call the [Get Map Tile v2 API](/rest/api/maps/render-v2/get-map-tile) or request tiles via Azure Maps web SDK. Radar tiles are available for up to 1.5 hours in the past, and for up to 2 hours in the future. The tiles are available in 5-minute intervals. Infrared tiles are provided for up to 3 hours in the past, and are available in 10-minute intervals. For more information, see the [Show weather overlays on a map](https://samples.azuremaps.com/?search=Show%20weather%20overlays%20on%20a%20map&sample=) sample.  
+          Yes. In addition to real-time radar and satellite tiles, Azure Maps customers can request past and future tiles to enhance data visualizations with map overlays. Customers can call the Get Map Tile v2 API or request tiles via Azure Maps web SDK. Radar tiles are available for up to 1.5 hours in the past, and for up to 2 hours in the future. The tiles are available in 5-minute intervals. Infrared tiles are provided for up to 3 hours in the past, and are available in 10-minute intervals. For more information, see the [Show weather overlays on a map](https://samples.azuremaps.com/?search=Show%20weather%20overlays%20on%20a%20map&sample=) sample.  
           
       - question: |
           Do you offer icons for different weather conditions? 
diff --git a/articles/azure-monitor/agents/agent-linux.md b/articles/azure-monitor/agents/agent-linux.md
@@ -121,7 +121,7 @@ Regardless of the installation method used, you need the workspace ID and key fo
 :::image type="content" source="media/log-analytics-agent/workspace-details.png" lightbox="media/log-analytics-agent/workspace-details.png" alt-text="Screenshot that shows workspace details.":::
 
 >[!NOTE]
->While regenerating the [Log Analytics Workspace shared keys](/rest/api/loganalytics/workspace-shared-keys) is possible, the intention for this is **not** to immediately restrict access to any agents currently using those keys. Agents use the key to generate a certificate that expires after three months. Regenerating the shared keys will only prevent agents from renewing their certificates, not continuing to use those certificates until they expire.
+>While regenerating the Log Analytics Workspace shared keys is possible, the intention for this is **not** to immediately restrict access to any agents currently using those keys. Agents use the key to generate a certificate that expires after three months. Regenerating the shared keys will only prevent agents from renewing their certificates, not continuing to use those certificates until they expire.
 
 ## Agent install package
 
diff --git a/articles/azure-monitor/agents/agent-windows.md b/articles/azure-monitor/agents/agent-windows.md
@@ -76,7 +76,7 @@ Regardless of the installation method used, you'll require the workspace ID and
 > You can't configure the agent to report to more than one workspace during initial setup. [Add or remove a workspace](agent-manage.md#add-or-remove-a-workspace) after installation by updating the settings from Control Panel or PowerShell.
 
 >[!NOTE]
->While regenerating the [Log Analytics Workspace shared keys](/rest/api/loganalytics/workspace-shared-keys) is possible, the intention for this is **not** to immediately restrict access to any agents currently using those keys. Agents use the key to generate a certificate that expires after three months. Regenerating the shared keys will only prevent agents from renewing their certificates, not continuing to use those certificates until they expire.
+>While regenerating the Log Analytics Workspace shared keys is possible, the intention for this is **not** to immediately restrict access to any agents currently using those keys. Agents use the key to generate a certificate that expires after three months. Regenerating the shared keys will only prevent agents from renewing their certificates, not continuing to use those certificates until they expire.
 
 ## Install the agent 
 
diff --git a/articles/azure-monitor/azure-monitor-rest-api-index.md b/articles/azure-monitor/azure-monitor-rest-api-index.md
@@ -55,7 +55,7 @@ Organized by subject area.
 | ***Manage Log Analytics workspaces and related resources*** |  |
 | [Available service tiers](/rest/api/loganalytics/available-service-tiers) | Retrieve the available service tiers for a Log Analytics workspace. |
 | [Clusters](/rest/api/loganalytics/clusters) | Manage Log Analytics clusters. |
-| [Data Collector Logs (Preview)](/rest/api/loganalytics/data%20collector%20logs%20%28preview%29) | Delete or retrieve a data collector log tables for a Log Analytics workspace and retrieve all data collector log tables for a Log Analytics workspace. |
+| Data Collector Logs (Preview) | Delete or retrieve a data collector log tables for a Log Analytics workspace and retrieve all data collector log tables for a Log Analytics workspace. |
 | [Data exports](/rest/api/loganalytics/data-exports) | Manage a data export for a Log Analytics workspace or retrieve the data export instances within a Log Analytics workspace. |
 | [Data Sources](/rest/api/loganalytics/data-sources) | Create or update data sources. |
 | [Deleted workspaces](/rest/api/loganalytics/deleted-workspaces) | Retrieve the recently deleted workspaces within a subscription or resource group. |
@@ -74,9 +74,9 @@ Organized by subject area.
 | [Storage Insights](/rest/api/loganalytics/storage-insights) | Create or update storage insights. |
 | [Tables](/rest/api/loganalytics/tables) | Manage Log Analytics workspace tables. |
 | [Workspace purge](/rest/api/loganalytics/workspace-purge) | Retrieve the status of an ongoing purge operation or purge the data in a Log Analytics workspace. |
-| [Workspace schema](/rest/api/loganalytics/workspace-schema) | Retrieves the schema for a Log Analytics workspace. |
-| [Workspace shared keys](/rest/api/loganalytics/workspace-shared-keys) | Retrieve or regenerate the shared keys for a Log Analytics workspace. |
-| [Workspace usages](/rest/api/loganalytics/workspace-usages) | Retrieve the usage metrics for a Log Analytics workspace. |
+| Workspace schema | Retrieves the schema for a Log Analytics workspace. |
+| Workspace shared keys | Retrieve or regenerate the shared keys for a Log Analytics workspace. |
+| Workspace usages | Retrieve the usage metrics for a Log Analytics workspace. |
 | [Workspaces](/rest/api/loganalytics/workspaces) | Manage Log Analytics workspaces. |
 | ***Metrics*** |  |
 | [Azure Monitor Workspaces](/rest/api/monitor/azure-monitor-workspaces) | Manage an Azure Monitor workspace and retrieve the Azure Monitor workspaces within a resource group or subscription. |
diff --git a/articles/managed-ccf/how-to-backup-restore-resource.md b/articles/managed-ccf/how-to-backup-restore-resource.md
@@ -17,7 +17,7 @@ In this article, you'll learn to perform backup of an Azure Managed CCF (Managed
 - A Managed CCF resource is an append only ledger at the core. It is impossible to delete few erroneous transactions without impacting the integrity of the ledger. To keep the data clean, a business could decide to recreate the resource sans the erroneous transactions.  
 - A developer could add reference data into a Managed CCF resource and create a back of it. The developer can use the copy later to create a fresh Managed CCF resource and save time.
 
-This article uses the commands found at the [Managed CCF's REST API Docs](/rest/api/confidentialledger/managed-ccf).
+This article uses the commands found at the Managed CCF's REST API Docs.
 
 ## Prerequisites
 
diff --git a/articles/sentinel/create-codeless-connector-legacy.md b/articles/sentinel/create-codeless-connector-legacy.md
@@ -585,7 +585,7 @@ After creating your [JSON configuration file](#create-a-connector-json-configura
 
     # [Connect via API](#tab/connect-via-api)
 
-    Use the [CONNECT](/rest/api/securityinsights/preview/data-connectors/connect) endpoint to send a PUT method and pass the JSON configuration directly in the body of the message. For more information, see [auth configuration](#auth-configuration).
+    Use the CONNECT endpoint to send a PUT method and pass the JSON configuration directly in the body of the message. For more information, see [auth configuration](#auth-configuration).
 
     Use the following API attributes, depending on the [authType](#authtype) defined. For each `authType` parameter, all listed attributes are mandatory and are string values.
 
diff --git a/articles/sentinel/create-codeless-connector.md b/articles/sentinel/create-codeless-connector.md
@@ -103,7 +103,7 @@ To understand how to create a complex DCR with multiple data flows, see the [DCR
 
 This component renders the UI for the data connector in the Microsoft Sentinel data connector gallery. Each data connector may have only one UI definition. 
 
-Build the data connector user interface with the [**Data Connector Definition**](/rest/api/securityinsights/preview/data-connector-definitions/create-or-update) API. Use the [Data connector definitions reference](data-connector-ui-definitions-reference.md) as a supplement to explain the API elements in greater detail.
+Build the data connector user interface with the **Data Connector Definition** API. Use the [Data connector definitions reference](data-connector-ui-definitions-reference.md) as a supplement to explain the API elements in greater detail.
 
 Notes: 
 1)	The `kind` property for API polling connector should always be `Customizable`.
diff --git a/articles/sentinel/data-connector-ui-definitions-reference.md b/articles/sentinel/data-connector-ui-definitions-reference.md
@@ -12,15 +12,15 @@ ms.author: austinmc
 
 # Data connector definitions reference for the Codeless Connector Platform
 
-To create a data connector with the Codeless Connector Platform (CCP), use this document as a supplement to the [Microsoft Sentinel REST API for Data Connector Definitions](/rest/api/securityinsights/data-connector-definitions) reference docs. Specifically this reference document expands on the following section:
+To create a data connector with the Codeless Connector Platform (CCP), use this document as a supplement to the Microsoft Sentinel REST API for Data Connector Definitions reference docs. Specifically this reference document expands on the following section:
 
 - `connectorUiConfig` - defines the visual elements and text displayed on the data connector page in Microsoft Sentinel.
 
 For more information, see [Create a codeless connector](create-codeless-connector.md).
 
 ## Data connector definitions - Create or update
 
-Reference the [Create Or Update](/rest/api/securityinsights/data-connector-definitions/create-or-update) operation in the REST API docs to find the latest stable or preview API version. The difference between the `create` and the `update` operation is the update requires the `etag` value.
+Reference the Create Or Update operation in the REST API docs to find the latest stable or preview API version. The difference between the `create` and the `update` operation is the update requires the `etag` value.
 
 **PUT** method
 ```http
@@ -67,7 +67,7 @@ The following screenshot shows a sample data connector page, highlighted with nu
 
 :::image type="content" source="media/create-codeless-connector/sample-data-connector-page.png" alt-text="Screenshot of a sample data connector page with sections labeled 1 through 9.":::
 
-Each of the following elements of the `connectorUiConfig` section needed to configure the user interface correspond to the [CustomizableConnectorUiConfig](/rest/api/securityinsights/data-connector-definitions/create-or-update#customizableconnectoruiconfig) portion of the API.
+Each of the following elements of the `connectorUiConfig` section needed to configure the user interface correspond to the CustomizableConnectorUiConfig portion of the API.
 
 |Field | Required | Type | Description | Screenshot notable area #|
 | ---- | ---- | ---- | ---- | ---- |
@@ -335,7 +335,7 @@ Some **InstallAgent** types appear as a button, others appear as a link. Here ar
 
 ## Example data connector definition
 
-The following example brings together some of the components defined in this article as a JSON body format to use with the [Create Or Update](/rest/api/securityinsights/data-connector-definitions/create-or-update) data connector API.
+The following example brings together some of the components defined in this article as a JSON body format to use with the Create Or Update data connector API.
 
 For more examples of the `connectorUiConfig` review [other CCP data connectors](https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors#codeless-connector-platform-ccp-preview--native-microsoft-sentinel-polling). Even connectors using the legacy CCP have valid examples of the UI creation.
 
diff --git a/articles/sentinel/threat-intelligence-integration.md b/articles/sentinel/threat-intelligence-integration.md
@@ -154,7 +154,7 @@ For more information about how to find and manage the solutions, see [Discover a
 ### ReversingLabs TitaniumCloud
 
 - Find and enable incident enrichment playbooks for [ReversingLabs](https://www.reversinglabs.com/products/file-reputation-service) in the [Microsoft Sentinel GitHub repository](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/ReversingLabs/Playbooks/ReversingLabs-EnrichFileHash).
-- See the ReversingLabs Intelligence Logic App [connector documentation](/connectors/reversinglabsintelligence/).
+- See the ReversingLabs Intelligence Logic App connector documentation.
 
 ### RiskIQ Passive Total
 
diff --git a/articles/sentinel/workspace-manager.md b/articles/sentinel/workspace-manager.md
@@ -122,11 +122,11 @@ Common reasons for failure include:
 - Currently, deleting content residing in member workspace(s) centrally via workspace manager isn't supported.
 
 ### API references
-- [Workspace Manager Assignment Jobs](/rest/api/securityinsights/preview/workspace-manager-assignment-jobs)
-- [Workspace Manager Assignments](/rest/api/securityinsights/preview/workspace-manager-assignments)
+- Workspace Manager Assignment Jobs
+- Workspace Manager Assignments
 - *Workspace Manager Configurations*
-- [Workspace Manager Groups](/rest/api/securityinsights/preview/workspace-manager-groups)
-- [Workspace Manager Members](/rest/api/securityinsights/preview/workspace-manager-members)
+- Workspace Manager Groups
+- Workspace Manager Members
 
 ## Next steps
 - [Manage multiple tenants in Microsoft Sentinel as an MSSP](multiple-tenants-service-providers.md)
