Troubleshoot Outlook Plug-In for Teams

-
It can be happen, that the Outlook Plug-In for Teams isn't showing up or is removed during a Teams client updates.

This behavior is well-known issue and can be solved with some of the following procedures:

Install the Teams app as an administrator of the Windows computer.

Download, install and sign into Teams and then restart Teams and Outlook, in that order. 

To ensure that the add-in is installed and loaded correctly, you may need to restart Teams and Outlook after installing.  Follow these steps:

  • Download the Teams desktop app, run it, and sign in at least once.
  • After signing into Teams, restart the app.
  • Restart Outlook (after restarting Teams).
Ensure that the add-in is installed and enabled.  If after all that, you still don't see the add-in, make sure that it isn't disabled for some reason.

  • In Outlook, click File and then Options.
  • Select the Add-ins tab of Outlook Options dialog box
  • Confirm that Microsoft Teams Meeting Add-in for Microsoft Office is listed in the Active Application Add-ins list
  • If the Teams Meeting Add-in is listed in the Disabled Application Add-ins list, select COM Add-ins in Manage and click Go…
  • Set the checkbox next to Microsoft Teams Meeting Add-in for Microsoft Office
  • Restart Outlook

Mostly you Outlook Plug-In will be reactivated.



Comments

  1. LoraJuly 24, 2018 at 11:29 AM

    And administrator mode works okay with VPN, doesn't it?

    ReplyDelete

Post a Comment

Popular posts from this blog

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more