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

[BULK] - DocuTune remediation - Sensitive terms with GUIDs (part 26) #3338

Conversation

meganbradley
Copy link
Contributor

Applying sensitive terms with GUID changes as part of Content SFI and outlined in Overview - Writing content securely - Platform Manual. Changes are part of the Microsoft-wide SFI effort. Point of contact: @CelesteDG

DocuTune v1.5.2.0
CorrelationId: ac15aa43-4e2b-437f-ab1c-fdd7e79cd4db

#docutune

@meganbradley
Copy link
Contributor Author

#docutune-review

Copy link
Contributor

Learn Build status updates of commit 7e9dbe7:

✅ Validation status: passed

File Status Preview URL Details
azps-12.5.0/Az.Maintenance/Get-AzApplyUpdate.md ✅Succeeded View (azps-12.5.0)
azps-12.5.0/Az.Maintenance/Get-AzConfigurationAssignment.md ✅Succeeded View (azps-12.5.0)
azps-12.5.0/Az.Maintenance/Get-AzMaintenanceUpdate.md ✅Succeeded View (azps-12.5.0)
azps-12.5.0/Az.Maintenance/New-AzApplyUpdate.md ✅Succeeded View (azps-12.5.0)
azps-12.5.0/Az.Maintenance/New-AzConfigurationAssignment.md ✅Succeeded View (azps-12.5.0)

For more details, please refer to the build report.

For any questions, please:

Copy link

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

  • It is not a draft PR.
  • It does not have a WIP prefix in the title.
  • It passes validation and build steps.
  • It does not have any merge conflicts.
  • You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

@mikefrobbins
Copy link
Contributor

LGTM

@mikefrobbins mikefrobbins merged commit f91ef5e into MicrosoftDocs:main Dec 2, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants