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 protect-against-consent-phishing.md with Security Copilot callout #1298

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AriSchorr1
Copy link
Contributor

Added note on use of public preview skills in Security Copilot for Microsoft Entra.

Added note on use of public preview skills in Security Copilot for Microsoft Entra.
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 08bb805:

⚠️ Validation status: warnings

File Status Preview URL Details
docs/identity/enterprise-apps/protect-against-consent-phishing.md ⚠️Warning Details

docs/identity/enterprise-apps/protect-against-consent-phishing.md

  • Line 69, Column 343: [Warning: file-not-found - See documentation] Invalid file link: 'entra/fundamentals/copilot-security-entra-investigate-risky-apps'.

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.

For any questions, please:

@Jak-MS
Copy link
Contributor

Jak-MS commented Dec 24, 2024

Hi @AriSchorr1 - it looks like you have access to the private repo, and if so - you should use that for content updates.

I'll leave this open in case @omondiatieno wants to review it, but in the future you should submit changes to the private repo: entra-docs-pr.

@omondiatieno
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.

NOTE: All validation warnings and suggestions much be addressed (and cleared) before we can merge this. Thanks.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants