Merge pull request #230730 from sdwheeler/sdw-fix-cloud-shell-links

Update links to cloud-shell docs

Author: Court72

articles/cognitive-services/openai/how-to/monitoring.md

@@ -1,8 +1,8 @@
 ---
-title: Monitoring Azure OpenAI Service 
-description: Start here to learn how to monitor Azure OpenAI Service  
-author: mrbullwinkle 
-ms.author: mbullwin 
+title: Monitoring Azure OpenAI Service
+description: Start here to learn how to monitor Azure OpenAI Service
+author: mrbullwinkle
+ms.author: mbullwin
 ms.service: cognitive-services
 ms.subservice: openai
 ms.topic: how-to
@@ -18,7 +18,7 @@ This article describes the monitoring data generated by Azure OpenAI Service. Az
 
 ## Monitoring data
 
-Azure OpenAI collects the same kinds of monitoring data as other Azure resources that are described in [Monitoring data from Azure resources](../../../azure-monitor/essentials/monitor-azure-resource.md#monitoring-data).
+Azure OpenAI collects the same kinds of monitoring data as other Azure resources that are described in [Monitoring data from Azure resources](/azure/azure-monitor/essentials/monitor-azure-resource#monitoring-data-from-azure-resources).
 
 ## Collection and routing
 
@@ -28,7 +28,7 @@ Resource Logs aren't collected and stored until you create a diagnostic setting
 
 See [Create diagnostic setting to collect platform logs and metrics in Azure](/azure/azure-monitor/platform/diagnostic-settings) for the detailed process for creating a diagnostic setting using the Azure portal, CLI, or PowerShell. When you create a diagnostic setting, you specify which categories of logs to collect.
 
-Keep in mind that using diagnostic settings and sending data to Azure Monitor Logs has additional costs associated with it. To understand more, consult the [Azure Monitor cost calculation guide](../../../azure-monitor/logs/cost-logs.md).  
+Keep in mind that using diagnostic settings and sending data to Azure Monitor Logs has additional costs associated with it. To understand more, consult the [Azure Monitor cost calculation guide](/azure/azure-monitor/logs/cost-logs).
 
 The metrics and logs you can collect are discussed in the following sections.
 
@@ -59,13 +59,13 @@ For the current subset of metrics available in Azure OpenAI:
 
 ## Analyzing logs
 
-Data in Azure Monitor Logs is stored in tables where each table has its own set of unique properties.  
+Data in Azure Monitor Logs is stored in tables where each table has its own set of unique properties.
 
 All resource logs in Azure Monitor have the same fields followed by service-specific fields. The common schema is outlined in [Azure Monitor resource log schema](../../../azure-monitor/essentials/resource-logs-schema.md).
 
-The [Activity log](../../../azure-monitor/essentials/activity-log.md) is a type of platform log in Azure that provides insight into subscription-level events. You can view it independently or route it to Azure Monitor Logs, where you can do much more complex queries using Log Analytics.  
+The [Activity log](/azure/azure-monitor/essentials/activity-log) is a type of platform log in Azure that provides insight into subscription-level events. You can view it independently or route it to Azure Monitor Logs, where you can do much more complex queries using Log Analytics.
 
-For a list of the types of resource logs available for Azure OpenAI and other Cognitive Services, see [Resource provider operations for Cognitive Services](../../../role-based-access-control/resource-provider-operations.md#microsoftcognitiveservices)  
+For a list of the types of resource logs available for Azure OpenAI and other Cognitive Services, see [Resource provider operations for Cognitive Services](/azure/role-based-access-control/resource-provider-operations#microsoftcognitiveservices)
 
 ### Kusto queries
 
@@ -111,10 +111,10 @@ Every organization's alerting needs are going to vary, and will also evolve over
 
 Errors below certain thresholds can often be evaluated through regular analysis of data in Azure Monitor Logs. As you analyze your log data over time, you may also find that a certain condition not occurring for a long enough period of time might be valuable to track with alerts. Sometimes the absence of an event in a log is just as important a signal as an error.
 
-Depending on what type of application you're developing in conjunction with your use of Azure OpenAI, [Azure Monitor Application Insights](../../../azure-monitor/overview.md#insights-and-visualizations) may offer additional monitoring benefits at the application layer.
+Depending on what type of application you're developing in conjunction with your use of Azure OpenAI, [Azure Monitor Application Insights](../../../azure-monitor/overview.md) may offer additional monitoring benefits at the application layer.
 
 
 ## Next steps
 
 - See [Monitoring Azure resources with Azure Monitor](../../../azure-monitor/essentials/monitor-azure-resource.md) for details on monitoring Azure resources.
-- Read [Understand log searches in Azure Monitor logs](../../../azure-monitor/logs/log-query-overview.md).
+- Read [Understand log searches in Azure Monitor logs](../../../azure-monitor/logs/log-query-overview.md).

articles/cosmos-db/how-to-container-copy.md

@@ -17,9 +17,9 @@ ms.reviewer: sidandrews
 
 This article describes how to create, monitor, and manage intra-account container copy jobs using Azure PowerShell or CLI commands.
 
-## Pre-requisites
+## Prerequisites
 
-* You may use the portal [Cloud Shell](../cloud-shell/quickstart-powershell.md#start-cloud-shell) to run container copy commands. Alternately, you may run the commands locally; make sure you have [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/install-az-ps-msi) downloaded and installed on your machine.
+* You may use the portal [Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell) to run container copy commands. Alternately, you may run the commands locally; make sure you have [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/install-az-ps-msi) downloaded and installed on your machine.
 * Currently, container copy is only supported in [these regions](intra-account-container-copy.md#supported-regions). Make sure your account's write region belongs to this list.
 
 
@@ -33,7 +33,7 @@ az extension add --name cosmosdb-preview
 
 ## Set shell variables
 
-First, set all of the variables that each individual script will use.
+First, set all of the variables that each individual script uses.
 
 ```azurepowershell-interactive
 $resourceGroup = "<resource-group-name>"
@@ -51,7 +51,7 @@ Create a job to copy a container within an Azure Cosmos DB API for NoSQL account
 
 ```azurepowershell-interactive
 az cosmosdb dts copy `
-    --resource-group $resourceGroup ` 
+    --resource-group $resourceGroup `
     --account-name $accountName `
     --job-name $jobName `
     --source-sql-container database=$sourceDatabase container=$sourceContainer `
@@ -116,7 +116,7 @@ az cosmosdb dts resume `
 ```
 
 ## Get support for container copy issues
-For issues related to intra-account container copy, please raise a New Support Request from the Azure Portal with the Problem Type as 'Data Migration' and Problem subtype as 'Intra-account container copy'.
+For issues related to intra-account container copy, please raise a **New Support Request** from the Azure portal. Set the **Problem Type** as 'Data Migration' and **Problem subtype** as 'Intra-account container copy'.
 
 
 ## Next steps

articles/cosmos-db/intra-account-container-copy.md

@@ -30,7 +30,7 @@ Intra-account container copy jobs can be [created and managed using CLI commands
 
 ## Get started
 
-To get started using container copy jobs, register for "Intra-account offline container copy (Cassandra & SQL)" preview from the ['Preview Features'](access-previews.md) list in the Azure portal. Once the registration is complete, the preview will be effective for all Cassandra and API for NoSQL accounts in the subscription.
+To get started using container copy jobs, register for "Intra-account offline container copy (Cassandra & SQL)" preview from the ['Preview Features'](access-previews.md) list in the Azure portal. Once the registration is complete, the preview is effective for all Cassandra and API for NoSQL accounts in the subscription.
 
 ## Overview of steps needed to do container copy
 
@@ -49,7 +49,7 @@ Intra-account container copy jobs perform offline data copy using the source con
 * The container copy jobs run on these instances.
 * A single job is executed across all instances at any time.
 * The instances are shared by all the container copy jobs running within the same account.
-* The platform may de-allocate the instances if they're idle for >15 mins.
+* The platform may deallocate the instances if they're idle for >15 mins.
 
 > [!NOTE]
 > We currently only support offline container copy jobs. So, we strongly recommend to stop performing any operations on the source container prior to beginning the container copy. Item deletions and updates done on the source container after beginning the copy job may not be captured. Hence, continuing to perform operations on the source container while the container job is in progress may result in additional or missing data on the target container.
@@ -78,15 +78,15 @@ Container copy jobs are currently supported on best-effort basis. We don't provi
 
 ### Can I create multiple container copy jobs within an account?
 
-Yes, you can create multiple jobs within the same account. The jobs will run consecutively. You can [list all the jobs](how-to-container-copy.md#list-all-the-container-copy-jobs-created-in-an-account) created within an account and monitor their progress.
+Yes, you can create multiple jobs within the same account. The jobs run consecutively. You can [list all the jobs](how-to-container-copy.md#list-all-the-container-copy-jobs-created-in-an-account) created within an account and monitor their progress.
 
 ### Can I copy an entire database within the Azure Cosmos DB account?
 
-You'll have to create a job for each container in the database.
+You must create a job for each container in the database.
 
 ### I have an Azure Cosmos DB account with multiple regions. In which region will the container copy job run?
 
-The container copy job will run in the write region. If there are accounts configured with multi-region writes, the job will run in one of the regions from the list.
+The container copy job runs in the write region. If there are accounts configured with multi-region writes, the job runs in one of the regions from the list.
 
 ### What happens to the container copy jobs when the account's write region changes?
 
@@ -95,8 +95,8 @@ The account's write region may change in the rare scenario of a region outage or
 ### Why is a new database *__datatransferstate* created in the account when I run container copy jobs? Am I being charged for this database?
 
 * *__datatransferstate* is a database that is created while running container copy jobs. This database is used by the platform to store the state and progress of the copy job.
-* The database uses manual provisioned throughput of 800 RUs. You'll be charged for this database.
-* Deleting this database will remove the container copy job history from the account. It can be safely deleted once all the jobs in the account have completed, if you no longer need the job history. The platform won't clean up the *__datatransferstate* database automatically.
+* The database uses manual provisioned throughput of 800 RUs. You are charged for this database.
+* Deleting this database removes the container copy job history from the account. It can be safely deleted once all the jobs in the account have completed, if you no longer need the job history. The platform doesn't clean up the *__datatransferstate* database automatically.
 
 ## Supported regions
 
@@ -141,7 +141,7 @@ Currently, container copy is supported in the following regions:
 
 * Error - (Request) is blocked by your Cosmos DB account firewall settings.
 
-    The job creation request could be blocked if the client IP isn't allowed as per the VNet and Firewall IPs configured on the account. In order to get past this issue, you need to [allow access to the IP through the Firewall setting](how-to-configure-firewall.md). Alternately, you may set **Accept connections from within public Azure datacenters** in your firewall settings and run the container copy commands through the portal [Cloud Shell](../cloud-shell/quickstart-powershell.md#start-cloud-shell).
+    The job creation request could be blocked if the client IP isn't allowed as per the VNet and Firewall IPs configured on the account. In order to get past this issue, you need to [allow access to the IP through the Firewall setting](how-to-configure-firewall.md). Alternately, you may set **Accept connections from within public Azure datacenters** in your firewall settings and run the container copy commands through the portal [Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell).
 
     ```output
     InternalServerError Request originated from IP xxx.xxx.xxx.xxx through public internet. This is blocked by your Cosmos DB account firewall settings. More info: https://aka.ms/cosmosdb-tsg-forbidden