Small Dedupe fix for SS8000 migration doc

Author: fauhse

articles/storage/files/storage-files-migration-storsimple-8000.md

@@ -141,7 +141,10 @@ The overall size of the data is less of a bottleneck - it is the number of items
 > Make sure that the VM is deployed in the same Azure region as the StorSimple 8020 virtual appliance. If as part of this migration, you also need to change the region of your cloud data from the region it is stored in today, you can do that at a later step, when you provision Azure file shares.
 
 > [!IMPORTANT]
-> To optimize for performance, deploy a **very fast OS disk** for your cloud VM. You will store the sync database on the OS disk for all of your data volumes. Furthermore, ensure that you create a **large OS disk**. Depending on the number of items (files and folders) on your StorSimple volumes, the OS disk might need a **several hundred GiB** of space to accommodate the sync database.
+> Often, an on-premises Windows Server is used to front your on-premises StorSimple appliance. In such a configuration, it is possible to enable the "[Data Deduplication](https://docs.microsoft.com/windows-server/storage/data-deduplication/install-enable)" feature on that Windows Server. **If you used Data Deduplication with your StorSimple data, ensure that you enable Data Deduplication on this Azure VM as well.** Don't confuse this file-level deduplication with StorSimples built-in block-level deduplication, for which no action is necessary.
+
+> [!IMPORTANT]
+> To optimize for performance, deploy a **fast OS disk** for your cloud VM. You will store the sync database on the OS disk for all of your data volumes. Furthermore, ensure that you create a **large OS disk**. Depending on the number of items (files and folders) on your StorSimple volumes, the OS disk might need a **several hundred GiB** of space to accommodate the sync database.
 
 ### Expose the StorSimple 8020 volumes to the Azure VM