ASK: support nested security groups in M365 Centralized Deployment Most organizations have already set up security groups before deploying Add-ins. Using those existing groups would be an efficient way to determine what add-ins should get deployed to what users. But because of Centralized Deployment not supporting nested security groups, organizations are forced to create new dedicated flat security groups for Add-in deployment. They also need to adjust their talent onboarding and leave processes, removing and adding users from and too those new groups. This is an extra effort that many organizations need to organize and fund only because nested groups are not supported in Centralized Deployment.
... View more
Currently, VSTO/COM add-ins are loaded and started automatically when an Office host starts. It allows adding capabilities or trigger actions without the user having to do anything.
However, office-js add-ins are only loaded in the document after the user triggers the loading the runtime, for instance by clicking on the add-in ribbon command. Setting Office.addin.setStartupBehavior(Office.StartupBehavior.load) is an effective way to load the add-in every time the document starts but it only applies to the current document. There doesn't seem to a way to apply it to all new and future documents.
Ideally, there would be a way in admin.microsoft.com to specify that an add-in must be loaded every time a new document starts (or an option in the manifest).
... View more
(Full story: https://github.com/OfficeDev/office-js/issues/2358) Problem: Back in Office add-ins Community call March 09, 2021, Microsoft revealed that admin-deployed add-ins would be automatically pinned to the ribbon in Web Outlook starting 21 April, 2021. We have many customers who already had deployed our add-in via Centralized Deployment before that date, but would now like to have it auto-pinned in Web Outlook. However, in our internal testing and testing done by our customers, re-deployed (remove+add) add-ins are not automatically pinned in Web Outlook. In addition to lack of auto-pinning, we are naturally not seeing the "nudge" notification. Completely new add-ins (not previously centrally deployed) are properly auto-pinned. I suspect the issue is in the design - the auto-pin was probably designed to increase the visibility of completely new add-ins, hence the nudge notification. But the auto-pinning is needed also for previously deployed add-ins. Centralized Deployment probably remembers the add-in was previously deployed (because of the same App ID) so neither auto-pinning nor nudge notification are triggered. Expected behaviour: Add-ins deployed via Centralized Deployment before April 21, 2021 should be auto-pinned in Web Outlook when they are re-deployed or updated. They don't need to have the nudge notification (unless you can track whether the user has ever used the add-in).
... View more
See more ideas labeled with:
Office Add-ins deployment
– New Idea
– under Review
– Rolled out
– More info required
– Not at this time
Welcome to the Microsoft 365 Community! This is the place to get the latest news, participate in live events, share best practices, and discuss topics related to Microsoft 365.