A family of Microsoft word processing software products for creating web, email, and print documents.
Hello @Rakesh Khullar
Welcome to the Microsoft Q&A Community!
Thank you for reaching out and sharing a detailed description of your scenario.
Based on your description, it appears your add‑in is a classic COM add‑in loaded through mscoree.dll. Microsoft is gradually guiding developers toward more modern and fully supported Office extensibility models.
To help with that transition, I recommend reviewing Microsoft’s official guidance on evolving or upgrading existing solutions: VSTO add-in developer's guide to Office Web Add-ins - Office Add-ins | Microsoft Learn
This article outlines recommended approaches for moving from legacy COM/VSTO models toward newer, more robust, and fully supported Office Add-in technologies. It may provide clarity on how your current architecture affects trust behavior, certificate handling, and how publisher information is surfaced within Office.
If the issue still persists after reviewing the transition guidance and validating your add‑in’s signing and deployment steps, please note that the Q&A forum mainly focuses on general Office usage issues. For deeper engineering insights, especially regarding COM add-in loaders, trust mechanisms, and certificate requirements, I recommend posting your question in the Microsoft Tech Community, where product engineers and experienced developers can provide more targeted assistance.
The experts there can help analyze advanced add‑in architectures and provide more specialized solutions.
Thank you in advance for your cooperation and understanding. Let me know how it goes on your end.
If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.