Merge pull request #184134 from jeffpatt24/patch-4

Update storage-files-scale-targets.md

Author: PRMerger4

articles/storage/file-sync/file-sync-planning.md

@@ -264,6 +264,9 @@ Using sysprep on a server that has the Azure File Sync agent installed is not su
 ### Windows Search
 If cloud tiering is enabled on a server endpoint, files that are tiered are skipped and not indexed by Windows Search. Non-tiered files are indexed properly.
 
+> [!Note]  
+> Windows clients will cause recalls when searching the file share if the **Always search file names and contents** setting is enabled on the client machine. This setting is disabled by default.
+
 ### Other Hierarchical Storage Management (HSM) solutions
 No other HSM solutions should be used with Azure File Sync.
 

articles/storage/files/storage-files-scale-targets.md

@@ -80,7 +80,7 @@ Azure supports multiple types of storage accounts for different storage scenario
 <sup>2 Subject to machine network limits, available bandwidth, IO sizes, queue depth, and other factors. For details see [SMB Multichannel performance](./storage-files-smb-multichannel-performance.md).</sup>
 
 ## Azure File Sync scale targets
-The following table indicates the boundaries of Microsoft's testing and also indicates which targets are hard limits:
+The following table indicates the boundaries of Microsoft's testing (soft limits) and also indicates which targets are hard limits:
 
 | Resource | Target | Hard limit |
 |----------|--------------|------------|