search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.24k stars 21.4k forks source link

AES #69437

Closed vercin7277 closed 3 years ago

vercin7277 commented 3 years ago

Old:

AES Encryption Select this checkbox to enable AES encryption for an SMB volume. See Requirements for Active Directory connections for requirements.

New:

AES Encryption Select this checkbox to enable AES encryption for AD Authentication. See Requirements for Active Directory connections for requirements.

Old:

You can enable AES encryption for an SMB volume by checking the AES Encryption box in the Join Active Directory window. Azure NetApp Files supports DES, Kerberos AES 128, and Kerberos AES 256 encryption types (from the least secure to the most secure).

New:

You can enable AES encryption for AD Authentication by checking the AES Encryption box in the Join Active Directory window. Azure NetApp Files supports DES, Kerberos AES 128, and Kerberos AES 256 encryption types (from the least secure to the most secure). Why:

Current text is confusing as customers believe it is for Volume Encryption.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

SumanthMarigowda-MSFT-zz commented 3 years ago

@vercin7277 Thanks for the feedback! The PR request has been initiated

b-hchen commented 3 years ago

vercin7277 - Thanks for the input. However, our product managers require that all doc changes be approved before merging. This PR was merged before I had a chance to review / request approval. Will get back on this PR if product managers disagree.

vercin7277 commented 3 years ago

No problem Julie!

Kind regards,

Verron Martina Cloud Solution Architect for Azure Alliance

From: Julie Chen notifications@github.com Sent: Monday, January 25, 2021 5:51 PM To: MicrosoftDocs/azure-docs Cc: Martina, Verron; Mention Subject: Re: [MicrosoftDocs/azure-docs] AES (#69437)

NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

vercin7277 - Thanks for the input. However, our product managers require that all doc changes be approved before merging. This PR was merged before I had a chance to review / request approval. Will get back on this PR if product managers disagree.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/69437#issuecomment-766953568, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APOGP7NFOS5G3NHVJZRWVWLS3WORPANCNFSM4WR3DBJA.

b-hchen commented 3 years ago

@ vercin7277 -- Thanks again Verron! Our Product Managers appreciated your input :) Thanks for your help in enhancing the documentation.

vercin7277 commented 3 years ago

You’re welcome !

Kind regards,

Verron Martina Cloud Solution Architect for Azure Alliance

From: Julie Chen notifications@github.com Sent: Monday, January 25, 2021 8:31:48 PM To: MicrosoftDocs/azure-docs azure-docs@noreply.github.com Cc: Martina, Verron Verron.Martina@netapp.com; Mention mention@noreply.github.com Subject: Re: [MicrosoftDocs/azure-docs] AES (#69437)

NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

@ vercin7277 -- Thanks again Verron! Our Product Managers appreciated your input :) Thanks for your help in enhancing the documentation.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/69437#issuecomment-767058742, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APOGP7MX3LR5PR42ET4ZQO3S3XBKJANCNFSM4WR3DBJA.

SumanthMarigowda-MSFT-zz commented 3 years ago

@vercin7277 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.