Repository navigation
Update Set-SPOTenantPreAuthSettings.md - #1215
Neil Hodgkinson (nellymo) wants to merge 3 commits into
Conversation
|
sachin-lalwani Before this PR can be merged, a Content Lead needs to add the Sign off label to it. Only one of the listed reviewers needs to add the Sign off label. Before you sign off a PR, confirm the following:
After you've confirmed the above, do the following to sign off:
After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours. If you think you were incorrectly added as a reviewer, have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp. |
|
Learn Build status updates of commit 128a761: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit de09450: ✅ Validation status: passed
For more details, please refer to the build report. |
Neil Hodgkinson (nellymo)
left a comment
There was a problem hiding this comment.
Updated documentation to include additional tempauth deprecation mcdlets
| | WebRendering | Scenarios for rendering previews of files in browser. | | | ||
| | WebRenderingEmbed | Embed SharePoint files in another application. 3rd party application and some 1st party applications may be broken | [Embed Web Part](https://support.microsoft.com/office/add-content-to-your-page-using-the-embed-web-part-721f3b2f-437f-45ef-ac4e-df29dba74de8) | | ||
| | Whiteboard | Teams integration with Whiteboard app will be broken for anonymous and guest users. | [Use Whiteboard in a Teams meeting - Microsoft Support](https://support.microsoft.com/office/use-whiteboard-in-a-teams-meeting-26f87802-b37f-4af0-806d-af79fbfb8ae6) | | ||
|
|
There was a problem hiding this comment.
I think we also missed the "Expected behavior for the Microsoft Graph URL settings" section from the original .md file.
There was a problem hiding this comment.
I have added this a little further up in the doc. Let me know if you think it should be at the bottom and I can move it today.
Updated documentation for Set-SPOTenantPreAuthSettings to include new expected API behaviors and parameters related to Microsoft Graph URL settings. Added missing parameters and API behavior
Neil Hodgkinson (nellymo)
left a comment
There was a problem hiding this comment.
Engineering to check on the changes
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit b742f65: ✅ Validation status: passed
For more details, please refer to the build report. |
|
|
||
| For APIs with a Microsoft Graph alternative, if the setting is enabled for the calling application, the response uses a Microsoft Graph URL, and the application can call that URL by using an appropriate Microsoft Graph access token. | ||
|
|
||
| For APIs without a Microsoft Graph alternative, the returned SharePoint Online URL does not contain temporary authentication information. The application must obtain an appropriate Microsoft Entra access token for SharePoint Online and include it when calling the returned URL. |
There was a problem hiding this comment.
We actually keep the behavior the same. So in this case we still return preauth urls.
There was a problem hiding this comment.
We can use this from the previous docs:
For APIs without a Microsoft Graph URL alternative, the response will continue to include a preauthenticated SharePoint Online URL.
There was a problem hiding this comment.
Updated to reflect the correct statement
|
|
||
| For APIs without a Microsoft Graph alternative, the returned SharePoint Online URL does not contain temporary authentication information. The application must obtain an appropriate Microsoft Entra access token for SharePoint Online and include it when calling the returned URL. | ||
|
|
||
| **APIs that currently return an HTTP 302 redirect** |
There was a problem hiding this comment.
This change is not made yet. Perhaps exclude for now?
There was a problem hiding this comment.
Removed the HTTP redirect section
|
|
||
| The tenant setting applies when the original request is made through Microsoft Graph. It does not change requests that applications make directly to SharePoint APIs. | ||
|
|
||
| **Affected API scenarios** |
There was a problem hiding this comment.
Same as above. Some of these changes are not available yet. Should we exclude them?
There was a problem hiding this comment.
lw-msft , Can you elaborate on which scenarios are not included yet. We can add them back as they become available.
|
|
||
| Affected APIs return content directly rather than redirecting the application to a temporary authentication URL. Applications must not depend on intercepting the redirect, extracting a temporary authentication value from the redirect location, passing the redirected URL to an unauthenticated client, or assuming that every content request returns an HTTP 302 status code. Applications should be prepared to process a successful content response from the original Microsoft Graph request. | ||
|
|
||
| **Direct SharePoint API requests** |
There was a problem hiding this comment.
This is a good callout we should keep this
Adriana Wood (AdwoodMicrosoft)
left a comment
There was a problem hiding this comment.
The added Graph URL guidance is important, but the current head still contains technically disputed behavior that could cause application authentication failures:
- Line 78 says APIs without a Microsoft Graph URL alternative return a SharePoint Online URL without temporary authentication information. The existing technical-review thread says those APIs continue returning a preauthenticated SharePoint URL until the broader retirement change. This also matches the published tempauth retirement guidance. Please correct the current-behavior statement and distinguish today's opt-in behavior from the April 1, 2027 retirement behavior.
- Lines 80-102 still document removal of HTTP 302 redirects and several API-specific behavior changes. The reviewer stated that some of these changes weren't implemented yet and suggested excluding them. Those threads remain unresolved. Please remove, clearly future-date, or product-owner-verify every scenario before publication.
- The replies saying the redirect section was removed and line 78 was corrected aren't represented in a commit: the current head is still
b742f65, and the disputed text remains. Please push the actual corrections and resolve the threads against the resulting head. - Add the effective timeline and lifecycle details, including the April 1, 2027 behavior-change date, whether
-UseGraphUrlIsEnabledand-UseGraphUrlAppsListare currently shipped or preview, and the minimum SharePoint Online Management Shell version that contains them. Confirm that the syntax, parameter types/defaults, empty-list semantics, and supported API matrix match the released module. - The branch is behind
main; please update it and rerun validation after the technical corrections.
The current automated checks pass, but they only show that this revision builds and meets structural policy. They don't validate runtime API behavior or feature availability.
Authoritative retirement guidance: https://devblogs.microsoft.com/microsoft365dev/pre-authenticated-tempauth-urls-are-retiring-move-to-microsoft-entra-id-tokens-before-april-1-2027/

Submitted via Learn Editor.