Skip to content

Conversation

@tvelosa
Copy link
Contributor

@tvelosa tvelosa commented Aug 21, 2025

Added a note about a known issue when trying to access a group team site due to previously reported incidents regarding this.

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) PR DOESN'T INCLUDE API.MD or PERMISSIONS CHANGES: ADD LINK HERE

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

I'm an SE in the Graph API and as per ADO {https://onedrive.visualstudio.com/DevPlat/_workitems/edit/2545215} I'm changing this to reflect the correct behavior reported by PG.

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.

Added a note about a known issue when trying to access a group team site due to previously reported incidents regarding this.
@tvelosa tvelosa added customer support issue Doc issue raised from customer support ready for content review PR is ready for a content review - content development and tech review are complete. labels Aug 21, 2025
@learn-build-service-prod
Copy link

Learn Build status updates of commit 4fa338e:

⚠️ Validation status: warnings

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

api-reference/v1.0/api/site-get.md

  • Line 58, Column 236: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/graph/api/site-getbypath?view=graph-rest-1.0' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 6, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Retrieve properties and relationships for a site resource.' is duplicated in 'v1.0/api/site-get.md(6,14)', 'v1.0/api/site-getbypath.md(6,14)'.
  • Line 58, Column 236: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/graph/api/site-getbypath?view=graph-rest-1.0' will be broken in isolated environments. Replace with a relative link.
  • Line 58, Column 236: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://learn.microsoft.com/en-us/graph/api/site-getbypath?view=graph-rest-1.0

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.

Performed changes as per the warning - replaced the absolute link to get a sharepoint site by path with a relative one.
@learn-build-service-prod
Copy link

Learn Build status updates of commit 096e3e0:

💡 Validation status: suggestions

File Status Preview URL Details
api-reference/v1.0/api/site-get.md 💡Suggestion Details

api-reference/v1.0/api/site-get.md

  • Line 6, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Retrieve properties and relationships for a site resource.' is duplicated in 'v1.0/api/site-get.md(6,14)', 'v1.0/api/site-getbypath.md(6,14)'.

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.

```

> [!IMPORTANT]
> This API has a known issue: when trying to access a group team site using `GET /groups/{group-id}/sites/root`, you may receive a **308 Permanent Redirect** response. If you follow the Location URL in the response header, it will lead to a **401 Unauthorized** error because the redirect targets the SharePoint REST API directly. **This happens when the group team's site has been renamed.**
Copy link
Contributor

@Danielabom Danielabom Sep 2, 2025

Choose a reason for hiding this comment

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

Suggested change
> This API has a known issue: when trying to access a group team site using `GET /groups/{group-id}/sites/root`, you may receive a **308 Permanent Redirect** response. If you follow the Location URL in the response header, it will lead to a **401 Unauthorized** error because the redirect targets the SharePoint REST API directly. **This happens when the group team's site has been renamed.**
> This API has a known issue: when trying to access a group team site using `GET /groups/{group-id}/sites/root`, you may receive a **308 Permanent Redirect** response. If you follow the Location URL in the response header, it leads to a **401 Unauthorized** error because the redirect targets the SharePoint REST API directly. This happens when the group team's site has been renamed.

Copy link
Contributor

@Danielabom Danielabom left a comment

Choose a reason for hiding this comment

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

PR approved.

@learn-build-service-prod
Copy link

Learn Build status updates of commit 1c31ad0:

💡 Validation status: suggestions

File Status Preview URL Details
api-reference/v1.0/api/site-get.md 💡Suggestion Details

api-reference/v1.0/api/site-get.md

  • Line 6, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Retrieve properties and relationships for a site resource.' is duplicated in 'v1.0/api/site-get.md(6,14)', 'v1.0/api/site-getbypath.md(6,14)'.

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.

@Danielabom
Copy link
Contributor

@tvelosa, what's the known issue ID? I couldn't find it here (https://developer.microsoft.com/en-us/graph/known-issues/?search={ID}).

@Danielabom Danielabom added awaiting internal response content review in progress and removed ready for content review PR is ready for a content review - content development and tech review are complete. labels Sep 2, 2025
@tvelosa
Copy link
Contributor Author

tvelosa commented Sep 3, 2025

@Danielabom I only have the internal issue IDs, I don't think an issue has been published in that portal yet

@Danielabom
Copy link
Contributor

@tvelosam, when will you have the issue ID available?

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