Merge pull request #271769 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: rmca14

articles/azure-large-instances/workloads/epic/create-a-volume-group.md

@@ -71,12 +71,12 @@ Expected output: lists all the logical volumes created.
 [root @themetal05 ~] chown root:root /prod
 ```
 
-8. Add mount to /etc/fstab
+8. Add mount entries to /etc/fstab
 
 ```azurecli 
-[root @themetal05 ~] /dev/mapper/prodvg-prod01 /prod01 xfs defaults 0 0
-[root @themetal05 ~] /dev/mapper/jrnvg-jrn /jrn xfs defaults 0 0 
-[root @themetal05 ~] /dev/mapper/instvg-prd /prd xfs defaults 0 0
+/dev/mapper/prodvg-prod01 /prod01 xfs defaults 0 0
+/dev/mapper/jrnvg-jrn /jrn xfs defaults 0 0 
+/dev/mapper/instvg-prd /prd xfs defaults 0 0
 ```
 
 9. Mount storage

articles/azure-resource-manager/bicep/deployment-script-bicep.md

@@ -407,6 +407,7 @@ The following table lists the error codes for the deployment script:
 | `DeploymentScriptStorageAccountAccessKeyNotSpecified` | The access key wasn't specified for the existing storage account.|
 | `DeploymentScriptContainerGroupContainsInvalidContainers` | A container group that the deployment script service created was externally modified, and invalid containers were added. |
 | `DeploymentScriptContainerGroupInNonterminalState` | Two or more deployment script resources use the same Azure container instance name in the same resource group, and one of them hasn't finished its execution yet. |
+| `DeploymentScriptExistingStorageNotInSameSubscriptionAsDeploymentScript` | The existing storage provided in deployment is not found in the subscription where the script is being deployed. |
 | `DeploymentScriptStorageAccountInvalidKind` | The existing storage account of the `BlobBlobStorage` or `BlobStorage` type doesn't support file shares and can't be used. |
 | `DeploymentScriptStorageAccountInvalidKindAndSku` | The existing storage account doesn't support file shares. For a list of supported types of storage accounts, see [Use an existing storage account](./deployment-script-develop.md#use-an-existing-storage-account). |
 | `DeploymentScriptStorageAccountNotFound` | The storage account doesn't exist, or an external process or tool deleted it. |

articles/container-apps/tutorial-ci-cd-runners-jobs.md

@@ -406,7 +406,7 @@ You can now create a job that uses to use the container image. In this section,
         --cpu "2.0" \
         --memory "4Gi" \
         --secrets "personal-access-token=$GITHUB_PAT" \
-        --env-vars "GITHUB_PAT=secretref:personal-access-token" "REPO_URL=https://github.com/$REPO_OWNER/$REPO_NAME" "REGISTRATION_TOKEN_API_URL=https://api.github.com/repos/$REPO_OWNER/$REPO_NAME/actions/runners/registration-token" \
+        --env-vars "GITHUB_PAT=secretref:personal-access-token" "GH_URL=https://github.com/$REPO_OWNER/$REPO_NAME" "REGISTRATION_TOKEN_API_URL=https://api.github.com/repos/$REPO_OWNER/$REPO_NAME/actions/runners/registration-token" \
         --registry-server "$CONTAINER_REGISTRY_NAME.azurecr.io"
     ```
 
@@ -429,7 +429,7 @@ You can now create a job that uses to use the container image. In this section,
         --cpu "2.0" `
         --memory "4Gi" `
         --secrets "personal-access-token=$GITHUB_PAT" `
-        --env-vars "GITHUB_PAT=secretref:personal-access-token" "REPO_URL=https://github.com/$REPO_OWNER/$REPO_NAME" "REGISTRATION_TOKEN_API_URL=https://api.github.com/repos/$REPO_OWNER/$REPO_NAME/actions/runners/registration-token" `
+        --env-vars "GITHUB_PAT=secretref:personal-access-token" "GH_URL=https://github.com/$REPO_OWNER/$REPO_NAME" "REGISTRATION_TOKEN_API_URL=https://api.github.com/repos/$REPO_OWNER/$REPO_NAME/actions/runners/registration-token" `
         --registry-server "$CONTAINER_REGISTRY_NAME.azurecr.io"
     ```
 

articles/databox/data-box-hardware-additional-terms.md

@@ -29,15 +29,15 @@ All right, title and interest in each Data Box Device is and shall remain the pr
 
 ### Fees
 
-Microsoft may charge Customer specified fees in connection with its use of the Data Box Device as part of the Service, as described at https://go.microsoft.com/fwlink/?linkid=2052173. For clarity, Azure Storage and Azure IoT Hub are separate Azure Services, and if used (even in connection with its use of the Service), separate Azure metered fees will apply. Additional Azure services Customer uses after completing a transfer of data using the Azure Data Box Service are also subject to separate usage fees.  For Data Box Devices, Microsoft may charge Customer a lost device fee, as provided in Table 1 below, if (i) the Data Box Device is lost or materially damaged while it is in Customer’s care; and/or (ii) Customer does not provide the Data Box Device to the Microsoft-designated carrier for return within the time period after the date it was delivered to Customer as provided in Table 1 below.  Microsoft reserves the right to change the fees charged for Data Box Device types, including charging different amounts for different device form factors.
+Microsoft may charge Customer specified fees in connection with its use of the Data Box Device as part of the Service, as described at https://go.microsoft.com/fwlink/?linkid=2052173. For clarity, Azure Storage and Azure IoT Hub are separate Azure Services, and if used (even in connection with its use of the Service), separate Azure metered fees will apply. Additional Azure services Customer uses after completing a transfer of data using the Azure Data Box Service are also subject to separate usage fees.  For Data Box Devices, Microsoft may charge Customer a lost device fee, as provided in Table 1 below, if the Data Box Device is lost or materially damaged while it is in Customer’s care. Microsoft reserves the right to change the fees charged for Data Box Device types, including charging different amounts for different device form factors.
 
 Table 1:
 
 |Data Box Device type | Lost or Materially Damaged Time Period and Amounts|
 |---------|---------|
-|Data Box           |   Period: After 90 days<br> Amount: $40,000.00 USD  |
-|Data Box Disk      |   Period: After 90 days<br> Amount: $2,500.00 USD      |
-|Data Box Heavy     |   Period: After 90 days<br> Amount: $250,000.00 USD      |
+|Data Box           |   Amount: $40,000.00 USD  |
+|Data Box Disk      |   Amount: $2,500.00 USD      |
+|Data Box Heavy     |   Amount: $250,000.00 USD      |
 |Data Box Gateway   |   N/A     |
 
 ### Shipment and Return of Data Box Device
@@ -61,4 +61,4 @@ If Customer wishes to move a Data Box Device to another country/region, then Cus
 ## Next steps
 
 - [Azure Data Box](data-box-overview.md)
-- [Azure Data Box pricing](https://azure.microsoft.com/pricing/details/databox/)
+- [Azure Data Box pricing](https://azure.microsoft.com/pricing/details/databox/)