Inconsistent docs
The page starts off with stating that "There is no plan to use Azure File Sync.". Then Azure File Sync is mentioned several times. It seems that the text for the hybrid scenario was used as a base for the cloud-only scenario.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: df97ab07-1788-0ea4-367b-dab9c2b21dfe
- Version Independent ID: 926ba1f4-5539-0e95-35f8-22ad9547e146
- Content: On-premises NAS migration to Azure file shares
- Content Source: articles/storage/files/storage-files-migration-nas-cloud-databox.md
- Service: storage
- Sub-service: files
- GitHub Login: @khdownie
- Microsoft Alias: kendownie
@kasimrehman Thanks for your feedback! We will investigate and update as appropriate.
This line is the problem: [!INCLUDE storage-files-migration-namespace-mapping].
You cannot include the same section for both the cloud-only and the hybrid scenario for Phase 1. At least not fully. Some part of this include will be the same for both scenarios and some part will be different. Please also check other places in the docs that are affected by assuming that this include applied to both the cloud-only as well as the hybrid scenario.
@kasimrehman Thanks for bringing this to our attention. I'm going to assign this to the document author so they can take a look at it accordingly
@khdownie Can you please check and add your comments on this doc update request as applicable.
@kasimrehman you're right, but this will take a bit of time to fix. I'll get someone to review the docs and verify the steps. Thank you!
@kasimrehman I have updated the article in question: https://learn.microsoft.com/en-us/azure/storage/files/storage-files-migration-nas-cloud-databox
However it seems that the other cloud-only article has this same issue. So I will update that as well.
@khdownie Looking good now.
Thanks @kasimrehman - I fixed the other cloud only migration article too:
https://learn.microsoft.com/en-us/azure/storage/files/storage-files-migration-robocopy
#please-close