Update backup-plan-to-protect-against-ransomware.md #126446
Open
+1
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added rw tag for ransomware metrics tracking
|
@Sarit1046 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@Sarit1046 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit de9dd06: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@Sarit1046 Did you intend to make this change in the private repo instead of the public repo? This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you! Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Hi Diana, yes, thank you, please merge these, and I will make sure to update content in the private repo next time. Azure isn't my typical repo, one of my articles just has thematic relevance there, so I will be more careful moving forward.
From: Diana Richards ***@***.***>
Sent: Thursday, April 10, 2025 1:31 PM
To: MicrosoftDocs/azure-docs ***@***.***>
Cc: Sarah Katz ***@***.***>; Mention ***@***.***>
Subject: Re: [MicrosoftDocs/azure-docs] Update backup-plan-to-protect-against-ransomware.md (PR #126446)
@Sarit1046<https://github.com/Sarit1046> Did you intend to make this change in the private repo<https://github.com/MicrosoftDocs/azure-docs-pr> instead of the public repo? This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!
…________________________________
@msmbaldwin<https://github.com/msmbaldwin>
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<https://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team>
-
Reply to this email directly, view it on GitHub<#126446 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIAJT3F5ILOES2OZYRNLUE32Y3IGTAVCNFSM6AAAAAB24PVXR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJVGA4TCMZUGE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
[https://avatars.githubusercontent.com/u/103777760?s=20&v=4]v-dirichards left a comment (MicrosoftDocs/azure-docs#126446)<#126446 (comment)>
@Sarit1046<https://github.com/Sarit1046> Did you intend to make this change in the private repo<https://github.com/MicrosoftDocs/azure-docs-pr> instead of the public repo? This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!
________________________________
@msmbaldwin<https://github.com/msmbaldwin>
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<https://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team>
-
Reply to this email directly, view it on GitHub<#126446 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIAJT3F5ILOES2OZYRNLUE32Y3IGTAVCNFSM6AAAAAB24PVXR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJVGA4TCMZUGE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @msmbaldwin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added rw tag for ransomware metrics tracking