You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if it is just me or what, but I have deployed a test custom copilot to a SharePoint site with SSO following your documentation. Everything is working as it should, however, every time a new interactive sign in is required (since, as I found out the SPA has a token expiry of 24 hours, so if you don't interact with the bot within a 24H timeframe, a new interactive sign-in is required. I only know this because initially, it got stuck on "Loading" as others have reported, but that turned out to be an issue with my Redirect URIs, but I digress). Is this normal? I have granted admin consent, but I am still getting prompted every time this interactive sign in process is getting kicked off
I don't anticipate that these copilots will be used daily by users as they will mainly be used to answer HR and IT questions as needed versus calling a ticket in.
Any help would be appreciated.
The text was updated successfully, but these errors were encountered:
I don't know if it is just me or what, but I have deployed a test custom copilot to a SharePoint site with SSO following your documentation. Everything is working as it should, however, every time a new interactive sign in is required (since, as I found out the SPA has a token expiry of 24 hours, so if you don't interact with the bot within a 24H timeframe, a new interactive sign-in is required. I only know this because initially, it got stuck on "Loading" as others have reported, but that turned out to be an issue with my Redirect URIs, but I digress). Is this normal? I have granted admin consent, but I am still getting prompted every time this interactive sign in process is getting kicked off
I don't anticipate that these copilots will be used daily by users as they will mainly be used to answer HR and IT questions as needed versus calling a ticket in.
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: