Merge pull request #235710 from richagaur/richagaur/dts-mongo-api-preview-update

updated intra-account container copy docs

Author: prmerger-automator[bot]

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

@@ -15,27 +15,27 @@ ms.reviewer: sidandrews
 
 [Container copy jobs](intra-account-container-copy.md) help create offline copies of containers within an Azure Cosmos DB account.
 
-This article describes how to create, monitor, and manage intra-account container copy jobs using Azure PowerShell or CLI commands.
+This article describes how to create, monitor, and manage intra-account container copy jobs using Azure CLI commands.
 
 ## Prerequisites
 
-* 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.
+* 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) 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.
 
 
 ## Install the Azure Cosmos DB preview extension
 
 This extension contains the container copy commands.
 
-```azurepowershell-interactive
+```azurecli-interactive
 az extension add --name cosmosdb-preview
 ```
 
 ## Set shell variables
 
 First, set all of the variables that each individual script uses.
 
-```azurepowershell-interactive
+```azurecli-interactive
 $resourceGroup = "<resource-group-name>"
 $accountName = "<cosmos-account-name>"
 $jobName = ""
@@ -49,7 +49,7 @@ $destinationContainer = ""
 
 Create a job to copy a container within an Azure Cosmos DB API for NoSQL account:
 
-```azurepowershell-interactive
+```azurecli-interactive
 az cosmosdb dts copy `
     --resource-group $resourceGroup `
     --account-name $accountName `
@@ -62,7 +62,7 @@ az cosmosdb dts copy `
 
 Create a job to copy a container within an Azure Cosmos DB API for Cassandra account:
 
-```azurepowershell-interactive
+```azurecli-interactive
 az cosmosdb dts copy `
     --resource-group $resourceGroup `
     --account-name $accountName `
@@ -76,7 +76,7 @@ az cosmosdb dts copy `
 
 View the progress and status of a copy job:
 
-```azurepowershell-interactive
+```azurecli-interactive
 az cosmosdb dts show `
     --resource-group $resourceGroup `
     --account-name $accountName `
@@ -87,7 +87,7 @@ az cosmosdb dts show `
 
 To list all the container copy jobs created in an account:
 
-```azurepowershell-interactive
+```azurecli-interactive
 az cosmosdb dts list `
     --resource-group $resourceGroup `
     --account-name $accountName
@@ -97,7 +97,7 @@ az cosmosdb dts list `
 
 In order to pause an ongoing container copy job, you may use the command:
 
-```azurepowershell-interactive
+```azurecli-interactive
 az cosmosdb dts pause `
     --resource-group $resourceGroup `
     --account-name $accountName `
@@ -108,7 +108,7 @@ az cosmosdb dts pause `
 
 In order to resume an ongoing container copy job, you may use the command:
 
-```azurepowershell-interactive
+```azurecli-interactive
 az cosmosdb dts resume `
     --resource-group $resourceGroup `
     --account-name $accountName `

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

@@ -70,6 +70,22 @@ The rate of container copy job progress is determined by these factors:
     > [!IMPORTANT]
     > The default SKU offers two 4-vCPU 16-GB server-side instances per account.
 
+## Limitations
+
+### Preview eligibility criteria
+
+Container copy jobs don't work with accounts having following capabilities enabled. You will need to disable these features before running the container copy jobs.
+
+- [Disable local auth](https://learn.microsoft.com/azure/cosmos-db/how-to-setup-rbac#use-azure-resource-manager-templates)
+- [Private endpoint / IP Firewall enabled](https://learn.microsoft.com/azure/cosmos-db/how-to-configure-firewall#allow-requests-from-global-azure-datacenters-or-other-sources-within-azure). You will need to provide access to connections within public Azure datacenters to run container copy jobs.
+- [Merge partition](https://learn.microsoft.com/azure/cosmos-db/merge).
+
+
+### Account Configurations
+
+- The time-to-live (TTL) setting is not adjusted in the destination container. As a result, if a document has not expired in the source container, it will start its countdown anew in the destination container.
+
+
 ## FAQs
 
 ### Is there an SLA for the container copy jobs?
@@ -92,11 +108,6 @@ The container copy job runs in the write region. If there are accounts configure
 
 The account's write region may change in the rare scenario of a region outage or due to manual failover. In such a scenario, incomplete container copy jobs created within the account would fail. You would need to recreate these failed jobs. Recreated jobs would then run in the new (current) write region.
 
-### 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 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
 
@@ -126,19 +137,10 @@ Currently, container copy is supported in the following regions:
     Make sure the target container is created before running the job as specified in the [overview section.](#overview-of-steps-needed-to-do-container-copy)
 
     ```output
-    "code": "500",
+    "code": "404",
     "message": "Response status code does not indicate success: NotFound (404); Substatus: 1003; ActivityId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx; Reason: (Message: {\"Errors\":[\"Owner resource does not exist\"]
     ```
 
-* Error - Shared throughput database creation isn't supported for serverless accounts
-
-    Job creation on serverless accounts may fail with the error *"Shared throughput database creation isn't supported for serverless accounts"*.
-    As a work-around, create a database called *__datatransferstate* manually within the account and try creating the container copy job again.
-
-    ```output
-    ERROR: (BadRequest) Response status code does not indicate success: BadRequest (400); Substatus: 0; ActivityId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx; Reason: (Shared throughput database creation is not supported for serverless accounts.
-    ```
-
 * 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](/azure/cloud-shell/quickstart?tabs=powershell).
@@ -147,6 +149,17 @@ Currently, container copy is supported in the following regions:
     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
     ActivityId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
     ```
+* Error - Error while getting resources for job.
+
+    This error can occur due to internal server issues. To resolve this issue, contact Microsoft support by raising a **New Support Request** from the Azure portal. Set the Problem Type as **'Data Migration'** and Problem subtype as **'Intra-account container copy'**.
+
+    ```output
+    "code": "500"
+    "message": "Error while getting resources for job, StatusCode: 500, SubStatusCode: 0, OperationId:  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, ActivityId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+    ``` 
+	
+
+
 
 ## Next steps