Update LegacyBrowserAuthProtocolsEnabled setting to reflect the ongoing deprecation#1047
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. 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 69a414e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 22953ca: ✅ 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 issues. Other issues are also a high priority. 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 |
This PR adds a note to the LegacyBrowserAuthProtocolsEnabled that warns that the protocol is being deprecated in Oct 2025 and will no longer be available. Since the deprecation is multiple phases, and not all customers will be blocked until late 2026, we cannot yet completely remove the setting, but will once possible.