Microsoft Teams Mac Desktop App

  1. Microsoft Teams Mac Desktop App Downloads
  2. Is There A Microsoft Teams App For Mac
  3. Is There A Ms Teams App For Mac
  4. Microsoft Teams Mac Desktop App Windows 10
-->

Windows users

  • Microsoft Teams is now generally available for Office 365 customers, and for those of you who are planning to use it you may be looking for a way to deploy the Teams client to your user’s computers. The Microsoft Teams desktop client installer is available for Windows, Mac, and mobile devices.
  • SITUATION: When you receive a link to a Teams file or folder, or really anything in Teams, like a Planner task - it sends you to the sharepoint site, regardless of whether you have the Desktop App installed and even if it is open. RESOLUTION: Make links to any Teams elements open directly in the Teams Desktop App This will save so much time and frustration from people, and also make Teams seem.

Microsoft recommends that organizations use recent versions of Windows 10 with either Hybrid Domain Join or Azure AD Join configuration. Using recent versions ensures that users’ accounts are primed in Windows’ Web Account Manager, which in turn enables single sign-on to Teams and other Microsoft applications. Single sign-on provides a better user experience (silent sign in) and a better security posture.

Teams desktop applications will support one work/school and one personal account side by side in December 2020, with support for multiple work/school accounts coming at a later date. The following images show how users can add multiple accounts in Teams mobile applications. Free communication and collaboration app from Microsoft. Microsoft Teams is a free-of-charge social and communication software developed by the leading multinational technology development company, Microsoft, for desktop and mobile devices. Before, Microsoft offered only business-oriented Teams monthly paid subscriptions.

Microsoft Teams uses modern authentication to keep the sign-in experience simple and secure. To see how users sign in to Teams, read Sign in to Teams.

How modern authentication works

Modern authentication is a process that lets Teams know that users have already entered their credentials, such as their work email and password elsewhere, and they shouldn't be required to enter them again to start the app. The experience varies depending on a couple factors, like if users are working in Windows or on a Mac. It will also vary depending on whether your organization has enabled single-factor authentication or multi-factor authentication. Multi-factor authentication usually involves verifying credentials via a phone, providing a unique code, entering a PIN, or presenting a thumbprint. Here's a rundown of each modern authentication scenario.

Modern authentication is available for every organization that uses Teams. If users aren't able to complete the process, there might be an underlying issue with your organization's Azure AD configuration. For more information, see Why am I having trouble signing in to Microsoft Teams?

  • If users have already signed in to Windows or to other Office apps with their work or school account, when they start Teams they're taken straight to the app. There's no need for them to enter their credentials.

  • Microsoft recommends using Windows 10 version 1903 or later for the best Single Sign-On experience.

  • If users are not signed in to their Microsoft work or school account anywhere else, when they start Teams, they're asked to provide either single-factor or multi-factor authentication (SFA or MFA). This process depends on what your organization has decided they'd like the sign-in procedure to require.

  • If users are signed in to a domain-joined computer, when they start Teams, they might be asked to go through one more authentication step, depending on whether your organization opted to require MFA or if their computer already requires MFA to sign in. If their computer already requires MFA to sign in, when they open up Teams, the app automatically starts.

  • On Domain joined PCs, when SSO isn't possible Teams may pre-fill its login screen with the user principal name (UPN). There are cases where you may not want this, especially if your organization uses different UPNs on-premises and in Azure Active Directory. If that's the case, you can use the following Windows registry key to turn off pre-population of the UPN:

    ComputerHKEY_CURRENT_USERSoftwareMicrosoftOfficeTeams
    SkipUpnPrefill(REG_DWORD)
    0x00000001 (1)

    Note

    Skipping or ignoring user name pre-fill for user names that end in '.local' or '.corp' is on by default, so you don't need to set a registry key to turn these off.

Signing out of Teams after completing modern authentication

To sign out of Teams, users can select their profile picture at the top of the app, and then select Sign out. They can also right-click the app icon in their taskbar, and then select Log out. Once they've sign out of Teams, they need to enter their credentials again to launch the app.

Signing in to another account on a Domain Joined computer

Users on domain-joined computer may not be able to sign in to Teams with another account in the same Active Directory domain.

macOS users

On macOS, Teams will prompt users to enter their username and credentials and may prompt for multi-factor authentication depending on your organization's settings. Once users enter their credentials, they won't be required to provide them again. From that point on, Teams automatically starts whenever they're working on the same computer.

Teams on iOS and Android users

Upon sign in, mobile users will see a list of all the Microsoft 365 accounts that are either currently signed-in or were previously signed-in on their device. Users can tap on any of the accounts to sign in. There are two scenarios for mobile sign in:

  1. If the selected account is currently signed in to other Office 365 or Microsoft 365 apps, then the user will be taken straight to Teams. There's no need for the user to enter their credentials.

  2. If user isn't signed in to their Microsoft 365 account anywhere else, they will be asked to provide single-factor or multi-factor authentication (SFA or MFA), depending on what your organization has configured for mobile sign-in policies.

Note

For users to experience the sign on experience as described in this section, their devices must be running Teams for iOS version 2.0.13 (build 2020061704) or later, or Teams for Android version 1416/1.0.0.2020061702 or later.

Using Teams with multiple accounts

Is there a microsoft teams app for mac

Teams for iOS and Android supports the use of multiple work or school and multiple personal accounts side by side. Teams desktop applications will support one work/school and one personal account side by side in December 2020, with support for multiple work/school accounts coming at a later date.

The following images show how users can add multiple accounts in Teams mobile applications.

Restrict sign in to Teams

Organization may want to restrict how corporate-approved apps are used on managed devices, for example to restrict students' or employees’ ability to access data from other organizations or use corporate-approved apps for personal scenarios. These restrictions can be enforced by setting Devices Policies that Teams applications recognize.

How to restrict sign in on mobile devices

Teams for iOS and Android offers IT administrators the ability to push account configurations to Microsoft 365 accounts. This capability works with any Mobile Device Management (MDM) provider that uses the Managed App Configuration channel for iOS or the Android Enterprise channel for Android.

For users enrolled in Microsoft Intune, you can deploy the account configuration settings using Intune in the Azure portal.

Once account setup configuration has been configured in the MDM provider, and after the user enrolls their device, on the sign-in page, Teams for iOS and Android will only show the allowed account(s) on the Teams sign-in page. The user can tap on any of the allowed accounts on this page to sign in.

Set the following configuration parameters in the Azure Intune portal for managed devices.

PlatformKeyValue
iOSIntuneMAMAllowedAccountsOnlyEnabled: The only account allowed is the managed user account defined by the IntuneMAMUPN key.
Disabled (or any value that is not a case insensitive match to Enabled): Any account is allowed.
iOSIntuneMAMUPNUPN of the account allowed to sign in to Teams.
For Intune enrolled devices, the {{userprincipalname}} token may be used to represent the enrolled user account.
Androidcom.microsoft.intune.mam.AllowedAccountUPNsOnly account(s) allowed are the managed user account(s) defined by this key.
One or more semi-colons;]- delimited UPNs.
For Intune enrolled devices, the {{userprincipalname}} token may be used to represent the enrolled user account.

Once the account setup configuration has been set, Teams will restrict the ability to sign in, so that only allowed accounts on enrolled devices will be granted access.

To create an app configuration policy for managed iOS/iPadOS devices, see Add app configuration policies for managed iOS/iPadOS devices.

To create an app configuration policy for managed Android devices, see Add app configuration policies for managed Android devices.

How to restrict sign in on desktop devices

Teams apps on Windows and macOS are gaining support for device policies that restrict sign in to your organization. The policies can be set via usual Device Management solutions such as MDM (Mobile Device Management) or GPO (Group Policy Object).

When this policy is configured on a device, users can only sign in with accounts homed in an Azure AD tenant that is included in the “Tenant Allow List” defined in the policy. The policy applies to all sign-ins, including first and additional accounts. If your organization spans multiple Azure AD tenants, you can include multiple Tenant IDs in the Allow List. Links to add another account may continue to be visible in the Teams app, but they won't be operable.

Note

  1. The policy only restricts sign-ins. It does not restrict the ability for users to be invited as guest in other Azure AD tenants, or switch to other tenants.
  2. The policy requires Teams for Windows version 1.3.00.30866 or higher, and Teams for macOS version 1.3.00.30882 (released mid-November 2020).

Policies for WindowsAdministrative Template files (ADMX/ADML) are available from the Download center (the policy setting descriptive name in the administrative template file is 'Restrict sign in to Teams to accounts in specific tenants'). Additionally, you can manually set keys in Windows Registry:

  • Value Name: RestrictTeamsSignInToAccountsFromTenantList
  • Value Type: String
  • Value Data: Tenant ID, or comma-separated list of Tenant IDs
  • Path: use one of the following

ComputerHKEY_CURRENT_USERSOFTWAREPoliciesMicrosoftCloudOffice16.0TeamsComputerHKEY_CURRENT_USERSOFTWAREPoliciesMicrosoftOffice16.0TeamsComputerHKEY_CURRENT_USERSOFTWAREMicrosoftOffice16.0Teams

Example:SOFTWAREPoliciesMicrosoftOffice16.0TeamsRestrictTeamsSignInToAccountsFromTenantList = Tenant IDorSOFTWAREPoliciesMicrosoftOffice16.0TeamsRestrictTeamsSignInToAccountsFromTenantList = Tenant ID 1,Tenant ID 2,Tenant ID 3

Xcode version for el capitan

Policies for macOSFor macOS managed devices, use .plist to deploy sign-in restrictions. The configuration profile is a .plist file that consists of entries identified by a key (which denotes the name of the preference), followed by a value, which depends on the nature of the preference. Values can either be simple (such as a numerical value) or complex, such as a nested list of preferences.

  • Domain: com.microsoft.teams
  • Key: RestrictTeamsSignInToAccountsFromTenantList
  • Data Type: String
  • Comments: Enter comma separate list of Azure AD tenant ID(s)

Sign out on mobile devices

Mobile users can sign out of Teams by going to the menu, selecting the More menu, and then selecting Sign out. Once signed out, users will need to reenter their credentials the next time they launch the app.

Note

Teams for Android uses single sign-on (SSO) to simplify the sign in experience. Users should make sure to log out of all Microsoft apps, in addition to Teams, in order to completely log out on the Android platform.

Global sign in and sign out

Microsoft Teams Mac Desktop App Downloads

The Teams Android app now supports Global sign-in and sign-out, to provide a hassle free sign-in and sign-out experience for Frontline Workers. Employees can pick a device from the shared device pool and do a single sign in to 'make it theirs' for the duration of their shift. At the end of their shift, they should be able to perform sign out to globally sign out on the device. This with remove all of their personal and company information from the device so they can return the device to the device pool. To get this capability, the device must be in shared mode. To learn how to set up a shared device, see How to use a shared device mode in Android.

The sign-in experience looks similar to our standard Teams sign experience, while sign out will look like the following two images:

URLs and IP address ranges

Teams requires connectivity to the Internet. To understand endpoints that should be reachable for customers using Teams in Office 365 plans, Government, and other clouds, read Office 365 URLs and IP address ranges.

Important

Teams presently requires access (TCP port 443) to the Google ssl.gstatic.com service for all users; this is true even if you're not using Gstatic. Teams will remove this requirement soon (early 2020), and we'll update this article accordingly at that time.

Related topics

-->

The Teams Meeting add-in lets users schedule a Teams meeting from Outlook. The add-in is available for Outlook on Windows, Mac, web, and mobile.

Teams Meeting add-in in Outlook for Windows

The Teams Meeting add-in is automatically installed for users who have Microsoft Teams and either Office 2013, Office 2016, or Office 2019 installed on their Windows PC. Users will see the Teams Meeting add-in on the Outlook Calendar ribbon.

Note

  • There is no direct URL that links to the Teams add-in.
  • There are additional considerations if your organization runs both Teams and Skype for Business. Under some circumstances, the Teams add-in is not available in Outlook. See Upgrade from Skype for Business to Teams for details.
  • User permissions to execute the Regsvr32.exe file is a minimum requirement for the Teams Meeting add-in to be installed on the computer.
  • If users do not see the Teams Meeting add-in, instruct them to close Outlook and Teams, then restart the Teams client first, then sign in to Teams, and then restart the Outlook client, in that specific order.
  • If you are using an Office Outlook installation from the Microsoft Store, the Teams Meeting add-in isn't supported. Users who require this add-in are advised to install Click-to-Run version of Office, as outlined in Office on Windows 10 in S mode article.

Teams Meeting add-in in Outlook for Mac

The Teams Meeting button in Outlook for Mac will appear in the Outlook for Mac ribbon if Outlook is running production build 16.24.414.0 and later and is activated with a Microsoft 365 or Office 365 client subscription.​

The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks Send.

Teams Meeting add-in in Outlook Web App

The Teams Meetings button in Outlook Web App will appear as part of new event creation if the user is on an early version of the new Outlook on the web. See the Outlook Blog to learn about how users can try the early version of the new Outlook on the web.

The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks Send.

Teams Meeting add-in in Outlook mobile (iOS and Android)

The Teams Meeting button shows up in latest builds of the Outlook iOS and Android app.

The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks Send.

Teams Meeting add-in and FindTime for Outlook

FindTime is an add-in for Outlook that helps users reach consensus on a meeting time across companies. Once the meeting invitees have provided their preferred times, FindTime sends out the meeting invite on the user's behalf. If the Online meeting option is selected in FindTime, FindTime will schedule a Skype for Business or Microsoft Teams meeting. (FindTime will use whichever has been set by your organization as the default online meeting channel.)

Is There A Microsoft Teams App For Mac

Note

If you saved a Skype for Business setting in your Findtime dashboard, FindTime will use that instead of Microsoft Teams. If you want to use Microsoft Teams, delete the Skype for Business setting in your dashboard.

For more information, see Schedule meetings with FindTime.

Authentication requirements

The Teams Meeting add-in requires users to sign in to Teams using Modern Authentication. If users do not use this method to sign in, they'll still be able to use the Teams client, but will be unable to schedule Teams online meetings using the Outlook add-in. You can fix this by doing one of the following:

  • If Modern Authentication is not configured for your organization, you should configure Modern Authentication.
  • If Modern Authentication is configured, but they canceled out on the dialog box, you should instruct users to sign in again using multi-factor authentication.

To learn more about how to configure authentication, see Identity models and authentication in Microsoft Teams.

Enable private meetings

Allow scheduling for private meetings must be enabled in the Microsoft Teams admin center for the add-in to get deployed. In the admin center, go to Meetings > Meeting Policies, and in the General section, toggle Allow scheduling private meetings to On.)

The Teams client installs the correct add-in by determining if users need the 32-bit or 64-bit version.

Note

Is There A Ms Teams App For Mac

Users might need to restart Outlook after an installation or upgrade of Teams to get the latest add-in.​

Is there a microsoft teams app for mac

Teams upgrade policy and the Teams Meeting add-in for Outlook

Customers can choose their upgrade journey from Skype for Business to Teams. Tenant admins can use the Teams co-existence mode to define this journey for their users. Tenant admins have the option to enable users to use Teams alongside Skype for Business (Islands mode).

When users who are in Island mode schedule a meeting in Outlook, they typically expect to be able to choose whether to schedule a Skype for Business or a Teams meeting. In Outlook on the web, Outlook Windows, and Outlook Mac, users see both Skype for Business and Teams add-ins when in Islands mode by default. You can configure a Teams meeting policy setting to control whether users in Islands mode can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins.

Due to certain limitations in the initial release, Outlook mobile can only support creating Skype for Business or Teams meetings. See the following table for details.

Coexistence mode in the Teams admin centerDefault meetings provider in Outlook mobile
IslandsSkype for Business
Skype for Business onlySkype for Business
Skype for Business with Teams collaborationSkype for Business
Skype for Business with Teams collaboration and meetingsTeams
Teams onlyTeams

Set whether users in Islands mode can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins

As an admin, you can configure a Teams meeting policy setting to control which Outlook meeting add-in is used for users who are in Islands mode. You can specify whether users can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins to schedule meetings in Outlook.

You can only apply this policy to users who are in Islands mode and have the AllowOutlookAddIn parameter set to True in their Teams meeting policy. For steps on how to set this policy, see set the meeting provider for users in Islands mode.

Other considerations

The Teams Meeting add-in is still building functionality, so be aware of the following:

  • The Teams Meeting add-in requires an Exchange mailbox for the primary user scheduling the meeting. Ensure that you have at least one Exchange mailbox configured in your Outlook profile and use it to schedule Teams meetings with the add-in. For Exchange requirements, see How Exchange and Teams interact.
  • The add-in is for scheduled meetings with specific participants, not for meetings in a channel. Channel meetings must be scheduled from within Teams.
  • The add-in will not work if an Authentication Proxy is in the network path of the user's PC and Teams Services.
  • Users can't schedule live events from within Outlook. Go to Teams to schedule live events. For more information, see What are Microsoft Teams live events?.

Learn more about meetings and calling in Microsoft Teams.

Troubleshooting

Use the following steps to troubleshoot issues with the Teams Meeting add-in.

Teams Meeting add-in in Outlook for Windows does not show

If you cannot get the Teams Meeting add-in for Outlook to install, try these troubleshooting steps.

Download and run the Microsoft Support Recovery Assistant to perform automated troubleshooting steps and fixes.

Alternatively, perform the following steps manually:

  • Windows 7 users must install the Update for Universal C Runtime in Windows for the Teams Meeting add-in to work.
  • Check that the user has a Teams Upgrade policy which enables scheduling meetings in Teams. See Upgrade from Skype for Business to Teams for more details.
  • Check that the user has a Teams Meeting policy that permits the Outlook Add-in. See Manage meeting policies in Teams for more details.
  • Ensure the user has the Teams desktop client installed. The meeting add-in will not be installed when only using the Teams web client.
  • Ensure the user has Outlook 2013 or later installed.
  • Make sure the user has permission to execute regsvr32.exe.
  • Ensure that all available updates for Outlook desktop client have been applied.
  • Follow these steps:
    • Restart the Teams desktop client.
    • Sign out and then sign back in to the Teams desktop client.
    • Restart the Outlook desktop client. (Make sure Outlook isn't running in admin mode.)

If you still don't see the add-in, make sure that it isn't disabled in Outlook.

Microsoft
  • In Outlook, choose 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 then select Go…
  • Set the checkbox next to Microsoft Teams Meeting Add-in for Microsoft Office.
  • Choose OK on all dialog boxes and restart Outlook.

For general guidance about how to manage add-ins, see View, manage, and install add-ins in Office programs.

If the add-in still does not show, use the following steps to verify the registry settings.

Note

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

Microsoft Teams Mac Desktop App Windows 10

  • Launch RegEdit.exe
  • Navigate to HKEY_CURRENT_USERSoftwareMicrosoftOfficeOutlookAddins
  • Verify TeamsAddin.FastConnect exists.
  • Within TeamsAddin.FastConnect, verify LoadBehavior exists and is set to 3.
    • If LoadBehavior has a value other than 3, change it to 3 and restart Outlook.

Delegate scheduling does not work

If your administrator has configured Microsoft Exchange to control access to Exchange Web Server (EWS), a delegate won't be able to schedule a Teams meeting on behalf of the boss. The solution for this configuration is under development and will be released in the future. As a workaround, your administrator can add the following string to the EWS Allow List: 'SchedulingService'.

Related topics