Teams Premium 101: Features, Licensing Strategy, and Deployment Approach

-

 


Teams Premium is an add-on license that bundles advanced Teams capabilities across meetings, events, and calling. Before you design ‘Premium-only’ experiences, start with two basic questions: who needs the license and what outcomes are you trying to achieve (security, event scale, AI recap, or branded experiences). Microsoft’s licensing guidance also lists features that moved into Teams Premium at general availability, such as live translated captions.

What often justifies Teams Premium

·       Security: advanced meeting protection features (such as watermarking) for sensitive scenarios.

·       Productivity: intelligent meeting recap and intelligent call recap features (where available).

·       Global collaboration: live translated captions and live translated transcription.

·       Events: enhanced webinar/town hall capabilities and scale.

Configuration guide: license and target the right users

1. Identify Premium ‘organizers’ (executive assistants, event producers, compliance organizers) - many meeting features hinge on the organizer’s license.

2. Assign Teams Premium licenses in the Microsoft 365 admin center to the targeted group (pilot first).

3. In Teams admin center, create or adjust meeting policies and templates that expose Premium controls (for example, watermarking).

4. Validate platform support and user experience, then move to ring-based rollout.

A licensing pitfall to avoid

Don’t ‘blanket license’ the tenant as a first move. Start with organizers and high-impact roles, validate value, then expand.

References

·       Teams Premium licensing: https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/licensing-enhance-teams

·       Teams Premium overview for admins: https://learn.microsoft.com/en-us/microsoftteams/enhanced-teams-experience


Comments

Post a Comment

Popular posts from this blog

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar....
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 modif...
Read more

Exchange x500 address x500:/o=ExchangeLabs

-
Image
 You have Exchange Hybrid in place. Now you wonder about an address with you see on-premises with all users. This address has the following format: x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOxxxxxx)/cn=Recipients/cn=234xxxx This address is now found in the Exchange proxyAddresses in On-Premises as well as in Entra ID. Additionally you will see them in msExchShadowProxyAddresses The ExchangeLabs is Microsoft internal Exchange Online Organization and therefore needed. This x500 address is created in Exchange Online and sync'ed via Azure AD Connect (Entra ID Connect) back on-premises. If you delete this address on-premises, the connection between will sync this Cloud leading attribute back to on-premisses. If you have multiple Domains and Active Directories connected to your Tenant, this x500 address from your tenant will be added to ALL users. Also to users which are from an local AD without Exchange / Exchange Hybrid. As long AAD Connect/ Entra ID Connect will...
Read more