Skip to content

Clarify accessTier parameters are unsupported on Azure Files provisioned v2 SKUs#431

Open
tdihp wants to merge 1 commit into
MicrosoftDocs:mainfrom
tdihp:fix/azurefiles-accesstier-provisioned-v2-unsupported
Open

Clarify accessTier parameters are unsupported on Azure Files provisioned v2 SKUs#431
tdihp wants to merge 1 commit into
MicrosoftDocs:mainfrom
tdihp:fix/azurefiles-accesstier-provisioned-v2-unsupported

Conversation

@tdihp

@tdihp tdihp commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

A.T.

The article recommends provisioned v2 SKUs (PremiumV2_, StandardV2_), but the storage class parameter table presented accountAccessTier and shareAccessTier as generally available. Combining a provisioned v2 SKU with an access tier parameter fails share creation with AccessTierNotSupported.

Note in both parameter rows that access tier doesn't apply to provisioned v2 SKUs.

…ned v2 SKUs

The article recommends provisioned v2 SKUs (PremiumV2_*, StandardV2_*),
but the storage class parameter table presented accountAccessTier and
shareAccessTier as generally available. Combining a provisioned v2 SKU
with an access tier parameter fails share creation with
AccessTierNotSupported.

Note in both parameter rows that access tier doesn't apply to
provisioned v2 SKUs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@prmerger-automator

Copy link
Copy Markdown
Contributor

@tdihp : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 5494c2f:

✅ Validation status: passed

File Status Preview URL Details
articles/aks/create-volume-azure-files.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner

Copy link
Copy Markdown
Contributor

@schaffererin

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

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the AKS Azure Files CSI driver documentation to clarify that accountAccessTier and shareAccessTier aren’t supported when using Azure Files provisioned v2 storage account SKUs, preventing users from configuring unsupported parameters that can cause share provisioning failures.

Changes:

  • Updated ms.date to reflect the documentation change date.
  • Clarified in the storage class parameters table that accountAccessTier doesn’t apply to provisioned v2 SKUs (PremiumV2_*, StandardV2_*).
  • Clarified that shareAccessTier isn’t supported for provisioned v2 SKUs and can fail share creation with AccessTierNotSupported.

@github-actions

Copy link
Copy Markdown

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@tdihp

tdihp commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

#sign-off

@prmerger-automator

Copy link
Copy Markdown
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @schaffererin

@github-actions github-actions Bot removed the inactive label Jun 25, 2026
@v-regandowner

Copy link
Copy Markdown
Contributor

@schaffererin - Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@prmerger-automator

Copy link
Copy Markdown
Contributor

@tdihp : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants