Update: I just realized that I can install it if I download it and then bring it in via Apps > Upload a custom app, so it's only installing it from within App Studio that gives the error.
I'm trying to work through the sample app at https://learn.microsoft.com/en-us/microsoftteams/platform/get-started/get-started-dotnet-app-studio, but I'm stuck at the part where you install it into Teams.
I get the error: "Uploading custom apps is not allowed."
According to Prepare your Office 365 tenant, in the admin center, under Settings > Services & add-ins > Microsoft Teams > Tenant-wide settings > Apps, I should turn on "Allow sideloading of external apps." In my tenant, that is indeed turned off:
But I can't turn it on. It's disabled, saying the settings have moved to the "Microsoft Teams & Skype for Business admin center."
In that admin center, I went to Teams apps > Permission policies. There, for "Global (Org-wide default), I have "allow all apps" for everything:
.
For "Org-wide app settings", I have interaction with custom apps turned on:
.
Under Setup policies > Global (Org-wide default), I have "Allow uploading custom apps" on:
.
And I'm signed in as a user governed by that policy:
I'm stumped. What else do I need to do so that I can sideload a Teams app for development?
I had the same problem and it actually made me crazy especially because it may take a few hours to apply changes. Finally I was able to resolve the problem in the following way. I can imagine that certain steps are unnecessary but who knows.
By following instructions in the Manage app setup policies in Microsoft Teams, enable "Upload custom apps" in "Global (Org-wide default)".
Following same instructions created a custom setup policy with enabled "Upload custom apps".
Enable all permissions in "Global (Org-wide default)" as described in the Manage app permission policies in Microsoft Teams
Create a new permission policy with everything enabled.
Wait about an hour.
Assign these new policies to the user.
Make sure that everything what is mentioned in Manage custom app policies and settings in Microsoft Teams is enabled.
Wait another hour.
Quit desktop application, and start it again.
Now, finally, it works.
Related
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.
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?
Is it possible to disable Google Drive UI integration, for our new Google Webstore App?
Our web app uses the Google Drive API scope for managing users' documents, but we don't yet support Google Drive UI integration (i.e. we don't have a page which can take in a document ID and show appropriate content. The user would have to navigate from the home page instead). The app has been rejected from the GAM on this basis, and Google directed us here for technical support.
I have seen the following in the UI:
In the 'Apps Marketplace SDK' settings, the checkbox for 'Google Drive SDK' is checked & disabled here (project ID replaced with XXXXX): https://console.developers.google.com/project/XXXXX/apiui/apiview/appsmarket_component/googleapps_sdk.
In the 'Drive SDK' settings, I cannot find a setting to disable Google Drive UI integration here (project ID replaced with XXXXX): https://console.developers.google.com/project/XXXXX/apiui/apiview/drive/drive_sdk
We do hope to integrate with the Google Drive UI in the future. In the meantime we would like our new app to be available to our customers, for installation by their domain administrators.
Is there a known way to achieve this?
Thanks
You should be able to disable the UI integration from the Developer Console.
In the Drive API's "Drive UI Integration" tab, find the "Creating files" checkbox and make sure it is unchecked. Also remove any MIME types you specified. You may want to uncheck any of the other checkboxes below "Creating files" that you may have checked. Save those changes.
In the GAM SDK settings, you can uncheck the "Drive extension" box and save. That should disassociate your GAM app from being a Drive app as well.
I am trying to create a project in Google Developers Console.
Note: I am the Domain Administrator.
I keep getting this error message;
Error
Developers Console has not been activated for your account. Your account may be suspended or disabled. If you are a Google Apps user, ask your domain administrator to enable Apphosting Admin on your account.
See my steps to produce the error (screen shots):
https://drive.google.com/file/d/0Bytqhoir_Tt5QmFTazM0SzZONU0/view?usp=sharing
https://drive.google.com/file/d/0Bytqhoir_Tt5c3BwSnA3bThCSXc/view?usp=sharing
https://drive.google.com/file/d/0Bytqhoir_Tt5SVZZWTRfQVBTRUk/view?usp=sharing
Can anyone share some light on how to solve this issue? Please note that I am the domain administrator.
You need to enable the Cloud Console for your domain or at least the organizational unit that your user is in.
Go to your domain's Control Panel : https://admin.google.com
Click on the "More Google Apps" button. It might be in the "More Controls" section at the bottom of the screen.
In the next screen, click on the "Filters" button and uncheck "Show top featured services"
Once done, the list of service will get quite big. Look for "Google Developers Console", click on it.
Enable the service
It seems to have changed slightly. I had to go to Apps
Then click the Additional Google Services
Then you can find Google Developers Console in there
And then you can Enable the service by selecting ON for everyone