I am interested in learning more about the attack vector that you describe here. This is someone creating https: // evilspoof / and placing your web application inside an iframe. Then, so that the end user goes to https: // evilspoof / and clicks some things inside your add-in?
Do you authenticate your users somehow? And they were worried that if they log into your site legally ... then when they go to the malicious site, they are already logged in, and thus the clicks / actions on your page will work, since they have already been authenticated?
: https://dev.outlook.com/reference/add-ins/Office.context.mailbox.html#getUserIdentityTokenAsync
. Exchange Server , . OWA/Outlook, . , getUserIdentityToken, . . , . , - ( ), ... ... ?