Skip to content

Update waf-logs-security.md #171

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

Closed
wants to merge 1 commit into from

Conversation

rativerma16
Copy link

Updated the date in note.

Updated the date in note.
Copy link
Contributor

Learn Build status updates of commit 8ceaf12:

💡 Validation status: suggestions

File Status Preview URL Details
articles/azure-monitor/logs/includes/waf-logs-security.md 💡Suggestion Details

articles/azure-monitor/logs/includes/waf-logs-security.md

  • Line 14, Column 52: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/loganalytics/operation-groups?view=rest-loganalytics-2022-10-27-preview

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@rativerma16
Copy link
Author

#sign-off

Copy link
Contributor

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

@rativerma16
Copy link
Author

#signoff

@v-dirichards
Copy link
Contributor

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


@austinmccollum

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Jun 26, 2025
@v-dirichards
Copy link
Contributor

This includes file has been substantially updated or deleted, and this change no longer applies. If you'd still like to update the article, please open a new PR. Or if you believe this PR was closed by mistake, email the PublicPRs alias.

#please-close
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aq-pr-triaged C+L Pull Request Review Team label do-not-merge review-team-triage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants