From time to time we push updates to our Apps on the Microsoft Office Store (AppSource). In most cases, the update is then automatically pushed to your app within a few days ensuring that your version is always up to date.
In some instances, users may also be asked to reinstall CloudExtend to ensure the app is on the latest version. In other instances, users may want to force an update to the app. This is done by removing and reinstalling the CloudExtend add-in.
We encourage you to check with your IT team before removing and reinstalling the App and ensure this process is OK with them. Once you've checked, follow the process below.
How to get your update now
Make a note of your version number (see here if you're not sure how to find your version number).
If you're running Outlook on the desktop click Get Add-Ins on your ribbon bar.
If you're running Outlook on the Web (ie via your browser) then (1) click on the Settings icon and (2) select Manage add-ins.
Before proceeding further check to see if your add-in is managed by your organization admin
Note, if your add-in was deployed by your administrator (it would say Admin Managed) please take note that it may have been deployed in a manner that prevents you from removing it and re-adding it. If this is the case please share this article with them so they can perform this action for you.
You can tell if your add-in is managed by your admin by checking for Admin-managed per the screenshot below.
On the next screen, locate the CloudExtend Add-In and (1) click the 3 dots at the bottom right, then (2) click Remove. Remember, if your add-in is managed by your organization this step may not be possible.
After the Add-In has been removed simply click Add to reinstall. There is no need to restart Outlook.
If you were forcing an update to a new version open the Add-In from Outlook and check that the version number at the bottom of the App is your expected version number.
Having trouble loading the App after the update?
If CloudExtend is not loading properly after the update please refer to this article for troubleshooting tips.