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

Add corresponding value to allowInvitesFrom #9527

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

Conversation

juntakata
Copy link
Contributor

@juntakata juntakata commented Mar 1, 2025

This is not related to API changes.

In [External collaboration settings] in Entra ID External Identities. "Guest invite settings" has 4 options.

  • Anyone in the organization can invite guest users including guests and non-admins (most inclusive)
  • Member users and users assigned to specific admin roles can invite guest users including guests with member permissions
  • Only users assigned to specific admin roles can invite guest users
  • No one in the organization can invite guest users including admins (most restrictive)

When an admin changed this option, an audit log activity "Update authorization policy" is generated. The audit log shows a property "AllowInvitesFrom" was changed, for example, from 2 to 1. However, there is no doc that explains which number corresponds to which option.

image

This is why I am adding the corresponding numbers to each option in this PR.


Important

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. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • 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.

Copy link

Learn Build status updates of commit a15f526:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/resources/authorizationpolicy.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

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.

1 participant