Can anyone please explain why the Office Add-In sub menu appears inconsistent?
The image below shows the dialog displayed after selecting 'Insert', 'My Add-Ins', 'See All'.
The 3 dialogs are from 3 machines that have the same version of Office installed, logged into the same live account and each machine has the same Trusted Location entry https://[???????].sharepoint.com/sites/AppCatalog/.
Yet i get 3 different sub menus. Any ideas?
I assume you refer to the tabs/section inside the dialog? It appears you have 3 different catalogs configured and potentially different identities on each machine. To give you context:
My Add-ins Tab: Shows all the add-ins for your current liveId/individual account.
My Organization: Only appears when you sideload an add-in via a file share. As you point out, via the trusted catalogs section on File>Options>Trust Center>Trusted Catalogs. We should probably rename that tab to "Developer" as reality is that is mostly intended for developers to sideload add-ins for testing purposes.
Office 365: This is the new Centralized Deployment feature that is currently in preview. It only appears when you are signed-in with an organizational account AND the tenant you are connected to supports the feature
Store. Self-explanatory.
So, double check your configuration and make sure to restart the application as configuration changes might not take effect until you do.
thanks for the reply Humberto,
I now have my Add-ins appearing for Desktop Excel.
If I deploy my Add-ins via the Centralized Deployment method, and they appear under 'Office 365' in Desktop Excel, how do i access them in Excel Online? The sub menu only contains 'My AddIns', 'My Organisation' and 'Store'
Related
I have a .xlam add-in which gives users an additional ribbon in Excel with several macros.
In the past, I have distributed these sorts of add-ins by saving the file to a saved network location, and asking the users to follow 5/6 simple steps to install (Excel > Options > Add-ins > Find the file and select OK). This also means that to update the toolbar across all users, I just need to overwrite the one file and everybody will then see the new version.
However, for the business I actually work for, many of our users are regularly at client sites, with no access to our own network - so the approach of saving the file to the network (as above) won't work.
I had heard that Add-ins could be rolled out via Office 365 admin center 'centralised deployment', however am I right in thinking this is for a different type of 'add-in'?
If so, are there any other approaches I can take to roll out a .xlam add-in to multiple users via the Cloud?
Thanks in advance!
Deployment by Office 365 Admin center is only for Web Add-in, the new generation, so your add-in in .xlam could not be deploy like that.
To deploy to many user you can do it by share network like you did, or by tool like SCCM to deploy more easily to lot of user
For info, I managed to solve this by saving the .xlam file into a Shared OneDrive folder, and instructing the users to install it from this location.
This allows me to update the .xlam file on OneDrive with new versions, and this will then automatically sync onto the users machines, meaning the toolbar is always up to date.
Like on the image:
Can't find any info on msdn. Also found sample Outlook add-ins on github, but they don't have icons on email items. Any help is appreciated.
It definitely does not apply to all add-ins installed from the marketplace. I have Salesforce plugin from marketplace and it is not pinned.
The configuration of the area where add-ins are pinned (known as "SurfaceArea") is stored in your mailbox under 7ae974c5-1af7-4923-af3a-fb1fd14dcb7a\OutlookOptions\RawJSON as a JSON object. If you are in a controlled environment, you can add GUID of your add-in to "ReadSurfaceAddins" property. You can use ApplicationImpersonation to do this for other people's mailboxes in your organization.
There are some plugins that pin themselves on install (the two examples I know are both from Microsoft Corporation). I tried to grab the cached manifest of one of those addins, change its GUID (so it won't conflict with the existing app in the store) and sideload it both as a user and via centralized deployment -- no luck, the add-in doesn't pin automatically. So the whatever magic makes those addins pin, does not happen in the manifest, but rather in some app store settings that aren't available to third party developers like us. UPD: I stand corrected, this feature is available to third parties as well - I've seen a third party add-in (Hubspot) that pins itself - again, this is an app store addin, not sideloaded.
You can go to Settings -> View all Outlook Settings -> Customize Actions -> Toolbar to configure the add-ins that appear on the Message compose surface. Additional documentation is here: https://support.office.com/en-us/article/customize-actions-on-your-messages-in-outlook-com-c8110dcb-892e-4903-94b3-f6eb41ada2a3
We have a Excel Web Addin, that was deployed to a group of users using the Office 365 Admin Center. But the add-in is not visible in Excel 2016 (Version 1803,Build 9126.2275, Click to Deploy) for those users.
Fiddler trace shows the following when the user tries to refresh the "Admin Managed" add-in dialog box.
Fiddler Trace
<MessageText>User must have a mailbox for name resolution operations.</MessageText>
<ResponseCode>ErrorNameResolutionNoMailbox</ResponseCode>
I also came across this post
"No add-ins currently available." when deploying add-in using Centralized Deployment
that talks about enabling Exchange. I am not sure what that really means.
So any help is appreciated in understanding the issue and resolution.
Thanks
-kudlur
Based on the error message, I'd assume you're having issues with users not being assigned mailboxes, which are required to enable Centralized Deployed add-ins.
Could you try running through the compatibility checking steps outlines here? It will help provide more detail on the exact issue.
Download the compatibility checker here: https://www.microsoft.com/en-us/download/details.aspx?id=55270
Run the compatibility checker Start an elevated PowerShell.exe window.
Run the \Import-Module O365CompatibilityChecker\ command.
Run the \Invoke-CompatibilityCheck\ command, which prompts you for TenantDomain (for example, TailspinToysIncorporated.onmicrosoft.com) and TenantAdmin credentials, and then requests consent.
You can also find more ways to debug in this help article: https://learn.microsoft.com/en-ie/office365/admin/manage/centralized-deployment-of-add-ins?redirectSourcePath=%252farticle%252fDetermine-if-Centralized-Deployment-of-add-ins-works-for-your-Office-365-organization-b4527d49-4073-4b43-8274-31b7a3166f92&view=o365-worldwide#BKMK_UserAndGroupAssignments?omkt=de-CH&ui=de-DE&rs=de-CH&ad=CH
Thanks, Alan
When trying to open excel TFS reports from within Visual Studio we keep getting prompted by excel for security credentials. It says it is trying to connect to
'http://myserver.mydomain.com'.
When I open the project portal using the above domain name in a browser and then try to open the report I get the prompt.
When I use just the server name, in other words,
'http://myserver'
to access the report, the security prompt goes away.
How do I configure TFS (or Visual Studio or whatever) so that when opening excel TFS reports it uses just the server name?
I have definitely run into this one before. It's a safety feature for Excel paired with SharePoint Document Libraries.
Essentially, here are the steps to "trust" the site:
Open Excel
Open Excel Options from the Backstage View
Head to Trust Center on right side at the very bottom.
Click "Trust Center Settings"
Click Trusted Locations
There are several things you want to do here next. If you want to trust network locations then click that option to enable it.
If you want to add a new trusted location then click "Add new location..."
Type in the full URL for the new location and then choose the box for "Subfolders of this location are also trusted."
That should do it!
BTW - from my un, you can have your IT department send these settings to all computers on your Active Directory domain through global policies so others don't have to go through these steps. They can also add this site to the Intranet Sites group in Internet Explorer for everyone internally which should help out in other similar scenarios.
I’ve got a moss document centre website with FBA and AD authentication enabled. After creating a picture library I seem to have reduced functionality when accessing the site through the FBA URL.
I’ve compared the web.config files from each IIS website and they are the same (apart from added FBA information that's required).
Here's two pictures to illustrate what I mean.
This picture shows the options available in the picture library when accessing the website through AD authentication:
alt text http://www.abbeylegal.com/Downloads/2006-07-26/Ad%20Authentication.jpg
This picture shows the reduced options available in the picture library when accessing the website through FBA authentication:
alt text http://www.abbeylegal.com/Downloads/2006-07-26/FBA%20Authentication.jpg
Anyone else seen this behaviour? I find it really strange.
This functionality is by design. As per Microsoft:
When you configure a zone to use forms authentication, the Enable Client Integration box is cleared by default. If a zone is configured in this way, the following changes occur in functionality:
Support for remote interfaces is turned off. That includes WebDAV, SOAP, and Microsoft Office FrontPage remote procedure calls (RPC). Some functionality is not available, such as Web folders or the Web services for accessing content in that site.
Some toolbar items no longer appear:
New Document
Open in Outlook
Open In Windows Explorer
Export to Spreadsheet
Open with Database Program
Explorer View option is hidden.
Create an Access View option is hidden.
In picture libraries, the following functionality is removed:
Upload Multiple
Edit Picture
Download
Send To
On the Edit Control Block (ECB) menu, the drop-down menu that appears when you click - items in document libraries, the following items are removed:
Edit in Word
Edit in Excel
Edit in PowerPoint
Discuss
Connect To Outlook
In slide libraries the following functionality is removed:
Publish Slide
Send to PowerPoint
Also, syncing SharePoint data with Microsoft Office Outlook no longer works.
Form Authentication will reduce some functionality such as in document library. We won't see the new document, be able to edit it in the spreadsheet, be able to open it with Windows Explorer etc.
For that, we need to enable the feature called Client Integration in Authentication
Provider. After enabling that, we'll get all menu items.