Skip to content

Update overview.md #127183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

thakurmishra21
Copy link
Contributor

No description provided.

Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 45f020b:

✅ Validation status: passed

File Status Preview URL Details
articles/storage-actions/overview.md ✅Succeeded

For more details, please refer to the build report.

@@ -62,7 +62,7 @@ See these articles to learn how to assign a storage task:
- [Azure roles for storage task assignments](storage-tasks/storage-task-authorization-roles.md)

> [!NOTE]
> Storage task assignment can't target general-purpose v1 accounts because those accounts don't support the latest features. If you have a general-purpose v1 account, we recommend you to upgrade to [general-purpose v2 accounts](/azure/well-architected/service-guides/storage-accounts/operational-excellence#design-considerations) to use all the latest features.
> Storage task assignment can't target general-purpose v1 & Legacy Blob Storage accounts because those accounts don't support the latest features. If you have a general-purpose v1 or Legacy Blob Storage account, we recommend you to upgrade to [general-purpose v2 accounts](/azure/well-architected/service-guides/storage-accounts/operational-excellence#design-considerations) to use all the latest features.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
> Storage task assignment can't target general-purpose v1 & Legacy Blob Storage accounts because those accounts don't support the latest features. If you have a general-purpose v1 or Legacy Blob Storage account, we recommend you to upgrade to [general-purpose v2 accounts](/azure/well-architected/service-guides/storage-accounts/operational-excellence#design-considerations) to use all the latest features.
> Storage task assignment can't target general-purpose v1 and legacy Blob Storage accounts because those accounts don't support the latest features. If you have a general-purpose v1 or legacy Blob Storage account, we recommend you to upgrade to [general-purpose v2 accounts](/azure/well-architected/service-guides/storage-accounts/operational-excellence#design-considerations) to use all the latest features.

Copy link
Contributor

@normesta normesta left a comment

Choose a reason for hiding this comment

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

Thanks! "Legacy" should be "legacy" (lower case)

@v-regandowner
Copy link
Contributor

@thakurmishra21 - Please review the suggested changes.

@normesta - 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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jun 19, 2025
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.

3 participants