David Chesnut

Hi @Stephen-C-Butler, Thanks for catching this! The sample needs a polyfill added so it can work for ES5 on older browsers. I put this on the backlog to fix the...

Hi @lenain71, it's important to know that you can't deploy an add-in using SSO to a static web site. SSO requires you to run server-side code so you need to...

You're right, we need to add this to the official documentation. I'm tracking this on the backlog here, and internally in item 4688697. Will work to get to this soon....

Assuming you are using Windows for your Web server, be sure you made the following change so that your node server starts correctly: * Modify the package.json to just start...

Okay, I see now. The SSO template uses the command "start:server": "office-addin-sso start manifest.xml" in the package.json. And unfortunately, the **office-addin-sso** package does not work in an Azure environment. You...

Nice! For SSO, hopefully you can just put a wrapper around the call to getAccessToken and call it from your React pages when you need the token. For the fallback...

Thanks @vault79 for that detail! Would you be developing the SSO add-in on Visual Studio for Mac and testing in that environment? Thanks!

Hi @bpatra, sorry, but this sample was archived. Once samples are archived we no longer maintain them. If you are still encountering any issues that the active samples aren't helping...

Hi @elthombre I apologize for not getting this answer posted sooner. I thought I had posted awhile back, but I dont see it here, so I must have missed this...

Hi @elthombre, to be clear, when you mention the "pre-existing environment" are you referring to the M365 tenant where your add-in is deployed? As long as the admin consents your...