Updating unattended EWS scripts using modern auth
Hi there, a lot of possibilities about phasing out legacy authentication have been discussed here. But I still have a lack of information or let's say I want to find the most comfortable and most secure possibility for my customers. https://docs.microsoft.com/en-us/powershell/exchange/app-only-auth-powershell-v2?view=exchange-ps But if your scripts contain EWS connections you have to initialize a different way of authentication. So I found the following option using MSAL, unfortunately this does not work in unattended mode. https://morgantechspace.com/2022/03/connect-ews-api-with-modern-authentication-using-powershell.html And then there is the possibility using the secure application model. https://docs.microsoft.com/en-us/powershell/partnercenter/multi-factor-auth?view=partnercenterps-3.0#secure-application-model I got this working now, the creation of the token for the first time has to be done interactively and the token only lasts for 90 days. I read the hint for securely saving the token to the Azure KeyVault, but how do I do this and how can I re-call this token? Is there even a better way of refreshing the token manually? Is this now the new go-to solution for unattended EWS scripts, or do you have a even better solution?
SharePoint legacy app access control vs Conditional Access legacy authentication
If we have a conditional access policy that blocks legacy authentication, do we still need to set the SharePoint access control setting of 'Apps that don't use modern authentication' to block access? Is having a conditional access policy blocking legacy authentication for 'Exchange ActiveSync' and "other clients' not sufficient? Also, conditional access policy allows us to run in report-only mode or even test with few users first. Whereas there doesn't appear to be any such controls available for SharePoint setting.
