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

Update wrong URL in Example on security-filethreatsubmission-post-fil… #9442

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

poleshe
Copy link
Contributor

@poleshe poleshe commented Oct 14, 2024

…ethreats.md

Instructions: Add any supporting information, such as a description of the PR changes, here.

The example to create a file submissions states that the URL is:

POST https://graph.microsoft.com/beta/security/threatSubmission/fileThreatSubmissions

But the actual URL is:

POST https://graph.microsoft.com/beta/security/threatSubmission/fileThreats

It might be confusing, so here's the fix

Note

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Your PR won't be reviewed until you add this label.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

…ethreats.md

The example to create a file submissions states that the URL is:

POST https://graph.microsoft.com/beta/security/threatSubmission/fileThreatSubmissions

But the actual URL is:

POST https://graph.microsoft.com/beta/security/threatSubmission/fileThreats

It might be confusing, so here's the fix
Copy link

Learn Build status updates of commit 81650a8:

✅ Validation status: passed

File Status Preview URL Details
api-reference/beta/api/security-filethreatsubmission-post-filethreats.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Lauragra Lauragra merged commit f6bef09 into microsoftgraph:main Oct 15, 2024
6 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