User Profile
joshualowerypromega
Copper Contributor
Joined 8 months ago
User Widgets
Recent Discussions
Re: Copilot for Sales Outlook addin error
Michael_Deacon TDLR: I thought i fixed it, but the error came back. The confusion is that the app store has two versions of this addin. One is called "Copilot for Sales" and it is billed as the enhanced application that works across Outlook, Teams and Outlook on the Web. There is a second addin called "Copilot for Sales for Microsoft Outlook" that says it only works in Outlook. This is only a theory so tread lightly. You cannot deploy both of them through the Integrated Apps process, but you can deploy the "classic" version through Centralized Deployment process. From the M365 Admin Center go to Settings-->Integrated apps. Across the top of the new window there are clickable links toAzure, Sharepoint, Teams, and Add-ins. SelectAdd-ins From the new window select "Deploy Add-in" HitNexton the wizard then select "Choose from the Store" Search forCopilot for Sales HitAddlocated next to "Copilot for Sales for Microsoft Outlook" then clickContinue Scope the deployment to a test account. (Not recommended to deploy to your users until you test.) Under deployment method, chooseOptionalthenNext Lastly, selectSaveto complete the deployment. Can take up to 48 hours to fully deploy This temporarily resolved the issue for my test account. I messed around with it all day yesterday, then came in this morning to find the error is back. Worth a try if you're willing to test.Copilot for Sales Outlook addin error
I have admin-deployed Copilot for Sales via M365 Intergrated App process. After about a week, we started getting dozens of users with an error message in the sidepane within Outlook. It simply states "We can't start this add-in because it isn't set up properly." I have tried to compare users who have the issue vs users who don't have the issue, but they appear to be on the same versions of Outlook (16.0.17531.20152). The addin was deployed on May 9th and issues started coming in around May 20th and I can't seem to find any rhyme or reason to some users error. What is also confusing is the addin technically "works", it just constantly is generating that error every time they open a new emailSolved
Groups
Recent Blog Articles
No content to show