Skip to content

Commit 8611f78

Browse files
author
BobbySchmidt2
committed
edit pass: storage-files-migration-overview
1 parent 7e221b0 commit 8611f78

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/storage/files/storage-files-migration-overview.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,9 @@ Taking the previous information into account, you can see that the target storag
4848

4949
Unlike object storage in Azure blobs, an Azure file share can natively store file metadata. Azure file shares also preserve the file and folder hierarchy, attributes, and permissions. NTFS permissions can be stored on files and folders because they're on-premises.
5050

51-
A user of Azure Active Directory (Azure AD) or Azure Active Directory Domain Services (Azure AD DS) can natively access an Azure file share. They use their current identity to get access based on share permissions and on file and folder ACLs. This behavior is similar to a user connecting to an on-premises file share.
51+
A user of Active Directory, which is their on-premises domain controller, can natively access an Azure file share. So can a user of Azure Active Directory Domain Services (Azure AD DS). Each uses their current identity to get access based on share permissions and on file and folder ACLs. This behavior is similar to a user connecting to an on-premises file share.
52+
53+
<!--A user of Azure Active Directory (Azure AD) or Azure Active Directory Domain Services (Azure AD DS) can natively access an Azure file share. They use their current identity to get access based on share permissions and on file and folder ACLs. This behavior is similar to a user connecting to an on-premises file share.-->
5254

5355
The alternative data stream is the primary aspect of file fidelity that currently can't be stored on a file in an Azure file share. It's preserved on-premises when Azure File Sync is used.
5456

0 commit comments

Comments
 (0)