Our Read The Web application uses oauth2 for users to login using their school Microsoft accounts.
Unfortunately we have received reports that students are able to circumvent web filtering by using the github sign-in option (and a number of other clicks using the initial 'security' link on the github login page) which is causing a major issue with school that are using our product and others utilizing the Microsoft oauth2 login at:
https://login.microsoftonline.com/common/oauth2/authorize
This post mentions one method of circumvention:
https://feedback.azure.com/d365community/idea/4b1c76f0-f525-ec11-b6e6-000d3a4f06a4
This is not the exact path that we have found but similar.

Clicking the 'security' link at the bottom of this page provides a gateway to circumvention. There should not be -any- links on a sign-in page in my opinion.
After some research I have found what appears to be the answer that the sign-in options cannot be hidden.
https://docs.microsoft.com/en-us/answers/questions/318708/remove-sign-in-options.html
https://docs.microsoft.com/en-us/answers/questions/361891/how-to-remove-the-sign-in-options-from-the-login-p.html
Removing the entire sign-in screen is not an option.
There should be the option to remove or disable the sign-in options either at the oauth request level at the very minimum. Certainly there should not be any links on any sign-in page other that what are strictly required for operation.
