I am trying to get my first Outlook Web add-in to work. So I:
Followed the instructions at https://learn.microsoft.com/en-us/office/dev/add-ins/tutorials/outlook-tutorial "Tutorial: Build a message compose Outlook add-in"
Per those instructions, I used the Yeoman generator to create an Office Add-in Task Pane project for Outlook. I followed the instructions to the "Test the generated add-in". So only the manifest had been changed. A very simple add-in at this point.
Tried npm start from the command line.
>npm start
> office-addin-taskpane-js#0.0.1 start C:\Users\Lindsay\OutlookTestAddin2\OutlookTestAddin2
> office-addin-debugging start manifest.xml
Debugging is being started...
App type: desktop
Enabled debugging for add-in a35130ed-92ee-4a47-a5e2-4588da510b2e.
Starting the dev server... (webpack serve --mode development)
The dev server is running on port 3000. Process id: 14044
Sideloading the Office Add-in...
Debugging started.
At this point, I can view the welcome page in a browser at the URL https://localhost:3000/taskpane.html.
Outlook is started with as a result of npm start. There is no "Show Taskpane" button to be found anywhere in Outlook.
Navigated to https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/sideload-outlook-add-ins-for-testing to follow instructions for "Sideload manually". This PC has Outlook 2016, so went to that section.
It says to select the "Get Add-ins" button, but this button is greyed out.
Checked File > Options > Trust Center > Trust Center Settings > Privacy Options > Privacy Settings and looked for “Enable optional connected experiences” as noted in http://makerblock.com/2021/05/how-to-fix-outlook-get-add-ins-grayed-out-button/ and several other pages. “Enable optional connected experiences” does not exist in my Outlook installation. "Turn on all connected experiences" does exist and is enabled.
Looked at other alternatives for sideloading problems. Found Unable to sideload outlook add-in says "It turns that under settings you may need to turn on which "actions" are available in your read/compose pane." I am not finding exactly to which "settings" this refers.
Tried the same on a different PC with Office 365. The results were essentially the same: No "Show Taskpane" button and the "Get Add-ins" button is greyed out. In this case, “Enable optional connected experiences” exists and is checked.
Seems more difficult than it should be. What am I missing here?
Thanks in advance...
After a lot of looking, I ran across the answer to my own question: on https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/add-in-requirements , I have found a statement that says: "The client must be connected to an Exchange server or Microsoft 365 using a direct connection. When configuring the client, the user must choose an Exchange, Office, or Outlook.com account type. If the client is configured to connect with POP3 or IMAP, add-ins will not load." I had only POP3/IMAP accounts, and when I added an Outlook.com account, it magically began working.
Related
I'm working on an outlook add-in I can't get event-based activations to work on the web client (but do actually work on the Mac Outlook app). I've been trying to run the examples hosted on github, both outlook-set-signature and outlook-encrypt-attachments provided by the Microsoft team.
And add-in is correctly loaded. I can manage to open the sidepanel and follow the instructions, but nothing changes. Trying the same thing using the Outlook client on Mac OS works as expected.
Here are my reproduction steps:
Visit https://outlook.live.com/calendar/
New event > Get Add-ins > My Add-ins > "Add Custom Addins" > From URL > Paste "https://officedev.github.io/Office-Add-in-samples/Samples/outlook-encrypt-attachments/manifest.xml"
Go back to the calendar app > Click on the three dots button > click "Event Activation Example" addin > The sidepanel shows as expected
Discard the event and create a new one
Add a new participant to the event and expect a notification / or add any lightweight attachment and expect an automatically generated encrypted version of the attachment
Nothing happens 🤷 . According to the docs, a notification message should be shown
This "unresponsiveness" also happens with my own add-in and also in another example provided by the outlook team https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/outlook-set-signature.
BUT, these add-ins do actually work when I use them on my Mac OS Outlook app (OS Version: Ventura). So I'm wondering if there's any limitation for event-based activations for non-365 users using outlook on a web browser.
I'm wondering if there's any limitation for event-based activations for non-365 users using outlook on a web browser
Classic Outlook UI when connected to Exchange on-premises doesn't support the requirement set 1.10 where the event-based activation was introduced.
Modern Outlook UI when connected to Exchange Online: Microsoft 365 subscription, Outlook.com supports the Outlook add-in API requirement set 1.10.
You can find the Outlook client support for specific requirement sets in MSDN.
Also you may find the Debug your event-based Outlook add-in page helpful.
Event based add-ins are currently supported for commercial accounts as they are only available as part of admin deployment. Supporting event-based activation for user acquired add-ins is on the road map and we will consider this as part of that requirement. We don't have an ETA for this yet.
I have created an custom outlook add in. When I side load it on using the website it works with no issues. When I go into the Outlook app and try to side load, it will install but not show up on the task pane. Is there a reason for this? Thanks!
There are multiple reasons why your add-ins may not be displayed in Office applications/task panes. One of them is the use of http protocol instead of https.
Another point is the privacy control setting in the registry that can be distributed by group policies. Especially the key:
HKEY_CURRENT_USER\Software\Policies\Microsoft\office\16.0\common\privacy -> controllerconnectedservicesenabled
if it is set to dword:00000002 (which is disabled).
You need to change it to dword:00000001 (enabled) and the add-in may immediately appear.The relevant information can be found in the article.
But I'd suggest starting from the Troubleshoot development errors with Office Add-ins article.
I'm currently learning Teams development and I just installed the Teams Toolkit extension. Following the quickstart guide, launching the app opens my browser with the Teams web app and the message
App not found, Please verify the app and it's[sic] access
permissions.
Fortunately, this app can still be launched when selecting the "Preview in Teams" option in the Developer Portal.
Quoting the GettingStarted.txt:
If you Start Debugging in a browser and Teams shows the message "App not found, Please verify the app and it's access permissions", it means the app hasn't been uploaded to Teams Dev Portal. To resolve this, follow the steps in the Quick start section above. The Project > TeamsFx > Configure for SSO menu command will do this step for you.
Except it was successfully uploaded to Dev Portal.
What I did
Did this "Configure for SSO" thing. No problems with that and the app was successfully added to the Developer Portal.
Where I searched for an answer
VS Marketplace page for Teams Toolkit (Reviews, Q&A)
Github page (issues) for Teams Toolkit
This very site - Stack Overflow.
Obviously, I'm not 100% sure that I haven't missed anything.
Temporary solution
In the meantime, I set the "launchBrowser" property to "false" in launchSettings.json. However, it's a waste of time to constantly go back to the Developer Portal to launch it, especially when the functionality is there.
Visual Studio 2019, Microsoft Development Account.
Thanks in advance.
We tried to repro this issue at our end and it is working fine for us. Could you please make sure app is opened in same tenant with which you configured for SSO. Also please remove all credentials from cache to make sure its not taking another credentials and try again.
Assuming nothing else was changed from the new project template, there are a few things you can try to narrow down the issue.
Open your browsers web dev tools and watch the console after clicking the Add button (before you see the error message). Sometimes a useful error message from the developer portal helps identify the issue.
Verify that when Visual Studio launches the URL, the correct tenant is loaded in Teams.
Run the project in VS, then manually navigate in your browser to the endpoint of your tab that you expect to work. It would be something like https://localhost:44357/tab by default (the value is in the manifest.json). The sample won't work completely because it's not running inside Teams, but you should be able to verify it's working locally.
If none of that helps, please log an issue on the GitHub page and we can investigate a bug.
We are working on an Outlook add-in that uses the On-send feature (https://learn.microsoft.com/en-us/outlook/add-ins/outlook-on-send-addins?tabs=unix). We want to know what our options are when it comes to deploying this add-in to actual users, with the focus being on users running Outlook on Mac. Per documentation, On-send Add-ins are not allowed on AppSource. The ideal flow we are looking for is one where there's little to no manual action required on behalf of either the end-users or the Admins.
Is there a way to deploy the add-in automatically on the end-user device (running Mac), with neither any admin-side action required, nor any manual action required by the user -- e.g., by downloading the Add-in manifest, and running a script on the device?
I'm aware user can sideload the manifest once the manifest is downloaded, but this is not acceptable in our case; we are looking for a way where the installation of the add-in is automated, without requiring any manual action on behalf of the user.
If the above is not an option, what is the recommended way to deploy the add-in? I found two links from MS, with possibly conflicting info; which of these two is the right one to try?
The first one is "Publish Office Add-ins using Centralized Deployment via the Office 365 admin center" from https://learn.microsoft.com/en-us/office/dev/add-ins/publish/centralized-deployment#end-user-experience-with-add-ins. Looks like this is supposed to be done from the O365 Admin Console --> Settings > Services & add-ins.
This approach requires (from https://learn.microsoft.com/en-us/office365/admin/manage/centralized-deployment-of-add-ins?view=o365-worldwide) the following as pre-requisites; are all of them actually required?
"have Exchange Online and active Exchange Online mailboxes" -- is there a difference between "Exchange Online" and "active Exchange Online mailboxes"?
"Version 1701 or later of Office 365 ProPlus." -- does this apply for Mac as well? If so, is there such a version for Mac?
"Your subscription'd directory must either be in, or federated to Azure Active Directory."
Looks like there's a Powershell-based alternative to this: https://learn.microsoft.com/en-us/office365/enterprise/use-the-centralized-deployment-powershell-cmdlets-to-manage-add-ins. Is this subject to the same requirements as the above?
The second flow, which is more geared towards Outlook (rather than the other Office apps) is https://learn.microsoft.com/en-gb/exchange/clients-and-mobile-in-exchange-online/add-ins-for-outlook/specify-who-can-install-and-manage-add-ins?redirectedfrom=MSDN. This is to be initiated from Exchange admin center under Organization > Add-ins > New Add Icon
Does this work with a non-ProPlus O365 subscription as well?
Does this work outside of Azure AD?
(Assuming Bullet 1. is not an option so we have to go with 2.) After deploying add-in from admin, is further action required to activate it on the end-user device?
Per https://learn.microsoft.com/en-us/office/dev/add-ins/publish/centralized-deployment#end-user-experience-with-add-ins:"For Outlook 2016 or later, users can do the following: In Outlook, choose Home > Store. Choose the Admin-managed item under the add-in tab. Choose the add-in, and then choose Add."
(Again assuming Bullet 1. is not an option so we have to go with 2.) Is there API support to help automate bullets 2 and 3?
Seems that UI was changed once again and I cannot deploy "Hello world" Gmail Contextual Gadget following the steps provided by Joc (Gmail contextual gadget):
There are no "Allow individual install" on the step #7
I also cannot find "Test installation flow" (step #10)
The gadget is not listed in the Marketplace list (step #11)
Could you please assist me?
In google apps marketplace sdk API, in tab configure, after Application info section, there is a checkbox Enable individual install
After you save changes at the bottom of this page there is a button Test installation flow at the top of the page. I admit, sometimes it doesn't appear to me.
the Marketplace list I can't reach at the current time. I don't know how to be an administrator or how to make a free trial domain (although it's written in apps.google.com)