Merge pull request #264169 from stevenmatthew/dbx-nfs-0124

dbx-nfs-0124: Adding NFS conflict limitation for DBX

Author: prmerger-automator[bot]

articles/databox/data-box-disk-limits.md

@@ -39,6 +39,7 @@ For the latest information on Azure storage service limits and best practices fo
 
 ## Data copy and upload caveats
 
+- Importing data into NFS Azure file shares isn't supported by Azure Data Box. Copying data from Data Box into an existing NFS Azure file share with an identical name as your source folder creates a conflict. To resolve this conflict, Data Box renames the source share to `databox-<GUID>` and uploads it to the target storage account as an SMB Azure file share.
 - Don't copy data directly into the disks. Copy data to pre-created *BlockBlob*, *PageBlob*, and *AzureFile* folders.
 - A folder under the *BlockBlob* and *PageBlob* is a container. For instance, containers are created as *BlockBlob/container* and *PageBlob/container*.
 - If a folder has the same name as an existing container, the folder's contents are merged with the container's contents. Files or blobs that aren't already in the cloud are added to the container. If a file or blob has the same name as a file or blob that's already in the container, the existing file or blob is overwritten.

includes/data-box-data-upload-caveats.md

@@ -17,6 +17,7 @@ ms.author: shaas
   - If a folder has the same name as an existing container, the folder's contents are merged with the container's contents. Files or blobs that aren't already in the cloud are added to the container. If a file or blob has the same name as a file or blob that's already in the container, the existing file or blob is overwritten.
   - An upload to a blob in the Archive tier will fail if the container has an existing archived blob with the same name. While a blob is in the Archive tier, it can't be read or modified. If you need to overwrite a blob, make sure the blob isn't set to archive. For more information, see [Archive access tier](../articles/storage/blobs/access-tiers-overview.md#archive-access-tier).
   - Any empty directory hierarchy (without any files) created under *StorageAccount_BlockBlob* and *StorageAccount_PageBlob* folders isn't uploaded.
+- Importing data into NFS Azure file shares isn't supported by Azure Data Box. Copying data from Data Box into an existing NFS Azure file share with an identical name as your source folder creates a conflict. To resolve this conflict, Data Box renames the source share to `databox-<GUID>` and uploads it to the target storage account as an SMB Azure file share. 
 - If you use both the SMB and NFS protocols for data copies, we recommend that you:
   - Use different storage accounts for SMB and NFS.
   - Don't copy the same data to the same end destination in Azure using both SMB and NFS. In these cases, the final outcome can't be determined.