편집

다음을 통해 공유

Know about New Microsoft Teams client

  • 아티클

Important

The Classic Teams client reaches end of availability on July 1, 2025. For more information, see end of availability for Classic Teams client.

The new Microsoft Teams client is reimagined from the ground up with performance in mind. It's faster, simpler, smarter, and flexible to provide better experience for your apps and users. The new Teams client supports all the existing Teams app capabilities except Adaptive Card tabs. If you have an app that runs inside Classic Teams, the app likely runs in the new Teams client without any issues.

The following are the advantages of the new Teams client:

  • The new Teams client uses the Evergreen version of Microsoft Edge WebView2 to ensure Teams client is always up to date with the latest fixes and improvements available in Microsoft Edge and Chromium.

  • The new Teams client has been rebuilt from the ground up with performance in mind and includes all the platform infrastructure responsible for bootstrapping your app and powering the SDK APIs that it uses.

You can use the following property to identify your app usage in the new Teams or Classic Teams client:

Note

If hostName isn't defined, then assume that your app is running in the Classic Teams client.

The Classic Teams client is represented using the teams field and the new Teams client is represented using the teamsModern field.

Timelines and rollout

To ensure a smooth transition, a phased rollout of the new platform is planned.

Availability of all platform features from Classic Teams: All apps are available in the new Teams Client. All platform features except the features listed under limitations are now available.

Limitations

The following Teams features are deprecated and aren't supported in the new Teams client:

  • Adaptive Card tabs: If your app is using Adaptive Card tabs, we recommend you rebuild the tab as a web-based tab. For more information, see build tabs for Teams.

  • window.alert, window.confirm, and window.prompt APIs: We recommended you to render a dialog within your own frame, for example, using the Fluent V9 dialog or use the Microsoft Teams JavaScript client library (TeamsJS) to display a Teams dialog using Adaptive Card or a nested <iframe>.

  • Location APIs: We recommend using HTML5 Geolocation APIs instead.

For more information on known issues and gaps in the new Teams client, see new Microsoft Teams.

If your app is working fine in the Classic Teams client but has issues in the new Teams, then raise an issue on GitHub. For any other issues, request you to raise an issue on support and feedback.

See also