Because of this, Microsoft Teams Rooms resource accounts shouldn't be configured to use multi-factor authentication (MFA), smart card authentication, or client certificate-based authentication (which are all available for end users). This is one of the key differences between how modern authentication works for user accounts versus resource accounts that are used by Microsoft Teams Rooms. The modern authentication mechanism uses the resource owner password credentials authorization grant type in OAuth 2.0, which doesn't require any user intervention. When you use modern authentication with the Microsoft Teams Rooms application, Active Directory Authentication Library (ADAL) is used to connect to Microsoft Teams, Exchange, and Skype for Business. Modern authentication is supported on Microsoft Teams Rooms version 4.4.25.0 and later. If you have an on-premises deployment of Exchange server or Skype for Business server, configure hybrid modern authentication with Azure Active Directory (Azure AD) to enable using modern authentication. Modern authentication is recommended for all customers using Microsoft Teams Rooms with Microsoft 365 or Office 365. This means that authentication for Teams Rooms happens in a different way than for end-user devices. Teams Rooms uses a dedicated resource account to allow for always-on capabilities, calling scenarios (for devices configured with a calling plan), and custom lockdown mechanisms. The application connects to Microsoft Teams, Skype for Business, and Exchange to get resources for the resource account to enable calling and meeting experiences.
Learn how to configure modern authentication for Microsoft Teams Rooms on WindowsĪuthentication in Microsoft Teams Rooms on WindowsĪccount management for Microsoft Teams Rooms is handled at the application level.
0 kommentar(er)
