Custom App not getting updated

Question

Custom App not getting updated

Lakshmi Kanth Allamsetty 0

Hello, I have updated the custom add in outlook for updating the ribbon, I see its not getting updated. its taking a lot of time, but still I do not see anything.

0 comments

2 answers

Your answer

Answer 1

For an Outlook add-in update, the behavior depends on what was changed.

If only the web app files changed, such as HTML, CSS, or JavaScript, users should get the update automatically. Ribbon artifacts such as icons can be cached, so closing and reopening Outlook may be required. If the old UI still appears, clearing the Office cache can force Outlook to download the latest artifacts again.
If the manifest was changed, the add-in package must be updated and the manifest version must be increased. Without raising the manifest version, Outlook won’t recognize the update correctly.
If the add-in was deployed by an admin, some manifest changes require admin consent again before users receive the updated version.

For a ribbon update, check these items in order:

Confirm whether the ribbon change was made in the manifest.
- Ribbon command changes are part of the add-in package/manifest, not just the web app.
Increase the manifest version.
- Any manifest change requires the version number to be raised.
Redeploy the updated add-in package.
- If the add-in was published through organizational deployment or Marketplace, the updated package must be deployed again.
Check whether the manifest change requires admin consent.
- Admin consent is required again if the update changed:
  - requested permissions
  - scopes
  - events
- Until consent is granted, users can remain on the old version or be blocked from the add-in.
Restart Outlook.
- Cached add-in artifacts may delay what appears in the ribbon.
If it still does not update, clear the Office cache.
- This removes cached add-in artifacts and forces Outlook to download them again the next time Office starts.

If the symptom is specifically that Outlook shows an upgrade message, this indicates the add-in is still upgrading and the current item should be closed and reopened after a short wait.

Answer 2

Aetherin 3,005 Independent Advisor

Hi @Lakshmi Kanth Allamsetty,

If the add-in was deployed through the Microsoft 365 admin center, updates may take up to 72 hours to appear for all users. If this is a sideloaded Office Add-in and the ribbon changes were made in the manifest, Classic Outlook for Windows may still be loading the previously cached manifest.

To help narrow this down, could you please confirm:

Is this a web-based Office Add-in or a COM/VSTO add-in?
How is the add-in deployed: sideloaded, through the Microsoft 365 admin center under Integrated apps, or through Microsoft Marketplace?
If the ribbon change was made in the manifest, did you update the add-in version and redeploy the updated manifest?
When was the update deployed, and does the updated ribbon appear in Outlook on the web or for another test user?

Whenever you have a moment, please feel free to reply with the details above by leaving a comment under this post. Your answers will help me better understand the deployment scenario and suggest the most appropriate troubleshooting approach.

Thank you for your time, and I look forward to hearing from you!

Lakshmi Kanth Allamsetty 0 Reputation points

2026-10-08T13:55:14.4833333+00:00
Is this a web-based Office Add-in or a COM/VSTO add-in --this is web based and that too in Ubuntu, It is VSTO(new outlook version)

How is the add-in deployed: sideloaded, through the Microsoft 365 admin center under Integrated apps, or through Microsoft Marketplace? --- I deployed to the user already and updating it using the integrated apps page with the shown below.

If the ribbon change was made in the manifest, did you update the add-in version and redeploy the updated manifest? -- in the manifest I updated the url from where I want to see the ui that I developed. and every time I update the version every time, it throws error if the version is same.

When was the update deployed, and does the updated ribbon appear in Outlook on the web or for another test user?- I specifically had it for my user only.
Aetherin 3,005 Reputation points Independent Advisor

2026-10-08T14:28:34.3566667+00:00

Hi @Lakshmi Kanth Allamsetty,

Thank you for your reply.

Since the question is currently posted under Classic Outlook for Windows, could you confirm where the ribbon is not updating: Classic Outlook for Windows or New Outlook for Windows?

I am asking because you described the add-in as both web-based and VSTO. These are different add-in models. VSTO/COM add-ins are supported in Classic Outlook but not in new Outlook, while web-based Outlook add-ins can be used in new Outlook.

Also, when exactly did you deploy the updated manifest through Integrated apps?
Lakshmi Kanth Allamsetty 0 Reputation points

2026-10-08T19:26:17.0733333+00:00

If this is new outlook then yes, I have a new outlook.

I updated the app in the morning once and using AI I updated it one more in the afternoon, but I see none in the ribbon and I inspect the network tab to see from where the ribbon image is getting uploaded. the url in the manifest that I uploaded is different from what I uploaded through manifest.xml
Aetherin 3,005 Reputation points Independent Advisor

2026-10-09T10:33:22.7066667+00:00
Hi @Lakshmi Kanth Allamsetty,

Thank you for the additional details. Based on the screenshot and the outlook.office.com address, you are currently testing the add-in in Outlook on the web, not classic Outlook or new Outlook for Windows. Could you please help confirm the following?

Is the image URL shown in the Network tab the old URL, while the latest manifest.xml contains the new URL?

In Integrated apps, does the app show the latest manifest version, and is the deployment status successful?

When updating the manifest, did you keep the same add-in ID, or did you change it?
Lakshmi Kanth Allamsetty 0 Reputation points

2026-10-09T11:29:41.51+00:00
Is the image URL shown in the Network tab the old URL, while the latest manifest.xml contains the new URL? -- its the old url my devs url, and the manifest.xml contains QA url

In Integrated apps, does the app show the latest manifest version, and is the deployment status successful? - attached is the image shown in admins console

When updating the manifest, did you keep the same add-in ID, or did you change it? I do not change anything except for version and the url that it needs.
Aetherin 3,005 Reputation points Independent Advisor

2026-10-10T15:39:25.2466667+00:00

Hi @Lakshmi Kanth Allamsetty,

Thank you for the details and screenshot.

The admin center shows that Secure Transfers QA is deployed for Outlook with an OK status and was last modified on October 8, 2026. Since the add-in ID remained unchanged and only the version was updated, the deployment itself appears to have been completed correctly.

However, Outlook on the web is still requesting the old Dev URL even though the latest manifest contains the QA URL. This suggests that the updated manifest has not yet propagated to your account, or the previous version is still being cached. An OK status indicates that the add-in is active, but it does not guarantee that the updated manifest has already reached the client. Centralized add-in updates can take up to 72 hours to propagate.

Please allow up to 72 hours from the latest update, then test again using an InPrivate/Incognito window. Also, verify that your account is still assigned to the app under Integrated apps > Users and groups.

If Outlook continues to load the old URL after 72 hours, I recommend opening a support ticket with Microsoft 365 Support so they can investigate the add-in deployment and manifest propagation from the backend.