Configure Copilot in Teams Phone and Calls (Admin Guide)

-

 

Copilot in Teams calls supports both 1:1 Teams calls and PSTN calls (when the user is voice-enabled). Microsoft documents two modes that mirror meetings: ‘During and after the call’ (retained) and ‘Only during the call’ (not retained). The policy choice interacts with calling transcription: if you need post-call access, transcription must be enabled and started during the call.

Prerequisites

·       For 1:1 Teams calls: Microsoft 365 Copilot license for the intended users.

·       For PSTN calls: Teams Phone license plus a PSTN connectivity option (Calling Plan, Operator Connect, Teams Phone Mobile, or Direct Routing).

·       Policy dependencies: calling transcription is the key dependency for ‘after the call’ experiences.

Configuration guide: Copilot in Teams calling policy

1. Open Teams admin center.

2. Go to Voice > Calling policies.

3. Select an existing policy or create a new one.

4. Set the Copilot setting to On, On with saved transcript required, or Off.

5. Align calling transcription settings with your desired mode (retained vs only during).

6. Assign the calling policy to users or groups and validate with a pilot call.

PowerShell examples

Set-CsTeamsCallingPolicy -Identity <policy name> -Copilot Enabled
Set-CsTeamsCallingPolicy -Identity <policy name> -Copilot Disabled
Set-CsTeamsCallingPolicy -Identity <policy name> -Copilot EnabledWithTranscript -AllowTranscriptionForCalling $true

Security and compliance considerations

·       Only-during mode avoids retention of transcript and Copilot content after the call ends.

·       Copilot in calls isn’t available in end-to-end encrypted calls.

·       Document user consent and call recording practices based on your regional requirements.

References

·       Manage Copilot in Teams calls: https://learn.microsoft.com/en-us/microsoftteams/copilot-teams-calling-transcription

·       Teams Phone overview: https://learn.microsoft.com/en-us/microsoftteams/what-is-phone-system-in-office-365

·       PSTN connectivity options: https://learn.microsoft.com/en-us/MicrosoftTeams/pstn-connectivity

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