MicrosoftDocs
Update azure-storage-windows-code-pivot.md
I was not able to mount Azure File Share with AES-128-CCM or AES-256-GCM only enabled. I had to enable AES-256-GCM
@coolhome : Thanks for your contribution! The author(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 877d11d:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/app-service/includes/configure-azure-storage/azure-storage-windows-code-pivot.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@msangapu-msft
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@msangapu-msft
Can you review this old PR and determine whether it needs to be closed or merged?
I was not able to mount Azure File Share with
AES-128-CCMorAES-256-GCMonly enabled. I had to enableAES-256-GCM
You wrote that you couldn't mount the share with 'AES-256-GCM', but then you enabled it... can you clarify? Might there be a typo?
@coolhome
Can you respond to the comment above?
@MicrosoftDocs/public-repo-pr-review-team
@coolhome
Can you respond to the comment above?
@MicrosoftDocs/public-repo-pr-review-team
Ahh yes sorry for the confusion. I meant to say:
I was not able to mount Azure File Share with AES-128-CCM or AES-256-GCM only enabled. I had to enable AES-128-GCM
@msangapu-msft Would you add a comment to indicate what action to take on this PR? Thanks!
@msangapu-msft Would you add a comment to indicate what action to take on this PR? Thanks!
I reached out to the product team... will get back to you.
@coolhome Can you respond to the comment above? @MicrosoftDocs/public-repo-pr-review-team
Ahh yes sorry for the confusion. I meant to say:
I was not able to mount Azure File Share with AES-128-CCM or AES-256-GCM only enabled. I had to enable AES-128-GCM
@coolhome - AES-256-GCM is supported: https://learn.microsoft.com/en-us/windows-server/storage/file-server/smb-security#smb-encryption
Do you know the Windows Server version?
@coolhome
Can you respond to the comment above?
@MicrosoftDocs/public-repo-pr-review-team
@msangapu-msft @ttorble unfortunately I deleted that app service plan. I was looking at some other ones we have here, and it appears they are on Windows Server 2022 now. I have a feeling I may of done this on a Windows Server 2016 app service plan.
@msangapu-msft Would you add a comment to indicate what action to take on this PR? Thanks!
Let's close this as it seems like it was done on an older server version. #please-close