Update backup-plan-to-protect-against-ransomware.md

[Sarit1046]

Added rw tag for ransomware metrics tracking

[prmerger-automator[bot]]

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

[prmerger-automator[bot]]

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

[learn-build-service-prod[bot]]

Learn Build status updates of commit de9dd06:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/security/fundamentals/backup-plan-to-protect-against-ransomware.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

[v-dirichards]

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

---

@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

[Sarit1046]

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)

@Sarit1046https://github.com/Sarit1046 Did you intend to make this change in the private repohttps://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!

---

@msmbaldwinhttps://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-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/126446#issuecomment-2795091341, or unsubscribehttps://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)https://github.com/MicrosoftDocs/azure-docs/pull/126446#issuecomment-2795091341

@Sarit1046https://github.com/Sarit1046 Did you intend to make this change in the private repohttps://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!

---

@msmbaldwinhttps://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-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/126446#issuecomment-2795091341, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BIAJT3F5ILOES2OZYRNLUE32Y3IGTAVCNFSM6AAAAAB24PVXR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJVGA4TCMZUGE. You are receiving this because you were mentioned.Message ID: @.@.>>

[prmerger-automator[bot]]

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

[PMEds28]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@msmbaldwin Would you add a comment to indicate what action to take on this PR?

Thanks!

[v-dirichards]

@msmbaldwin

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[v-ccolin]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team