![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 28.999999999999996%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENR%3C/text%3E%3C/svg%3E)
Microsoft 365 and Office | Development | Other
Building custom solutions that extend, automate, and integrate Microsoft 365 apps.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 9%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
Hi @Nathan Rosales
Thank you for reaching out to the Q&A Forum.
Based on the information you shared, I understand that your issue is that the buttons you added to the Outlook ribbon only appear in Classic Outlook, but do not show up in New Outlook or Outlook on the web.
After doing some research, this behavior is expected due to platform differences, and it is important that the Unified Manifest (JSON format) is configured correctly for commands to appear across different Outlook versions. You currently have two buttons:
-One button to open a Task Pane (“Test”)
-One button to execute a JavaScript function (“Perform an action”)
From your manifest, the runtime configuration appears mostly correct:
-TaskPaneRuntime: This runtime is of type general with lifetime: short and is used for opening the task pane. It includes an action with "id": "TaskPaneRuntimeShow" of type openPage, pointing to the task pane HTML page (e.g. TaskPaneShell.html). This part is already configured correctly.
-CommandsRuntime (for executeFunction actions): The button with "actionId": "action" must correspond to an action with the same ID defined in this runtime, and the function must be associated in commands.js using Office.actions.associate(...). Please verify that this association exists.
Regarding the Ribbon configuration, this section determines whether buttons appear only in Classic Outlook:
-You are using "contexts": ["mailRead"], which means the buttons will only appear when reading an email. This is correct for your intended behavior. If you want the buttons to also appear while composing an email, you will need to add "mailCompose" to the contexts (and define the corresponding command group).
However, to support New Outlook and Outlook Web, you should additionally define Command Surface controls, which:
Do not belong in ribbons and must be defined directly under extensions
For example:
"extensions": [
{
...
"controls": [
{
"id": "msgReadOpenPaneButton",
"type": "button",
"label": "Test",
"contexts": ["messageRead"],
"actionId": "TaskPaneRuntimeShow"
}
]
}
]
You can refer to the following Microsoft documentation:
• extensionRibbonsArray object | Microsoft Learn
Additionally, based on reports from other users experiencing the same behavior, add-ins may not appear in New Outlook or Outlook Web if the manifest does not define appDomains correctly. Several users reported that once the correct appDomains entries were added, the issue was resolved.
You may find the following documentation helpful:
• AppDomain element in the manifest file | Microsoft Learn
Since I don’t have access to your environment or tenant configuration, I’ve shared the most relevant guidance and documentation available. I hope this information helps resolve the issue.
Please feel free to let me know if you need further assistance.
If the answer is helpful, please click ""Accept Answer"" and kindly upvote it. 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.
