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.

Sign up for GitHub

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

Jump to bottom

All "Directory Synchronization Accounts" role assignees are excluded from security defaults #737

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

All "Directory Synchronization Accounts" role assignees are excluded from security defaults #737

wants to merge 1 commit into from

Conversation

cnotin
Copy link
Contributor

@cnotin cnotin commented Apr 30, 2024

As highlighted by @DrAzureAD in https://twitter.com/DrAzureAD/status/1531600224711483392 this limitation really concerns all "Directory Synchronization Accounts" role assignees and not only the one expected legitimate account. Also, as explained in this other PR #734, Microsoft Entra Cloud Sync also uses this role.

Replacing #736

@cnotin
All "Directory Synchronization Accounts" role assignees are excluded …
fff5369 
…from security defaults

As highlighted by @DrAzureAD in https://twitter.com/DrAzureAD/status/1531600224711483392 this limitation really concerns all "Directory Synchronization Accounts" role assignees and not only the one expected legitimate account.
Also, as explained in this other PR MicrosoftDocs#734, Microsoft Entra Cloud Sync also uses this role.
@prmerger-automator PRMerger Automator
Copy link
Contributor

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

@learn-build-service-prod Learn Build Service (PROD)
Copy link
Contributor

Learn Build status updates of commit fff5369:

✅ Validation status: passed

File Status Preview URL Details
docs/fundamentals/security-defaults.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Apr 30, 2024

@MicrosoftGuyJFlo

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

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

@github-actions GitHub Actions
Copy link

This pull request has been inactive for 90 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.

If this PR is inactive for 1 more day, it will be closed automatically. Thank you!

Microsoft Entra Content Team Contact Us

@cnotin
Copy link
Contributor Author

cnotin commented Jul 29, 2024

Still applies!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@MicrosoftGuyJFlo MicrosoftGuyJFlo Awaiting requested review from MicrosoftGuyJFlo

Assignees

@MicrosoftGuyJFlo MicrosoftGuyJFlo

Labels
aq-pr-triaged Change sent to author do-not-merge entra/svc fundamentals/subsvc qualifies-for-auto-merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@cnotin @Court72 @MicrosoftGuyJFlo