Announcement ID | MC715681 | Published Date | 02-14-2024 | |
Service | microsoftteams | Last Updated | 02-14-2024 | |
Category | Plan for change | Expiration Date | 06-30-2024 | |
Roadmap ID | Action Required by Date | |||
Tags | Major update, Admin impact, Retirement, User impact |
Summary |
---|
Microsoft Teams for Windows is discontinuing support for the legacy ADAL Authentication SDK. Organizations that haven't transitioned to New Teams on Windows PCs may be impacted. New Teams removes support for ADAL, which may cause sign-in issues for impacted PCs. Organizations can identify if they rely on ADAL for Teams sign-in using Entra sign-in logs. If sign-in issues occur, organizations should try signing in to New Teams and contact their CSAM for further assistance. |
More Information |
---|
Note: This message is relevant to organizations that haven't yet fully transitioned to New Teams on Windows PCs. If every Teams user in your organization is already using New Teams, no further action is required. New Teams removes support for ADAL (Active Directory Authentication Library), a legacy SDK used in rare cases by Teams Classic. This change is part of our broader effort to improve performance and security. On Windows PCs, some third-party/custom sign-in solutions leverage undocumented hooks which cause Teams Classic to fall back to the legacy ADAL SDK. This fallback path doesn't exist in New Teams. When this will happen: As your organization transitions to New Teams. How this will affect your organization: Teams users on impacted PCs may not be able to sign in to New Teams. How to identify if your organization relies on ADAL for Teams sign-in: You can leverage Entra sign-in logs to make this determination:
What you need to do to prepare:
|