Hi @Spkn
Thank you for reaching out.
The "Allow public client flows" setting is related to the OAuth 2.0 client credentials flow, which is used by confidential client applications to authenticate and obtain access tokens from the Microsoft identity platform.
When this setting is enabled, public client applications (such as mobile or desktop applications) can also use this flow to obtain access tokens. This can be useful in scenarios where the client application cannot keep a client secret confidential, such as in a native mobile application.
If you change the default value to "Yes" for the "Allow public client flows" option in the advanced setting, the application registration is a public client application and a certificate or secret isn't required. The "Yes" value is useful when you want to use the client application in your mobile app or a JavaScript app where you don't want to store any secrets.
Regarding your question, changing this setting to "Yes" should not affect the functionality of clients that are currently using your application, as long as they are using confidential client applications. However, if any of your clients are using public client applications, they will need to update their application to use the client credentials flow to obtain access tokens.
It is important to note that enabling public client flows can increase the risk of unauthorized access to your application's resources. Therefore, it is recommended to only enable this setting if it is necessary for your scenario and if you have implemented appropriate security measures to mitigate the increased risk.
Hope this will help.
Thanks,
Shweta
Please remember to "Accept Answer" if answer helped you.