Skip to content

Update user-list.md#9574

Merged
FaithOmbongi merged 1 commit into
microsoftgraph:mainfrom
rykoma:patch-1
Jun 4, 2025
Merged

Update user-list.md#9574
FaithOmbongi merged 1 commit into
microsoftgraph:mainfrom
rykoma:patch-1

Conversation

@rykoma
Copy link
Copy Markdown
Contributor

@rykoma rykoma commented May 22, 2025

Fixed some mistakes in the 12th example section.


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.

Fixed some mistakes in the 12th example section.
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 5865363:

⚠️ Validation status: warnings

File Status Preview URL Details
api-reference/v1.0/api/user-list.md ⚠️Warning Details

api-reference/v1.0/api/user-list.md

  • Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'List users - Microsoft Graph v1.0' is duplicated in: 'v1.0/api/intune-devices-user-list.md(2,8), v1.0/api/intune-mam-user-list.md(2,8), v1.0/api/intune-onboarding-user-list.md(2,8), v1.0/api/intune-troubleshooting-user-list.md(2,8), v1.0/api/user-list.md(2,8)'. Titles must be unique within a docset.
  • Line 12, Column 1: [Warning: duplicate-h1s - See documentation] H1 'List users' is duplicated with other articles: 'v1.0/api/intune-devices-user-list.md(11,1), v1.0/api/intune-mam-user-list.md(11,1), v1.0/api/intune-onboarding-user-list.md(11,1), v1.0/api/intune-troubleshooting-user-list.md(11,1), v1.0/api/user-list.md(12,1)'. First level headings must be unique within a docset.

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:

@FaithOmbongi FaithOmbongi self-assigned this Jun 4, 2025
@FaithOmbongi FaithOmbongi added area: Entra APIs and issues relating to Microsoft Entra (previously Azure AD) features. area: users ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master. labels Jun 4, 2025
@FaithOmbongi FaithOmbongi merged commit 1bf6569 into microsoftgraph:main Jun 4, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Entra APIs and issues relating to Microsoft Entra (previously Azure AD) features. area: users ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants