We have a JavaScript Outlook on-send add-in (not Smart Alerts) that has recently been updated and published. The add-in is hosted on an Azure Storage Blob.
When Exchange admins go to remove the add-in, then re-add it using Integrated Apps, and follow the instructions at https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-deployment-of-add-ins?view=o365-worldwide, there is an error that says that the manifest file has failed:
Integrated Apps Failed Validation Message
How can we correct this problem?
Our manifest file is located at https://addins.sperrysoftware365.com/prd-addins/SafeguardSend/manifest.xml?ver=3.2
Why does it work when sideloading it into Outlook but not work when admins deploy it through Integrated Apps?
I suppose they do the same check as the store does. Try to run the following command to validate the manifest file on your machine:
npx office-addin-manifest validate -p MANIFEST_FILE
The office-addin-manifest package/tool calls a service endpoint (which is also used by the store) and just report the results.
Related
i have added a new app in to the Dev Portal the manifest version on 1.13 and the apps seems to working in the Teams, But the same app is not working in Outlook
The static tab url is localhost URL, I can see the error
owa.ven.extframework.js:2 Uncaught (in promise) Url is invalid
error details
To run in Outlook and Office, your app will need to reference the npm package #microsoft/teams-js#2.0.0 (or higher). While code with downlevel versions is supported in Outlook and Office, deprecation warnings are logged, and support for downlevel versions of TeamsJS in Outlook and Office will eventually cease.
See Extend a Teams personal tab across Microsoft 365 for more information on that.
In order to publish an addin to appstore, do we need to host the manifest (XML) + webpage (HTML, JS) for the addin?
The documentation implies that we should host the manifest on sharepoint and the webpage for the addin on our own servers for both the approval process, but also for end users to download and use the word addin.
The alternative is that we deliver these elements to MS and they host they host the addin on their servers.
Can you please confirm?
You must host your own add-in and associated resources. Microsoft will not host your webpage on your behalf.
You should submit the manifest to Microsoft for validation via the SellerDashboard (as explained here)
Using Azure Bot Service with C# Bot Builder SDK v4 v4.0.7 (the GA version released September 2018).
I'm using the BOT file to store configuration settings for a GenericService and so have changed the BOT file from the default that was provided with the Azure template.
Changes were made via MSBOT CLI.
When running locally via the emulator, the bot code sees modified local BOT file and all is good.
However, the BOT is never deployed to Azure and therefore the Azure service does not see my changes (it is stuck with the default BOT file). I've deployed via Visual Studio publish and GitHub CI.
I had to manually upload the file using Visual Studio Cloud Explorer and the bot was then able to use the modified version and all is good.
Question is why is the BOT file not deployed with the rest of the bot code and how can I make sure it is deployed. Not sure if this is a bug or not?
I believe this is the fix to deploy the .bot file. In Visual Studio,
Right click on the .bot file
Click Properties
Under file properties, verify that "Copy to Output Directory" option says Copy Always.
Here's a screencap:
I created a custom Outlook add-in using the Visual Studio Outlook Add-In project template. When I install the add-in from the manifest file using URLs pointing to a localhost site, everything works fine.
When I install the add-in from the manifest file using URLs pointing to an external site, it works in the Office365 Outlook web client, but not my desktop Outlook application. The add-in claims that it successfully installs, but then disappears from the list of "My Add-ins", and doesn't appear in the setting as an inactive add-in either. However, on the web client it is listed as an installed add-in and works completely fine.
Any idea on something I might be missing?
I have developed an ASP.NET MVC5 app for Office365 using latest update of the Office 365 API Tools for Visual Studio. The app works fine with my own development Office365 site.
I understand that Visual Studio has registered the app in my Active Directory for me.
What I don't understand is how I am supposed to allow my customers to use this app with theirs Office 365 installations.
Somehow they are supposed to register the app in their Active Directory - that is the step I don't know how to explain to them.
Is there an automated way to provision the app registration to a customer's Active Directory?
The same way Visual Studio did it when I started the development? How did it do that? Through what kind of API?
You need to set your app in Azure AD to be multi-tenant. You can do this through the Azure Management portal. (Applications > [Your Directory] > Applications > [Your Application] > Configure).
Once the app is multi-tenant, your customer can navigate to the app and log in to trigger the common consent flow. Assuming that your customer has the permissions necessary to consent and allows the app to access their data, the customer will then be able to use the app with their Office 365 subscription.