Skip to content
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

Update storage-dev-guide-stored-access-policy.md #122481

Closed
wants to merge 1 commit into from

Conversation

azarboon
Copy link
Contributor

I've added following for further clarification: "With stored access policy, you can grant or revoke permissions for specific operations such as read, write, delete, list, and more. "

I've added following for further clarification: "With stored access policy, you can grant or revoke permissions for specific operations such as read, write, delete, list, and more. "
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 222c057:

✅ Validation status: passed

File Status Preview URL Details
includes/storage-dev-guides/storage-dev-guide-stored-access-policy.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@pauljewellmsft
Copy link
Contributor

@azarboon Thanks so much for contributing to the docs. As I look at this specific suggestion, it appears to me that we cover this detail in the next paragraph: "You can use a stored access policy to change the start time, expiry time, or permissions for a signature." Since this sentence gets at the fact that an access policy can be used to manage permissions, it seems like we're covered.

Let me know if I'm misunderstanding the suggestion at all - glad to discuss further.

@Court72
Copy link
Contributor

Court72 commented May 14, 2024

#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 May 14, 2024
@pauljewellmsft
Copy link
Contributor

@azarboon Thanks so much for your contribution to the docs. Per my earlier comment, it seems that the clarification you're suggesting is already included in the next paragraph.

Since we haven't heard back from you, I'm going to close this PR. If you have further comments, please re-open the PR and let us know. Thanks!

#please-close

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.

None yet

3 participants