MicrosoftDocs
Update backup-plan-to-protect-against-ransomware.md
Updating custom tag for all ransomware pages, per Macky and Paul's advice
@Sarit1046 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 0eea83f:
: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
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@sarit1046 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
Hi Diana, definitely, thank you for letting me know!
From: Diana Richards @.> Sent: Friday, March 21, 2025 8:46 AM To: MicrosoftDocs/azure-docs @.> Cc: Sarah Katz @.>; Mention @.> Subject: Re: [MicrosoftDocs/azure-docs] Update backup-plan-to-protect-against-ransomware.md (PR #126273)
@Sarit1046https://github.com/Sarit1046 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/126273#issuecomment-2743768507, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BIAJT3BYRS3OOEHCVRCXRBL2VQX43AVCNFSM6AAAAABZQJJKTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBTG43DQNJQG4. You are receiving this because you were mentioned.Message ID: @.***> [Image removed by sender. v-dirichards]v-dirichards left a comment (MicrosoftDocs/azure-docs#126273)https://github.com/MicrosoftDocs/azure-docs/pull/126273#issuecomment-2743768507
@Sarit1046https://github.com/Sarit1046 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/126273#issuecomment-2743768507, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BIAJT3BYRS3OOEHCVRCXRBL2VQX43AVCNFSM6AAAAABZQJJKTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBTG43DQNJQG4. 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
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
@msmbaldwin
Can you review this old PR and determine whether it needs to be closed or merged?
@MicrosoftDocs/public-repo-pr-review-team
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
