Revise SharePoint tab sections for clarity

[loryanstrant]

Updated SharePoint tab sections to clarify app IDs and configuration support.

Important

Required for API changes:

• [] Link to API.md file: ADD LINK HERE
• [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

---

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.

[Copilot]

Pull Request Overview

This PR updates the SharePoint tab documentation to provide clearer distinctions between different SharePoint tab types and their respective app IDs and configuration support. The changes improve the organization of SharePoint-related tab information by separating what was previously grouped under "SharePoint page and list tabs" into more specific categories.

Key changes:

• Reorganized SharePoint tab sections for better clarity and specificity
• Added separate sections for SharePoint Pages and Lists tabs with distinct app IDs
• Updated configuration support information for each tab type

[learn-build-service-prod]

Learn Build status updates of commit f722e04:

✅ Validation status: passed

File	Status	Preview URL	Details
concepts/teams-configuring-builtin-tabs.md	✅Succeeded

For more details, please refer to the build report.

[Danielabom]

@loryanstrant, which PM authorized this change? Would you mind sharing the api.md?

[loryanstrant]

Hi @Danielabom, I haven't spoken to any PM.
The documentation has been incorrect for as many months as I've been using this endpoint, so I'm correcting it - as many other MVPs do.

[Danielabom]

@loryanstrant, thanks for the quick reply. I understand and appreciate your contribution. Ideally, you’d contact someone from the workload team so they can submit the change request through our private repo. The reason is that this isn’t a cosmetic change, so we need to meet certain minimum criteria before we can work on the update. Thanks, again.

[loryanstrant]

The guidance we've been given previously was just to go in an submit a PR, as finding someone who owns the endpoint and/or has knowledge to validate and it is not always practical.