Skip to content

Conversation

@westleyMS
Copy link
Contributor

there was an error in the permissions that listed the delegated work/school perms twice, and didn't mention the application permissions which are required to create the entry.


Add other supporting information, such as a description of the PR changes:

ADD INFORMATION HERE


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.

there was an error in the permissions that listed the delegated work/school perms twice, and didn't mention the application permissions which are required to create the entry.
@learn-build-service-prod
Copy link

Learn Build status updates of commit cc58224:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/api/site-post-permissions.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Danielabom Danielabom self-assigned this May 21, 2025
|Delegated (work or school account)|Not supported.|Not supported.|
|Delegated (work or school account)|Sites.FullControl.All|Not available.|
|Delegated (personal Microsoft account)|Not supported.|Not supported.|
|Application|Sites.FullControl.All|Not available.|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@westleyMS, can you confirm that the correction you made is what your workload has on the permissions model?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure what you mean by that. There is an error in that you can't have that permission as 'not available' but then also set to something else. It is there twice, so this was an error.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @westleyMS, sorry about that. I realize I wasn’t clear enough earlier. Yes, we did have duplicate rows for the Delegated (work or school account) permission, but we don’t recommend updating permissions manually.

So my question is: have you confirmed that your permissions model contains the correct data? Thanks!

@microsoft-github-policy-service
Copy link
Contributor

Hello @@westleyMS! This pull request has been inactive for 2 weeks with the changes requested label. Please address the feedback left by your reviewer and add the review feedback addressed. If you have any questions, please contact your reviewer.

  • If you are still working on this pull request, please add a comment or push changes. Remove changes requested and add review feedback addressed once you've made all requested changes.
  • If the pull request is no longer needed, please close it.
  • If the pull request is on hold or otherwise blocked, please add the blocked label.

Note

Pull requests that are inactive more than 6 weeks will be automatically closed.

@microsoft-github-policy-service
Copy link
Contributor

Hello @@westleyMS! This pull request has been inactive for 4 weeks with the changes requested label. Please address the feedback left by your reviewer and add the review feedback addressed. If you have any questions, please contact your reviewer.

  • If you are still working on this pull request, please add a comment or push changes. Remove changes requested and add review feedback addressed once you've made all requested changes.
  • If the pull request is no longer needed, please close it.
  • If the pull request is on hold or otherwise blocked, please add the blocked label.

Note

Pull requests that are inactive more than 6 weeks will be automatically closed.

@microsoft-github-policy-service
Copy link
Contributor

Hello @@westleyMS! This pull request has been inactive for 6 weeks with the changes requested label. Please address the feedback left by your reviewer and add the review feedback addressed. If you have any questions, please contact your reviewer.

  • If you are still working on this pull request, please add a comment or push changes. Remove changes requested and add review feedback addressed once you've made all requested changes.
  • If the pull request is no longer needed, please close it.
  • If the pull request is on hold or otherwise blocked, please add the blocked label.

Note

This pull request will be automatically closed in 7 days if you do not take action.

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.

2 participants