Group policy will always override user settings and users are prevented from changing add-in settings for add-ins that have been configured by the group policy List of Managed Add-ins.ДЇor Outlook, the registry keys and settings are described in the following tables.

Beginning with Office 2013, system administrators can configure an enhanced level of control for add-ins by using group policy. The user has control over which add-ins run on their computer. System administrator control over add-ins Polling is an expensive operation, so always prefer an event-driven model over polling. In Outlook 2013, calls to the Outlook object model return E_RPC_WRONG_THREAD when the Outlook object model is called from a background thread. Avoid making long-running Outlook object model calls if possible. If possible, cache data locally rather than making expensive network calls during the FolderSwitch and BeforeFolderSwitch events of an explorer, or Open events of an item.Д«e aware that all calls to the Outlook object model execute on Outlook's main foreground thread. If you have long-running tasks such as making an expensive connection to a database, defer those tasks to occur after startup. Prefer native COM add-ins over managed add-ins because managed add-ins must incur the overhead of loading the. While most add-ins will not be disabled by the add-in disabling feature, you don't want your add-in to be disabled consistently.ДЇollowing are some suggestions for improving add-in performance: However, you can re-enable add-ins and prevent add-ins from being auto-disabled by other Office programs. Programs in Office 2013 and later versions provide add-in resiliency, meaning that apps will disable an add-in if it performs slowly.

Outlook 365 add ins ever