diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 916638ed1f..7c67c60c26 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -2687,7 +2687,7 @@ }, { "source_path": "Teams/data-collection-practices.md", - "redirect_url": "/microsoftteams/privacy/teams-privacy", + "redirect_url": "/microsoftteams/privacy/location-of-data-in-teams", "redirect_document_id": false }, { @@ -4737,8 +4737,8 @@ }, { "source_path": "teams/teams-privacy.md", - "redirect_url": "/microsoftteams/privacy/teams-privacy", - "redirect_document_id": true + "redirect_url": "/microsoftteams/privacy/location-of-data-in-teams", + "redirect_document_id": false }, { "source_path": "teams/location-of-data-in-teams.md", @@ -4777,13 +4777,38 @@ }, { "source_path": "teams/privacy/index.md", - "redirect_url": "/microsoftteams/privacy/teams-privacy", + "redirect_url": "/microsoftteams/privacy/location-of-data-in-teams", "redirect_document_id": false }, { "source_path": "teams/new-teams-automatic-upgrade-announced.md", "redirect_url": "/microsoftteams/teams-classic-client-end-of-availability", "redirect_document_id": false -} +}, +{ + "source_path": "teams/manage-freemium.md", + "redirect_url": "/microsoftteams/user-access", + "redirect_document_id": false +}, +{ + "source_path": "teams/upgrade-freemium.md", + "redirect_url": "/microsoftteams/user-access", + "redirect_document_id": false +}, +{ + "source_path": "teams/teams-add-on-licensing/remove-assign-free-licenses.md", + "redirect_url": "/microsoftteams/user-access", + "redirect_document_id": false +}, +{ + "source_path": "Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-skype-for-business-online.md", + "redirect_url": "/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud", + "redirect_document_id": false +}, +{ + "source_path": "teams/privacy/teams-privacy.md", + "redirect_url": "/microsoftteams/privacy/location-of-data-in-teams", + "redirect_document_id": false +} ] } diff --git a/Skype/SfbHybrid/hybrid/move-users-between-on-premises-and-cloud.md b/Skype/SfbHybrid/hybrid/move-users-between-on-premises-and-cloud.md index 61bb1371e5..fa1962ed6f 100644 --- a/Skype/SfbHybrid/hybrid/move-users-between-on-premises-and-cloud.md +++ b/Skype/SfbHybrid/hybrid/move-users-between-on-premises-and-cloud.md @@ -97,11 +97,7 @@ To move users between on-premises and the cloud, you must use an account with su > [!IMPORTANT] > If you are using the Skype for Business Admin Control Panel, you will be prompted to provide credentials for a Microsoft 365 account with the appropriate roles, as noted above. You must supply an account that ends in .onmicrosoft.com. If that is not possible, then use the Move-CsUser cmdlet. > - > If you are using Move-CsUser in PowerShell, you can either use an account that ends in .onmicrosoft.com, or you can use any on-premises account that is synchronized into Microsoft Entra ID, provided that you also specify the HostedMigrationOverrideUrl parameter in the cmdlet. The value of the hosted migration override URL is a variant of the following URL: `https://adminXX.online.lync.com/HostedMigration/hostedmigrationService.svc` In the above URL, replace the XX with either two or three characters, determined as follows: - > - > - In a Teams PowerShell session, run the following cmdlet:
`Get-CsTenant | ft ServiceInstance` - > - The resulting value will be in the following format:
`MicrosoftCommunicationsOnline/YYYY-XX-ZZ` - > - The two- or three-character code is the XX contained in the section YYYY-XX-ZZ. If it’s a two-character code, it will be a digit followed by a number (such as 4A). If it’s a three-character code, it will be two letters followed by a digit (such as JP1). An example is NOAM-4A-S7. + > If you are using Move-CsUser in PowerShell, you can either use an account that ends in .onmicrosoft.com, or you can use any on-premises account that is synchronized into Microsoft Entra ID. ## Voice configuration requirements diff --git a/Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-skype-for-business-online.md b/Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-skype-for-business-online.md deleted file mode 100644 index 7c1d9431e9..0000000000 --- a/Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-skype-for-business-online.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -ms.date: 03/17/2018 -title: "Move users from on premises to Skype for Business Online" -author: MicrosoftHeidi -ms.author: heidip -manager: jtremper -ms.reviewer: bjwhalen -audience: ITPro -f1.keywords: -- NOCSH -ms.topic: article -ms.service: skype-for-business-server -ms.localizationpriority: medium -ms.collection: -- Hybrid -- M365-voice -- m365initiative-voice -- M365-collaboration -- Teams_ITAdmin_Help -- Adm_Skype4B_Online -ms.custom: -description: "Learn how to move users to Skype for Business Online." ---- - -# Move users from on premises to Skype for Business Online - -[!INCLUDE [sfbo-retirement](../../Hub/includes/sfbo-retirement.md)] - -After you move a user from on-premises to Skype for Business Online, the user interacts with Skype for Business Online for its functionality. Any contacts that existed on-premises will be available in Skype for Business Online, and any existing meetings the user organized for the future are updated to so the links point to Skype for Business Online. If the user is enabled for Audio Conferencing, the meetings will also include dial-in coordinates. To move users from an on-premises environment to Skype for Business Online, use either the Move-CsUser cmdlet or the Skype for Business Server Control Panel, both of which are on-premises tools. - -Before moving any users, be sure to review the [prerequisites](move-users-between-on-premises-and-cloud.md#prerequisites) to move users to the cloud. - -> [!NOTE] -> In preparation for the upcoming retirement of Skype for Business Online, Microsoft has simplified how organizations move to Teams. When moving users from on-premises to the cloud, users are now automatically assigned TeamsOnly mode and their meetings from on-premises are automatically converted to Teams meetings, just as if the `-MoveToTeams` switch had been specified, regardless of whether the switch was actually specified. Prior to retirement of Skype for Business Online, organizations that require moving users from on-premises to Skype for Business Online can achieve this in two steps by updating the user's mode *after the user is moved to TeamsOnly*. However in the near future, it will no longer be possible to assign a mode other than TeamsOnly to users homed in the cloud. - -## Move users with Move-CsUser - -Move-CsUser is available from an on-premises Skype for Business Management Shell PowerShell window. You must have sufficient privileges in both the on-premises environment and in the Microsoft 365 organization as described in [Required administrative credentials](move-users-between-on-premises-and-cloud.md#required-administrative-credentials). You can either use a single account that has privileges in both environments, or you can start an on-premises Skype for Business Server Management Shell window with on-premises credentials, and use the `-Credential` parameter to specify credentials for a Microsoft 365 account with the necessary administrative role. - -To move a user to online using Move-CsUser: - -- Specify the user to move using the Identity parameter. -- Specify the -Target parameter with the value “sipfed.online.lync.com”. -- If you do not have one account with sufficient permissions in both on premises and Microsoft 365, use the -credential parameter to supply an account with sufficient permissions in Microsoft 365. -- If the account with permissions in Microsoft 365 doesn't end in “.onmicrosoft.com”, then you must specify the -HostedMigrationOverrideUrl parameter, with the correct value as described in [Required administrative credentials](move-users-between-on-premises-and-cloud.md#required-administrative-credentials). - -The following cmdlet sequence can be used to move a user to Skype for Business Online and assigns the tenant default mode to the user. It assumes the Microsoft 365 credential is a separate account and supplied as input for the Get-Credential prompt. - -```PowerShell -# From an on-premises Skype for Business Server or Lync Server 2013 management shell window, run: - -$cred=Get-Credential -$url="https://admin1a.online.lync.com/HostedMigration/hostedmigrationService.svc" -Move-CsUser -Identity username@contoso.com -Target sipfed.online.lync.com -Credential $cred -HostedMigrationOverrideUrl $url - -# And then from a Teams PowerShell window, remove TeamsOnly mode by running: -Grant-CsTeamsUpgradePolicy -Identity username@contoso.com -PolicyName $null -``` - -If the administrator account is MFA (Multi-Factor Authentication) enabled, do not specify the -Credential parameter. The administrator will be prompted for credentials. - -## Move users with Skype for Business Server Control Panel and Teams Admin Center - -1. Open the Skype for Business Server Control Panel app. -2. In the left navigation, choose **Users**. -3. Use **Find** to locate the user(s) you would like to move to Skype for Business Online. -4. Select the user(s), and then, from the **Action** dropdown above the list, choose **Move selected users to Skype for Business Online** or **Move selected users to Teams**. Either option will initially move the user to TeamsOnly mode but after the move you can assign another mode. -5. In the wizard, select **Next**. -6. If prompted, sign in to Microsoft 365 with an account that ends in .onmicrosoft.com and has sufficient permissions. -7. Click **Next**, and then **Next** one more time to move the user. -8. Note that status messages regarding success or failure are provided at the top of the main Control Panel app, not in the wizard. -9. Open the Teams Admin Center and select "Users" in the left hand navigation. -10. Click on the desired user in the listview. -11. Click the **Edit** in the section that says **Teams upgrade**. -12. In the right-hand flyout, select the desired coexistence mode and click **Apply**. - -## See also - -[Move-CsUser](/powershell/module/skype/move-csuser) diff --git a/Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-teams.md b/Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-teams.md index 586f41969a..00123c4bec 100644 --- a/Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-teams.md +++ b/Skype/SfbHybrid/hybrid/move-users-from-on-premises-to-teams.md @@ -64,23 +64,20 @@ Move-CsUser is available from an on-premises Skype for Business Server Managemen - Specify the user to move using the `Identity` parameter. - Specify the `-Target` parameter with the value “sipfed.online.lync.com” (or similar value if your tenant is government cloud). -- If you don't have one account with sufficient permissions in both on premises and the cloud service (Microsoft 365), use the `-credential` parameter to supply an account with sufficient permissions in Microsoft 365. -- If the account with permissions in Microsoft 365 doesn't end in “onmicrosoft.com”, you must specify the `-HostedMigrationOverrideUrl` parameter, with the correct value as described in [Required administrative credentials](move-users-between-on-premises-and-cloud.md#required-administrative-credentials). +- You must have sufficient privileges in both the on-premises environment and the cloud service (Microsoft 365), as described in [Required administrative credentials](move-users-between-on-premises-and-cloud.md#required-administrative-credentials). - Make sure the computer running the on-premises administration tools is using the latest CU for your version of Skype for Business Server or Lync Server 2013, to ensure OAuth is used for authentication. The following cmdlet sequence can be used to move a user to TeamsOnly, and assumes the Microsoft 365 credential is a separate account and supplied as input for the Get-Credential prompt. The behavior is the same whether `-MoveToTeams` switch is specified or not. ```powershell $cred=Get-Credential - $url="https://admin1a.online.lync.com/HostedMigration/hostedmigrationService.svc" - Move-CsUser -Identity username@contoso.com -Target sipfed.online.lync.com -Credential $cred -HostedMigrationOverrideUrl $url - ``` + Move-CsUser -Identity username@contoso.com -Target sipfed.online.lync.com -Credential $cred > [!TIP] > As there are different circumstances requiring different parameters, the default command for most cases is: ```powershell -Move-CsUser -Identity username@contoso.com -Target sipfed.online.lync.com -HostedMigrationOverrideUrl $url +Move-CsUser -Identity username@contoso.com -Target sipfed.online.lync.com ``` ### Move to Teams using Skype for Business Server Control Panel diff --git a/Skype/SfbHybrid/hybrid/move-users-from-the-cloud-to-on-premises.md b/Skype/SfbHybrid/hybrid/move-users-from-the-cloud-to-on-premises.md index 9fb90d1b89..c03e447701 100644 --- a/Skype/SfbHybrid/hybrid/move-users-from-the-cloud-to-on-premises.md +++ b/Skype/SfbHybrid/hybrid/move-users-from-the-cloud-to-on-premises.md @@ -54,14 +54,13 @@ To move a user to on-premises using Move-CsUser: - Specify the user to move using the Identity parameter. - Specify the -Target parameter with the fully qualified domain name of the desired on-premises pool that will host the user. - If you don't have one account with sufficient permissions in both on-premises and the cloud service (Microsoft 365), use the -credential parameter to supply an account with sufficient permissions in Microsoft 365. -- If the account with permissions in Microsoft 365 doesn't end in “on.microsoft.com”, you must specify the -HostedMigrationOverrideUrl parameter, with the correct value as described in [Required administrative credentials](move-users-between-on-premises-and-cloud.md#required-administrative-credentials). +- You must have sufficient privileges in both the on-premises environment and the cloud service (Microsoft 365), as described in [Required administrative credentials](move-users-between-on-premises-and-cloud.md#required-administrative-credentials). The following cmdlet sequence can be used to move a user to Skype for Business Server, and assumes the Microsoft 365 credential is a separate account and supplied as input for the Get-Credential prompt. ```PowerShell $cred=Get-Credential -$url="https://admin1a.online.lync.com/HostedMigration/hostedmigrationService.svc" -Move-CsUser -Identity username@contoso.com -Target pool.corp.contoso.com -Credential $cred -HostedMigrationOverrideUrl $url +Move-CsUser -Identity username@contoso.com -Target pool.corp.contoso.com -Credential $cred ``` ### Move users with the Skype for Business Server Control Panel diff --git a/Skype/SfbServer/skype-for-business-hybrid-solutions/plan-your-phone-system-cloud-pbx-solution/enable-users-for-phone-system.md b/Skype/SfbServer/skype-for-business-hybrid-solutions/plan-your-phone-system-cloud-pbx-solution/enable-users-for-phone-system.md index b11c5e5421..c9fb3e8cb0 100644 --- a/Skype/SfbServer/skype-for-business-hybrid-solutions/plan-your-phone-system-cloud-pbx-solution/enable-users-for-phone-system.md +++ b/Skype/SfbServer/skype-for-business-hybrid-solutions/plan-your-phone-system-cloud-pbx-solution/enable-users-for-phone-system.md @@ -48,6 +48,4 @@ Enabling a user for Phone System with on-premises PSTN connectivity and then mov - [Synchronize users to the cloud and assign licenses](../../../SfbHybrid/hybrid/configure-hybrid-connectivity.md?bc=%2fSkypeForBusiness%2fbreadcrumb%2ftoc.json&toc=%2fSkypeForBusiness%2ftoc.json) (performed using Office 365). -- [Move on-premises users to Skype for Business Online](../../../SfbHybrid/hybrid/move-users-from-on-premises-to-skype-for-business-online.md) (performed using Windows PowerShell on-premises, but using your Office 365 administrator credentials). - - [Enable users for Enterprise Voice online and Phone System Voicemail](enable-users-for-enterprise-voice-online-and-phone-system-voicemail.md) (performed using Remote PowerShell. diff --git a/Teams/ITAdmin-readiness.md b/Teams/ITAdmin-readiness.md index acae5f4529..aed1b47775 100644 --- a/Teams/ITAdmin-readiness.md +++ b/Teams/ITAdmin-readiness.md @@ -59,6 +59,8 @@ Use the training resources to educate yourself about Teams, teach others or run | SIP gateway enablement and migration | | [Deck](https://aka.ms/SIP-gateway-enablement-migration-playbook) | | Teams Devices Deployment playbook | | [Deck](https://aka.ms/teams-devices-deployment-playbook) | | Teams Phone Deployment playbook | | [Deck](https://aka.ms/teams-phone-deployment-playbook) | +| Teams Phone for Frontline Workers Deployment playbook | | [Deck](https://aka.ms/teams-phone-FLW-deployment-playbook) | +| Teams Phone Service Reliability and Survivability playbook | | [Deck](https://aka.ms/teams-phone-service-reliability-playbook) | | Upgrade from Skype for Business to Teams | [Video 1: Introduction to Upgrade](https://aka.ms/teams-upgrade-intro)
[Video 2: Plan your upgrade](https://aka.ms/teams-upgrade-plan)
[Video 3: Coexistence and Interoperability](https://aka.ms/teams-upgrade-coexistence-interop)
[Video 4: Administrator experience](https://aka.ms/teams-upgrade-admin) | [Deck](https://aka.ms/teams-upgrade-deck)| | Windows desktop client | [Video](https://aka.ms/teams-clients) | [Deck](https://aka.ms/teams-clients-deck) | | Windows Defender Application Control for new Teams | | [Deck](https://aka.ms/new-teams-WDAC) | diff --git a/Teams/app-centric-management.md b/Teams/app-centric-management.md index 7c469db20c..06e5f1aa44 100644 --- a/Teams/app-centric-management.md +++ b/Teams/app-centric-management.md @@ -31,7 +31,7 @@ ms.custom: seo-marvel-apr2020 App centric management functionality introduces a new way to control how you control access to Teams apps for users and groups. It replaces app permission policies. This functionality lets you specify which users and groups can use each app and you can control it on a per-app basis. -When you start using this functionality, we retain your existing app access that you defined using permission policies. Users continue to have access to only those apps that you've allowed for them. +When you start using this functionality, we retain your existing app access that you defined using permission policies. Users continue to have access to only those apps that you allow for them. You can manage access to apps for individual users, supported groups, or everyone in the organization. You have complete control over who can or can't add and use apps in your organization. You can also control the access to new apps that we publish to Teams app store. @@ -69,7 +69,7 @@ To assign users or groups to an app, follow these steps: 1. To remove one or more users or groups from an app, select the rows and select **Remove**. - :::image type="content" source="media/acm-remove-access.png" alt-text="Screenshot showing how to remove an existing app assignment from the app details page."::: + :::image type="content" source="media/acm-remove-access.png" alt-text="Screenshot showing how to remove an existing app assignment from the app details page." lightbox="media/acm-remove-access-large.png"::: > [!NOTE] > You can view and modify the assignments of a blocked app but your assignments take effect only when you [allow the app](manage-apps.md#allow-or-block-apps). @@ -131,8 +131,11 @@ When your tenant's admin center receives this feature, the following updates are | Allowed | Blocked | No one can install | | Allowed | Allowed | Everyone | -> [!NOTE] -> You can't access, edit, or use permission policies after switching to this feature. +## Considerations and limitations + +* After you switch to this feature, you can't access, edit, or use permission policies. + +* [PowerShell cmdlets](/powershell/module/teams/?view=teams-ps&preserve-view=true) for permission policies aren't supported on tenants that switch to this feature. These cmdlets return the results but the results aren't applicable to tenants that use this feature. App permission policy PowerShell cmdlets are not supported if you use this feature. ## Related article diff --git a/Teams/bookings-app-admin.md b/Teams/bookings-app-admin.md index 59d212a9d9..b0587b2226 100644 --- a/Teams/bookings-app-admin.md +++ b/Teams/bookings-app-admin.md @@ -23,9 +23,8 @@ ms.collection: - teams-1p-app-admin - highpri - m365initiative-meetings - - m365-virtual-appointments -ms.reviewer: revathim -ms.date: 03/23/2023 +ms.reviewer: pritikar +ms.date: 04/01/2024 description: Learn how to manage the Bookings app in Teams for users in your organization. --- @@ -33,33 +32,41 @@ description: Learn how to manage the Bookings app in Teams for users in your org ## Overview of Bookings -The Bookings app in Microsoft Teams offers a simple way to schedule in-person and virtual appointments. For example, healthcare visits, financial consultations, interviews, customer support, and education office hours. To learn more, see [What is Bookings?](https://support.microsoft.com/office/what-is-bookings-42d4e852-8e99-4d8f-9b70-d7fc93973cb5). +The Bookings app in Microsoft Teams offers a simple way to organize schedules and manage appointments. -Schedulers can manage multiple department and staff calendars and communications with internal and external attendees, from a single experience. Virtual appointments are held via Teams meetings that offer robust videoconferencing capabilities. +Customize appointment types and details, booking requirements, and manage staff schedules and availability to streamline the booking experience. Bookings is integrated with your and your staff’s Microsoft 365 calendar to help your customers and clients quickly find available times from the booking page. -## Prerequisites to use the Bookings app in Teams +You can create and manage multiple booking pages, each with their own unique setup, to fit the scheduling needs of your organization. + +- [Personal bookings](/microsoft-365/bookings/bookings-overview#personal-bookings) let you manage your own appointment time slots. You can set and share your availability with your customers, clients, or coworkers. After you create a personal booking page, you can share the link with others, who can then see your availability and schedule a time when you're free. +- [Shared bookings](/microsoft-365/bookings/bookings-overview#shared-bookings) are booking pages that you create and manage for your team. They allow you to invite your team members so that your customers and clients can book time with you and your team. + +Every appointment booked as an online meeting creates a meeting link that people can use to join and meet virtually in Teams. -* The Exchange mailbox is in Exchange Online. On-premises Exchange Server mailboxes aren't supported. -* Microsoft Bookings is available for the organization. -* Users have an appropriate license. Office 365 A3, A5, E1, E3, E5, F1, F3, Microsoft 365 A3, A5, E3, E5, F1, F3, and Business Standard are supported. -* All users of the Bookings app and all staff participating in meetings have a license that supports Teams meeting scheduling. -* [Software and browser prerequisites](hardware-requirements-for-the-teams-app.md). +To learn more, see [Microsoft Bookings](/microsoft-365/bookings/bookings-overview). -## Availability of Bookings in Teams +## Prerequisites to use the Bookings app in Teams + +- The Exchange mailbox is in Exchange Online. On-premises Exchange Server mailboxes aren't supported. +- Microsoft Bookings is turned on for the organization. +- Users have an appropriate license. Microsoft Bookings is available in the following subscriptions: + - Office 365: A3, A5, E1, E3, E5, F1, F3, G1, G3, and G5 + - Microsoft 365: A3, A5, E3, E5, F1, F3, Business Basic, Business Standard, Business Premium, Teams Essentials, Teams Premium +- All users of the Bookings app and all staff participating in meetings have a license that supports Teams meeting scheduling. -The Bookings app for Teams is available on the desktop and web. It can be found under [Apps in Teams](https://teams.microsoft.com/l/app/4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b?source=store-copy-link) and under **Manage Apps** in the Teams admin center. +To add the Bookings app to Teams, go to **Apps**, and then search for [Bookings](https://teams.microsoft.com/l/app/4c4ec2e8-4a2c-4bce-8d8f-00fc664a4e5b). ## Control access to Bookings within your organization -There are several ways to control who has access to the Bookings app and to specific features of the app. You can make Microsoft Bookings app available or disable it from Microsoft 365 admin center. Alternately, you can create a Bookings app policy to allow select users to create Bookings calendars. See [Get access to Microsoft Bookings](/microsoft-365/bookings/get-access). +There are several ways to control who has access to the Bookings app and to specific features of the app. You can turn on or turn off Bookings for your organization or for individual users in the Microsoft 365 admin center. Alternatively, you can create a Bookings app policy to allow select users to create Bookings calendars. To learn more, see [Turn Microsoft Bookings on or off](/microsoft-365/bookings/turn-bookings-on-or-off). You can also [create a Teams app setup policy to pin the Bookings app for select users](teams-app-setup-policies.md). ## Recommended meeting policy settings -To enable the best experience for Bookings, create a Teams meeting policy to automatically admit **People in my organization** and assign the policy to your staff. The policy allows staff to join the appointment automatically and enable the lobby experience for external attendees. See [who can bypass the lobby to meetings](meeting-policies-participants-and-guests.md#who-can-bypass-the-lobby). +To enable the best experience for Bookings, create a Teams meeting policy to automatically admit **People in my organization** and assign the policy to your staff. The policy allows staff to join the appointment automatically and enable the lobby experience for external attendees. To learn more, see [Control who can bypass the meeting lobby in Microsoft Teams](who-can-bypass-meeting-lobby.md). -For more information about meeting policies, see [Manage meeting policies in Teams](meeting-policies-in-teams.md) and [Meeting policies and meeting expiration in Teams](meeting-expiration.md). +For more information about meeting policies, see [Manage meeting and event policies in Teams](meeting-policies-overview.md). ## SMS text notifications @@ -69,12 +76,12 @@ SMS text notifications are currently available in Canada, the United Kingdom, an You can control whether SMS text notifications can be sent to external attendees for virtual appointments scheduled by your staff in your organization. -By default, this setting is on, and SMS text notifications are enabled for all Bookings calendars in your organization. Keep in mind that Bookings admins and schedulers can later choose to turn off or turn on SMS notifications on an as-needed basis in scheduled appointment types and scheduled individual appointments. +By default, this setting is on, and SMS text notifications are enabled for all booking pages in your organization. Keep in mind that Bookings admins and schedulers can later choose to turn off or turn on SMS notifications on an as-needed basis in scheduled appointment types and scheduled individual appointments. To configure this setting, go to the Microsoft 365 admin center \> **Settings** \> **Org settings**, and then choose **Bookings**. Select or clear the **Allow Microsoft to send SMS text message notifications** check box. Learn more about how to [configure SMS text notifications for your organization](/microsoft-365/bookings/turn-bookings-on-or-off). -Use the [SMS notifications usage report](/microsoft-365/frontline/sms-notifications-usage-report) to understand how your organization is using SMS notifications. +Use the [Teams SMS notifications usage report](/microsoft-365/frontline/sms-notifications-usage-report) to understand how your organization is using SMS notifications. ## Optional staff approvals setting @@ -82,7 +89,7 @@ You can require staff to opt in before Bookings shares their schedule availabili To enable this setting, go to the Microsoft 365 admin center \> **Settings** \> **Org settings**, and then choose **Bookings**. Select the **Require staff approvals** check box. -With this setting turned on, staff receive an email in which they're requested to approve membership to a booking calendar. +With this setting turned on, staff receive an email in which they're requested to approve membership to a booking page. Learn more about [how to configure the staff approvals setting](/microsoft-365/bookings/turn-bookings-on-or-off). @@ -107,8 +114,6 @@ To learn more, see [Set Mailbox](/powershell/module/exchange/mailboxes/set-mailb To send feedback, select the **Help** option at bottom of the Teams left navigation bar, and then select **Report a Problem**. Select **Other**, and then enter your feedback or details about the issue you're experiencing. Indicate at the beginning of your feedback report that you're sending feedback about "Bookings" so we can easily identify Bookings issues. -## Related articles - -[Manage the join experience for Teams Virtual Appointments on browsers](/microsoft-365/frontline/browser-join) +## See also -[Bookings documentation for end users](https://support.office.com/article/apps-and-services-cc1fba57-9900-4634-8306-2360a40c665b?ui=en-US&rs=en-US&ad=US#PickTab=Bookings) +[Microsoft Bookings documentation](/microsoft-365/bookings/bookings-overview) diff --git a/Teams/copilot-teams-transcription.md b/Teams/copilot-teams-transcription.md index 2635d0e970..f1873022f4 100644 --- a/Teams/copilot-teams-transcription.md +++ b/Teams/copilot-teams-transcription.md @@ -4,7 +4,7 @@ ms.author: wlibebe author: wlibebe manager: pamgreen ms.reviewer: elederman -ms.date: 1/29/2024 +ms.date: 4/5/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -28,21 +28,21 @@ description: Learn how to manage Copilot admin policies in the Teams admin cente **APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls -Copilot for Microsoft Teams meetings and events is an artificial intelligence (AI) tool that can capture important conversation points. Each meeting and webinar participant with a Copilot license can ask prompts that are only visible to them. Participants and organizers can learn things like who said what and where people agree or disagree. Copilot can also recommend follow-up tasks, all in real time during a meeting. For town halls, organizers, co-organizers, presenters can use Copilot during the event. +Copilot for Microsoft Teams meetings and events is an artificial intelligence (AI) tool that can capture important conversation points. Each meeting and webinar participant with a Copilot license can ask prompts that are only visible to them. Participants and organizers can learn things like who said what and where people agree or disagree. Copilot can also recommend follow-up tasks, all in real time during a meeting. For town halls, organizers, co-organizers, presenters can use Copilot during the event. There are two ways for users in your organization to use Copilot in meetings: -**1. Copilot with transcription turned on**
+**1. Copilot during and after the meeting**
-When organizers create a meeting or event, they can set Copilot’s value to **With transcription** from the dropdown in their meeting options. Once someone with a Copilot license selects the Copilot button and enables transcription during the meeting or event, Copilot starts running for all licensed users. Copilot is available both during and after the meeting. If you assign a policy that disables transcription, organizers with this policy can’t use Copilot with transcription in their meetings. Instead, they must use Copilot with transcription turned off. +When organizers create a meeting or event, they can set Copilot’s value to **During and after the meeting** from the dropdown in their meeting options. Once someone with a Copilot license selects the Copilot button and enables transcription during the meeting or event, Copilot starts running for all licensed users. Copilot is available both during and after the meeting. If you assign a policy that disables transcription, organizers with this policy can’t use Copilot with transcription in their meetings. Instead, they must use Copilot only during the meeting. -To learn more about how organizers can use Copilot with transcription, see [Get started with Copilot in Microsoft Teams meetings](https://support.microsoft.com/office/get-started-with-copilot-in-microsoft-teams-meetings-0bf9dd3c-96f7-44e2-8bb8-790bedf066b1). +To learn more about how organizers can use Copilot during and after the meeting, see [Get started with Copilot in Microsoft Teams meetings](https://support.microsoft.com/office/get-started-with-copilot-in-microsoft-teams-meetings-0bf9dd3c-96f7-44e2-8bb8-790bedf066b1). -**2. Copilot with transcription turned off**
+**2. Copilot only during the meeting**
-When organizers create a meeting or event, they can set Copilot’s value to **Without transcription** from the dropdown in their meeting options. Once someone with a Copilot license selects the Copilot button during the meeting or event, Copilot without transcription starts running for all licensed users. This option relies on a temporary transcript that gets deleted when the meeting or event ends, so Copilot isn't accessible after the meeting or event. If you assign organizers a policy that disables transcription, any organizers with this policy must use Copilot with transcription turned off to access Copilot in their meetings. +When organizers create a meeting or event, they can set Copilot’s value to **Only during the meeting** from the dropdown in their meeting options. Once someone with a Copilot license selects the Copilot button during the meeting or event, Copilot starts running for all licensed users. This option relies on a temporary transcript that gets deleted when the meeting or event ends, so Copilot isn't accessible after the meeting or event. If you assign organizers a policy that disables transcription, any organizers with this policy must use Copilot only during the meeting to access Copilot in their meetings and events. -To learn more about how organizers can use Copilot without transcription, see [Use Copilot without recording a Teams meeting](https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9). +To learn more about how organizers can use Copilot only during the meeting, see [Use Copilot without recording a Teams meeting](https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9). For more information about transcription policies, see [Configure transcription and captions for Teams meetings](meeting-transcription-captions.md). @@ -67,12 +67,12 @@ As an admin, you can manage the default value for Copilot that your organizers 5. Navigate to the **Recording & transcription** section and note your setting for the **Transcription** policy. 6. Select one of the following values from the dropdown for the **Copilot** setting: - - **On**- Select this value if you want your organizers to use Copilot without the transcript. You should use this value if you disabled **Transcription** for organizers with this policy. When organizers with this policy create meetings, Copilot isn’t accessible once the meeting is over. - - **On with transcript**- Select this value if you want your organizers to use Copilot with the transcript. You should use this value if you enabled **Transcription** for organizers with this policy. Copilot is available both during and after meetings that organizers with this policy create meetings. + - **On**- Select this value if you want your organizers to use Copilot only during the meeting. You should use this value if you disabled **Transcription** for organizers with this policy. When organizers with this policy create meetings, Copilot isn’t accessible once the meeting is over. + - **On with transcript**- Select this value if you want your organizers to use Copilot during and after the meeting. You should use this value if you enabled **Transcription** for organizers with this policy. Copilot is available both during and after meetings that organizers with this policy create meetings. 7. Select **Save** -You can apply your Copilot meeting policies to groups or individual users. You can also add Copilot to your meeting templates. To learn how to apply Copilot meeting policies to meeting templates, see [IT admins - Create a custom meeting template in Microsoft Teams](create-custom-meeting-template.md). +You can apply your Copilot meeting policies to groups or individual users. You can also add Copilot to your meeting templates. To learn how to apply Copilot meeting policies to meeting templates, see [IT admins - Create a custom meeting template in Microsoft Teams](create-custom-meeting-template.md). ## Manage Copilot using PowerShell @@ -82,10 +82,10 @@ The following table shows the behaviors of the settings for the **`-Copilot`** p |Setting value| Behavior| |---------|---------------| -|Enabled| When organizers with this policy create meetings, the default value for Copilot in their meeting options is **Without transcription**. If the organizer keeps the default, transcription isn’t required to use Copilot for the meeting. Copilot starts once a licensed user selects the Copilot button and is only available to use during the meeting. | -|EnabledWithTranscript| **This is the default value**. When organizers with this policy create meetings, the default value for Copilot in their meeting options is **With transcription**. If the organizer keeps the default, transcription must be enabled to use Copilot for the meeting. Copilot is still available to use after the meeting ends.| +|Enabled| When organizers with this policy create meetings, the default value for Copilot in their meeting options is **Only during the meeting**. If the organizer keeps the default, transcription isn’t required to use Copilot for the meeting. Copilot starts once a licensed user selects the Copilot button and is only available to use during the meeting. | +|EnabledWithTranscript| **This is the default value**. When organizers with this policy create meetings, the default value for Copilot in their meeting options is **During and after the meeting**. If the organizer keeps the default, transcription must be enabled to use Copilot for the meeting. Copilot is still available to use after the meeting ends.| -For organizers with this policy to have the default value for Copilot set to **Without transcription**, use the following script: +For organizers with this policy to have the default value for Copilot set to **Only during the meeting**, use the following script: ```PowerShell Set-CsTeamsMeetingPolicy -Identity -Copilot Enabled diff --git a/Teams/devices/cloud-intelliframe.md b/Teams/devices/cloud-intelliframe.md index 37831636dd..c093711bc3 100644 --- a/Teams/devices/cloud-intelliframe.md +++ b/Teams/devices/cloud-intelliframe.md @@ -67,7 +67,7 @@ Cloud IntelliFrame runs on Azure and is fully compliant with M365 data processin ### Supported cameras -The following camera models when deployed in a Microsoft Teams Room on Windows with a Pro license automatically use the Cloud IntelliFrame: +The following camera models when deployed in Microsoft Teams Rooms on Windows with a Pro license automatically use the Cloud IntelliFrame: - AVer CAM520 Pro - AVer CAM520 Pro2 diff --git a/Teams/devices/common-area-mobile-phones.md b/Teams/devices/common-area-mobile-phones.md index 08be891f72..efd1a98821 100644 --- a/Teams/devices/common-area-mobile-phones.md +++ b/Teams/devices/common-area-mobile-phones.md @@ -27,7 +27,7 @@ description: Learn how to set up common area Android phones # Set up an Android mobile phone as a common area phone -A Teams Android mobile app singed in with an account tied to **Microsoft Teams Shared Device** license is used as a shared device by frontline workers to make and receive calls as part of their daily work using Teams. +A Teams Android mobile app signed in with an account tied to **Microsoft Teams Shared Device** license is used as a shared device by frontline workers to make and receive calls as part of their daily work using Teams. > [!IMPORTANT] > To use this feature you must have version 1.0.0.2023143401 (2023143401) or later installed on the Android mobile phone. diff --git a/Teams/devices/qos-on-teams-devices.md b/Teams/devices/qos-on-teams-devices.md index 045defe02a..e102120111 100644 --- a/Teams/devices/qos-on-teams-devices.md +++ b/Teams/devices/qos-on-teams-devices.md @@ -28,11 +28,11 @@ Deploying one or many Microsoft Teams Rooms devices requires planning. One of th This article explains: -1. [How much bandwidth a Teams Room device will consume?](#how-much-bandwidth-will-a-microsoft-teams-rooms-device-use) +1. [How much bandwidth a Teams Rooms device will consume?](#how-much-bandwidth-will-a-microsoft-teams-rooms-device-use) 1. [How to control that bandwidth usage?](#how-do-i-control-microsoft-teams-rooms-bandwidth-usage) 1. [How to ensure your devices are optimized with the right quality of service (QoS) configuration to align to your organizations requirements?](#quality-of-service-qos-with-microsoft-teams-rooms) -Wired network connectivity is recommended for Microsoft Teams Room devices. If wireless network connectivity is the only option, see best practice guidance [here](../rooms/rooms-plan.md). +Wired network connectivity is recommended for Microsoft Teams Rooms devices. If wireless network connectivity is the only option, see best practice guidance [here](../rooms/rooms-plan.md). ## How much bandwidth will a Microsoft Teams Rooms device use? diff --git a/Teams/devices/usb-devices.md b/Teams/devices/usb-devices.md index 6df03f3a1b..d9f4bfd774 100644 --- a/Teams/devices/usb-devices.md +++ b/Teams/devices/usb-devices.md @@ -79,13 +79,14 @@ If you're a manufacturer and want to join the certification program, see [How to ## Certified devices -*Table Updated March 2024* +*Table Updated April 2024* > [!NOTE] > The date format is MM/DD/YYYY. | Manufacturer | Model | Qualified | Certified Program | |:--------------------|:----------------------------------------------------------|:---------------|:-------------------------------------------------------| +|Yealink |UH35 Dual/Mono Teams Headset |3/28/2024 |Certified for Microsoft Teams | |Bang & Olufsen Cisco |950 MS Earbuds |3/28/2024 |Certified for Microsoft Teams | |Dell |WL7024 Headset |3/28/2024 |Certified for Microsoft Teams | |EPOS |IMPACT 760T |2/13/2024 |Certified for Microsoft Teams | diff --git a/Teams/devices/use-teams-panels.md b/Teams/devices/use-teams-panels.md index 2cdac97283..2d0714f882 100644 --- a/Teams/devices/use-teams-panels.md +++ b/Teams/devices/use-teams-panels.md @@ -122,7 +122,7 @@ The right tile on the Home screen now appears in purple and displays the **Reser :::image type="content" source="../media/panels-right-tile-reserved-adhoc.png" alt-text="Home screen showing that meeting space is reserved for an ad hoc meeting."::: > [!NOTE] - > If the meeting space is a Microsoft Teams Room, you can _join_ this Teams meeting with the in-room Microsoft Teams Rooms or Surface Hub devices. + > If the meeting space is a Microsoft Teams Rooms, you can _join_ this Teams meeting with the in-room Microsoft Teams Rooms or Surface Hub devices. ### View or update a device setting diff --git a/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md b/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md index b380ee8779..d59b5811fa 100644 --- a/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md +++ b/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md @@ -4,13 +4,14 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: jamp -ms.date: 10/26/2023 +ms.date: 04/02/2024 ms.topic: article ms.assetid: e97aeeee-9e43-416f-b433-9cdd63d8874b ms.tgt.pltfrm: cloud ms.service: msteams ms.collection: - M365-voice + - m365initiative-voice - Tier1 search.appverid: MET150 audience: Admin @@ -82,7 +83,7 @@ For example, the Duration (Minutes) dimension represents the call duration in se The \ is used to control the sort order when presenting the data and can be used for filtering. For example, a filter on Duration (Minutes) < "065", would show streams with duration less than 2 minutes (The leading '0' is needed for the filter to work as expected). The actual value of the sort order string isn't significant. > [!NOTE] -> You might notice ranges that seem to be invalid for a given dimension. An example is Wifi Signal Strength showing calls in the 082: [100 - 110) range when 100 is the maximum possible value. This range is due to how numbers are assigned to ranges in CQD's data model. If a whole number value is 99, it is counted in the 081: [90 - 100) range. If that value is 100, it is counted in the 082: [100 - 110) range. This doesn't indicate that there are Wifi Signal Strength values greater than 100% being reported. +> You might notice ranges that seem to be invalid for a given dimension. An example is Wifi Signal Strength showing calls in the 082: [100 - 110) range when 100 is the maximum possible value. This range is due to how numbers are assigned to ranges in CQD's data model. If a whole number value is 99, it's counted in the 081: [90 - 100) range. If that value is 100, it's counted in the 082: [100 - 110) range. This doesn't indicate that there are Wifi Signal Strength values greater than 100% being reported. #### Enumeration strings @@ -333,12 +334,24 @@ Second Media Bypass | Boolean | Indicates if the audio stream was bypassing the | Second Mic Device Failure | Boolean | Indicates if an audio capture device failure is detected on the second endpoint. || | First No Mic Devices Enumerated Failure | Boolean | Indicates that no audio capture devices were detected on the first endpoint. || | Second No Mic Devices Enumerated Failure | Boolean | Indicates that no audio capture devices were detected on the second endpoint. || +| First Mic Is Silent | Boolean | Indicates no audio is detected from the first endpoint microphone while unmuted. || +| Second Mic Is Silent | Boolean | Indicates no audio is detected from the second endpoint microphone while unmuted. || | First Mic Initialization Failure| Boolean | Indicates that a failure occurred during the hardware initialization of the microphone device on the first endpoint. || | Second Mic Initialization Failure| Boolean | Indicates that a failure occurred during the hardware initialization of the microphone device on the second endpoint. || | First Mic Connection Type | Enumeration string |The connection interface or type of the microphone device used on the first endpoint
Possible values: BlueTooth, HDAudio, Internal, PCI, USB, Virtual, Other|| | Second Mic Connection Type | Enumeration string | The connection interface or type of the microphone device used on the second endpoint
Possible values: BlueTooth, HDAudio, Internal, PCI, USB, Virtual, Other|| +| First Speaker Device Failure | Boolean | Indicates if an audio render device failure is detected on the first endpoint. || +| Second Speaker Device Failure | Boolean | Indicates if an audio render device failure is detected on the second endpoint. || +| First No Speaker Devices Enumerated Failure | Boolean | Indicates that no audio render devices were detected on the first endpoint. || +| Second No Speaker Devices Enumerated Failure | Boolean | Indicates that no audio render devices were detected on the second endpoint. || +| First Speaker Initialization Failure | Boolean | Indicates that a failure occurred during the hardware initialization of the audio render device on the first endpoint. || +| Second Speaker Initialization Failure | Boolean | Indicates that a failure occurred during the hardware initialization of the audio render device on the second endpoint. || +| First Speaker Connection Type | Enumeration string | The connection interface or type of the audio render device used on the first endpoint
Possible values: USB, Wireless, Other || +| Second Speaker Connection Type | Enumeration string | The connection interface or type of the audio render device used on the second endpoint
Possible values: USB, Wireless, Other || | First Compute Device Name | String | The detected system manufacturer and system model of the first endpoint.
Example: microsoft corporation surface pro | • System manufacturer and model weren't detected.| | Second Compute Device Name | String |The detected system manufacturer and system model of the second endpoint.
Example: microsoft corporation surface pro | • System manufacturer and model weren't detected.| +| First Device Failure | Boolean | Indicates if an audio capture or render device failure is detected on the first endpoint. || +| Second Device Failure | Boolean | Indicates if an audio capture or render device failure is detected on the second endpoint. || |**WiFi**|||| | First WiFi Microsoft Driver | String | Name of Microsoft WiFi driver used reported by the first endpoint. Value might be localized based on the language used by endpoint.
**Example value:** Microsoft Hosted Network Virtual Adapter |
• WiFi wasn't used by the endpoint
• The driver information wasn't reported| | Second WiFi Microsoft Driver | String | Name of Microsoft WiFi driver used reported by the second endpoint. Value might be localized based on the language used by endpoint.
**Example value:** Microsoft Hosted Network Virtual Adapter |
• WiFi wasn't used by the endpoint
• The driver information wasn't reported| @@ -371,15 +384,15 @@ Second Media Bypass | Boolean | Indicates if the audio stream was bypassing the | Ratio Stretched Samples Avg | Range (ratio) | Ratio of the number of audio frames with samples that are stretched to compensate for jitter or loss to the total number of audio frames. Values grouped by range. 0.1 indicates 10% audio frames contained stretched samples.
**Example value:** 017: [0.03 - 0.04) | • The receiver of the stream didn't report this value
• The stream wasn't an audio stream | |Healer Packet Drop Ratio|Range (ratio) |Ratio of audio packets dropped by healer over total number of audio packets received by healer. See [2.2.1.12.1 Child Elements](/openspecs/office_protocols/ms-qoe/56d41628-26d5-44c8-8f79-6bac4b0355a5) for more information.| | | Healer FEC Packet Used Ratio| Range (ratio) |Ratio of used Forward Error Correction (FEC) packets over total number of received FEC packets. See [2.2.1.12.1 Child Elements](/openspecs/office_protocols/ms-qoe/56d41628-26d5-44c8-8f79-6bac4b0355a5) for more information. | | -| Round Trip | Range (milliseconds) | Average network propagation round-trip time computed as specified in RFC3550 in milliseconds. Values grouped by range.
**Example value:** 070: [15 - 20) |
• The endpoint didn't compute the value
• The value wasn't reported | -| Round Trip Max | Range (milliseconds) | Maximum network propagation round-trip time computed as specified in RFC3550 in milliseconds. Values grouped by range.
**Example value:** 098: [350 - 375) |
• The endpoint didn't compute the value
• The value wasn't reported | -| Packet Utilization | Number (Packets) |Number of Real-Time Transport Protocol (RTP) packets sent in the session.|| -| Jitter Buffer Size Avg|Number (Range) |Average size of jitter buffer during session.| | -| Jitter Buffer Size Max|Number (Range)|Maximum size of jitter buffer during session. || -| Jitter Buffer Size Min|Number (Range)|Minimum size of jitter buffer during session.|| -|Relative OneWay Gap Duration| Duration of gaps in the relative one way delay of the peer.||| -| Audio Post FECPLR| Number |Reports packet loss rate after FEC is applied for audio. Value between 0.00 and 1.00.| | -| Network Jitter Avg | Range (milliseconds) | Average of network jitter in milliseconds computed over 20 second windows during the session. Values grouped by range.
**Example value:** 066: [3–4) |
• The stream wasn't an audio stream
• The endpoint receiving the stream didn't report data | +| Round Trip | Range (milliseconds) | Average network propagation round-trip time computed as specified in RFC3550 in milliseconds. Values grouped by range.
**Example value:** 070: [15 - 20) |
• The value wasn't computed by the endpoint
• The value wasn't reported | +| Round Trip Max | Range (milliseconds) | Maximum network propagation round-trip time computed as specified in RFC3550 in milliseconds. Values grouped by range.
**Example value:** 098: [350 - 375) |
• The value wasn't computed by the endpoint
• The value wasn't reported | +| Packet Utilization | Range (packets) |Number of Real-Time Transport Protocol (RTP) packets sent in the session.|| +| Jitter Buffer Size Avg|Range (number) |Average size of jitter buffer during session. || +| Jitter Buffer Size Max|Range (number) |Maximum size of jitter buffer during session. || +| Jitter Buffer Size Min|Range (number) |Minimum size of jitter buffer during session. || +| Relative OneWay Gap Duration|Range (number) | Duration of gaps in the relative one way delay of the peer. || +| Audio Post FECPLR| Number |Reports packet loss rate after FEC has been applied for audio. Value between 0.00 and 1.00.| | +| Network Jitter Avg | Range (milliseconds) | Average of network jitter in milliseconds computed over 20 second windows during the session. Values grouped by range.
**Example value:** 066: [3–4) |
• The stream wasn't an audio stream
• Data wasn't reported by the endpoint receiving the stream | |Network Jitter Max|Number of events|Maximum of network jitter computed over 20 second windows during the session.|| | Network Jitter Min|Number of events|Minimum of network jitter computed over 20 second window during the session.| | | Video Post FECPLR | Range (ratio) | Packet loss rate after FEC is applied for aggregated across all video streams and codecs. Values grouped by range.
**Example value:** 014: [0 - 0.01) |
• The stream wasn't a video or video-based-screen-sharing stream
• The endpoint receiving the stream didn't report data | @@ -396,8 +409,8 @@ Second Media Bypass | Boolean | Indicates if the audio stream was bypassing the | Second Network Delay Event Ratio | Range (ratio) | Fraction of the call that the second endpoint detected the network delay was significant enough to impact the ability to have real-time two-way communication. Values grouped by range.
**Example value:** 016: [0.02 - 0.03) | • Indicates a non-audio stream
• The second endpoint didn't report data | | First Network Bandwidth Low Event Ratio | Range (ratio) | Fraction of the call that the first endpoint detected the available bandwidth or bandwidth policy was low enough to cause poor quality of the audio sent. Values grouped by range.
**Example value:** 016: [0.02 - 0.03) | • Stream was a non-audio stream
• The first endpoint didn't report data | | Second Network Bandwidth Low Event Ratio | Range (ratio) | Fraction of the call that the second endpoint detected the available bandwidth or bandwidth policy was low enough to cause poor quality of the audio sent. Values grouped by range.
**Example value:** 016: [0.02 - 0.03) | • Indicates a non-audio stream
• The second endpoint didn't report data | -| First Mic Glitch Rate| Number |Average glitches per 5 minutes for the microphone capture of the first endpoint. See [2.2.1.12.1 Child Elements](/openspecs/office_protocols/ms-qoe/56d41628-26d5-44c8-8f79-6bac4b0355a5) for more information. || -| Second Mic Glitch Rate|Number |Average glitches per 5 minutes for the microphone capture of the second endpoint. See [2.2.1.12.1 Child Elements](/openspecs/office_protocols/ms-qoe/56d41628-26d5-44c8-8f79-6bac4b0355a5) for more information. || +| First Mic Glitch Rate| Number |Average glitches per 5 minutes for the microphone capture of the first endpoint. For more information, see [2.2.1.12.1 Child Elements](/openspecs/office_protocols/ms-qoe/56d41628-26d5-44c8-8f79-6bac4b0355a5). || +| Second Mic Glitch Rate|Number |Average glitches per 5 minutes for the microphone capture of the second endpoint. For more information, see [2.2.1.12.1 Child Elements](/openspecs/office_protocols/ms-qoe/56d41628-26d5-44c8-8f79-6bac4b0355a5). || | First Speaker Glitch Rate|Number of events|Average glitches per 5 minutes for the first loudspeaker rendering.| | | Second Speaker Glitch Rate|Number of events|Average glitches per 5 minutes for the second loudspeaker rendering.| | | First Send Mute Percent | Range (Percentage) | Percentage of the audio stream from the first endpoint where the client was muted.| • Stream isn't an audio stream
• The first endpoint didn't report data| @@ -594,6 +607,16 @@ Second Media Bypass | Boolean | Indicates if the audio stream was bypassing the | Second Recv Resolution Width | Number (pixels) | Horizontal resolution of the video stream received by the second endpoint. | • Stream isn't a video stream | | First Video Duration Seconds |Range (seconds)| Duration of the first endpoint's video stream, measured in seconds and displayed as a range.
**Example value:** 254: [1000 - 1500] | • Not reported by the endpoint. | | Second Video Duration Seconds |Range (seconds)| Duration of the second endpoint's video stream, measured in seconds and displayed as a range.
**Example value:** 254: [1000 - 1500] | • Not reported by the endpoint. | +| First Recv Avg Freeze Duration | Range (seconds) | Average duration in seconds of received video freeze events on the first endpoint. | • Stream isn't a video stream | +| Second Recv Avg Freeze Duration | Range (seconds) | Average duration in seconds of received video freeze events on the second endpoint. | • Stream isn't a video stream | +| First Recv Rms Freeze Duration | Range (seconds) | Root-mean-square (RMS) in seconds of received video freeze events on the first endpoint. | • Stream isn't a video stream | +| Second Recv Rms Freeze Duration | Range (seconds) | Root-mean-square (RMS) in seconds of received video freeze events on the second endpoint. | • Stream isn't a video stream | +| First Recv Freeze Duration Percent | Range (percentage) | Percentage of the received video duration that was affected by freeze events on the first endpoint. | • Stream isn't a video stream | +| Second Recv Freeze Duration Percent | Range (percentage) | Percentage of the received video duration that was affected by freeze events on the second endpoint. | • Stream isn't a video stream | +| First Video Frame Rate Avg | Range (frames per second) | Average rate in frames-per-second of video on the first endpoint. | • Stream isn't a video stream | +| Second Video Frame Rate Avg | Range (frames per second) | Average rate in frames-per-second of video on the second endpoint. | • Stream isn't a video stream | +| First Video Bit Rate Avg | Range (kbps) | Average bit rate in kilobytes-per-second of video on the first endpoint. | • Stream isn't a video stream | +| Second Video Bit Rate Avg | Range (kbps) | Average bit rate in kilobytes-per-second of video on the second endpoint. | • Stream isn't a video stream | |**PSTN**|||| |First PSTN Country Region|String|If FirstIsCaller is true, First PSTN Country Region is the caller's country. If it's false, then Second PSTN Country region is the caller's country.
**Example:** US|| |Second PSTN Country Region|String|If FirstIsCaller is false, Second PSTN Country Region is the caller's country. If it's true, then First PSTN Country region is the caller's country.
**Example:** US|| @@ -687,15 +710,17 @@ Many Measurement values can also be used as filters. The following table lists t |Total Call Setup Succeeded Stream Count |number of streams |Number of streams where media path could be established between the endpoints at the start of the call.| |Total Call Setup Failure Percentage |Percentage |Percentage of all streams where media path couldn't be established between the endpoints at the start of the call. | |Total Call Dropped Failure Percentage |Percentage |Percentage of successfully established streams where media path didn't terminate normally.| +|Total Short Call Count |Number of streams |Number of calls with a duration equal to or less than five seconds. | |Total Answer Seizure Ratio |Ratio |Ratio of calls with duration less than 5 seconds over the total number of calls. | |Total Short Call Percentage |Percentage |Percentage of total calls less than 1 minute long. | |Total Media Failure Percentage |Percentage |Percentage of all streams where either media path couldn't be established or didn't terminate normally. | -|Media Failed Due To Firewall DPI Stream Count |Number of streams |Number of streams that failed to be established due to network equipment blocking access due to deep packet inspection not allowing Skype for Business traffic. These failures typically indicate a proxy, firewall or other network security device isn't correctly configured. These devices might be blocking access to the IP address and ports that are used by Skype for Business in Microsoft 365 or Office 365. | -|Firewall DPI Media Failure Percentage |Percentage |Percentage of streams that failed to be established due to network equipment blocking access due to deep packet inspection not allowing Skype for Business traffic. These failures typically indicate a proxy, firewall or other network security device isn't correctly configured. These devices might be blocking access to the IP address and ports that are used by Skype for Business in Microsoft 365 or Office 365. | -|Media Failed Due To Firewall IP Blocked Stream Count |Number of streams |Number of streams that failed to be established due to network equipment blocking access to Skype for Business servers. These failures typically indicate a proxy, firewall or other network security device isn't correctly configured. These devices might be blocking access to the IP address and ports that are used by Skype for Business in Microsoft 365 or Office 365. | +|Media Failed Due To Firewall DPI Stream Count |Number of streams |Number of streams that failed to be established due to network equipment blocking access due to deep packet inspection not allowing Skype for Business traffic. These failures typically indicate a proxy, firewall, or other network security device isn't correctly configured. These devices might be blocking access to the IP address and ports that are used by Skype for Business in Microsoft 365 or Office 365. | +|Firewall DPI Media Failure Percentage |Percentage |Percentage of streams that failed to be established due to network equipment blocking access due to deep packet inspection not allowing Skype for Business traffic. These failures typically indicate a proxy, firewall, or other network security device isn't correctly configured. These devices might be blocking access to the IP address and ports that are used by Skype for Business in Microsoft 365 or Office 365. | +|Media Failed Due To Firewall IP Blocked Stream Count |Number of streams |Number of streams that failed to be established due to network equipment blocking access to Skype for Business servers. These failures typically indicate a proxy, firewall, or other network security device isn't correctly configured. These devices might be blocking access to the IP address and ports that are used by Skype for Business in Microsoft 365 or Office 365. | |Firewall IP Blocked Media Failure Percentage |Percentage |Percentage of streams that failed to be established because network equipment blocked access to Skype for Business servers. These failures typically indicate a proxy, firewall, or other network security device isn't correctly configured. These devices might be blocking access to the IP address and ports that are used by Skype for Business in Microsoft 365 or Office 365. | | Media Failed Due To Other Stream Count|Number of streams| Number of streams where media path couldn't be established between the endpoints due to an undetermined/unclassified reason.| | Other Media Failure Percentage|Percentage| Percentage of streams where media path couldn't be established between the endpoints due to an undetermined/unclassified reason. | +| Total Call Count | Number of calls | Number of distinct calls, either as peer-to-peer calls or call legs within a conference. | | Total CDR Available Call Count|Number of streams|Total number of calls with reliability/diagnostics information available. There's an up to 0.2% error for this measure. See note below for details.| | Total Media Failed Call Count|Number of streams|Number of calls where media path couldn't be established between the endpoints. There's an up to 0.2% error for this measure. See note below for details.| |Audio Stream Count |Number of streams |Number of audio streams. | @@ -725,7 +750,7 @@ Many Measurement values can also be used as filters. The following table lists t | Audio Poor Call Percentage |Percentage of calls|Percentage of classified calls involving audio classified as poor. There's an up to 0.2% error for this measure. See note below for details.| |AppSharing Stream Count |Number of streams |Number of RDP-based application sharing streams. | |AppSharing Poor Due To SpoiledTilePercentTotal Count |Number of streams |Number of application sharing streams where the spoiled tile percent total metric exceeds thresholds listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | -|AppSharing Poor Due To RelativeOneWayAverage Count |Number of streams |Number of application sharing streams where the spoiled tile percent total metric exceeds thresholds listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | +|AppSharing Poor Due To RelativeOneWayAverage Count |Number of streams |Number of application sharing streams where the relative one-way average metric exceeds thresholds listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | |AppSharing Poor Due To RDPTileProcessingLatencyAverage Count |Number of streams |Number of application sharing streams where the RDP tile processing latency average exceeds thresholds listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | |AppSharing Poor Stream Count |Number of streams |Number of application sharing streams classified as poor based on network metrics listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | |AppSharing Good Stream Count |Number of streams |Number of application sharing streams classified as good based on network metrics listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | @@ -740,6 +765,7 @@ Many Measurement values can also be used as filters. The following table lists t |Video Good Stream Count |Number of streams |Number of video streams classified as good based on network metrics listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | |Video Unclassified Stream Count |Number of streams |Number of video streams that didn't have sufficient data to be classified as good or poor based on network metrics listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). Unclassified streams are omitted from 'Poor Percentage' calculations. | |Video Poor Percentage|Percentage |Percentage of classified video streams that were classified as poor based on network metrics listed here [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | +|Video Call Count | Number of calls | Number of calls involving video. There's an up to 0.2% error for this measure. See note below for details. | |Video Poor Percentage Due to Freeze|Percentage | Percentage of main video streams that were classified as poor based on the Video Poor metric Due to Freeze listed here [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). This field is specific to Microsoft Teams only | |VBSS Stream Count |Number of streams |Number of video-based-screen sharing streams. | |VBSS Poor Due To VideoPostFecplr Count |Number of streams |Number of video-based-screen-sharing streams where the Video Post Fec plr exceeds thresholds listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | @@ -749,6 +775,25 @@ Many Measurement values can also be used as filters. The following table lists t |VBSS Good Stream Count |Number of streams |Number of video-based-screen-sharing streams classified as good based on network metrics listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | |VBSS Unclassified Stream Count |Number of streams |Number of video-based-screen-sharing streams that didn't have sufficient data to be classified as good or poor based on network metrics listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). Unclassified streams are omitted from 'Poor Percentage' calculations.| |VBSS Poor Percentage |Percentage |Percentage of classified video-based-screen-sharing streams that classified as poor based on network metrics listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | +|Audio Device Failure Percentage |Percentage |Percentage of all audio streams in which an audio capture or render device failure is detected. | +|Audio Device General Failure Percentage |Percentage |Percentage of all audio streams in which a general hardware failure on an audio device is detected. | +|No Mic Device Enumerated Failure Count |Number of streams |Total number of audio streams in which no audio capture devices were detected. | +|No Mic Device Enumerated Failure Percentage |Percentage |Percentage of all audio streams in which no audio capture devices were detected. | +|Mic Initialization Failure Count |Number of streams |Total number of audio streams in which a failure occurred during the hardware initialization of the microphone device. | +|Mic Initialization Failure Percentage |Percentage |Percentage of all audio streams in which a failure occurred during the hardware initialization of the microphone device. | +|Speaker Initialization Failure Count |Number of streams |Total number of audio streams in which a failure occurred during the hardware initialization of the audio render device. | +|Speaker Initialization Failure Percentage |Percentage |Percentage of all audio streams in which a failure occurred during the hardware initialization of the audio render device. | +|No Speaker Device Enumerated Failure Count |Number of streams |Total number of audio streams in which no audio render devices were detected. | +|No Speaker Device Enumerated Failure Percentage |Percentage |Percentage of all audio streams in which no audio render devices were detected. | +|Mic Is Silent Failure Count |Number of streams |Total number of audio streams in which no audio is detected from the microphone while unmuted. | +|Mic Is Silent Failure Percentage |Percentage |Percentage of all audio streams in which no audio is detected from the microphone while unmuted. | +|Audio Device Failure Count |Number of streams |Number of streams with either a mic or speaker failure. | +|First Audio Device General Failure Rate |Percentage |Percentage of all audio streams with a general audio hardware failure on the first endpoint. | +|Second Audio Device General Failure Rate |Percentage |Percentage of all audio streams with a general audio hardware failure on the second endpoint. | +|First Mic Device Failure Rate |Percentage |Percentage of all audio stream in which an audio capture device failure is detected on the first endpoint. | +|Second Mic Device Failure Rate |Percentage |Percentage of all audio stream in which an audio capture device failure is detected on the second endpoint. | +|First Speaker Device Failure Rate |Percentage |Percentage of all audio stream in which an audio render device failure is detected on the first endpoint. | +|Second Speaker Device Failure Rate |Percentage |Percentage of all audio stream in which an audio render device failure is detected on the second endpoint. | |Avg Call Duration |Seconds |Average duration of streams in seconds. | |Total Audio Stream Duration (Minutes) |Minutes |Total audio stream duration in minutes in the selected time range. | |First Feedback Rating Avg |User rating (1-5) |Average rating of streams reported by the user using the first endpoint. Calls are rated from 1-5 and the rating is applied to all streams of the call. | @@ -809,7 +854,7 @@ Many Measurement values can also be used as filters. The following table lists t | Avg Healer FEC Packet Used Ratio|Range (Ratio)|Average ratio of used FEC packets over total number of received FEC packets.| |Avg Round Trip |Milliseconds |Average of average network propagation round-trip time computed as specified in RFC3550 in milliseconds for streams. | |Avg Round Trip Max |Milliseconds |Average of maximum network propagation round-trip time computed as specified in RFC3550 in milliseconds for streams. | - Avg Packet Utilization|Number of packets|Average number of Real-Time Transport Protocol (RTP) packets sent per second in the session.| +|Avg Packet Utilization|Number of packets|Average number of Real-Time Transport Protocol (RTP) packets sent per second in the session.| |Avg Network Jitter |Milliseconds | Average of network jitter computed over 20 second windows during the session. This metric is contained in the audio payload of the QoE. Stream types other than audio won't report a value for this measurement. | | Avg Network Jitter Max|Milliseconds |Average of maximum network jitter in milliseconds computed over 20 second windows during the session. This metric is contained in the audio payload of the QoE. Stream types other than audio won't report a value for this measurement. | | Avg Network Jitter Min|Milliseconds|Average of minimum network jitter values in milliseconds computed over 20 second windows during the session for streams. This metric is contained in the audio payload of the QoE. Stream types other than audio won't report a value for this measurement.| @@ -817,6 +862,7 @@ Many Measurement values can also be used as filters. The following table lists t | Avg Jitter Buffer Size Max|Milliseconds|Maximum size of jitter buffer during session. This metric is contained in the audio payload of the QoE. Stream types other than audio won't report a value for this measurement.| | Avg Jitter Buffer Size Min|Milliseconds|Minimum size of jitter buffer during session. This metric is contained in the audio payload of the QoE. Stream types other than audio won't report a value for this measurement.| | Avg Relative OneWay |Milliseconds|Average computed relative one way delay of the peer. | +| Avg Relative OneWay Max | Milliseconds | Average of the maximum relative one-way delay of the peer. | | Avg Relative OneWay Gap Occurrences|Milliseconds|Average number of instances of gaps in the relative one way delay of the peer.| | Avg Relative OneWay Gap Density|Milliseconds|Average density of gaps in the relative one way delay of the peer.| | Avg Relative OneWay Gap Duration|Number (Milliseconds)|Average duration of gaps in the relative one way delay of the peer.| @@ -863,8 +909,9 @@ Many Measurement values can also be used as filters. The following table lists t |P50 Latency | Milliseconds | 50% of the requests should be faster than given latency.| |P50 Jitter | Milliseconds | 50% of the requests should be faster than given Jitter.| |P50 Packet Loss Rate | Percentage | 50% of the requests should have lower than the given Packet Loss Rate.| -|PSTN Outgoing Post Dial Delay| Milliseconds | The delay that occurs on outgoing calls measured from the time a number is dialed until the caller or called party hears ringing.| -|PSTN Incoming Post Dial Delay | Milliseconds | The time or delay that occurs on incoming calls measured from the time a number is dialed until the caller or called party hears ringing.| +|PSTN Outgoing Post Dial Delay| Milliseconds | The delay that occurs on outgoing calls measured from the time a number has been dialed until the caller or called party hears ringing.| +|PSTN Incoming Post Dial Delay | Milliseconds | The time or delay that occurs on incoming calls measured from the time a number has been dialed until the caller or called party hears ringing.| +|PSTN Calls Affected By NER | Number of calls | Number of PSTN calls considered unsuccessful according to the Network Effectiveness Ratio (NER). | |PSTN NER Good Percentage | Percentage | The NER measures the ability of a network to deliver calls by measuring the number of calls sent versus the number of calls delivered to a recipient.
NER = (Answered calls + User Busy + Ring no Answer + Terminal Reject Seizures) / Total Attempt Calls x 100. There's an up to 0.2% error for this measure. See note below for details.| | Avg Auto Attendant Chain Duration Seconds | Integer | The average duration that users spend in the Auto Attendant, measured in seconds. | | Avg Call Queue Duration Seconds | Integer | The average duration that users are waiting for a Call Queue to be answered by an agent, measured in seconds. | @@ -876,7 +923,7 @@ Many Measurement values can also be used as filters. The following table lists t | Detected Inbound Network Problem True Count | Integer | Number of instances that there's high confidence that a First-to-Second media stream might be impacted due to the inbound network. | | Detected Inbound Network Problem False Count | Integer | Number of instances that there isn't high confidence that a First-to-Second media stream might be impacted due to the inbound network. | | Detected Inbound Network Problem Null Count | Integer | Number of instances that the Detected Inbound Network Problem model returned a null value. See Detected Inbound Network Problem dimension for explanation. | -| Detected Inbound Network Problem Rate | Percentage | Percentage of streams for which there is high confidence that a First-to-Second media stream might be impacted due to the inbound network. | +| Detected Inbound Network Problem Rate | Percentage | Percentage of streams for which there's high confidence that a First-to-Second media stream might be impacted due to the inbound network. | | Avg First Healed Data Ratio Value | Percentage (Decimal) | Percentage of the audio stream in which the audio healer on the first endpoint is invoked, averaged across the number of streams in a given row. High HDR indicates that the client expected audio but Teams didn't have any content to play back. High healer usage is experienced by end-users as choppy audio. This measurement isn't currently calculated for WebRTC-based clients. | | Avg Second Healed Data Ratio Value | Percentage (Decimal) | Percentage of the audio stream in which the audio healer on the second endpoint is invoked, averaged across the number of streams in a given row. High HDR indicates that the client expected audio but Teams didn't have any content to play back. High healer usage is experienced by end-users as choppy audio. This measurement isn't currently reported by WebRTC-based clients. | | Avg First Received Audio Seconds | Seconds (Decimal) | Amount of active audio received by the first endpoint in seconds, excluding silence. This measurement isn't currently reported by WebRTC based clients. | diff --git a/Teams/expand-teams-across-your-org/educationImages/ai-recommendations-setting-large.png b/Teams/expand-teams-across-your-org/educationImages/ai-recommendations-setting-large.png new file mode 100644 index 0000000000..b2b900b647 Binary files /dev/null and b/Teams/expand-teams-across-your-org/educationImages/ai-recommendations-setting-large.png differ diff --git a/Teams/expand-teams-across-your-org/educationImages/ai-recommendations-setting.png b/Teams/expand-teams-across-your-org/educationImages/ai-recommendations-setting.png new file mode 100644 index 0000000000..c16e19dd8b Binary files /dev/null and b/Teams/expand-teams-across-your-org/educationImages/ai-recommendations-setting.png differ diff --git a/Teams/get-started-with-teams-essentials.md b/Teams/get-started-with-teams-essentials.md index 0b38806671..dbabd25cd2 100644 --- a/Teams/get-started-with-teams-essentials.md +++ b/Teams/get-started-with-teams-essentials.md @@ -3,7 +3,7 @@ title: Microsoft Teams Essentials QuickStart guide for small businesses author: MicrosoftHeidi ms.author: heidip manager: jtremper -ms.date: 11/19/2021 +ms.date: 03/26/2024 ms.topic: article ms.service: msteams audience: admin @@ -24,13 +24,13 @@ appliesto: Microsoft Teams Essentials is a standalone Teams subscription that provides an all-in-one solution with meetings, chat, and collaboration for small businesses. As your business adapts to the increased need for remote working and virtual connections, you may be searching for a way to securely collaborate with employees, partners, suppliers, and customers. Whether you're a multi-city bakery, or a nine-person event agency, Microsoft Teams Essentials can bring your business together through one connected experience. -### Before you continue +## Before you continue -Microsoft Teams Essentials is available for purchase through Microsoft's direct website and select Microsoft Cloud Partners. Subscriptions through direct and partner differ in some ways because they use different identity systems. For more information, see [Microsoft Teams Essentials plans](#how-does-microsoft-teams-essentials-compare-to-other-microsoft-teams-plans) +Microsoft Teams Essentials is available for purchase through Microsoft's direct website and select Microsoft Cloud Partners. Subscriptions through direct and partner differ in some ways because they use different identity systems. For more information, see [Microsoft Teams Essentials plans](#how-does-microsoft-teams-essentials-compare-to-other-microsoft-teams-plans). -A subscription purchased through Microsoft's direct website uses Microsoft account identity, which allows you to use your existing email address like TomislavK@outlook.com, TomislavK@gmail.com, or TomislavK@ContosoLandscaping.com to sign up. +A subscription purchased through Microsoft's direct website uses Microsoft account identity, which allows you to use your existing email address like `TomislavK@outlook.com`, `TomislavK@gmail.com`, or `TomislavK@ContosoLandscaping.com` to sign up. -Alternatively, Teams Essentials purchased through select Microsoft Certified Partners uses Microsoft Entra which asks you to create a new login/identity. Partners can configure Teams Essentials to connect to your existing email address so you can sign in using your existing email address. +Alternatively, Teams Essentials purchased through select Microsoft Certified Partners uses Microsoft Entra, which asks you to create a new login/identity. Partners can configure Teams Essentials to connect to your existing email address so you can sign in using your existing email address. ## What Microsoft Teams Essentials subscription do I have? @@ -38,12 +38,10 @@ If you purchased Teams Essentials through Microsoft's website (direct), you own If you purchased Teams Essentials through a Microsoft Certified Partner, you own **Microsoft Teams Essentials (Microsoft Entra identity)**. - ## How does Microsoft Teams Essentials compare to other Microsoft Teams plans? The following table lists the major Microsoft Teams features available across plans. Certain caveats apply. For more information, see the footnotes. This table may change without notice. For the most up-to-date, complete list of features, visit [Microsoft Teams service description](/office365/servicedescriptions/teams-service-description). - |Microsoft Teams Plan | **Microsoft Teams (free)** | [**Microsoft Teams Essentials** ](#get-microsoft-teams-essentials) | **Microsoft Teams Essentials (Microsoft Entra identity)** | [**Microsoft 365 Business Basic**](/microsoft-365/admin/setup/setup-business-basic?) | |---------|---------|---------|---------|---------| |***Feature*** | | | | | @@ -90,10 +88,6 @@ The following table lists the major Microsoft Teams features available across pl 2 Teams Essentials (Microsoft Entra identity) through partner includes 2 GB Exchange mailbox and no archiving, allowing users to sync with third-party email providers. - -> [!IMPORTANT] -> To get enhanced administration and entire full set of Teams features, you'll need to upgrade to the full version of Teams by purchasing an appropriate [Microsoft 365 or Office 365 subscription plan](https://www.microsoft.com/en-us/microsoft-teams/compare-microsoft-teams-options) for your users. We recommend this as you'll have more flexibility to manage the way your organization collaborates. - ## Administration limits and specifications for Microsoft Teams Essentials See [Microsoft Teams limits and specifications](/microsoftteams/limits-specifications-teams) to learn more about the limits, specifications, and other requirements that apply to Teams. @@ -106,46 +100,31 @@ To get started with Teams Essentials, follow these steps: 1. **Purchase the subscription.** Go to [Microsoft Teams Essentials for small business](https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-options) and select **Buy now** under Microsoft Teams Essentials. 2. **Sign up with your existing email address.** Use an existing email address and follow the instructions to purchase user licenses. -3. **Review Teams service description.** Visit [Microsoft Teams service description ](/office365/servicedescriptions/teams-service-description) to learn more about Microsoft Teams. +3. **Review Teams service description.** Visit [Microsoft Teams service description](/office365/servicedescriptions/teams-service-description) to learn more about Microsoft Teams. -When you've completed these tasks, you're ready to plan, deploy, and use the Teams app. +When you complete these tasks, you're ready to plan, deploy, and use the Teams app. To do that, complete these three steps: -1. **Install the Teams app.** Install the Teams client on your PC or mobile device by going to [Download Microsoft Teams](https://www.microsoft.com/microsoft-teams/download-app). +1. **Install the Teams app.** Install the Teams client on your PC or mobile device by going to [Download Microsoft Teams](https://www.microsoft.com/microsoft-teams/download-app). 2. **Get Familiar with Teams.** The best way to become familiar with Teams is to start using it right away. Take some time to explore the application so you have a better understanding of its capabilities. 3. **Plan for adoption.** For small businesses, planning for user adoption can be as simple as individually showing your users how to use Teams. Often, small business customers don't consider this step for new applications, which negatively affects the application's success and adoption. -4. **Manage Microsoft Teams Essentials.** Any Teams (free) users who have upgraded to Microsoft Teams Essentials can manage it. +4. **Manage Microsoft Teams Essentials.** Any Teams (free) users who upgraded to Microsoft Teams Essentials can manage it. -> [!NOTE] -> For information on how to to upgrade from Teams (free) to Microsoft Teams Essentials, see [Upgrade from Teams (free) to Microsoft Teams Essentials](#upgrade-from-teams-free-to-microsoft-teams-essentials). - -Managing Microsoft Teams Essentials refers to assigning Microsoft Teams Essentials seats to other users - on whose behalf you purchased - in the intended proportions. You can manage Microsoft Teams Essentials through the Microsoft Admin center. +Managing Microsoft Teams Essentials refers to assigning Microsoft Teams Essentials seats to other users - on whose behalf you purchased - in the intended proportions. You can manage Microsoft Teams Essentials through the Microsoft admin center. ### Upgrade from Teams (free) to Microsoft Teams Essentials If your organization is using a free version of Microsoft Teams, you can easily upgrade to the Teams Essentials version by purchasing a plan for your users directly in Teams from [Find the right Microsoft Teams for your needs](https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-options). -## Upgrade from Teams Free (classic) to Teams - -A Teams Free (classic) user can upgrade to the full version of Teams, that is, to subscriptions such as Microsoft 365 Business (Basic) and Microsoft 365 Business (Standard). - -The upgrade can be done by following the steps specified in [Upgrade from Teams Free (classic) to Teams](https://support.microsoft.com/office/upgrade-from-teams-free-classic-to-teams-29475bbd-a34f-4175-9b33-d44430f8ad39). - ### Limitations Keep the following limitations in mind: -- You can't switch back to Teams Free (classic) after you upgrade. - -- You can't merge multiple Teams Free (classic) tenants into a single paid tenant. - -- All users must be in the same domain. (All users will get a sign-in email in the format *username*@*domain.com*.) - -- All users must be upgraded: a mix of Teams Free (classic) and paid subscription users in the same tenant isn't supported. +- All users must be in the same domain. (All users get a sign-in email in the format *username*@*domain.com*.) @@ -155,7 +134,7 @@ No. Teams Essentials with Microsoft Entra identity is only available through sel #### Can I use an existing email system with Microsoft Teams Essentials? -Yes. You can keep your existing email system and use Teams Essentials to meet, chat and collaborate. +Yes. You can keep your existing email system and use Teams Essentials to meet, chat, and collaborate. #### Can I connect my existing calendar solution with Teams Essentials? @@ -169,12 +148,8 @@ To connect an existing calendar solution with Teams Essentials (Microsoft Entra To get started, visit [**Connect Microsoft Teams Essentials (Microsoft Entra identity) to an existing email system with calendar**](connect-teams-essentials-to-email.md) for more information. You can connect an existing email system like Google Workspace to Microsoft Teams Essentials (Microsoft Entra identity) to stay connected across platforms with integrated calendars and sign in. -#### Can I upgrade Teams Essentials bought directly through Microsoft's website to Microsoft 365? - -Upgrades from Teams Essentials to Microsoft 365 will be available soon. - ## More information - Visit [Configuration Guide](connect-teams-essentials-to-email.md) for configuration steps on connecting Microsoft Teams Essentials (Microsoft Entra identity) to an existing email system with calendar -- To find out more about Teams versions and their capabilities, visit [Compare Teams plans](https://www.microsoft.com/en-us/microsoft-teams/compare-microsoft-teams-options) +- To find out more about Teams versions and their capabilities, visit [Compare Teams plans](https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-options) diff --git a/Teams/hardware-requirements-for-the-teams-app.md b/Teams/hardware-requirements-for-the-teams-app.md index 89568fc67a..392229a8ee 100644 --- a/Teams/hardware-requirements-for-the-teams-app.md +++ b/Teams/hardware-requirements-for-the-teams-app.md @@ -55,7 +55,7 @@ All of the requirements in the following sections apply to both the Microsoft Te |Operating system | One of the three most recent versions of macOS. You can find information about the latest macOS versions, and how to upgrade your version of macOS, [here](https://support.apple.com/en-us/HT201260). For example, when a new version of macOS is released, the new version and the two immediately preceding it become the supported versions. | |Video | Compatible webcam | |Voice | Compatible microphone and speakers, headset with microphone, or equivalent device | -|Video calls and meetings |
  • Requires two-core processor. For higher video/screen share resolution and frame rate, a four-core processor or better is recommended.
  • Joining a meeting using proximity detection in a Microsoft Teams Room requires Bluetooth LE. Bluetooth LE requires Bluetooth to be enabled on the client device.
+|Video calls and meetings |
  • Requires two-core processor. For higher video/screen share resolution and frame rate, a four-core processor or better is recommended.
  • Joining a meeting using proximity detection in Microsoft Teams Rooms requires Bluetooth LE. Bluetooth LE requires Bluetooth to be enabled on the client device.
| ## Hardware requirements for Teams on Linux diff --git a/Teams/inbound-call-routing.md b/Teams/inbound-call-routing.md index 4af21c80de..340869a81c 100644 --- a/Teams/inbound-call-routing.md +++ b/Teams/inbound-call-routing.md @@ -37,7 +37,7 @@ Calls that come from the PSTN or are federated can be routed in the following wa - **Use default settings** The call is routed using your default inbound call routing settings. This is the default setting for PSTN and federated calls. - **Use unanswered settings** The call is routed according to the unanswered call forwarding settings set for that user. - **Send to voicemail** The call is routed directly to voicemail and isn't shown to the user. If the called user doesn't have voicemail enabled, the call will be disconnected. For more information on voicemail, see [Set up Cloud Voicemail](set-up-phone-system-voicemail.md). -- **Let users decide** (PSTN calls only) The call is routed as **Use default settings**. +- **Let users decide** (PSTN calls only) Users can determine their PSTN call routing choice from call settings in the Teams app. For information on busy options, see [Configure busy options](#configure-busy-options). diff --git a/Teams/includes/eea-teams-licensing.md b/Teams/includes/eea-teams-licensing.md index 354cf3eeae..749f85d95f 100644 --- a/Teams/includes/eea-teams-licensing.md +++ b/Teams/includes/eea-teams-licensing.md @@ -1,6 +1,9 @@ -> [!IMPORTANT] -> Starting October 1, 2023, new commercial customers in the EEA and Switzerland who wish to provide workers with both Microsoft Teams and the value in existing Microsoft 365 or Office 365 Enterprise suites (E1/E3/E5) will need to purchase two SKUs: one E1/E3/E5 EEA (no Teams) suite and Microsoft Teams EEA. Microsoft 365 Business suites (up to 300 users) and Frontline workers will be available in versions both with and without Teams in these regions. +> Starting April 1, 2024, all new Enterprise customers who wish to provide workers with both Microsoft Teams and the value in existing Microsoft 365 or Office 365 Enterprise suites (E1/E3/E5) will need to purchase two SKUs: one E1/E3/E5 (no Teams) suite and one Teams standalone (*Microsoft Teams Enterprise* or *Microsoft Teams EEA*). Microsoft 365 Business suites (up to 300 users) and Frontline worker suites will be available in versions both with and without Teams. > -> EEA and Switzerland customers who were already subscribed to Microsoft 365 or Office 365 suites that include Teams prior to October 1, 2023 will continue to be able to use and renew those subscriptions. +> For Enterprise customers in the European Economic Area (EEA) and Switzerland, this change became effective on October 1, 2023. > -> For more information on this licensing change in the EEA and Switzerland, see [New subscription structure for Microsoft 365 in Europe](https://www.microsoft.com/licensing/news/Microsoft365-Teams-EEA). +> Enterprise customers already subscribed to Microsoft 365 or Office 365 suites that include Teams prior to April 1, 2024 will continue to be able to use, renew, upgrade, and otherwise adjust their subscriptions that include Teams as before. +> +> For more information on this licensing change in the EEA and Switzerland, see [New subscription structure for Microsoft 365 in Europe]. +> +> For more information on this licensing change for all other global regions, see [Microsoft Teams licensing announcement](https://aka.ms/MSTeamsLicensingROW). diff --git a/Teams/institution-settings.md b/Teams/institution-settings.md new file mode 100644 index 0000000000..3db87ea561 --- /dev/null +++ b/Teams/institution-settings.md @@ -0,0 +1,46 @@ +--- +title: Set up AI content recommendations for educators in an institution +author: NiravRawell21 +ms.author: nirawell +manager: michalgi +ms.reviewer: nirawell +ms.date: 02/26/2024 +ms.topic: article +ms.tgt.pltfrm: cloud +ms.service: msteams +audience: Admin +f1.keywords: + - NOCSH +appliesto: + - Microsoft Teams +ms.localizationpriority: medium +search.appverid: MET150 +description: How to enable or disable AI content recommendations for educators in an institution. +ms.collection: + - M365-collaboration + - tier2 +--- + +# Set up AI content recommendations in an institution + +Institution settings in educational contexts are crucial for administrators to tailor and oversee their digital environments effectively. These settings encompass user management with role-based access control, curriculum and course configuration, communication tools for efficient interaction, and robust data privacy measures to comply with established standards. + +## Generative AI functionality + +Using this functionality, educators use AI to generate content such as reading passages, comprehension questions, rubrics, assignment instructions, and class module outlines. It allows the use of generative AI enhancements for Assignments, Classwork, Reading Progress, and Insights apps. + +## Enable AI for Educators + +The generative AI feature integrates with the Teams Education Applications and is enabled by default. To disable or re-enable the AI recommendations, follow these steps: + +1. In Teams admin center, access **Education** > [**Institution settings**](https://admin.teams.microsoft.com/education/institution-settings). + +1. Enable or disable the **AI content recommendations** and select **Save**. + + :::image type="content" source="expand-teams-across-your-org/educationImages/ai-recommendations-setting.png" alt-text="Screenshot showing the setting for admins to enable or disable AI recommendations for content in an educational institution." lightbox="expand-teams-across-your-org/educationImages/ai-recommendations-setting-large.png"::: + +## Related articles + +* [Instructions Generation: Responsible AI FAQ](https://support.microsoft.com/en-us/topic/instructions-generation-responsible-ai-faq-f44f9d1e-152e-4456-a3f8-b1bb0595eda8) +* [Rubric Generation: Responsible AI FAQ](https://support.microsoft.com/en-us/topic/rubric-generation-responsible-ai-faq-5d74dd6f-7a9c-4053-a3e1-0af50e94218b) +* [Reading Progress Passage generation FAQ](https://support.microsoft.com/en-us/topic/reading-progress-passage-generation-faq-62a6c3d8-4ee6-4809-804e-78ada1d327e6) diff --git a/Teams/manage-apps.md b/Teams/manage-apps.md index 851613d5ea..6df772b49c 100644 --- a/Teams/manage-apps.md +++ b/Teams/manage-apps.md @@ -8,7 +8,7 @@ ms.service: msteams ms.subservice: teams-apps ms.custom: intro-get-started audience: admin -ms.date: 03/18/2024 +ms.date: 03/30/2024 ms.collection: - M365-collaboration - tier2 @@ -158,7 +158,7 @@ As an admin, you can [delete custom apps](teams-custom-app-policies-and-settings Blocked apps may still have access to data from the teams that the apps were added to. To turn off app data access, a Global Administrator, an Application Administrator, or a Cloud Application Administrator must [turn off user sign-in in the Microsoft Entra admin center](/azure/active-directory/manage-apps/disable-user-sign-in-portal?pivots=portal). -## Manage org-wide app settings for Microsoft 365 Government +## Manage org-wide app settings for Microsoft 365 Government In a Microsoft 365 Government - GCC, GCCH and DoD deployment of Teams, all third-party apps are blocked by default. In GCC, you see the following note about managing third-party apps on the app permission policies page in the Microsoft Teams admin center. @@ -181,6 +181,12 @@ Use org-wide app settings to control whether users can install third-party apps. To allow third-party apps, either edit and use the Global (Org-wide default) policy or create and assign an admin-created policy. +## Manage apps in Gallatin and Air-gapped cloud environments + +In Gallatin and air-gapped cloud environments, admins can get an overview of the Teams apps in Teams admin center on the Teams apps > Manage apps page. + +To view more details of an app, click an app's name to access the app details page. You can allow or block the app for your users. + ## Support information for apps You may have queries about admin settings or configuration, user flows and app features, app troubleshooting, and more. You receive support information about apps from the following two different sources: diff --git a/Teams/manage-freemium.md b/Teams/manage-freemium.md deleted file mode 100644 index b17780ff3c..0000000000 --- a/Teams/manage-freemium.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Manage Microsoft Teams Free (classic) -author: DaniEASmith -ms.author: danismith -manager: pamgreen -ms.topic: conceptual -ms.service: msteams -audience: admin -ms.reviewer: -ms.date: 04/12/2019 -search.appverid: MET150 -description: Learn about who can manage users in Teams Free (classic) and learn about the differences between the various Teams plans. -ms.localizationpriority: medium -f1.keywords: -- CSH -ms.custom: - - NewAdminCenter_Update - - seo-marvel-apr2020 -ms.collection: - - M365-collaboration - - m365initiative-deployteams - - tier1 -appliesto: - - Microsoft Teams ---- - -# Manage Microsoft Teams Free (classic) - -In the classic free version of Microsoft Teams, the first person who signs up in your organization has a limited admin role. The person who has this limited role can add and remove team members and specify whether anyone can invite more members, but this user has no advanced administrative capabilities and no access to the Microsoft Teams admin center. To learn more, read [Invite people to Teams Free (classic)](https://support.office.com/article/invite-people-to-teams-free-53a9b20c-2ad7-442e-967c-2e9305e96463). - -To get the full set of Teams features, including enhanced administration, you'll need to [upgrade to the full version of Teams](upgrade-freemium.md) by purchasing an appropriate Microsoft 365 or Office 365 subscription plan for your users. - -To find out more about Teams versions and their capabilities, see [Compare Teams plans](https://products.office.com/microsoft-teams/free). - -## More information - -- For a quick summary of the differences between Teams and Teams Free (classic), see [Differences between Microsoft Teams and Microsoft Teams Free (classic)](https://support.office.com/article/0b69cf39-eb52-49af-b255-60d46fdf8a9c). -- For more information about upgrading to the full version of Teams, see [Upgrade from Teams Free (classic) to Teams](https://support.office.com/article/29475bbd-a34f-4175-9b33-d44430f8ad39) and [Upgrade Microsoft Teams Free (classic) to subscription version](upgrade-freemium.md). -- To get started with more admin tasks associated with upgrading users, including adding user licenses, changing user names, and assigning temporary passwords, see [For admins upgrading from Teams Free (classic) to a paid subscription](https://support.office.com/article/75a95e7f-001e-42d0-a787-ae8b992d5a52). - -## Get the right Teams trial - -- As an alternative to Teams Free (classic), check out [Teams Exploratory](teams-exploratory.md). - -- EDU customers should use the free [Office 365 A1 license](https://www.microsoft.com/microsoft-365/academic/compare-office-365-education-plans). - diff --git a/Teams/manage-praise-app.md b/Teams/manage-praise-app.md index 2f93c91641..d1f6c6ebea 100644 --- a/Teams/manage-praise-app.md +++ b/Teams/manage-praise-app.md @@ -1,10 +1,10 @@ --- title: Manage the Praise app in the Teams admin center -author: MicrosoftHeidi -ms.author: heidip +author: Lana-Chin +ms.author: v-chinlana manager: jtremper ms.reviewer: rjam -ms.date: 06/14/2023 +ms.date: 04/01/2024 audience: admin ms.topic: how-to ms.service: msteams @@ -21,7 +21,7 @@ ms.collection: ## Overview of Praise -The Praise app in Microsoft Teams helps users show appreciation to members of your organization or classroom. The badges in Praise are designed to help recognize the effort that goes into the wide range of work that Teams users do, from educators to frontline workers. To learn more, check out [Send Praise to people](https://support.microsoft.com/office/send-praise-to-people-50f26b47-565f-40fe-8642-5ca2a5ed261e). +The Praise app in Microsoft Teams helps users show appreciation to members of your organization or classroom. The badges in Praise are designed to help recognize the effort that goes into the wide range of work that Teams users do, from educators to frontline workers. To learn more, check out [Send Praise to people in Teams](https://support.microsoft.com/office/send-praise-to-people-50f26b47-565f-40fe-8642-5ca2a5ed261e). Admins must have a Teams license to access this feature. If you try to access this feature without a Teams license, you'll get an error message. @@ -43,7 +43,7 @@ If you set the status to **Blocked**, the Praise app is blocked within a few min ## Enable or disable Praise for specific users in your organization -To allow or block specific users in your organization from using Praise, make sure Praise is turned on for your organization on the [Manage apps](manage-apps.md) page. Then create a custom policy for app permissions and assign it to those users. To learn more, see [Manage app permission policies in Teams](teams-app-permission-policies.md). +To allow or block specific users in your organization from using Praise, make sure Praise is turned on for your organization on the [Manage apps](manage-apps.md) page. Then create a custom policy for app permissions and assign it to those users. To learn more, see [Use app permission policies to control user access to apps](teams-app-permission-policies.md). ## Composer @@ -61,5 +61,4 @@ To send feedback, select the **Help** option at bottom of the Teams left navigat ## Related articles -[Manage your apps in the Microsoft Teams admin center](manage-apps.md) - +[Overview of app management and governance in Teams admin center](manage-apps.md) \ No newline at end of file diff --git a/Teams/media/acm-add-modify-access.png b/Teams/media/acm-add-modify-access.png index 85b4407ebe..891299f804 100644 Binary files a/Teams/media/acm-add-modify-access.png and b/Teams/media/acm-add-modify-access.png differ diff --git a/Teams/media/acm-manage-user-apps-tab.png b/Teams/media/acm-manage-user-apps-tab.png index f6a4cf3fc0..6983197a4a 100644 Binary files a/Teams/media/acm-manage-user-apps-tab.png and b/Teams/media/acm-manage-user-apps-tab.png differ diff --git a/Teams/media/acm-org-wide-app-settings.png b/Teams/media/acm-org-wide-app-settings.png index 29023d64d0..2c82d3c35c 100644 Binary files a/Teams/media/acm-org-wide-app-settings.png and b/Teams/media/acm-org-wide-app-settings.png differ diff --git a/Teams/media/acm-remove-access-large.png b/Teams/media/acm-remove-access-large.png new file mode 100644 index 0000000000..3b10be63b5 Binary files /dev/null and b/Teams/media/acm-remove-access-large.png differ diff --git a/Teams/media/acm-remove-access.png b/Teams/media/acm-remove-access.png index 3b10be63b5..80b1a61752 100644 Binary files a/Teams/media/acm-remove-access.png and b/Teams/media/acm-remove-access.png differ diff --git a/Teams/media/meeting-privacy-statement-configure.png b/Teams/media/meeting-privacy-statement-configure.png new file mode 100644 index 0000000000..a3dcf30144 Binary files /dev/null and b/Teams/media/meeting-privacy-statement-configure.png differ diff --git a/Teams/media/meeting-privacy-statement-experience.png b/Teams/media/meeting-privacy-statement-experience.png new file mode 100644 index 0000000000..67dfce6e95 Binary files /dev/null and b/Teams/media/meeting-privacy-statement-experience.png differ diff --git a/Teams/media/mtr-devices/dual-for-qr.png b/Teams/media/mtr-devices/dual-for-qr.png new file mode 100644 index 0000000000..3af23cdc27 Binary files /dev/null and b/Teams/media/mtr-devices/dual-for-qr.png differ diff --git a/Teams/media/mtr-devices/mtrw-console-qr.png b/Teams/media/mtr-devices/mtrw-console-qr.png new file mode 100644 index 0000000000..c8326c225a Binary files /dev/null and b/Teams/media/mtr-devices/mtrw-console-qr.png differ diff --git a/Teams/media/mtr-devices/mtrw-for-qr-16x9.png b/Teams/media/mtr-devices/mtrw-for-qr-16x9.png new file mode 100644 index 0000000000..a90e948c85 Binary files /dev/null and b/Teams/media/mtr-devices/mtrw-for-qr-16x9.png differ diff --git a/Teams/media/mtr-devices/mtrw-for-qr-21x9.png b/Teams/media/mtr-devices/mtrw-for-qr-21x9.png new file mode 100644 index 0000000000..b2450139bf Binary files /dev/null and b/Teams/media/mtr-devices/mtrw-for-qr-21x9.png differ diff --git a/Teams/media/mtr-devices/mtrw-touchboard-qr-16x9.png b/Teams/media/mtr-devices/mtrw-touchboard-qr-16x9.png new file mode 100644 index 0000000000..3054bd317c Binary files /dev/null and b/Teams/media/mtr-devices/mtrw-touchboard-qr-16x9.png differ diff --git a/Teams/media/mtr-devices/mtrw-touchboard-qr-3x2.png b/Teams/media/mtr-devices/mtrw-touchboard-qr-3x2.png new file mode 100644 index 0000000000..3af6a6574d Binary files /dev/null and b/Teams/media/mtr-devices/mtrw-touchboard-qr-3x2.png differ diff --git a/Teams/meeting-privacy-statement.md b/Teams/meeting-privacy-statement.md new file mode 100644 index 0000000000..c471a98023 --- /dev/null +++ b/Teams/meeting-privacy-statement.md @@ -0,0 +1,48 @@ +--- +title: Customize and display your privacy statement in the meeting join experience +author: lana-chin +ms.author: v-chinlana +manager: jtremper +ms.topic: conceptual +ms.service: msteams +ms.reviewer: revathim +ms.date: 04/05/2024 +search.appverid: MET150 +searchScope: + - Microsoft Teams +audience: admin +description: Learn how to customize and display a link to your organization's privacy statement in the Teams meeting join experience. +ms.localizationpriority: medium +ms.collection: +- M365-collaboration +- m365-frontline +- m365initiative-meetings +- m365-virtual-appointments +appliesto: + - Microsoft Teams +--- + +# Customize and display your privacy statement in the meeting join experience + +**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls + +Microsoft Teams enables businesses to schedule and conduct business-to-customer engagements with customers, clients, and other people outside your organization, as well as with employees within your organization. Organizations have a need to make their privacy statement available to attendees when they join a meeting, especially in engagements with external participants. + +You can customize and display a link to your organization's privacy statement in the Teams meeting join experience to ensure attendees are aware of your organization's privacy guidelines before they join a meeting. + +## Set your organization's privacy statement + +Tenant admins can configure your organization's privacy statement in the Microsoft 365 admin center. + +1. In the left navigation of the Microsoft 365 admin center, go to **Settings** > **Org Settings**, and then select the **Security & privacy** tab. +1. Choose **Privacy profile**. + :::image type="content" source="media/meeting-privacy-statement-configure.png" alt-text="Screenshot of the Privacy profile pane in the Microsoft 365 admin center, showing where to configure the privacy statement URL and privacy contact." lightbox="media/meeting-privacy-statement-configure.png"::: +1. Enter the URL of your organization's privacy statement and the email address of your privacy contact, and then select **Save**. + +## Meeting join experience + +After it's set up, the privacy statement link is shown to attendees in the lower-left corner of the meeting join experience. When external and internal attendees join using the Teams meeting link in their meeting invitation or from their Teams or Outlook calendar, they can go the privacy statement link to view your organization's privacy statement. + +:::image type="content" source="media/meeting-privacy-statement-experience.png" alt-text="Screenshot of the meeting join experience in Teams, showing the privacy statement link." lightbox="media/meeting-privacy-statement-experience.png"::: + +With this capability, organizations can ensure that a relevant privacy statement is available to external and internal attendees before they join a meeting. diff --git a/Teams/network-planner.md b/Teams/network-planner.md index 2771c6397b..24310b15ec 100644 --- a/Teams/network-planner.md +++ b/Teams/network-planner.md @@ -32,7 +32,7 @@ Network Planner is a new tool that is available in the Teams admin center. It ca Network planner allows you to: -- Create representations of your organization using sites and Microsoft recommended personas (office workers, remote workers, and Teams room system). +- Create representations of your organization using sites and Microsoft recommended personas (office workers, remote workers, and Teams Rooms System). > [!NOTE] > The recommended personas were developed based on data from Teams best use scenarios and typical usage patterns. However, you can create up to three custom personas in addition to the three recommended personas. diff --git a/Teams/new-teams-known-issues.md b/Teams/new-teams-known-issues.md index fc9d0b54f6..1bacbb2255 100644 --- a/Teams/new-teams-known-issues.md +++ b/Teams/new-teams-known-issues.md @@ -38,6 +38,7 @@ ms.localizationpriority: high - When editing a TLE on the web, users can't use the **Manage live event resources** link at the bottom of the page. Selecting the link redirects the user to a different page. Resources for the event, can be found at the top of the page. - The **Manage live event resources** link in the calendar invite doesn't work outside of Teams. Users must open the invite in Teams calendar to edit the session and access event resources. - If a user closes a TLE session on the web, the next time they open Teams on the web, Teams might try and relaunch the last TLE event the user was in. +- The app will crash on startup with the error APPLICATION_FAULT_c06d007e_PvDSSource64.ax if the Pleora Technologies eBUS SDK is installed. Update to the latest version of the SDK or uninstall. ## Issues specifically for the new Microsoft Teams for Education diff --git a/Teams/new-teams-vdi-requirements-deploy.md b/Teams/new-teams-vdi-requirements-deploy.md index 99f6a8a9c2..4170f9c485 100644 --- a/Teams/new-teams-vdi-requirements-deploy.md +++ b/Teams/new-teams-vdi-requirements-deploy.md @@ -180,7 +180,7 @@ If IT administrators set restrictions for MSIX or deploy GPOs, it could prevent :::image type="content" source="media/new-teams-troubleshooting-error-isntallation-org-policies.png" alt-text="error with org policies"::: > [!IMPORTANT] -> The 'side by side' method is only supported in persistent environments. +> The 'side by side' method is only supported in persistent environments. Classic Teams 1.7.00.7956 or higher will suppress the app switcher toggle irrespective of the Teams Admin Center policy value when classic Teams is running in a non-persistent environment, where non-persistent is detected based on the installation folder of classic Teams MSI, C:\Program Files (x86). ## Classic Teams versus new Teams installers in VDI environments @@ -223,7 +223,6 @@ Known limitations: - Classic Teams on Windows Server 2019 isn't displaying the app switcher toggle if Classic Teams version is lower than 1.6.00.33567 - New Teams on Windows Server 2019 currently isn't compatible with FSLogix and fails to launch. See [FSLogix known issues](/fslogix/troubleshooting-known-issues) for more details. -- New Teams MSIX installer isn't registering UC Typelib, causing Outlook presence bubbles to show as grey/unknown even if the virtual machine does have the Classic Teams client installed as well. ### Outlook presence integration with New Teams in Windows Server 2019 @@ -269,17 +268,31 @@ Value: 1 All the user settings and configurations are now stored in: - C:\Users\\\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\ +- C:\Users\\\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\Settings\settings.dat - C:\Users\\\AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\app_switcher_settings.json - C:\Users\\\AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\tma_settings.json Make sure these folders and files are persisted for proper Teams functioning. +> [!NOTE] +> It's critical that **all** the necessary directories and top folder structure under AppData\Local\Packages\MSTeams_8wekyb3d8bbwe are correctly set up as directories, not as files or reparse points: +> +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\AC +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\AppData +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalState +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\RoamingState +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\Settings +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\SystemAppData +> AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\TempState + **TeamsSharedConfig** stores user configurations for the Teams app switcher toggle (and what should be the default app, the Classic or New Teams), and the Teams Meeting Add In for Outlook. The folder "meeting-addin" under TeamsSharedConfig shouldn't be persisted, as this could cause issues with the default meeting coordinates in the meeting templates inserted into Outlook. >[!Important] >Customers using FSLogix need to install hotfix [2.9.8784.63912](/fslogix/overview-release-notes#fslogix-2210-hotfix-3-29878463912) in order to guarantee proper integration with the new Teams client in VDI. The hotfix addresses the following issues: +> >- In non-persistent multiuser environments, the new Teams can become unregistered for some users after a new Teams update >- During user sign out, new Teams client user data/cache located in %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache **was not saved** in the FSLogix Profile or ODFC containers. > @@ -452,9 +465,11 @@ Learn more: [Manage accounts and organizations in Microsoft Teams](https://suppo ## Features currently not available in VDI with the new Teams -- Screen sharing from chat for Azure Virtual Desktops/Windows 365. -- Screen sharing from chat for Citrix. +- Screen sharing from chat for Azure Virtual Desktops/Windows 365 (This issue is now fixed on RD Client 1.2.5105 and Redirector Service +[1.50.2402.29001](/azure/virtual-desktop/whats-new-webrtc#updates-for-version-150240229001)). +- Screen sharing from chat for Citrix when using Workspace app 2311 only. - The app switcher toggle isn't shown in new Teams if the virtual machine has the machine-wide classic Teams installed (MSI with ALLUSERS=1). **Note:** This issue is fixed on new Teams version 23320.3021.2567.4799 or higher. +- msteams_autostart.exe "The parameter is incorrect": In non-persistent environments that use FSLogix (any version) or Citrix Profile Manager profile containers, when new Teams attempts to autostart or a user tries to launch Teams from the Start menu, it throws the error: "The parameter is incorrect." The frequency and reproducibility of the error varies depending on the environment and especially the antivirus software being used (SentinelOne, Palo Alto, Trend Micro, Bitdefender, CrowdStrike, and so on.) and exclusions in place. >[!Note] >Microsoft is working on a solution and plan to remove these limitations soon. diff --git a/Teams/new-teams-web.md b/Teams/new-teams-web.md index 551cdadcf8..72fba57d98 100644 --- a/Teams/new-teams-web.md +++ b/Teams/new-teams-web.md @@ -41,11 +41,9 @@ General availability of New Teams for Web for Chrome and Microsoft Edge was anno ### Availability on Firefox and Safari browsers, and Linux -|Date |Availability | -|:-----------------|:----------------------------------------------------------------------------------------------------| -|1st Quarter, 2024 |
  • New Teams for Web on Firefox browser on Windows, macOS, and Linux
  • New Teams for Web on Safari browser on macOS
  • Microsoft Edge and Chrome browsers with Progressive Web App (PWA) support on Linux
| - -More-specific dates and details for Firefox, Safari, and PWA on Linux will be shared at a later date. +|Date |Availability | +|:------------------------------|:----------------------------------------------------------------------------------------------------| +|April 1 through April 15, 2024 |
  • New Teams for Web is currently rolling out to general audiences for these clients:
  • New Teams for Web on Firefox browser on Windows, macOS, and Linux
  • New Teams for Web on Safari browser on macOS
  • Microsoft Edge and Chrome browsers with Progressive Web App (PWA) support on Linux
| ## How to try new Teams: App Switcher diff --git a/Teams/new-teams-whats-changing.md b/Teams/new-teams-whats-changing.md index e93a272063..c0f1255468 100644 --- a/Teams/new-teams-whats-changing.md +++ b/Teams/new-teams-whats-changing.md @@ -51,3 +51,4 @@ As we improved the client, the experience also improved to align with similar fe |Ability to sign out from the notification area at the far right of the taskbar (system tray). |No longer available.| |Adaptive Card-based tabs in personal app tabs.|No longer available.| |Whiteboard Tab automatically displayed in meeting tabs.|Using Recap tab from the calendar allows you to access the Whiteboard file shared in the meeting in the content section.| +|Third-party and custom sign-in solutions using RunAs or undocumented hooks.|No longer available.| diff --git a/Teams/privacy/intelligent-recap.md b/Teams/privacy/intelligent-recap.md index da2b2552ac..7f54ff8a6c 100644 --- a/Teams/privacy/intelligent-recap.md +++ b/Teams/privacy/intelligent-recap.md @@ -50,7 +50,7 @@ Customer data isn‘t logged or used for any AI model training or testing. Intelligent recap automatically inherits your organization’s security, compliance, and privacy policies for Microsoft Teams. -Intelligent recap abides by Microsoft’s commitments to data security and privacy in the enterprise. Data is managed in accordance with our current commitments, while the existing compliance boundaries and privacy protections make intelligent recap the AI solution you can trust. For more information, see [Privacy and Microsoft Teams](teams-privacy.md) and [regional and country compliance information on the Microsoft Trust Center](https://www.microsoft.com/trust-center/compliance/regional-country-compliance). +Intelligent recap abides by Microsoft’s commitments to data security and privacy in the enterprise. Data is managed in accordance with our current commitments, while the existing compliance boundaries and privacy protections make intelligent recap the AI solution you can trust. For more information, see [regional and country compliance information on the Microsoft Trust Center](https://www.microsoft.com/trust-center/compliance/regional-country-compliance). Intelligent recap also abides by Microsoft’s commitments to data residency in the enterprise. Data in Teams resides in the geographic region associated with your Microsoft 365 (or Office 365) organization. Intelligent recap is also [multi-geo](/microsoft-365/enterprise/microsoft-365-multi-geo) capable, for tenants that span multiple geographic locations. To review Microsoft’s data residency policy and documentation, see [Data Residency Overview and Definitions](/microsoft-365/enterprise/m365-dr-overview). diff --git a/Teams/privacy/teams-privacy-oce-overview.md b/Teams/privacy/teams-privacy-oce-overview.md index 7b49cc0946..06dc6ed418 100644 --- a/Teams/privacy/teams-privacy-oce-overview.md +++ b/Teams/privacy/teams-privacy-oce-overview.md @@ -58,7 +58,6 @@ The URL Preview service automatically generates a preview snippet and attaches u ## Related articles - [Overview of policy controls for Teams](policy-control-overview.md) -- [Privacy and Microsoft Teams](teams-privacy.md) - [Overview of optional connected experiences in Office](/deployoffice/privacy/optional-connected-experiences) - [Required service data for Office](/deployoffice/privacy/required-service-data) - [Account Privacy Settings](https://support.microsoft.com/office/3e7bc183-bf52-4fd0-8e6b-78978f7f121b) diff --git a/Teams/privacy/teams-privacy.md b/Teams/privacy/teams-privacy.md deleted file mode 100644 index ecbb695b07..0000000000 --- a/Teams/privacy/teams-privacy.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Microsoft Teams Privacy -ms.author: danbrown -author: DHB-MSFT -manager: laurawi -ms.topic: reference -ms.service: msteams -audience: admin -ms.reviewer: stbyer -ms.date: 04/14/2020 -description: Privacy guidance and information for Microsoft Teams. -ms.localizationpriority: high -search.appverid: MET150 -f1.keywords: -- NOCSH -ms.collection: - - M365-collaboration - - essentials-privacy - - privacy-teams -appliesto: - - Microsoft Teams ---- - -# Privacy and Microsoft Teams - -When an organization is considering relying on Microsoft Teams for communication and collaboration, privacy is something that needs to be addressed at every level. The topics we discuss in this article should address your privacy concerns when planning your Teams implementation, or at any point during Teams usage. - -## What personal data does Microsoft Teams collect and for what purposes does Microsoft Teams use this data? - -Microsoft processes the personal data in Microsoft Teams to deliver the agreed-upon services defined in the [Online Services Terms](https://go.microsoft.com/fwlink/p/?linkid=2050263) and for the purposes determined by the data controller obtaining the service. Microsoft Teams, as a cloud-based service, processes various types of personal data as part of delivering the service. This personal data includes: - -- **Content** Your meetings and conversations chats, voicemail, shared files, recordings, and transcriptions. -- **Profile Data** Data that is shared within your company about you. Examples include your E-mail address, profile picture, and phone number. -- **Call History** A detailed history of the phone calls you make, which allows you to go back and review your own call records. -- **Call Quality data** Details of meetings and call data are available to your system administrators, which allows your administrators to diagnose issues related to poor call quality and service usage. -- **Support/Feedback data** Information related to troubleshooting tickets or feedback submission to Microsoft. -- **Diagnostic and service data** Diagnostic data related to service usage. This personal data allows Microsoft to deliver the service (troubleshoot, secure, and update the product and monitor performance) as well as perform some internal business operations, such as: - - Determine revenue - - Develop metrics - - Determine service usage - - Conduct product and capacity planning - -To the extent Microsoft Teams processes personal data with Microsoft's legitimate business operations, Microsoft is an independent data controller for such use and is responsible for complying with all applicable laws and controller obligations. - -## Legal Basis of Processing - -Our customers are controllers for the data provided to Microsoft, as set forth in the [Online Services Terms](https://go.microsoft.com/fwlink/p/?linkid=2050263), and they determine legal bases of processing. Microsoft, in turn, processes the data on the customers' instructions, as a processor. - -To the extent Microsoft processes personal data with its own legitimate business operations, as described in the [Online Services Terms](https://go.microsoft.com/fwlink/p/?linkid=2050263), Microsoft is an independent controller for such processing, the legal basis of which is legitimate interests. "Microsoft's legitimate business operations" consist of the following, each as incident to delivery of Microsoft Teams to the customer: (1) billing and account management; (2) compensation (for example, calculating employee commissions and partner incentives); (3) internal reporting and modeling (for example, forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, cybercrime, or cyber-attacks that may affect Microsoft or Microsoft Products; (5) improving the core functionality of accessibility, privacy, or energy-efficiency; and (6) financial reporting and compliance with legal obligations. - -## What third parties have access to personal data? - -Microsoft won't disclose personal data except: - -1. as the customer directs (including as required to complete phone calls); -1. as described in the Online Service Terms (such as the use of authorized subcontractors to provide certain components of services); -1. as required by law. - -If law enforcement contacts Microsoft with a demand, Microsoft will attempt to redirect the law enforcement agency to request that personal data directly from the customer. If compelled to disclose personal data to law enforcement, Microsoft will promptly notify the customer and provide a copy of the demand unless legally prohibited from doing so. For more information about data that we disclose in response to requests from law enforcement and other government agencies, please see our [Law Enforcement Requests Report](https://www.microsoft.com/corporate-responsibility/law-enforcement-requests-report). - -The [Teams Security Guide](../security-compliance-overview.md#compliance-standards) has more information about our compliance standards. - -## Where does Teams transfer and store personal data? - -Personal data is transferred and stored as set forth in the [Online Service Terms](https://go.microsoft.com/fwlink/p/?linkid=2050263). - -For transfers of personal data from the EEA, EU, Switzerland, and the UK, Microsoft is certified to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks and the commitments they entail, although Microsoft does not rely on the EU-U.S. Privacy Shield Framework as a legal basis for transfers of Personal Data in light of the judgment of the Court of Justice of the EU in Case C-311/18. - -We have information on the [Location of data in Microsoft Teams](location-of-data-in-teams.md) if you need to learn more. - -## How long does Microsoft Teams retain personal data? - -Microsoft Teams retains your data for the minimum amount of time necessary to deliver the service. - -Because this data is required to provide the service, this typically means that we retain personal data until the user stops using Microsoft Teams, or until the user deletes personal data. If a user (or an administrator on the user's behalf) deletes the data, Microsoft will ensure that all copies of the personal data are deleted within 30 days. - -If a company terminates service with Microsoft, corresponding personal data will all be deleted between 90 and 180 days of service termination. - -In some circumstances, local laws require that Microsoft Teams retains telephone records (for billing purposes) for a specific period of time, in those circumstances Microsoft Teams follows the law for each region. - -Additionally, if a company requests that Microsoft Teams holds a user's data to support a legal obligation, Microsoft will respect the company administrator's request. - -### Right to withdraw consent - -If Microsoft Teams processes any personal data based on consent, you may have the right to withdraw your consent at any time. You should direct your request to withdraw consent to your administrator, where your administrator is the controller of the personal data at issue. - -## Contact Details of Microsoft's Data Protection Officer - -If you have a privacy concern, complaint or question for the Microsoft Chief Privacy Officer and EU Data Protection Officer, please contact us by using [our web form](https://go.microsoft.com/fwlink/?LinkId=321116). Our EU Data Protection Officer is located at Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland. Telephone: +353 1 706 3117. You can also raise a concern or lodge a complaint with a data protection authority or other official with jurisdiction. diff --git a/Teams/rooms/android-app-firmware.md b/Teams/rooms/android-app-firmware.md index 7f5d84cce8..0eb2a9fa42 100644 --- a/Teams/rooms/android-app-firmware.md +++ b/Teams/rooms/android-app-firmware.md @@ -49,6 +49,14 @@ The following are the latest firmware versions released via Microsoft Teams Admi | Device model | Latest Firmware version | Minimum Firmware version required| Teams client | Company Portal | Admin Agent | Release date | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| Cisco Board Pro 55 | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product` | April 01, 2024| +| Cisco Board Pro 75 | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product` | April 01, 2024| +| Cisco Room Bar | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product` | April 01, 2024| +| Cisco Room Kit Pro | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product`| April 01, 2024| +| Cisco Desk Pro | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product` | April 01, 2024| +| Cisco Room Bar Pro | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product` | April 01, 2024| +| Cisco Room Kit EQ | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product` | April 01, 2024| +| Cisco Navigator | `11.14.1.5` | N/A | `1449/1.0.96.2024020802` | `5.0.6061.0` | `1.0.0.202310260109.product` | April 01, 2024| | Cisco Board Pro 55 | `11.11.1.10` | N/A | `1449/1.0.96.2023111001` | `5.0.6061.0` | `1.0.0.202310260109.product` | January 25, 2024| | Cisco Board Pro 75 | `11.11.1.10` | N/A | `1449/1.0.96.2023111001` | `5.0.6061.0` | `1.0.0.202310260109.product` | January 25, 2024| | Cisco Room Bar | `11.11.1.10` | N/A | `1449/1.0.96.2023111001` | `5.0.6061.0` | `1.0.0.202310260109.product` | January 25, 2024| diff --git a/Teams/rooms/autopilot-autologin.md b/Teams/rooms/autopilot-autologin.md index 7ae692b583..060c50e7c7 100644 --- a/Teams/rooms/autopilot-autologin.md +++ b/Teams/rooms/autopilot-autologin.md @@ -1,5 +1,5 @@ --- -title: Use AutoPilot and Autologin to easily deploy Microsoft Teams Rooms consoles +title: Use Autopilot and Autologin to easily deploy Microsoft Teams Rooms consoles author: tonysmit ms.author: tonysmit manager: pamgreen @@ -17,23 +17,23 @@ appliesto: - Microsoft Teams ms.localizationpriority: medium search.appverid: MET150 -description: Learn how to set up and use the AutoPilot and Autologin features to deploy and provisioning Microsoft Teams Rooms on Windows consoles in your organization. +description: Learn how to set up and use the Autopilot and Autologin features to deploy and provisioning Microsoft Teams Rooms on Windows consoles in your organization. --- -# AutoPilot and Autologin for Teams Rooms on Windows +# Autopilot and Autologin for Teams Rooms on Windows -You can use Windows AutoPilot and Autologin to deploy, provision, reset, redeploy, and recover Teams Rooms on Microsoft Teams Rooms on Windows consoles in your organization. +You can use Windows Autopilot and Autologin to deploy, provision, reset, redeploy, and recover Teams Rooms on Microsoft Teams Rooms on Windows consoles in your organization. -Windows AutoPilot with Autologin for Teams Rooms simplifies and accelerates the on-site deployment time for Teams Rooms consoles running Windows. The combination of these technologies removes the need for direct interaction with the Teams Rooms console during provisioning and deployment. Using AutoPilot and Autologin, there isn't a need for someone to physically interact with the Teams Room console to deploy it. +Windows Autopilot with Autologin for Teams Rooms simplifies and accelerates the on-site deployment time for Teams Rooms consoles running Windows. The combination of these technologies removes the need for direct interaction with the Teams Rooms console during provisioning and deployment. Using Autopilot and Autologin, there isn't a need for someone to physically interact with the Teams Room console to deploy it. Instead, the Teams Rooms console completes the Windows and Teams app installation automatically out-of-box. Once installation is complete, it then signs in to the Teams Room app without the need for someone to have physical access to the device. The combinations of these features greatly simplify the Teams Rooms console lifecycle, from its initial deployment to its end of life. ## Overview of steps -To use AutoPilot and Autologin to provision and deploy Microsoft Teams Rooms consoles in your organization, you must perform these tasks: +To use Autopilot and Autologin to provision and deploy Microsoft Teams Rooms consoles in your organization, you must perform these tasks: - Step 1: [Verify that all prerequisites are met](#step-1-prerequisites) -- Step 2: [Register devices as AutoPilot devices](#step-2-registering-teams-rooms-consoles-using-windows-autopilot) +- Step 2: [Register devices as Autopilot devices](#step-2-registering-teams-rooms-consoles-using-windows-autopilot) - Step 3: [Create a device group](#step-3-create-a-group-for-the-teams-rooms-consoles) - Step 4: [Deploy Teams Rooms app update tool](#step-4-deploy-teams-room-app-update-tool) - Step 5: [Create an Enrollment Status Page (ESP) profile](#step-5-create-an-autopilot-enrollment-status-page-esp-status-page-profile) @@ -46,28 +46,29 @@ To use AutoPilot and Autologin to provision and deploy Microsoft Teams Rooms con To successfully deploy Microsoft Teams Rooms consoles, verify that these prerequisites are met. -1. You must buy enough Teams Rooms Pro licenses for each of the consoles you're provisioning and deploying. Teams Rooms Pro licenses include the correct Intune and Microsoft Entra ID P1 licenses. To see more information on the licensing requirements for AutoPilot, see [AutoPilot licensing requirements](/autopilot/licensing-requirements). +1. You must buy enough Teams Rooms Pro licenses for each of the consoles you're provisioning and deploying. Teams Rooms Pro licenses include the correct Intune and Microsoft Entra ID P1 licenses. To see more information on the licensing requirements for Autopilot, see [Autopilot licensing requirements](/autopilot/licensing-requirements). 2. You must verify the account you're using to deploy the consoles has the correct permissions. 1. For Intune, verify that the account has the Intune Administrator or Policy and Profile Manager permissions, see [Learn more](/autopilot/add-devices#required-permissions). 1. For the Teams Management Pro portal, the account has the Teams Rooms Pro Manager permissions. 3. You must [Set up Windows automatic Intune enrollment](/autopilot/tutorial/self-deploying/self-deploying-automatic-enrollment#set-up-windows-automatic-intune-enrollment). -4. You must create and set up the required resource accounts. See, [Create a resource account](/microsoftteams/rooms/create-resource-account). -5. You must be only deploying Microsoft Teams Rooms on Windows consoles. See, [Teams Rooms Windows support](/microsoftteams/rooms/rooms-lifecycle-support). +4. You must Microsoft Entra join devices. Autopilot self-deploying mode is not supported for Microsoft Entra hybrid join devices. +5. You must create and set up the required resource accounts. See, [Create a resource account](/microsoftteams/rooms/create-resource-account). +6. You must be only deploying Microsoft Teams Rooms on Windows consoles with Windows 11 installed. See, [Teams Rooms Windows support](/microsoftteams/rooms/rooms-lifecycle-support). ## Step 2: Registering Teams Rooms consoles using Windows Autopilot -To register your Teams Rooms consoles for your organization, you can use Windows Autopilot device registration to collect the hardware identity of your consoles using hardware hashes and having this information in a comma-separated-values (CSV) file, and the uploading it to Intune. See [Register devices as AutoPilot +To register your Teams Rooms consoles for your organization, you can use Windows Autopilot device registration to collect the hardware identity of your consoles using hardware hashes and having this information in a comma-separated-values (CSV) file, and the uploading it to Intune. See [Register devices as Autopilot devices](/autopilot/tutorial/self-deploying/self-deploying-register-device). > [!IMPORTANT] > For Teams Rooms on Windows consoles, it is required that the GroupTag has the prefix **MTR-ConsoleName**. You can easily do this by adding the GroupTag to the .csv file described [here](/autopilot/add-devices#ensure-that-the-csv-file-meets-requirements) or entering the prefix and console name in the **Group name** field by adding it using the Microsoft Partner Center. -This GroupTag field is critical for the Teams Pro Management portal so it can tell the difference between the Teams Rooms consoles and other devices that are registered with Windows AutoPilot. The GroupTag field is also useful when you're using dynamic device groups. +This GroupTag field is critical for the Teams Pro Management portal so it can tell the difference between the Teams Rooms consoles and other devices that are registered with Windows Autopilot. The GroupTag field is also useful when you're using dynamic device groups. > [!Note] -> To test AutoPilot, you can manually register AutoPilot devices in Intune. You can do this several different ways, see [Manually register devices with Windows Autopilot](/autopilot/add-devices). +> To test Autopilot, you can manually register Autopilot devices in Intune. You can do this several different ways, see [Manually register devices with Windows Autopilot](/autopilot/add-devices). ## Step 3: Create a group for the Teams Rooms consoles @@ -76,7 +77,7 @@ To create a Teams Rooms on Windows consoles device group, see [Create a device g > [!Note] > Intune's **Group Tag** field is the same as the **OrderID** attribute on Microsoft Entra devices. -To create a dynamic device group that includes all of the Teams Rooms consoles to use AutoPilot, use the following query: +To create a dynamic device group that includes all of the Teams Rooms consoles to use Autopilot, use the following query: ```odata (device.devicePhysicalIds -any _ -startswith"[OrderID]:MTR-") @@ -84,9 +85,9 @@ To create a dynamic device group that includes all of the Teams Rooms consoles t ## Step 4: Deploy Teams Room app update tool -The Teams Rooms app update tool updates the Teams room app running on the device to a version that supports AutoPilot and Autologin. The update tool needs to be first downloaded, then uploaded to Intune, and deployed to the Teams Rooms on Windows consoles. Although it's not required, use dynamic device groups. During the AutoPilot Enrollment Status Page (ESP), Intune installs the update tool to the Teams Rooms console and updates the Teams room app before it starts. +The Teams Rooms app update tool updates the Teams room app running on the device to a version that supports Autopilot and Autologin. The update tool needs to be first downloaded, then uploaded to Intune, and deployed to the Teams Rooms on Windows consoles. Although it's not required, use dynamic device groups. During the Autopilot Enrollment Status Page (ESP), Intune installs the update tool to the Teams Rooms console and updates the Teams room app before it starts. -Going through these steps enables Intune to push the update tool to the Teams Rooms enrolling through AutoPilot. The update tool then automatically updates the Teams app on the console so it can automatically log in. +Going through these steps enables Intune to push the update tool to the Teams Rooms enrolling through Autopilot. The update tool then automatically updates the Teams app on the console so it can automatically log in. To deploy the Teams Rooms app update tool to your consoles: @@ -110,14 +111,14 @@ To deploy the Teams Rooms app update tool to your consoles: 9. Under **Dependencies**, select **Next**. 10. Under **Supersedence**, select **Next**. 11. Under **Assignments**, select **Add group**. -12. Under the **Required** section, in the **Select groups** detail pane, choose the group created for the Microsoft Teams Rooms consoles being deployed with Windows AutoPilot. Select **Next**. +12. Under the **Required** section, in the **Select groups** detail pane, choose the group created for the Microsoft Teams Rooms consoles being deployed with Windows Autopilot. Select **Next**. 13. On the **Review + create** page, review your settings. If everything is set correctly, select **Create**. For more information on Win32 app deployment in Intune, see [Add and assign Win32 apps to Microsoft Intune](/mem/intune/apps/apps-win32-add#add-a-win32-app-to-intune). -## Step 5: Create an AutoPilot Enrollment Status Page (ESP) status page profile +## Step 5: Create an Autopilot Enrollment Status Page (ESP) status page profile -To create an enrollment status page profile for your Teams Room on Windows consoles, see [Configure and assign AutoPilot Enrollment Status Page (ESP)](/autopilot/tutorial/self-deploying/self-deploying-esp). +To create an enrollment status page profile for your Teams Room on Windows consoles, see [Configure and assign Autopilot Enrollment Status Page (ESP)](/autopilot/tutorial/self-deploying/self-deploying-esp). The required settings for ESP on Teams Rooms are: @@ -139,12 +140,12 @@ Under **Blocking apps**, select the Microsoft Teams Rooms Pro Provisioning (MTRP Then assign the ESP to the device group you created in [Step 3](#step-3-create-a-group-for-the-teams-rooms-consoles). -## Step 6: Create an AutoPilot profile +## Step 6: Create an Autopilot profile For the Teams Rooms consoles, you must create a Self-deploying Autopilot profile. See [Create and assign Autopilot profile](/autopilot/tutorial/self-deploying/self-deploying-autopilot-profile). -Then assign the AutoPilot profile to the previously created device group in [Step 3](#step-3-create-a-group-for-the-teams-rooms-consoles). +Then assign the Autopilot profile to the previously created device group in [Step 3](#step-3-create-a-group-for-the-teams-rooms-consoles). ## Step 7: Create and assign a Local Administrator Password Solution (LAPS) policy @@ -154,18 +155,18 @@ To set up and configure a LAPS policy, see [LAPS authentication on Teams Rooms w ## Step 8: Set up Autologin in the Teams Rooms Pro Management portal -After the Endpoint Manager portal configuration is complete, you must assign the resource accounts for the consoles listed as AutoPilot devices that let the Teams Rooms consoles automatically log in when they're deployed. +After the Endpoint Manager portal configuration is complete, you must assign the resource accounts for the consoles listed as Autopilot devices that let the Teams Rooms consoles automatically log in when they're deployed. > [!IMPORTANT] > Only Teams Rooms consoles that are running Windows 11 will be able to Autologin. Windows 10 devices aren't currently supported. 1. Go to the Microsoft Teams Rooms Pro Management portal and sign in. -2. In the left navigation of the Microsoft Teams Rooms Pro Management portal, go to **Planning > AutoPilot devices**. +2. In the left navigation of the Microsoft Teams Rooms Pro Management portal, go to **Planning > Autopilot devices**. -3. On the **Windows AutoPilot devices** page, select **Sync** to populate the device list. +3. On the **Windows Autopilot devices** page, select **Sync** to populate the device list. -To assign an account to an AutoPilot device, the device must have an AutoPilot profile assigned. You can see the devices in the **Profile assignment status** column and they should be listed as **Assigned**. +To assign an account to an Autopilot device, the device must have an Autopilot profile assigned. You can see the devices in the **Profile assignment status** column and they should be listed as **Assigned**. 1. Select a device from the list. 2. Select **Assign account**. @@ -178,7 +179,7 @@ To assign an account to an AutoPilot device, the device must have an AutoPilot p > [!Note] > Generate password requires Exchange Admin privileges to work. This option won't work with Hybrid resource accounts. -6. On the **Review** page, select **Finish** to link the resource account to AutoPilot device. +6. On the **Review** page, select **Finish** to link the resource account to Autopilot device. When the console is ready to be provisioned, the **Provisioning status** shows as **Ready**. @@ -195,13 +196,13 @@ When you take the console out of the box: **Autologin if you are resetting a Teams Room** -When resetting a Teams Room for AutoPilot and Autologin, verify there's a resource account assigned to the AutoPilot device with the **Provisioning status** showing as **Ready**. If the status is **Consumed**, you must reassign the resource account to the AutoPilot device for the console you're resetting. +When resetting a Teams Room for Autopilot and Autologin, verify there's a resource account assigned to the Autopilot device with the **Provisioning status** showing as **Ready**. If the status is **Consumed**, you must reassign the resource account to the Autopilot device for the console you're resetting. ## Step 9: Deploy the Teams Rooms console -Once all the configuration steps for Windows AutoPilot self-deploying deployment and Autologin are completed, the next step is to start the deployment process for the console. +Once all the configuration steps for Windows Autopilot self-deploying deployment and Autologin are completed, the next step is to start the deployment process for the console. -To start the AutoPilot deployment process on the console that is AutopAutoPilotilot registered and has a resource account assigned. +To start the Autopilot deployment process on the console that is Autopilot registered and has a resource account assigned. 1. If a wired network connection is available, connect the device to the wired network connection. 2. Turn on the device. @@ -210,7 +211,7 @@ To start the AutoPilot deployment process on the console that is AutopAutoPiloti > [!IMPORTANT] > Connectivity to the Internet is required. - - If the device is connected to a wired network, the device may reboot to apply critical security updates if they're available. After the reboot to apply critical security updates, the AutoPilot process begins. + - If the device is connected to a wired network, the device may reboot to apply critical security updates if they're available. After the reboot to apply critical security updates, the Autopilot process begins. - If the device isn't connected to a wired network or if it doesn't have network connectivity, it prompts you to connect to a network. @@ -219,7 +220,7 @@ To start the AutoPilot deployment process on the console that is AutopAutoPiloti 1. The keyboard screen appears to select a keyboard layout. Select the appropriate keyboard layout, and then select **Yes**. If needed, you can select additional keyboard layouts by selecting **Add layout**, or select **Skip** if you don't want to add additional keyboard layouts. > [!Note] - > When there's no network connectivity, the device can't downloaded the AutoPilot profile to identify the country/region and keyboard settings to use. This is why when there's no network connectivity, the country/region and keyboard screens appear and must be set to hidden in the AutoPilot profile. These settings need to be set in order for the network connectivity screensto work properly. + > When there's no network connectivity, the device can't download the Autopilot profile to identify the country/region and keyboard settings to use. This is why when there's no network connectivity, the country/region and keyboard screens appear and must be set to hidden in the Autopilot profile. These settings need to be set for the network connectivity screensto work properly. 1. The **Let's connect you to a network** screen appears. At this screen, either plug the device into a wired network (if available), or select and connect to a wireless Wi-Fi network. @@ -237,16 +238,22 @@ To start the AutoPilot deployment process on the console that is AutopAutoPiloti > [!Note] > User ESP and **Account setup** aren't recommended for Teams Rooms deployments. -5. During **Device setup** the Teams Rooms app update tool runs and updates the Teams app. When the device ESP process completes, the Windows AutoPilot self-deploying deployment is complete, and the Teams Rooms Out-of-box experience starts. +5. During **Device setup** the Teams Rooms app update tool runs and updates the Teams app. When the device ESP process completes, the Windows Autopilot self-deploying deployment is complete, and the Teams Rooms Out-of-box experience starts. -6. The Teams Room app now detects the AutoPilot profile and initiates Autologin. The credentials for the resource account assigned to this AutoPilot device are used. When this part is complete, the console will automatically log in and is ready for Teams meetings. +6. The Teams Room app now detects the Autopilot profile and initiates Autologin. The credentials for the resource account assigned to this Autopilot device are used. When this part is complete, the console will automatically log in and is ready for Teams meetings. ## Frequently asked questions -**Question** Why aren't my AutoPilot devices syncing into the Teams Room Pro Management portal? +**Question** Why aren't my Autopilot devices syncing into the Teams Room Pro Management portal? -**Answer** In the Teams Pro Management portal on the AutoPilot device page, select **Sync** to initiate an update to the device list. Check the "Last synced" time on the page to see if it corresponds to the time the last sync was initiated. If it isn't, check your Intune permissions. The user initiating the sync must have at least read permissions for the consoles in Intune. +**Answer** In the Teams Pro Management portal on the Autopilot device page, select **Sync** to initiate an update to the device list. Check the "Last synced" time on the page to see if it corresponds to the time the last sync was initiated. If devices are still not syncing, check that the GroupTag is configured correctly with the prefix **MTR-ConsoleName**. -**Question** Can I use AutoPilot to EntraID join the device into one tenant and manually log in the Teams Room app to a resource account from another tenant? +**Question** Why does the console not automatically login after resetting the console? + +**Answer** If the console has not completed Windows Autopilot provisioing before, a Windows reset is required. It is recommended to reset to a factory image. A simple reset initiated through the Teams app will not reset Windows. + +If the device succesfully completed Windows Autopilot provisioning and the Teams app fails to login, check the respective device in the Pro Management portal and verify the **Provisioing status** shows as **Ready**. + +**Question** Can I use Autopilot to EntraID join the device into one tenant and manually log in the Teams Room app to a resource account from another tenant? **Answer** No. Using EntraID to join the device isn't a supported scenario. When the console attempts to log in, it fails because the device is registered to a different domain than the resource account. diff --git a/Teams/rooms/certified-hardware.md b/Teams/rooms/certified-hardware.md index fbd381c0ef..c013b67702 100644 --- a/Teams/rooms/certified-hardware.md +++ b/Teams/rooms/certified-hardware.md @@ -140,7 +140,7 @@ The following devices are certified under the Microsoft Teams Rooms on Android C | Device model | Firmware version | Current certification end date | Room size | Android OS version | |:-|:-|:-|:-|:-| -| DTEN DCR200 Bar | `1.0.2` | October 4, 2026 | Medium size room (4.5 m x 4.5 m) | 12 | +| DTEN DCR200 Bar | `1.0.2` | October 4, 2026 | Small size room (4.5 m x 4.5 m) | 12 | | Cisco Room Kit EQX | `RoomOS11.15` | September 3, 2025 | Large Meeting Room (4.5m x 8.5 m)| 11 | | Cisco Board Pro G2 55 | `RoomOS11.15` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 11 | | Cisco Board Pro G2 75 | `RoomOS11.15` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 11 | diff --git a/Teams/rooms/create-otp.md b/Teams/rooms/create-otp.md index 78e4912cb7..a22a973b92 100644 --- a/Teams/rooms/create-otp.md +++ b/Teams/rooms/create-otp.md @@ -35,7 +35,7 @@ When someone is adding Microsoft Teams Rooms consoles to your organization, the To create a one-time password, perform the following steps: 1. Sign in to the Teams Rooms Pro Management portal. -1. On the left navigation pane, select **Planning > Resource accounts**. The **Resource accounts** page appears. +1. On the left navigation pane, select **Planning > Resource Accounts**. The **Resource Accounts** page appears. 1. Select **Generate OTP** wizard on the command bar. The **Account selection** page appears. @@ -50,9 +50,10 @@ To create a one-time password, perform the following steps: :::image type="content" source="../media//mtr-devices/configuration-screen.png" alt-text="Screenshot that shows the Configuration page." lightbox="../media/mtr-devices/configuration-screen.png"::: -1. Select **Automatically generate passwords for all selected accounts**. You'll select this option if you want to reset/delete the existing password for the resource accounts for which you're generating a one-time password. - OR -1. Select **Upload sign in data from CSV file**. You'll select this option if you want to retain the existing password for the resource accounts in which you're generating a one-time password. +1. Select if you would like to **Automatically generate passwords for all selected accounts** OR **Upload sign in data from CSV file**. + + 1. Select the **Automatically generate passwords for all selected accounts** option if you want to reset/delete the existing password for the resource accounts for which you're generating a one-time password. + 2. Select **Upload sign in data from CSV file** if you want to retain the existing password for the resource accounts in which you're generating a one-time password. 1. Select **Next**. The **Review** page appears. @@ -61,10 +62,9 @@ To create a one-time password, perform the following steps: 1. Review the settings you have configured, and then select **Generate**. > [!NOTE] - > On the **Review** page, if you want to edit the **Auto generate passwords** setting, select the **Edit** icon next to **Configuration**. Then, select **Generate**. + > On the **Review** page, if you want to edit the **Auto generate passwords** setting, select the **Edit** icon next to **Configuration** or if you want to change the resource accounts for which you want to create a one-time password, select the **Edit** icon next to **Account selection**. Then, select **Generate**. - > [!NOTE] - > On the **Review** page, if you want to change the resource accounts for which you want to create a one-time password, select the **Edit** icon next to **Account selection**. Then, select **Generate**. +1. Once you've generated the OTP you're presented with the option to download the OTPs with or without the resource account passwords so you can save this information and share it with whomever might be setting up your devices. ## Verify and approve/reject one-time password @@ -73,7 +73,7 @@ You can verify and approve a one-time password that was entered by the setup per To verify and approve a one-time password, do the following: 1. Sign in to the Teams Rooms Pro Management portal. -1. On the left navigation pane, select **Planning > Resource accounts**. The **Resource accounts** page appears. +1. On the left navigation pane, select **Planning > Resource Accounts**. The **Resource Accounts** page appears. 1. Select a resource account that has the value **Awaiting OTP Approval**. :::image type="content" source="../media/mtr-devices/resource-account-provisioning-status.png" alt-text="Screenshot that shows the page on which you select a resource account that has awaiting one-time password approval as its provisioning status." lightbox="../media/mtr-devices/resource-account-provisioning-status.png"::: @@ -92,3 +92,15 @@ To verify and approve a one-time password, do the following: :::image type="content" source="../media/mtr-devices/select-reason-for-rejection.png" alt-text="Screenshot that shows the page on which you choose the reason for rejecting the OTP request." lightbox="../media/mtr-devices/select-reason-for-rejection.png"::: 1. Select **Submit**. + +## Modify the one-time passcode expiration or enable OTP auto approval + +By default the OTP is valid for 8 hours, however you can adjust the validity period of the OTP to be up to 2 weeks (336 hours). You can also choose to automatically approve OTPs instead of needing to select the approve button as the IT admin. + +To change these settings: +1. Sign in to the Teams Rooms Pro Management portal. +2. In the left navigation pane, select **Planning > Resource Accounts**. The **Resource Accounts** page appears. +3. Select **Preferences** on the command bar. +4. Adjust the OTP expiration by selecting from the predefined hours or set a custom expiration (between 1 hour and 336 hours). +5. You can also toggle **OTP Auto approval** on or off. +6. Select **Save** when you're done to save your changes. diff --git a/Teams/rooms/custom-backgrounds.md b/Teams/rooms/custom-backgrounds.md index cd2640494a..440e5f2058 100644 --- a/Teams/rooms/custom-backgrounds.md +++ b/Teams/rooms/custom-backgrounds.md @@ -129,18 +129,18 @@ When you create a custom background: - **Size**: 650 x 90 - **Right side** - Room calendar. - **Size**: up to 36% of the screen width, up to 72% of the screen height depending on the display settings - + **16:9 - Single front-of-room display dimensions** -:::image type="content" source="../media/front-of-room-16-9-single-dimensions.png" alt-text="A custom background showing a 16:9 front of room display with element dimensions." lightbox="../media/front-of-room-16-9-single-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-for-qr-16x9.png" alt-text="A custom background showing a 16:9 front of room display with element dimensions and a QR code." lightbox="../media/mtr-devices/mtrw-for-qr-16x9.png"::: **16:9 - Dual front-of-room display dimensions** -:::image type="content" source="../media/front-of-room-16-9-dual-display-dimensions.png" alt-text="A custom background showing dual 16:9 front of room displays with element dimensions." lightbox="../media/front-of-room-16-9-dual-display-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/dual-for-qr.png" alt-text="A custom background showing dual 16:9 front of room displays with element dimensions and a QR code." lightbox="../media/mtr-devices/dual-for-qr.png"::: **21:9 - Single front-of-room display dimensions** -:::image type="content" source="../media/front-of-room-21-9-dimensions.png" alt-text="Custom background showing a 21:9 front of room display with element dimensions." lightbox="../media/front-of-room-21-9-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-for-qr-21x9.png" alt-text="Custom background showing a 21:9 front of room display with element dimensions and a QR code." lightbox="../media/mtr-devices/mtrw-for-qr-21x9.png"::: These guidelines are also available in a [custom theme template](#custom-background-template) that you can download. @@ -161,7 +161,7 @@ When you create a custom background, avoid placing text, logos, or icons, near t **16:9 - Touch console dimensions** -:::image type="content" source="../media/console-16-9-dimensions.png" alt-text="A custom background showing a 16:9 touch console display with element dimensions." lightbox="../media/console-16-9-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-console-qr.png" alt-text="A custom background showing a 16:9 touch console display with element dimensions with QR code." lightbox="../media/mtr-devices/mtrw-console-qr.png"::: #### Touch board displays @@ -178,11 +178,11 @@ When you create a custom background, avoid placing text, logos, or icons, on the **16:9 - Touch board display dimensions** -:::image type="content" source="../media/touch-board-16-9-display-dimensions.png" alt-text="A custom background showing a 16:9 touch board display with element dimensions." lightbox="../media/touch-board-16-9-display-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-touchboard-qr-16x9.png" alt-text="A custom background showing a 16:9 touch board display with element dimensions with QR code." lightbox="../media/mtr-devices/mtrw-touchboard-qr-16x9.png"::: **3:2 - Touch board display dimensions** -:::image type="content" source="../media/touch-board-3-2-display-dimensions.png" alt-text="A custom background showing a 3:2 touch board display with element dimensions." lightbox="../media/touch-board-3-2-display-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-touchboard-qr-3x2.png" alt-text="A custom background showing a 3:2 touch board display with element dimensions with QR code." lightbox="../media/mtr-devices/mtrw-touchboard-qr-3x2.png"::: ### Custom background template @@ -249,15 +249,15 @@ When you create a custom background, use the following guidelines: **16:9 - Single front-of-room display dimensions** -:::image type="content" source="../media/front-of-room-16-9-single-dimensions.png" alt-text="A custom background showing a 16:9 front of room display with element dimensions." lightbox="../media/front-of-room-16-9-single-dimensions.png"::: +:::image type="content" source="../media//mtr-devices/mtrw-for-qr-16x9.png" alt-text="A custom background showing a 16:9 front of room display with element dimensions with QR code." lightbox="../media/mtr-devices/mtrw-for-qr-16x9.png"::: **16:9 - Dual front-of-room display dimensions** -:::image type="content" source="../media/front-of-room-16-9-dual-display-dimensions.png" alt-text="A custom background showing dual 16:9 front of room displays with element dimensions." lightbox="../media/front-of-room-16-9-dual-display-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/dual-for-qr.png" alt-text="A custom background showing dual 16:9 front of room displays with element dimensions with QR code." lightbox="../media/mtr-devices/dual-for-qr.png"::: **21:9 - Single front-of-room display dimensions** -:::image type="content" source="../media/front-of-room-21-9-dimensions.png" alt-text="Custom background showing a 21:9 front of room display with element dimensions." lightbox="../media/front-of-room-21-9-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-for-qr-21x9.png" alt-text="Custom background showing a 21:9 front of room display with element dimensions with QR code." lightbox="../media/mtr-devices/mtrw-for-qr-21x9.png"::: #### Touch board displays @@ -274,11 +274,11 @@ When you create a custom background, avoid placing text, logos, or icons, near t **16:9 - Touch board display dimensions** -:::image type="content" source="../media/touch-board-16-9-display-dimensions.png" alt-text="A custom background showing a 16:9 touch board display with element dimensions." lightbox="../media/touch-board-16-9-display-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-touchboard-qr-16x9.png" alt-text="A custom background showing a 16:9 touch board display with element dimensions with a QR code." lightbox="../media/mtr-devices/mtrw-touchboard-qr-16x9.png"::: **3:2 - Touch board display dimensions** -:::image type="content" source="../media/touch-board-3-2-display-dimensions.png" alt-text="A custom background showing a 3:2 touch board display with element dimensions." lightbox="../media/touch-board-3-2-display-dimensions.png"::: +:::image type="content" source="../media/mtr-devices/mtrw-touchboard-qr-3x2.png" alt-text="A custom background showing a 3:2 touch board display with element dimensions with a QR code." lightbox="../media/mtr-devices/mtrw-touchboard-qr-3x2.png"::: ### Custom background template diff --git a/Teams/rooms/managed-meeting-rooms-portal.md b/Teams/rooms/managed-meeting-rooms-portal.md index e4289a1ebb..beac2d2536 100644 --- a/Teams/rooms/managed-meeting-rooms-portal.md +++ b/Teams/rooms/managed-meeting-rooms-portal.md @@ -34,11 +34,11 @@ The scope of the monitoring is - View of incidents - Top issues affecting your rooms - Actions required to restore rooms to healthy status -- View of Microsoft Teams Room devices +- View of Microsoft Teams Rooms devices - Snapshot of status at Microsoft Teams Rooms (MTR) device level - Basic history and details for every device -**View of Microsoft Teams Room devices** +**View of Microsoft Teams Rooms devices** - Snapshot of status at Microsoft Teams Rooms (MTR) device level - Basic history and details for every device @@ -52,9 +52,9 @@ Here are frequently used terms in the portal. |Term |Meaning | | :- | :- | -|**Monitoring Software** |Monitoring agent that is deployed in each of the Microsoft Teams Room devices. | -|**App** |Microsoft Teams Room system app (regardless of whether it uses Skype for Business or Microsoft Teams as the collaboration service. | -|**Room/Device** |The certified Microsoft Teams Room system device. | +|**Monitoring Software** |Monitoring agent that is deployed in each of the Microsoft Teams Rooms devices. | +|**App** |Microsoft Teams Rooms system app (regardless of whether it uses Skype for Business or Microsoft Teams as the collaboration service. | +|**Room/Device** |The certified Microsoft Teams Rooms system device. | |**Unmonitored** | Microsoft monitoring software deployed as part of management services isn't able to connect to the cloud services. We aren't receiving telemetry about the device. | |

**Healthy /**

**Unhealthy**

|Abnormalities in device / peripheral. | |**Suppressed** |If a device is known to be in maintenance, and its alerts should be ignored, the device can be suppressed deliberately. | @@ -72,7 +72,7 @@ The top-level summary shows at a glance the issues affecting your rooms, what yo Incidents are expected to be in one of two states: - **Need Action**: Action required by you to resolve the incident. -- **System Investigating**: Under automatic investigation by the monitoring platform. Next steps will be provided if it cannot be automatically resolved. +- **System Investigating**: Under automatic investigation by the monitoring platform. Next steps will be provided if it can't be automatically resolved. ### Reviewing incidents @@ -89,9 +89,9 @@ A warning might transition to “**Important**” if not attended to for a while ## Health status of device and incidents -Incidents that are classified as **“Important”** in severity will affect the health status of a device. If there is at least one incident of **Severity = “Important”** associated with a device, it's classified as ***unhealthy*** device. +Incidents that are classified as **“Important”** in severity will affect the health status of a device. If there's at least one incident of **Severity = “Important”** associated with a device, it's classified as ***unhealthy*** device. -Incidents classified as **“Warning”** severity do not affect the health status reported on a device. However, if a device has warning level incidents associated with it, then it would be shown with the health status of the device. +Incidents classified as **“Warning”** severity don't affect the health status reported on a device. However, if a device has warning level incidents associated with it, then it would be shown with the health status of the device. Following are some of the types of incidents that you might see and the explanations for each type. For each type, the action associated with the incident will be more specific depending on the issue. @@ -113,7 +113,7 @@ Following are some of the types of incidents that you might see and the explanat |Type |Explanation | | :- | :- | -|**App version** |The version of the Microsoft Teams Room App running on the device isn't current. Stale versions are known causes to problems experienced by users. | +|**App version** |The version of the Microsoft Teams Rooms App running on the device isn't current. Stale versions are known causes of problems experienced by users. | |**OS version** |The version of Windows operating system running in the meeting room is no longer recommended. | |**Network** |This will be removed as a type of warning in the near term due to additional work required after evaluation. | @@ -142,22 +142,22 @@ The top panel on the Rooms view provides a quick snapshot of how many of your de **Healthy / Unhealthy rooms**: -Devices/peripherals which do not have any incidents of severity “Important” are meeting current criteria for health are marked as healthy. However, it doesn't imply that there is a room outage for every unhealthy device in the portal. The description and action part of the incident contains more specific details about the issue and potential impact on user experience. +Devices/peripherals which don't have any incidents of severity “Important” are meeting current criteria for health are marked as healthy. However, it doesn't imply that there's a room outage for every unhealthy device in the portal. The description and action part of the incident contains more specific details about the issue and potential impact on user experience. **Disconnected device:** -The Microsoft monitoring agent deployed is disconnected from Pro Management cloud services. We aren't receiving telemetry about the room and do not have latest health status. This may happen due to network issues, firewall policy changes or if there are changes made to the device image. +The Microsoft monitoring agent deployed is disconnected from Pro Management cloud services. We aren't receiving telemetry about the room and don't have latest health status. This may happen due to network issues, firewall policy changes or if there are changes made to the device image. ## Room Detail: Status and Changes **Room Details: Status** -The device *Status* tab provides a consolidated view of status of a device, all the issues active for the device, the actions that are needed to resolve them, or that are ongoing. The Status tab also contains the breakdown of different components of health for the device under *Incidents tab*. If a device is disconnected, Status details will not be available. +The device *Status* tab provides a consolidated view of status of a device, all the issues active for the device, the actions that are needed to resolve them, or that are ongoing. The Status tab also contains the breakdown of different components of health for the device under *Incidents tab*. If a device is disconnected, Status details won't be available. **Show all signals:** To view all signals contained within a signal category, enable the Show all signals toggle button. Expansion arrows will appear next to category headings which can be clicked on to expand the accordion view. **Suppress/Unsuppress Ticket** -When a room is enrolled, you are indicating that you want to receive notifications for changes in room telemetry. There are occasions when a particular device or peripheral is in a known state where you do not want tickets or notifications generated. Using the Suppress ticket functionality, will silence any notification about that particular signal. When you are ready for the service to monitor and notify you about that signal, simply unsuppress the individual signal. +When a room is enrolled, you're indicating that you want to receive notifications for changes in room telemetry. There are occasions when a particular device or peripheral is in a known state where you don't want tickets or notifications generated. Using the Suppress ticket functionality, will silence any notification about that particular signal. When you're ready for the service to monitor and notify you about that signal, unsuppress the individual signal. **Active Ticket Category Expansion** Under each ticket category, any active or latest resolved ticket will be displayed along with the severity and when the ticket was last updated. By clicking on the expansion arrow, all tickets will appear with an active link to the ticket information. @@ -173,11 +173,11 @@ Active Ticket: Messages The messages UI is the primary communication tool to interact with your own team and monitor messages from the Pro Management bot. Active Ticket: Attachments -There are occasions where your team will need additional information to augment their investigation of the issue. The attachment tab provides you with the ability to upload pictures, videos or logs that are requested. +There are occasions where your team will need additional information to augment their investigation of the issue. The attachment tab provides you with the ability to upload pictures, videos, or logs that are requested. Active Ticket: History -Each room signal has only one ticket number that is assigned to it on purpose. A room device or peripheral persists in a room and may have issues over time. By maintaining this information under a specific unique ticket id, all historic information is maintained and can be analyzed for patterns of behavior. The History UI provides a view of all tickets actions created and resolved for this signal. +Each room signal has only one ticket number that is assigned to it on purpose. A room device or peripheral persists in a room and may have issues over time. By maintaining this information under a specific unique ticket ID, all historic information is maintained and can be analyzed for patterns of behavior. The History UI provides a view of all tickets actions created and resolved for this signal. FAQ How does dynamic tickets affect me and the operations of my rooms? -Customers will see the creation of smarter tickets and remediations that expand beyond just a binary signal ticket. For example, there can be as many as three displays in a Meeting Room (Display 1, Display 2 & the MTR touch panel display). However, there is only 1 (one) display signal that is either Healthy or Unhealthy. With the new dynamic tickets, we can now generate tickets unique to each display signal. +Customers will see the creation of smarter tickets and remediations that expand beyond just a binary signal ticket. For example, there can be as many as three displays in a Meeting Room (Display 1, Display 2 & the MTR touch panel display). However, there's only 1 (one) display signal that is either Healthy or Unhealthy. With the new dynamic tickets, we can now generate tickets unique to each display signal. diff --git a/Teams/rooms/meetings-with-SIP-H323-devices.md b/Teams/rooms/meetings-with-SIP-H323-devices.md index 8be827fa9b..ba1fd05adf 100644 --- a/Teams/rooms/meetings-with-SIP-H323-devices.md +++ b/Teams/rooms/meetings-with-SIP-H323-devices.md @@ -37,7 +37,7 @@ If you have multiple Teams Rooms all with a Pro licenses deployed in your organi To enable your Teams Rooms on Windows to use SIP and H.323 dialing: -1. The Teams Room account that is used to sign in to the device must have a Teams Room Pro license assigned. +1. The Teams Rooms account that is used to sign in to the device must have a Teams Rooms Pro license assigned. 2. You must have a signed agreement with one of the certified [Cloud Video Interop providers](../cloud-video-interop.md) (CVI) that offers this feature like for example, Poly and Pexip. Please reach out to your chosen CVI provider for more information. ## How to configure a Teams Room diff --git a/Teams/rooms/multi-tenant-management-partner.md b/Teams/rooms/multi-tenant-management-partner.md index c216a6b65c..bd44900170 100644 --- a/Teams/rooms/multi-tenant-management-partner.md +++ b/Teams/rooms/multi-tenant-management-partner.md @@ -2,7 +2,7 @@ title: Multitenant customer management for partners author: mstonysmith ms.author: tonysmit -ms.date: 07/25/2022 +ms.date: 04/04/2024 manager: pamgreen ms.reviewer: altsou ms.topic: article @@ -23,52 +23,52 @@ f1keywords: # Multitenant customer management for partners -Multitenant management (MTM) in the Teams Rooms Pro Management service helps partner organizations manage multiple customers in one place, with their own domain credentials. Partner users will see only those customer rooms that they are assigned to manage. It is possible to apply custom roles for each customer in the MTM portal, giving partner organizations granular control of permissions to the customer’s resources. +Multitenant management (MTM) in the Teams Rooms Pro Management helps partner organizations manage multiple customers in one place with their own domain credentials. Partner users will see only those customer rooms that they are assigned to manage. It's possible to apply custom roles for each customer in the MTM portal which will give partner organizations granular control of permissions to the customer’s resources. The MTM portal can be accessed through this [link](https://partner.rooms.microsoft.com/). -> [!Note] -> Partner organizations cannot manage their own rooms through the MTM portal. Those rooms can be managed in the [Pro Management portal](https://portal.rooms.microsoft.com/). +> [!Note] +> Partner organizations can't manage their own rooms through the MTM portal. Those rooms can be managed in the [Teams Rooms Pro Management portal](https://portal.rooms.microsoft.com/). -## Prerequisites for managing your customers through the MTM experience +## Pre-requisites for managing your customers through the MTM experience -Partners who meet specific eligibility criteria with a proven track record and the organizational capabilities to deploy, configure, and manage Microsoft Teams Rooms, including Surface Hub. Partners interested in learning more about the requirements for becoming a Microsoft Teams Rooms Partner can submit their request at https://aka.ms/MicrosoftTeamsRoomsPartnerInquiry. +Partners must meet specific eligibility criteria that have a proven track record and the organizational capabilities to deploy, configure, and manage Microsoft Teams Rooms, including Surface Hub. Partners interested in learning more about the requirements for becoming a Microsoft Teams Rooms Partner can submit their request at [link](https://aka.ms/MicrosoftTeamsRoomsPartnerInquiry). -## On-boarding customers +## Onboarding customers -To manage customers through the Pro Management-MTM portal, a relationship must be established between the partner organization’s tenant and the customer through an invitation sent by the customer. +To manage customers through the Teams Rooms Pro Management-MTM portal, a relationship is established between the partner organization’s tenant and the customer through an invitation that is sent by the customer. ## Tenant managers -This built-in role is only configurable in the Pro Management-MTM portal. This role allows you to assign a group of users that accept invitations, but are not involved with the management of customer rooms. In order to assign Tenant manager permissions in the Pro Management-MTM portal, the assigning account must be set to be a Managed Service Administrator in the Pro Management Customer portal. Before attempting to set Tenant manager permissions ensure your account is configured correctly in your Customer portal. You won't be able to configure it from the Pro Management-MTM portal. -It is recommended to configure this role so designated Tenant managers can accept customer invitations and sub-delegate permissions to others in your organization. If this doesn't happen, only those users with the Managed Service Administrator role in your tenant will be able to accept invitations. +This built-in role is only configurable in the Teams Rooms Pro Management-MTM portal. This role allows you to assign a group of users that accepts invitations, but aren't involved with the management of customer rooms. In order to assign Tenant manager permissions in the Teams Rooms Pro Management-MTM portal, the assigning account must be set to be a Teams Rooms Pro Manager in the Teams Rooms Pro Management portal for customers. Before attempting to set Tenant manager permissions, please verify the account is set up correctly in your Teams Rooms Pro management customer portal. This isn't configurable from the Teams Rooms Pro Management-MTM portal. + +It's recommended to configure this role so designated Tenant managers can accept customer invitations and sub-delegate permissions to others in your organization. Otherwise, only users with the Teams Rooms Pro Manager role in your tenant will be able to accept invitations. **To configure tenant managers** -1. Log in to the Pro Management-MTM portal as either a Global admin or Managed Service admin. +1. Log in to the Teams Rooms Pro Management-MTM portal as either a Global admin or Teams Rooms Pro Manager role. 2. Go to Tenant managers. 3. Select **Add tenant managers**. 4. In the detail pane, search for the users or security groups. 5. Select the user or group. 6. Select **Add**. - ### Invitation from the customer -The partner should provide the domain name to customers. Only the Global admin, Managed service admin, and Tenant managers roles can see and accept the invitation when they log in to the Pro Management-MTM portal. +The partner will provide the domain name to customers. Only the Global admin, Teams Rooms Pro Manager, and Tenant managers roles can see and will accept the invitation when they log in to the Teams Rooms Pro Management-MTM portal. > [!Note] -> Even though these roles can see invitations and high-level Tenant metadata, you will not see the customer’s data until you are assigned a role with that customer. +> Even though these roles can see invitations and high-level Tenant metadata, you won't see the customer’s data until you are assigned a role with that customer. Details on the customer invitation are outlined in [Multitenant management for Customers](Multi-tenant-management-customer.md). **To accept a pending invite** -1. Log in to the Pro Management-MTM portal as either a Global admin, Managed Service admin, or Tenant manager. +1. Log in to the Teams Rooms Pro Management-MTM portal as either a Global admin, Teams Rooms Pro Manager, or Tenant manager. 1. Go to **Tenants**. -1. Select the invitation that shows a “Pending” status. +1. Select the invitation that shows a **Pendin** status. 1. Review the invitation details. -1. Assign users that will be the admins for this customer. +1. Assign the users that will be part of the admins for the customer. 1. Select **Accept** to establish the partner-customer relationship. Selecting **Deny** deletes the invitation. @@ -77,7 +77,7 @@ Details on the customer invitation are outlined in [Multitenant management for C > There is no permanent association with the user that accepts the invitation. > [!Note] - > *If the invitation is accidentally denied the invitation, the customer must create a new invitation.* + > If the invitation is accidentally denied the invitation, the customer must then create a new invitation. **To review the configuration or add more primary admins for a tenant** @@ -92,7 +92,7 @@ To off-board a customer, you must remove them from the **Tenants** list. **To remove a customer** -1. Log in to the Pro Management-MTM portal as a Primary admin for the customer you wish to remove. +1. Log in to the Teams Rooms Pro Management-MTM portal as a Primary admin for the customer you wish to remove. 1. Go to **Tenants**. 1. Select the customer you wish to remove. 1. In the customer detail pane, select **Remove customer**. @@ -100,36 +100,33 @@ To off-board a customer, you must remove them from the **Tenants** list. ## Managing partner roles -Partner roles allow for delegation of responsibilities to additional personnel. The concept of these roles is the same as described in [Role-based access control](rooms-pro-rbac.md), but in context of each customer. Further, it is important to note that partner roles are distinct from the customer’s roles. The partner roles can be deleted by the customer. +Partner roles allow for delegation of responsibilities to additional personnel. The concept of these roles is the same as described in [Role-based access control](rooms-pro-rbac.md), but this is within context of each customer. Also, it's important to note that partner roles are distinct from the customer’s roles. The partner roles can be deleted by the customer. -The **Primary admins** role is the only built-in role for each on-boarded customer and has almost all permissions—in context of the customer—for the Pro Management service (see table 1). Partner** role permissions only extend as far as the rooms designated by the customer. For example, if the customer is a global organization and assigns the Partner to manage All US rooms, the primary admin would only be able to manage and delegate permissions for those rooms. The Partner has no visibility to other rooms the Customer may have in other countries/regions. +The **Primary admins** role is the only built-in role for each onboarded customer and has almost all permissions, in context of the customer, for the Teams Rooms Pro Management service. See the table. **Partner** role permissions only extend as far as the rooms designated by the customer. For example, if the customer is a global organization and assigns the Partner to manage All US rooms (all rooms in the United States), the primary admin will only be able to manage and delegate permissions for those rooms. The Partner has no visibility to other rooms the customer may have in other countries/regions. **To manage users in the **Partner** role for a customer** -1. Go to **Settings > Roles**. +1. Go to **Settings > Roles**. 1. Select the customer from the dropdown list for which you want to edit the partner role. 1. Select the **Primary admins** built-in role from the list. 1. Select **Assignments.** 1. From the list, select **Assigned Admins.** 1. Select **Members.** -1. Select **Edit.** +1. Select **Edit.**. 1. Search for the user or security group you wish to add in the search bar. 1. Select the user or group. 1. Select **Save** to confirm the changes. ### Managing custom partner roles for a customer -As a partner, you can create custom roles to suit your operational requirements. For example, you might create a help desk role that should only have incident management permissions. +As a partner, you can create custom roles to suit your operational requirements. For example, you might create a help desk role that should only have incident management permissions. **To manage roles** -1. Go to **Settings > Roles**. +1. Go to **Settings > Roles**. 1. Select the customer from the dropdown menu for which you want to edit the partner role. 1. Create a [custom role](rooms-pro-rbac.md#built-in-roles). - - - |Feature|Permission|**MMR Admin**|**Site Lead**|**Site Tech**|**Primary admins**| | :- | :- | :- | :- | :- | :- | |Rooms|View| ✔|✔|✔|✔| @@ -147,50 +144,51 @@ As a partner, you can create custom roles to suit your operational requirements. ||Create customer incident|✔|✔|✔|✔| |Tickets Management|View|✔|✔|✔|✔| ||Update|✔|✔|✔|✔| -|MMR Settings|View|✔|||| +|Teams Rooms Pro Settings|View|✔|||| ||Modify|✔|||| |Role management|View |✔|||✔| ||Modify|✔|||✔| > [!Note] -> A user assigned as a Primary admin for Customer A has full permissions in the Pro Management service for only that customer. The permissions of the user in Customer A have no influence on other customers. +> A user assigned as a Primary admin for Customer A has full permissions in the Teams Rooms Pro Management service for only that customer. The permissions of the user in Customer A have no influence on other customers. ## Security End customers retain control over access to their data and can completely remove a partner or specific roles at any time. -With the delegated access feature, a partner does not gain any other privileges outside of the Pro Management portal. For example, by using this feature to invite a partner to manage rooms in the Pro Management portal, no permissions are granted to Microsoft Entra ID or the Teams Admin Center or any other Microsoft product. In addition, partners do not have any access to view or modify rooms not defined in the invitation scope. +With the delegated access feature, a partner doesn't gain any other privileges outside of the Teams Rooms Pro Management portal. For example, by using this feature to invite a partner to manage rooms in the Teams Rooms Pro Management portal, no permissions are granted to Microsoft Entra ID or the Teams Admin Center or any other Microsoft product. In addition, partners don't have any access to view or modify rooms that aren't defined in the invitation scope. -Once the partner—customer relationship is established—as described in the “Onboarding customers” of this doc – the partner can view room data in the Pro Management portal. This includes any data present in the Pro Management portal but derived from other Microsoft products. For example, call quality reports in the Pro Management portal are derived from Teams call quality data. +Once the partner—customer relationship is established, the partner can view room data in the Teams Rooms Pro Management portal. This includes any data present in the Teams Rooms Pro Management portal but derived from other Microsoft products. For example, call quality reports in the Teams Rooms Pro Management portal are derived from Teams call quality data. -Data resides in the customer’s tenant and isn't copied to the partner’s tenant. +Data resides in the customer’s tenant and isn't copied to the partner’s tenant. -The MTM portal uses Microsoft Entra authentication to validate the login credentials of the partner. It is important to note that at this time, the customer’s authentication policies will not apply to the partner. For example, if the customer has a multi-factor authentication policy, it does not translate to the partner. +The Teams Rooms Pro management MTM portal uses Microsoft Entra authentication to validate the login credentials of the partner. It's important to note that at this time, the customer’s authentication policies won't apply to the partner. For example, if the customer has a multifactor authentication policy, it won't translate to the partner. -The customer can pull audit logs for the Pro Management portal, which includes partner activity. See [Audit logging in the Teams Rooms Managed service](Multi-tenant-auditing.md). +The customer can pull audit logs for the Teams Rooms Pro Management portal, which includes partner activity. See [Audit logging in the Teams Rooms Managed service](multi-tenant-auditing.md). > [!Note] -> Microsoft Entra auditing and Office 365 auditing does not capture logs from the Pro Management portal. +> Microsoft Entra auditing and Office 365 auditing doesn't capture logs from the Teams Rooms Pro Management portal. ## Navigating the MTM portal -The MTM portal has two interactive models to navigate between customer data: +The Teams Rooms Pro Management MTM portal has two interactive models to navigate between customer data: -- Aggregate views where data from all your customers is consolidated in a single list and can be filtered. +- **Aggregate** views where data from all your customers is consolidated in a single list and can be filtered. > [!Note] > This view is only supported in the **Incidents** page when **Enable all tickets view** is toggled on. > > ![Figure 1](../media/Multi-tenant-management-partner-001.png) - - Tenant switching where only data from the **Customer** selected in the dropdown list is displayed. + - **Tenant switching** where only data from the **Customer** selected in the dropdown list is displayed. -## Features not offered by Multitenant Management +## Features that aren't offered by Multitenant Management -Due to technical, compliance, or other limitations, some features are not available in the Teams Rooms Pro Multitenant Management portal. These include: +Due to technical, compliance, or other limitations, these features aren't available in the Teams Rooms Pro management Multitenant Management portal. - - ServiceNow API integration -- Room Planner +- ServiceNow API integration +- Standards/Room Planner - One Time Password - Remote Control - +- Bring Your Own Device (BYOD) +- Windows Autopilot \ No newline at end of file diff --git a/Teams/rooms/rooms-operations.md b/Teams/rooms/rooms-operations.md index dc9db4f041..71f5d753df 100644 --- a/Teams/rooms/rooms-operations.md +++ b/Teams/rooms/rooms-operations.md @@ -42,7 +42,7 @@ The logs will be output as a ZIP file in c:\rigel. ### Managing Disk Space -Downloaded logs on the device can take up disk space. If logs are not regularly cleaned up, they can interfere with the normal functionality of the room. Teams Rooms deletes downloaded logs after 30 days. IT admins can override the log clean-up using the device registry setting. +Downloaded logs on the device can take up disk space. If logs aren't regularly cleaned up, they can interfere with the normal functionality of the room. Teams Rooms deletes downloaded logs after 30 days. IT admins can override the log clean-up using the device registry setting. |Setting|Allows| |:-----|:-----| @@ -109,11 +109,11 @@ This section covers system settings that Microsoft Teams Rooms depends on to fun Joining Teams Rooms to an Active Directory domain provides the following benefits: -- Domain-joining Teams Rooms enables you to grant domain users and groups administrative rights. By doing so, you will not have to remember the local machine level administrator account password. +- Domain-joining Teams Rooms enables you to grant domain users and groups administrative rights. By doing so, you won't have to remember the local machine level administrator account password. - You can deploy Windows Quality of Service configuration to Teams Rooms. -When you join Teams Rooms to a domain, it is required that you create a separate Organizational Unit (OU), so that you can provide Group Policy Object (GPO) exclusions to the OU where all Teams Rooms objects reside. Disable all GPO inheritance so that unsupported Group Policy settings do not get applied to Teams Rooms. Create machine objects in the OU before joining Teams Rooms to the domain to assure that Group Policies applied to the default computers OU are not applied. +When you join Teams Rooms to a domain, it's required that you create a separate Organizational Unit (OU), so that you can provide Group Policy Object (GPO) exclusions to the OU where all Teams Rooms objects reside. Disable all GPO inheritance so that unsupported Group Policy settings don't get applied to Teams Rooms. Create machine objects in the OU before joining Teams Rooms to the domain to assure that Group Policies applied to the default computers OU aren't applied. > [!NOTE] > Even if you create a separate OU and block inheritance, there are some group policies which could cause issues if they have No Override set. A Group Policy with No Override set beats an OU with Block Policy Inheritance set. @@ -241,7 +241,7 @@ Some management functions, like manually installing a private CA certificate, re 7. Perform the necessary administrative tasks. 8. Restart the machine when you're finished. -The console is now back in its normal operation mode. The following procedure requires you to attach a keyboard to the device if one is not already attached. +The console is now back in its normal operation mode. The following procedure requires you to attach a keyboard to the device if one isn't already attached. ### Clearing the Teams Rooms on Windows Client Cache @@ -258,7 +258,7 @@ The console is now back in its normal operation mode. The following procedure re 7. Restart the Teams Rooms device. 8. Sign in and restart again, once the Teams Room's interface has appeared. -### Changing the Teams Room console language or date & time format +### Changing the Teams Rooms console language or date & time format 1. Switch to Admin mode. 2. Select the **Start** menu. diff --git a/Teams/rooms/rooms-release-note.md b/Teams/rooms/rooms-release-note.md index a12c0878c8..a02574a30b 100644 --- a/Teams/rooms/rooms-release-note.md +++ b/Teams/rooms/rooms-release-note.md @@ -663,6 +663,7 @@ Introduced in this update: |Release |Release date | |---------|---------| +|[1449/1.0.96.2024032804](#144910962024032804-april-2024) | April 2024 | |[1449/1.0.96.2024030101](#144910962024030101-march-2024) | March 2024 | |[1449/1.0.96.2024020802](#144910962024020802-february-2024) | February 2024 | |[1449/1.0.96.2023120901](#144910962023120901-february-2024) | February 2024 | @@ -689,6 +690,12 @@ Introduced in this update: Features with :::image type="icon" source="../media/mtr-pro-icon.png"::: are only available with Teams Rooms Pro license. +### 1449/1.0.96.2024032804 (April 2024) + +Introduced in this update: + +- Bug fixes for issues with launching whiteboard and meeting join failures. + ### 1449/1.0.96.2024030101 (March 2024) Introduced in this update: diff --git a/Teams/rooms/xml-config-file.md b/Teams/rooms/xml-config-file.md index 916d4ab44c..9e424542ef 100644 --- a/Teams/rooms/xml-config-file.md +++ b/Teams/rooms/xml-config-file.md @@ -162,7 +162,7 @@ If a variable value is of the wrong type, elements are out of order, elements ar | `` | Boolean ❷ | First ❶ | If true, dual screen mode is enabled. Otherwise the device uses single screen mode. | | `` | Boolean ❷ | First ❶ | If true, content is shown on both screens in dual screen mode, when out of meeting. | | `` | Boolean ❷ | First ❶ | Set to true to disable HDMI audio sharing to meeting participants in Teams meeting. The default is false. | -| `` | Boolean ❷ | First ❶ | Enabled by default. If true, Cloud IntelliFrame will be enabled for the Team Room.| +| `` | Boolean ❷ | First ❶ | Enabled by default. If true, Cloud IntelliFrame will be enabled for the Team Room.| | `` | Boolean ❷ | First ❶ | Enabled by default to provide warnings to in room participants that the room has reached capacity (this requires the room capacity be set in Exchange and a camera capable of people counting). Set to false if you wish to disable these warnings. | | `` | Boolean ❷ | First ❶ | Enabled by default. If false, Front Row is disabled. For more information, see [Set front row as the default layout](manage-front-row.md).| | `` | String | | Lets you set the size of Front Row to provide more or less space for remote participant video and shared content. Possible values are `small`, `medium`, and `large`. The default value is `medium`. For more information, see [Set front row as the default layout](manage-front-row.md). | diff --git a/Teams/teams-add-on-licensing/assign-teams-add-on-licenses.md b/Teams/teams-add-on-licensing/assign-teams-add-on-licenses.md index 84d2f9b39d..595a4d18ef 100644 --- a/Teams/teams-add-on-licensing/assign-teams-add-on-licenses.md +++ b/Teams/teams-add-on-licensing/assign-teams-add-on-licenses.md @@ -18,7 +18,7 @@ search.appverid: MET150 f1.keywords: - NOCSH ms.reviewer: mikedav -ms.date: 12/14/2018 +ms.date: 03/26/2024 description: Learn how to assign Teams add-on licenses to users for capabilities like Audio Conferencing, Phone System, and Calling Plans. appliesto: - Microsoft Teams @@ -169,7 +169,8 @@ To learn more, see [View licenses and services with PowerShell](/office365/enter | Microsoft Teams Rooms Pro without Audio Conferencing | Microsoft_Teams_Rooms_Pro_without_Audio_Conferencing | | Microsoft Teams Shared Devices | MCOCAP | | Microsoft Teams Premium | Microsoft_Teams_Premium | -| Microsoft Teams EEA | Microsoft_Teams_EEA | +| Microsoft Teams Enterprise EEA | Microsoft_Teams_EEA | +| Microsoft Teams Enterprise | Microsoft_Teams_Enterprise | ## Related content diff --git a/Teams/teams-add-on-licensing/licensing-enhance-teams.md b/Teams/teams-add-on-licensing/licensing-enhance-teams.md index 8dd09f41ff..bb6aac72af 100644 --- a/Teams/teams-add-on-licensing/licensing-enhance-teams.md +++ b/Teams/teams-add-on-licensing/licensing-enhance-teams.md @@ -4,7 +4,7 @@ author: DaniEASmith ms.author: danismith manager: pamgreen ms.reviewer: margidesai, spraveen -ms.date: 12/07/2023 +ms.date: 03/26/2024 ms.topic: conceptual ms.service: msteams ms.subservice: teams-premium @@ -70,6 +70,7 @@ The following tables compare key features between Teams and Teams Premium. Becau | Add organization branding to meeting lobbies | | ✔️ | | Customize meeting backgrounds for your organization | | ✔️ | | Customize Together mode scenes for your organization | | ✔️ | +| Add branding to meeting invites and meeting join launch pages | | ✔️ | | Read live translated captions during meetings | | ✔️ | | Manage what attendees see | | ✔️ | | Use RTMP-In for meetings | | ✔️ | @@ -118,7 +119,8 @@ The following tables compare key features between Teams and Teams Premium. Becau | Broadcast town halls to 20k attendees | | ✔️ | | Host up to 50 town halls simultaneously | | ✔️ | | Town hall Q&A capacity of 20k attendees | | ✔️ | -| Microsoft eCDN for town halls\* | | ✔️ | +| Use Microsoft eCDN for town halls\* | | ✔️ | +| Choose an eCDN provider for town halls\* | | ✔️ | | View Microsoft Town hall insights | | ✔️ | | Town hall organizers can view engagement reports | | ✔️ | | Edit town hall emails | | ✔️ | @@ -237,8 +239,8 @@ The **tenant requirement** is: The **user requirement** is: -- An Office 365 or Microsoft 365 subscription with a Teams license. - - For new customers in the European Economic Area (EEA), Teams licenses must be purchased separately from Office 365/Microsoft 365 licenses, but both licenses are still required for Teams Premium. For more information on this licensing change in the EEA, see [New subscription structure for Microsoft 365 in Europe](https://www.microsoft.com/licensing/news/Microsoft365-Teams-EEA). +- An Office 365 or Microsoft 365 subscription and a Teams license. +For new customers, Teams licenses must be purchased separately from Office 365/Microsoft 365 licenses, but both licenses are still required for Teams Premium. ### Can I acquire Teams Premium features without the Teams Premium license? diff --git a/Teams/teams-add-on-licensing/microsoft-teams-add-on-licensing.md b/Teams/teams-add-on-licensing/microsoft-teams-add-on-licensing.md index 261de483a4..2f41cef32b 100644 --- a/Teams/teams-add-on-licensing/microsoft-teams-add-on-licensing.md +++ b/Teams/teams-add-on-licensing/microsoft-teams-add-on-licensing.md @@ -4,7 +4,7 @@ author: DaniEASmith ms.author: danismith manager: pamgreen ms.reviewer: mikedav -ms.date: 07/07/2023 +ms.date: 03/26/2024 ms.topic: conceptual ms.service: msteams search.appverid: MET150 @@ -31,13 +31,13 @@ description: Learn about Microsoft add-on licenses for Microsoft Teams and the c Add-on licenses are licenses for specific Microsoft Teams capabilities. They give you the flexibility to add capabilities only for users in your organization who need them. To add a capability, buy one add-on license for each user who will use it. -The add-on licensing options available to you depend on the Microsoft 365 plan you have. To see which voice calling and audio conferencing options are available to you, see the [Which Microsoft capabilities are available with my plan?](#which-microsoft-capabilities-are-available-with-my-plan) section of this article. +The add-on licensing options available to you depend on the Microsoft Teams plan you have. To see which voice calling and audio conferencing options are available to you, see the [Which Microsoft capabilities are available with my plan?](#which-microsoft-capabilities-are-available-with-my-plan) section of this article. Here's a list of Teams add-on licenses and their capabilities that you can add to your Teams subscription. |License|Description| |-------|-----------| -| **Microsoft Teams Premium** | Microsoft Teams Premium is a Teams add-on license that allows organizations with Microsoft 365 subscriptions to enhance their Teams experience with benefits like more personalized and intelligent meetings, enhanced meeting protection, and advanced management and reporting capabilities. For more information about the Teams Premium add-on license, see [Microsoft Teams Premium licensing](licensing-enhance-teams.md). | +| **Microsoft Teams Premium** | Microsoft Teams Premium is a Teams add-on license that allows organizations with Microsoft 365 subscriptions and Teams licenses to enhance their Teams experience with benefits like more personalized and intelligent meetings, enhanced meeting protection, and advanced management and reporting capabilities. For more information about the Teams Premium add-on license, see [Microsoft Teams Premium licensing](licensing-enhance-teams.md). | | **Teams Phone with Calling Plan bundle** | The Teams Phone with Calling Plan license bundles Teams Phone System's PBX capabilities and a Domestic Calling Plan for PSTN connectivity. | | **Teams Phone Standard** |[Teams Phone System](../what-is-phone-system-in-office-365.md) is a hosted telephone service that gives you call control and Private Branch Exchange (PBX) capabilities. Teams Phone Standard licenses give you all Teams Phone System capabilities like cloud voicemail, call park, call forwarding, auto attendants, call queues, call transfer, and caller ID.

To learn more about Phone System, see [Here's what you get with Teams Phone System](../here-s-what-you-get-with-phone-system.md). | | **Microsoft Teams Calling Plans** | If your users need to call phone numbers outside your organization, you can purchase [Microsoft Teams Calling Plans](../calling-plans-for-office-365.md) to connect to PSTN phone numbers with Microsoft as your PSTN provider. There are Domestic Calling Plans, International Calling Plans, and Pay-As-You-Go Calling Plans.

To find out whether Teams Calling Plans is available in your country or region, see [Country and region availability for Audio Conferencing and Calling Plans](../country-and-region-availability-for-audio-conferencing-and-calling-plans/country-and-region-availability-for-audio-conferencing-and-calling-plans.md). | @@ -56,21 +56,21 @@ Most Microsoft 365 plans allow Teams users to make peer-to-peer calls within you Whether you're a small business, enterprise organization, educational institution, government agency, or nonprofit, you have three ways to get Teams Phone System and PSTN connectivity: -- Buy a Teams Essentials with Microsoft Entra ID, Microsoft 365 Business, E1/E3, A1/A3, F1/F3, or G1/G3 plan and then buy **Teams Phone with Calling Plan** bundle licenses. +- Buy a Teams Essentials with Microsoft Entra ID, Microsoft 365 Business, E1/E3 and the Microsoft Teams Enterprise license, A1/A3, F1/F3, or G1/G3 plan; and then buy **Teams Phone with Calling Plan** bundle licenses. - This model will give you Teams Phone System PBX capabilities and a Microsoft Domestic Calling Plan. - Choose this setup if you want all phone number management and billing to be handled by Microsoft. - Check to see if the [Teams Phone with Calling Plan bundle license is available in your region](../country-and-region-availability-for-audio-conferencing-and-calling-plans/country-and-region-availability-for-audio-conferencing-and-calling-plans.md). -- Buy a Teams Essentials with Microsoft Entra ID, Microsoft 365 Business, E1/E3, A1/A3, F1/F3, or G1/G3 plan, buy **Teams Phone Standard** licenses (*If you're adding Teams Phone to F1/F3, buy -**Teams Phone Standard for Frontline Workers** licenses*), and buy a Microsoft standalone calling plan or choose a third-party PSTN carrier. +- Buy a Teams Essentials with Microsoft Entra ID, Microsoft 365 Business, E1/E3 and the Microsoft Teams Enterprise license, A1/A3, F1/F3, or G1/G3 plan; buy **Teams Phone Standard** licenses (*If you're adding Teams Phone to F1/F3, buy +**Teams Phone Standard for Frontline Workers** licenses*); and buy a Microsoft standalone calling plan or choose a third-party PSTN carrier. - This model will give you Teams Phone System, but you'll still need to connect to the PSTN. - To view all your PSTN connectivity options, see [PSTN connectivity options](../pstn-connectivity.md). - To learn about all voice solutions, see [Plan your Teams voice solution](../cloud-voice-landing-page.md). -- Buy an E5/A5/G5 plan and buy **Microsoft Calling Plans** or connect to a third-party PSTN connectivity provider. +- Buy an E5 plan and add a Microsoft Teams Enterprise license or buy an A5 or G5 plan; and then buy **Microsoft Calling Plans** or connect to a third-party PSTN connectivity provider. - Most Microsoft 365 E5, A5, and G5 plans include Teams Phone System, but organizations still need to choose a [PSTN connectivity option](../pstn-connectivity.md). -Here's a summary of which Microsoft voice and calling licenses to purchase, based on Microsoft 365 plan: +Here's a summary of which Microsoft voice and calling licenses to purchase: diff --git a/Teams/teams-add-on-licensing/remove-assign-free-licenses.md b/Teams/teams-add-on-licensing/remove-assign-free-licenses.md deleted file mode 100644 index 27e47ee781..0000000000 --- a/Teams/teams-add-on-licensing/remove-assign-free-licenses.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Retire Microsoft Teams Free (classic) for your organization -author: DaniEASmith -ms.author: danismith -manager: pamgreen -ms.reviewer: -ms.date: 08/28/2023 -ms.topic: conceptual -ms.service: msteams -search.appverid: MET150 -ms.collection: - - M365-collaboration - - m365initiative-meetings - - tier1 - - ContentEnagagementFY24 -audience: Admin -appliesto: - - Microsoft Teams -ms.localizationpriority: medium -ms.custom: - - Licensing - - admindeeplinkMAC -description: Learn how to remove the Teams free (classic) licenses and assign paid Teams licenses for your organization's users. ---- - -# Retire Microsoft Teams Free (classic) for your organization - -This article is for IT admins who already have Microsoft 365 subscriptions and need to retire their users' **Teams Free (Classic)** licenses and assign them paid Teams licenses. - -In mid-April 2023, Microsoft retired the **Microsoft Teams Free (classic)** license. - -If you didn't move your users' free Teams licenses to paid Teams licenses by mid-April 2023, your users lost access to Teams. - -To complete this process, you can choose one of two methods: - -- [Use the Microsoft 365 admin center.](#use-microsoft-365-admin-center-to-replace-licenses) -- [Use Microsoft PowerShell.](#use-microsoft-powershell-to-replace-licenses) - -If your organization decides not to migrate to a paid Teams license, you can export your organization's content from Teams. For instructions on how to export Teams content, see [Export content with Microsoft Teams Export APIs](/microsoftteams/export-teams-content). - -## Use Microsoft 365 admin center to replace licenses - -If your organization has few users assigned the **Teams Free (classic)** license, we recommend using the Microsoft 365 admin center for removing and assigning licenses. - -### Check users' current Teams licensing - -1. Sign into the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339). -1. On the left-side menu, go to **Users** > and select [**Active users**](https://go.microsoft.com/fwlink/p/?linkid=834822) to view licenses assigned to users. - 1. The **License** column will show **Microsoft Teams Free (classic)** next to the users assigned that license. -1. On the left-side menu, go to **Billing** > and select [**Licenses**](https://go.microsoft.com/fwlink/p/?linkid=842264) to see if you have available paid Teams licenses. - 1. If your organization has available licenses, skip to [Assign paid Teams licenses](#assign-paid-teams-licenses) to assign those licenses to the users with **Teams Free (classic)** licenses. -1. Determine the number of paid Teams licenses you need to buy, if any. - -### Purchase paid Teams licenses - -1. In the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339), go to **Billing** > and select **Purchase services**. -1. Select **View products** to view all available licenses. -1. Select the **Communication and collaboration** category filter to see Teams licenses. -1. Choose the paid Teams license you would like to replace **Teams Free (classic)**. - 1. We recommend the [**Teams Essentials** license](https://admin.microsoft.com/adminportal/home#/catalog/offer-details/microsoft-teams-essentials-aad-identity-/2D7C59AC-F814-43E0-8E8E-E4EA91A09CAF), which is available up to 300 seats. - 1. If you need more than 300 seats, we recommend purchasing [Microsoft 365 E1 licenses](https://admin.microsoft.com/Adminportal/Home#/catalog/offer-details/office-365-e1/CF4A479A-2119-4EF2-83D1-37CF8460EADA). -1. Enter in the number of licenses you would like to purchase, and then choose a billing frequency. -1. Select the **Buy** button to complete the purchasing process. - -#### Purchase licenses in the admin center Marketplace - -Some tenants have access to the Microsoft 365 admin center Marketplace. For these tenants, you will purchase licenses in the Marketplace. - -1. In the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339), select **Marketplace** from the left-side menu. -1. Select the **All products** tab. -1. Select the **Communication and collaboration** category filter to see Teams licenses. -1. Choose the paid Teams license you would like to replace **Teams Free (classic)**. -1. Enter in the number of licenses you would like to purchase, and then choose a billing frequency. -1. Select the **Buy** button to complete the purchasing process. - -### Assign paid Teams licenses - -1. When you're ready to replace the **Teams Free (classic)** licenses, in the Microsoft 365 admin center, go to **Users** > [**Active users**](https://admin.microsoft.com/adminportal/home#/users). -1. Select all users with the **Teams Free (classic)** license listed in the **Licenses** column. -1. At the top of the admin center, select the **Manage product licenses** option. -1. In the right-side pane, select **Replace**. - 1. Selecting the **Replace** option requires you to reselect all licenses you wish those users to be assigned. If you only select the new paid Teams license, the other licenses those users were assigned will be removed from the users and replaced with the Teams license. - 1. If your users have different licensing needs, complete this process in batches to prevent incorrectly licensing users. -1. In the ride-side pane, choose the new paid Teams license and any other licenses the users should be assigned, and then select the **Save changes** button. - -## Use Microsoft PowerShell to replace licenses - -If your organization has a large number of users assigned the **Teams Free (classic)** license, we recommend using PowerShell to bulk unassign and assign licenses to users. - -Before you can complete this process, you'll need paid Teams licenses for users assigned the **Teams Free (classic)** license. To purchase licenses for those users, see [Purchase paid Teams licenses](#purchase-paid-teams-licenses). - -1. Connect your Microsoft 365 tenant to the [Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/get-started). -1. Open the Microsoft PowerShell desktop app. -1. [Set user and organization permissions for Graph API](/microsoft-365/enterprise/remove-licenses-from-user-accounts-with-microsoft-365-powershell#use-the-microsoft-graph-powershell-sdk). -1. [Remove **Teams Free (classic)** licenses from users accounts](/microsoft-365/enterprise/remove-licenses-from-user-accounts-with-microsoft-365-powershell#removing-licenses-from-user-accounts). -1. [Assign paid Teams licenses to users](/microsoft-365/enterprise/assign-licenses-to-user-accounts-with-microsoft-365-powershell#assigning-licenses-to-user-accounts). - -For more information on the Graph PowerShell SDK process, see [Use the Microsoft Graph PowerShell SDK](/microsoft-365/enterprise/view-licenses-and-services-with-microsoft-365-powershell). diff --git a/Teams/teams-classic-client-uninstall.md b/Teams/teams-classic-client-uninstall.md new file mode 100644 index 0000000000..94c4ac0ca5 --- /dev/null +++ b/Teams/teams-classic-client-uninstall.md @@ -0,0 +1,115 @@ +--- +title: How to uninstall the classic Teams client +ms.author: heidip +author: MicrosoftHeidi +manager: jtremper +ms.topic: article +ms.date: 04/02/2024 +ms.service: msteams +audience: admin +ms.collection: +- M365-collaboration +- m365initiative-deployteams +ms.reviewer: +search.appverid: MET150 +f1.keywords: +- NOCSH +description: Uninstalling classic Teams client from client machines if the automatic uninstall doesn't work, or if an admin needs to do a manual removal after the end of availability for classic Teams client and the upgrade to new Teams client. +appliesto: +- Microsoft Teams +ms.localizationpriority: high +--- + +# Uninstalling classic Microsoft Teams + +After installing the new Teams client and setting the **New Teams Only** policy (or reaching the end of life period for classic Teams), there will be an attempt to remove classic Teams client application after 14 days. This removal will be attempted by Microsoft, but in some cases, due to permissions or other settings, the removal may fail. This article outlines the steps and considerations for IT administrators to uninstall the classic Teams client manually. + +> [!NOTE] +> This article discusses removing the classic Teams client application. Users may also, depending on how the classic Teams client was installed, also have the Machine-Wide Installer to remove, and this will also appear as an application, but its removal isn't covered in this documentation. For more information, see [How the Microsoft Teams MSI file works](msi-deployment.md#how-the-microsoft-teams-msi-file-works). + +## Understanding Your Deployment Scenario + +Before proceeding with the uninstallation, you should try to identify how classic Teams was deployed in your organization. The most common configurations are: + +1. **User-Deployed or Peruser Admin Deployment**: + - Classic Teams was installed individually by users or by admins on a per-user basis, typically through the web, Microsoft Store, or admin tools. In **Add or Remove Programs**, you'll only see an entry for classic Teams. + - **Action**: No immediate action required. classic Teams will attempt to be automatically uninstalled 14 days after the new Teams installation. + +2. **Commercial Version of Microsoft 365 Apps Installed**: + - In **Start** > **Settings** > **Apps**, classic Teams and the Teams Machine-Wide Installer are both present. + - **Action**: No immediate action required. The new Teams installation will replace classic Teams, which will be removed after 14 days, and Microsoft 365 Apps will attempt to uninstall the Teams Machine-Wide Installer at a later point. + +3. **Admin-Deployed Teams Machine-Wide Installer Without Microsoft 365 Apps**: + - Classic Teams was deployed machine-wide by an admin without using Microsoft 365 Apps (typically by deploying the Teams Machine-Wide Installer directly). + - **Action**: After new Teams is deployed, an attempt will be made to remove classic Teams after 14 days. If Microsoft 365 Apps is present, after new Teams is deployed, an attempt to remove the Teams Machine-Wide Installer will be made as well. Otherwise, admins must proactively uninstall the Teams Machine-Wide Installer using their existing deployment tools. See [Bulk install classic Teams using Windows Installer (MSI)](msi-deployment.md) for more information. + +> [!NOTE] +> If your organization has the **New Teams as default** setting, which allows users to switch back, the uninstallation of classic Teams removes the switch option. + +## Uninstalling classic Teams + +### For User-Deployed or Per-user Admin Deployments + +These users won't see the "Teams Machine-Wide Installer" in their system. As the **New Teams Only** policy rolls out, classic Teams will be automatically uninstalled 14 days after the new Teams installation. No further action is required unless users haven't signed in for an extended period. In those cases, make sure that new Teams is deployed machine-wide to prevent users from being left without a Teams installation. + +### For Commercial Version of Microsoft 365 Apps + +The classic Teams app will be uninstalled automatically by the new Teams installation. Microsoft 365 Apps will remove the Teams Machine-Wide Installer in a future update. You should make sure that the new Teams installation isn't blocked by admin configuration. + +### For Admin-Deployed Teams Machine-Wide Installer Without Microsoft 365 Apps + +> [!CAUTION] +> Before proceeding, ensure new Teams is deployed machine-wide using the Microsoft 365 apps version or through the [Bulk upgrade to the new Microsoft Teams client](new-teams-bulk-install-client.md) option, or users may be left without a Teams client. + +Admins should use their existing deployment tools to uninstall the Teams Machine-Wide Installer. This action will trigger the uninstallation of classic Teams for each user as they sign in. + +### An example uninstall using Intune on Windows + +To uninstall an application across all devices using Intune on Windows, you can follow these steps:  + +1. Sign in to the Microsoft Endpoint Manager admin center [https://endpoint.microsoft.com/](https://endpoint.microsoft.com/). +2. Go to Devices > Windows > Windows Apps. +3. Select the **Add** button and then select **Windows app (Win32)**. +4. In the **Add app** wizard, select **App package file** and upload the .intunewin file for the application you want to uninstall. +5. In the **Detection rules** section, select **Manually configure detection rules**. +6. In the **Detection rules** section, select the **Add** button and select **File**. +7. In the **File** section, enter the path and file name of the uninstaller for the application you want to uninstall. +8. In the **Uninstall command** section, enter the command to run the uninstaller silently. For example, if the uninstaller is "uninstall.exe" and the silent switch is "/quiet", the command would be: + - "MsiExec.exe -x {731F6BAA-A986-45A4-8936-7C3AAAAA760B} /quiet" + +You can learn more at [Uninstall an app with Intune for Windows](/mem/intune/apps/apps-add). + +### Special Considerations for VDI Environments + +- For **Persistent VDI** configurations, follow the steps for admin-deployed Teams Machine-Wide Installer without Microsoft 365 Apps. +- For **Non-Persistent VDI** configurations, admins must manage the uninstallation process according to their device configuration. + +## FAQs + +- **How do I know if users still have classic Teams?** + Use your tenant dashboard or device management tools to scan for classic Teams and the Teams Machine-Wide Installer. + +- **When will classic Teams be removed automatically?** + If the policy is set to **New Teams only**, Classic Teams will be uninstalled 14 days after the new Teams installation completes, and once users receive the new Teams policy settings. If the Teams Machine-Wide Installer is present, Microsoft 365 Apps can uninstall it for each user as they sign in. + +> [!NOTE] +> If the administrator has changed policies to T2.1 Default within the 14-day period, then classic Teams will be retained. If the policy is changed after 14 days, classic Teams will need to be reinstalled by a user or an admin. + +- **How much network bandwidth is required for the new Teams update?** + The initial update is approximately 150 MB, with subsequent updates ranging from 15-30 MB. This update is automatically downloaded and installed from the internet once per device (multi-user devices do not download the binaries for each user). An admin can also choose to do an offline installation using the [bulk installer](new-teams-bulk-install-client.md). Subsequent updates should be 15-30MB, and the [MSIX app package updates](/windows/msix/desktop/managing-your-msix-deployment-update) article will have more details. + +- **How can I remove all copies of classic Teams from a multi-user device without each user signing in?** + Manual deletion is possible but not recommended as it may leave residual files. + +- **Will users be notified of the uninstallation attempt?** + No, the process is designed to be silent to minimize disruptions. + +- **Are there any workarounds for the 14-day uninstallation timer?** + No, this timer isn't configurable. Admins can use device management software, such as Intune, to directly uninstall classic Teams. + +## Future updates + +This article will be updated at a later time with additional information on: + +- Uninstalling classic Teams from macOS +- VDI-specific guidance diff --git a/Teams/teams-custom-app-policies-and-settings.md b/Teams/teams-custom-app-policies-and-settings.md index efaf449cb2..6954a6d005 100644 --- a/Teams/teams-custom-app-policies-and-settings.md +++ b/Teams/teams-custom-app-policies-and-settings.md @@ -8,7 +8,7 @@ ms.tgt.pltfrm: cloud ms.subservice: teams-apps ms.service: msteams audience: Admin -ms.date: 10/18/2023 +ms.date: 03/30/2024 ms.reviewer: mhayrapetyan ms.collection: - M365-collaboration @@ -187,6 +187,10 @@ Consider a scenario where you want to allow only team owners to upload custom ap * Turn off the **Allow members to upload custom apps** for every team to which you want to restrict access. * Create and assign a custom policy in app setup policy in admin center with the **Upload custom apps** setting turned on and assign the policy to the team owners. +## Custom apps in Gallatin and air-gapped cloud environments + +You can [upload custom apps](#upload-a-custom-app-using-teams-admin-center) in these cloud environments by the Teams apps > Manage apps page. Also, you can [update your existing custom app](#update-a-custom-app-to-a-new-version) from the app details page. + ## Related article * [Assign policies to your users in Teams](assign-policies-users-and-groups.md) diff --git a/Teams/teams-powershell-release-notes.md b/Teams/teams-powershell-release-notes.md index bdfe4e332e..0a5dbfe54e 100644 --- a/Teams/teams-powershell-release-notes.md +++ b/Teams/teams-powershell-release-notes.md @@ -26,41 +26,42 @@ This page provides the latest Teams PowerShell change log for both General Avail | Date | Version | Updates | |------- | -------------------- | ------------------------------ | +| April 2024 | [6.1.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.1.0) |
  • Adds BlockAllSubDomains parameter to the Set-CsTenantFederationConfiguration cmdlet.
  • Adds new parameters to [Set\|New]-CsCallQueue cmdlets for configuring courtesy callback.
  • Releases [Get\|New\|Set\|Grant]-CsTeamsMediaConnectivityPolicy cmdlets.
  • Releases [Get\|New\|Set\|Grant]-CsTeamsWorkLocationDetectionPolicy cmdlets.
  • [BREAKING CHANGE] Removes LocationPolicy attribute from the output of Get-CsOnlineUser cmdlet. More details in [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser).
  • Releases [Get\|New\|Remove\|Set\|Grant]-CsTeamsRecordingRollOutPolicy cmdlets.
  • Contains a new implementation of [Get\|Set]-CsTeamsEducationConfiguration. Functionality remains the same as previous implementation.
  • Adds new parameter SmsNotifications to TeamsMeetingPolicy cmdlets.
  • Adds new parameter UpdateParentInformation to TeamsEducationConfiguration cmdlets.
  • Adds new parameters to [Set\|New]-CsCallQueue cmdlets for configuring response time service level threshold.
    • | March 2024 | [6.0.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/6.0.1-preview) |
  • Adds BlockAllSubDomains parameter to the Set-CsTenantFederationConfiguration cmdlet.
  • Adds new parameters to [Set\|New]-CsCallQueue cmdlets for configuring courtesy callback.
  • Releases [Get\|New\|Set\|Grant]-CsTeamsMediaConnectivityPolicy cmdlets.
  • Releases [Get\|New\|Set\|Grant]-CsTeamsWorkLocationDetectionPolicy cmdlets.
    • | February 2024 | [6.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.0.0) |
  • Fixes expiration time related issues while using AccessTokens in Connect-MicrosoftTeams.
  • Releases Remove-CsUserLicenseGracePeriod cmdlet in private preview.
  • Adds IsInGracePeriod & GracePeriodExpiryDate to each plan in the AssignedPlan attribute in the Get-CsOnlineUser output.
    • -| January 2024 | [5.9.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.9.0) |
  • Adds support for managed identity based auth for \*-Cs cmdlets using -Identity parameter in Connect-MicrosoftTeams in commercial environments. Few [cmdlets](teams-powershell-application-authentication.md#cmdlets-supported) that don't support application-based authentication are not supported for this as well.
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support user-ful/userless update in runtime routing options for telephone numbers.
  • Releases major updates for Get-CsOnlineUser in GCC High & DoD environments with significant performance improvements and new filtering capabilities to scenarios without the "-Identity" parameter:
    • Performance improvements especially with "-Filter" scenarios like using wildcard operator (\*), OnPrem\* and Timestamp attributes.
    • Correct values will start populating in the output for CountryAbbreviation, UserValidationErrors, WhenCreated.
    • These attributes are now enabled for filtering: Alias, City, Company, HostingProvider, UserValidationErrors, OnPremEnterpriseVoiceEnabled, OnPremHostingProvider, OnPremLineURI, OnPremSIPEnabled, SipAddress, SoftDeletionTimestamp, StateOrProvince, Street, TeamsOwnersPolicy, WhenChanged, WhenCreated, FeatureTypes, PreferredDataLocation, LastName.
    • These filtering operators have been reintroduced into Get-CsOnlineUser:
      • "-like" operator now supports use of wildcard operators in 'contains' and 'ends with' scenarios. Example: Get-CsOnlineUser -Filter "DisplayName -like '\*abc\*'"
      • "-contains" can now be used for filtering on properties that are an array of strings like FeatureTypes, ProxyAddresses and ShadowProxyAddresses. Example: Get-CsOnlineUser -Filter {FeatureTypes -contains "PhoneSystem"}
      • "-gt" (greater than), "-lt" (less than) can now be used for filtering all string properties. Example: Get-CsOnlineUser -Filter {UserPrincipalName -gt/-lt "abc"}
      • "-ge" (greater than or equal to), "-gt" (greater than), "-lt" (less than), "-le" (less than or equal to) can now also be used for filtering on policies. Example: Get-CsOnlineUser - Filter {ExternalAccessPolicy -ge "xyz_policy"}
    • Updates to type of users displayed:
      • Unlicensed Users - Unlicensed users would show up in the output of Get-CsOnlineUser.
      • Soft deleted users - These users will be displayed in the output with SoftDeletionTimestamp set to a value.
      • Guest users are now available in the output.
      • [BREAKING CHANGE] IneligibleUser - AccountType as Unknown will be renamed to IneligibleUser. IneligibleUser will include users who do not have any valid Teams licenses (except Guest, SfbOnPremUser, ResourceAccount).
  • Updates Set-CsTeamsMeetingConfiguration to support enabling or disabling anonymous meeting participants to receive surveys using FeedbackSurveyForAnonymousUsers parameter.
  • Removes unused DomainController parameter from [Set\|Register\|Unregister]-CsOnlineDialInConferencingServiceNumber, Set-CsOnlineDialInConferencingBridge & Set-CsOnlineDialInConferencingUser cmdlets.
    • -| December 2023 | [5.8.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.8.1-preview) |
  • Adds support for managed identity based auth for \*-Cs cmdlets using -Identity parameter in Connect-MicrosoftTeams in commercial environments. Few [cmdlets](teams-powershell-application-authentication.md#cmdlets-supported) that don't support application-based authentication are not supported for this as well.
    • -| November 2023 | [5.8.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.8.0) |
  • Updates the Get-MultiGeoRegion cmdlet to provide PreferredDataLocation and LastMovementTimeStamp of User/Group. Also, the cmdlet is now supported without enablement of port 8653.
  • Fixes a bug in Set-Team cmdlet where setting GiphyContentRating was not working.
  • Adds ContentSharingInExternalMeetings and UseMicrosoftECDN parameters to [New\|Set]-CsTeamsMeetingPolicy.
  • Adds NumberOfResultsToSkip parameter (which was deprecated earlier) to Get-CsOnlineLisLocation and Get-CsOnlineLisCivicAddress cmdlets.
    • -| October 2023 | [5.7.2-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.7.2-preview) |
  • Updates the Get-MultiGeoRegion cmdlet to provide PreferredDataLocation and LastMovementTimeStamp of User/Group. Also, the cmdlet is now supported without enablement of port 8653.
  • Fixes a bug in Set-Team cmdlet where setting GiphyContentRating was not working.
  • Adds ContentSharingInExternalMeetings and UseMicrosoftECDN parameters to [New\|Set]-CsTeamsMeetingPolicy.
    • -| October 2023 | [5.7.1](https://www.powershellgallery.com/packages/MicrosoftTeams/5.7.1) |
  • Fixes an issue introduced in versions 5.6.1-preview & 5.7.0, due to which Get-CsTeamsMeetingConfiguration cmdlet was not present in the module.
    • -| October 2023 | [5.7.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.7.0) |
  • Removes deprecated ExternalAccessPrefix and OptimizeDeviceDialing parameters from [New\|Set]-CsTenantDialPlan cmdlets.
  • Fixes Get-CsTenantDialPlan cmdlet to return correct format of dial plan policy.
  • Adds AdministrativeUnitReference to Get-CsOnlineUser output. This is currently populated in the commercial environments only.
  • Fixes an issue with Connect-MicrosoftTeams to display the relevant TenantId, when authenticated using Managed Service Identity.
  • Fixes the error in Sync-CsOnlineApplicationInstance output.
  • Contains a new implementation of [New\|Get\|Set\|Remove\|Grant]-CsTeamsVdiPolicy cmdlets. Functionality remains the same as previous implementation.
  • Adds NumberSource output attribute to the Get-CsPhoneNumberAssignment cmdlet.
  • Adds CreateCustomEmojis and DeleteCustomEmojis parameters to [New\|Set]-CsTeamsMessagingPolicy.
  • Adds ParticipantNameChange and AutoRecording parameters to [New\|Set]-CsTeamsMeetingPolicy.
  • Fixes a bug in Get-Team cmdlet where duplicate progress record was appearing.
  • Fixes token expiry issue with Get-Team cmdlet.
  • [BREAKING CHANGE] Due to an issue, Get-CsTeamsMeetingConfiguration cmdlet is missing in versions 5.6.1-preview & 5.7.0. This issue is fixed from version 5.7.1 onwards.
    • -| October 2023 | [5.6.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.6.1-preview) |
  • Removes deprecated ExternalAccessPrefix and OptimizeDeviceDialing parameters from [New\|Set]-CsTenantDialPlan cmdlets.
  • Fixes Get-CsTenantDialPlan cmdlet to return correct format of dial plan policy.
  • Adds AdministrativeUnitReference to Get-CsOnlineUser output. This is currently populated in the commercial environments only.
  • Fixes an issue with Connect-MicrosoftTeams to display the relevant TenantId, when authenticated using Managed Service Identity.
  • Fixes the error in Sync-CsOnlineApplicationInstance output.
  • [BREAKING CHANGE] Due to an issue, Get-CsTeamsMeetingConfiguration cmdlet is missing in versions 5.6.1-preview & 5.7.0. This issue is fixed from version 5.7.1 onwards.
    • -| September 2023 | [5.6.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.6.0) |
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support NetworkSiteId of un-assigned numbers.
  • Fixes Get-CsTenantNetworkSite cmdlet error introduced in version 5.5.0.
  • Releases [Get\|Set]-CsTeamsSipDevicesConfiguration cmdlets.
  • Releases New-CsSdgBulkSignInRequest, Get-CsSdgBulkSignInRequestStatus & Get-CsSDGBulkSignInRequestsSummary cmdlets in GA.
  • Releases [New\|Get\|Set\|Remove]-CsTeamsCustomBannerText cmdlets.
  • Contains a new implementation of [Get\|Set]-CsTeamsMeetingConfiguration. Functionality remains the same as previous implementation.
  • Adds new parameters CopyRestriction, CopilotWithoutTranscript and VoiceIsolation to [New\|Set]-CsTeamsMeetingPolicy cmdlets.
  • Fixes issues with pipeline input for Grant-Cs\ cmdlets.
    • -| August 2023 | [5.5.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.5.1-preview) |
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support NetworkSiteId of un-assigned numbers.
  • Fixes Get-CsTenantNetworkSite cmdlet error introduced in version 5.5.0.
  • Releases [Get\|Set]-CsTeamsSipDevicesConfiguration cmdlets.
    • -| August 2023 | [5.5.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.5.0) |
  • Releases New-CsTeamsHiddenTemplate cmdlet.
  • Releases [New\|Get\|Set\|Remove]-CsTeamsTemplatePermissionPolicy cmdlets.
  • Adds a new parameter -IncludePhoneNumbers to Get-CsTenantNetworkSite.
  • [BREAKING CHANGE] Deprecates EnableShiftPresence parameter from TeamsShiftsPolicy.
  • Contains a new implementation of [Get\|Set]-CsTeamsUpgradeConfiguration, [Get\|Set\|Remove\|New]-CsTeamsComplianceRecordingPolicy, [Get\|Set\|Remove\|New]-CsTeamsComplianceRecordingApplication, New-CsTeamsComplianceRecordingPairedApplication. Functionality remains the same as previous implementation.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsSharedCallingRoutingPolicy cmdlets.
  • [BREAKING CHANGE] Get-CsTenantNetworkSite cmdlet has an unintended issue and throws error "Provided type NetworkSiteType is not valid". It is suggested to use versions greater than 5.5.0 to mitigate this issue.
    • +| January 2024 | [5.9.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.9.0) |
  • Adds support for managed identity based auth for \*-Cs cmdlets using -Identity parameter in Connect-MicrosoftTeams in commercial environments. Few [cmdlets](teams-powershell-application-authentication.md#cmdlets-supported) that don't support application-based authentication aren't supported for this method as well.
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support user-ful/userless update in runtime routing options for telephone numbers.
  • Releases major updates for Get-CsOnlineUser in GCC High & DoD environments with significant performance improvements and new filtering capabilities to scenarios without the "-Identity" parameter:
    • Performance improvements especially with "-Filter" scenarios like using wildcard operator (\*), OnPrem\*, and Timestamp attributes.
    • Correct values start populating in the output for CountryAbbreviation, UserValidationErrors, WhenCreated.
    • These attributes are now enabled for filtering: Alias, City, Company, HostingProvider, UserValidationErrors, OnPremEnterpriseVoiceEnabled, OnPremHostingProvider, OnPremLineURI, OnPremSIPEnabled, SipAddress, SoftDeletionTimestamp, StateOrProvince, Street, TeamsOwnersPolicy, WhenChanged, WhenCreated, FeatureTypes, PreferredDataLocation, LastName.
    • These filtering operators are reintroduced into Get-CsOnlineUser:
      • "-like" operator now supports use of wildcard operators in 'contains' and 'ends with' scenarios. Example: Get-CsOnlineUser -Filter "DisplayName -like '\*abc\*'"
      • "-contains" can now be used for filtering on properties that are an array of strings like FeatureTypes, ProxyAddresses, and ShadowProxyAddresses. Example: Get-CsOnlineUser -Filter {FeatureTypes -contains "PhoneSystem"}
      • "-gt" (greater than), "-lt" (less than) can now be used for filtering all string properties. Example: Get-CsOnlineUser -Filter {UserPrincipalName -gt/-lt "abc"}
      • "-ge" (greater than or equal to), "-gt" (greater than), "-lt" (less than), "-le" (less than or equal to) can now also be used for filtering on policies. Example: Get-CsOnlineUser - Filter {ExternalAccessPolicy -ge "xyz_policy"}
    • Updates to type of users displayed:
      • Unlicensed Users - Unlicensed users would show up in the output of Get-CsOnlineUser.
      • Soft deleted users - These users are displayed in the output with SoftDeletionTimestamp set to a value.
      • Guest users are now available in the output.
      • [BREAKING CHANGE] IneligibleUser - AccountType as Unknown is renamed to IneligibleUser. IneligibleUser includes users who don't have any valid Teams licenses (except Guest, SfbOnPremUser, ResourceAccount).
  • Updates Set-CsTeamsMeetingConfiguration to support enabling or disabling anonymous meeting participants to receive surveys using FeedbackSurveyForAnonymousUsers parameter.
  • Removes unused DomainController parameter from [Set\|Register\|Unregister]-CsOnlineDialInConferencingServiceNumber, Set-CsOnlineDialInConferencingBridge & Set-CsOnlineDialInConferencingUser cmdlets.
    • +| December 2023 | [5.8.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.8.1-preview) |
  • Adds support for managed identity based auth for \*-Cs cmdlets using -Identity parameter in Connect-MicrosoftTeams in commercial environments. Few [cmdlets](teams-powershell-application-authentication.md#cmdlets-supported) that don't support application-based authentication aren't supported for this method as well.
    • +| November 2023 | [5.8.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.8.0) |
  • Updates the Get-MultiGeoRegion cmdlet to provide PreferredDataLocation and LastMovementTimeStamp of User/Group. Also, the cmdlet is now supported without enablement of port 8653.
  • Fixes a bug in Set-Team cmdlet where setting GiphyContentRating wasn't working.
  • Adds ContentSharingInExternalMeetings and UseMicrosoftECDN parameters to [New\|Set]-CsTeamsMeetingPolicy.
  • Adds NumberOfResultsToSkip parameter (which was deprecated earlier) to Get-CsOnlineLisLocation and Get-CsOnlineLisCivicAddress cmdlets.
    • +| October 2023 | [5.7.2-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.7.2-preview) |
  • Updates the Get-MultiGeoRegion cmdlet to provide PreferredDataLocation and LastMovementTimeStamp of User/Group. Also, the cmdlet is now supported without enablement of port 8653.
  • Fixes a bug in Set-Team cmdlet, where setting GiphyContentRating wasn't working.
  • Adds ContentSharingInExternalMeetings and UseMicrosoftECDN parameters to [New\|Set]-CsTeamsMeetingPolicy.
    • +| October 2023 | [5.7.1](https://www.powershellgallery.com/packages/MicrosoftTeams/5.7.1) |
  • Fixes an issue introduced in versions 5.6.1-preview & 5.7.0, due to which Get-CsTeamsMeetingConfiguration cmdlet wasn't present in the module.
    • +| October 2023 | [5.7.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.7.0) |
  • Removes deprecated ExternalAccessPrefix and OptimizeDeviceDialing parameters from [New\|Set]-CsTenantDialPlan cmdlets.
  • Fixes Get-CsTenantDialPlan cmdlet to return correct format of dial plan policy.
  • Adds AdministrativeUnitReference to Get-CsOnlineUser output. This attribute is currently populated in the commercial environments only.
  • Fixes an issue with Connect-MicrosoftTeams to display the relevant TenantId, when authenticated using Managed Service Identity.
  • Fixes the error in Sync-CsOnlineApplicationInstance output.
  • Contains a new implementation of [New\|Get\|Set\|Remove\|Grant]-CsTeamsVdiPolicy cmdlets. Functionality remains the same as previous implementation.
  • Adds NumberSource output attribute to the Get-CsPhoneNumberAssignment cmdlet.
  • Adds CreateCustomEmojis and DeleteCustomEmojis parameters to [New\|Set]-CsTeamsMessagingPolicy.
  • Adds ParticipantNameChange and AutoRecording parameters to [New\|Set]-CsTeamsMeetingPolicy.
  • Fixes a bug in Get-Team cmdlet where duplicate progress record was appearing.
  • Fixes token expiry issue with Get-Team cmdlet.
  • [BREAKING CHANGE] Due to an issue, Get-CsTeamsMeetingConfiguration cmdlet is missing in versions 5.6.1-preview & 5.7.0. This issue is fixed from version 5.7.1 onwards.
    • +| October 2023 | [5.6.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.6.1-preview) |
  • Removes deprecated ExternalAccessPrefix and OptimizeDeviceDialing parameters from [New\|Set]-CsTenantDialPlan cmdlets.
  • Fixes Get-CsTenantDialPlan cmdlet to return correct format of dial plan policy.
  • Adds AdministrativeUnitReference to Get-CsOnlineUser output. This attribute is currently populated in the commercial environments only.
  • Fixes an issue with Connect-MicrosoftTeams to display the relevant TenantId, when authenticated using Managed Service Identity.
  • Fixes the error in Sync-CsOnlineApplicationInstance output.
  • [BREAKING CHANGE] Due to an issue, Get-CsTeamsMeetingConfiguration cmdlet is missing in versions 5.6.1-preview & 5.7.0. This issue is fixed from version 5.7.1 onwards.
    • +| September 2023 | [5.6.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.6.0) |
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support NetworkSiteId of unassigned numbers.
  • Fixes Get-CsTenantNetworkSite cmdlet error introduced in version 5.5.0.
  • Releases [Get\|Set]-CsTeamsSipDevicesConfiguration cmdlets.
  • Releases New-CsSdgBulkSignInRequest, Get-CsSdgBulkSignInRequestStatus & Get-CsSDGBulkSignInRequestsSummary cmdlets in GA.
  • Releases [New\|Get\|Set\|Remove]-CsTeamsCustomBannerText cmdlets.
  • Contains a new implementation of [Get\|Set]-CsTeamsMeetingConfiguration. Functionality remains the same as previous implementation.
  • Adds new parameters CopyRestriction, CopilotWithoutTranscript, and VoiceIsolation to [New\|Set]-CsTeamsMeetingPolicy cmdlets.
  • Fixes issues with pipeline input for Grant-Cs\ cmdlets.
    • +| August 2023 | [5.5.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.5.1-preview) |
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support NetworkSiteId of unassigned numbers.
  • Fixes Get-CsTenantNetworkSite cmdlet error introduced in version 5.5.0.
  • Releases [Get\|Set]-CsTeamsSipDevicesConfiguration cmdlets.
    • +| August 2023 | [5.5.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.5.0) |
  • Releases New-CsTeamsHiddenTemplate cmdlet.
  • Releases [New\|Get\|Set\|Remove]-CsTeamsTemplatePermissionPolicy cmdlets.
  • Adds a new parameter -IncludePhoneNumbers to Get-CsTenantNetworkSite.
  • [BREAKING CHANGE] Deprecates EnableShiftPresence parameter from TeamsShiftsPolicy.
  • Contains a new implementation of [Get\|Set]-CsTeamsUpgradeConfiguration, [Get\|Set\|Remove\|New]-CsTeamsComplianceRecordingPolicy, [Get\|Set\|Remove\|New]-CsTeamsComplianceRecordingApplication, New-CsTeamsComplianceRecordingPairedApplication. Functionality remains the same as previous implementation.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsSharedCallingRoutingPolicy cmdlets.
  • [BREAKING CHANGE] Get-CsTenantNetworkSite cmdlet has an unintended issue and throws error "Provided type NetworkSiteType is not valid". Use versions 5.5.0 or later to mitigate this issue.
    • | July 2023 | [5.4.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.4.0) |
  • Fixes the issue with few scenarios like Set-CsUser, OnPrem to Cloud migrations etc. These scenarios had an unintended issue in versions 5.3.0, 5.2.1-preview & 5.3.1-preview where errors like "Forest header can’t be null" were seen.
  • Adds State output attribute to Get-CsTeamsShiftsConnectionTeamMap cmdlet.
  • Releases Remove-CsTeamsShiftsConnection cmdlet.
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support AssignmentCategory.
  • Updates Set-CsPhoneNumberAssignment to support location update of unassigned numbers.
    • -| July 2023 | [5.3.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.3.1-preview) |
  • [BREAKING CHANGE] Few cmdlets (like Set-CsUser) have an unintended issue in versions 5.3.0, 5.2.1-preview & 5.3.1-preview where errors like “Forest header can’t be null” is seen. It's suggested to use 5.4.0 to mitigate this issue.
  • Adds State output attribute to Get-CsTeamsShiftsConnectionTeamMap cmdlet.
  • Releases Remove-CsTeamsShiftsConnection cmdlet.
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support AssignmentCategory.
  • Updates Set-CsPhoneNumberAssignment to support location update of unassigned numbers.
    • -| June 2023 | [5.3.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.3.0) |
  • [BREAKING CHANGE] Few cmdlets (like Set-CsUser) have an unintended issue in versions 5.3.0, 5.2.1-preview & 5.3.1-preview where errors like “Forest header can’t be null” is seen. It's suggested to use 5.4.0 to mitigate this issue.
  • [BREAKING CHANGE] Adds State parameter & output attribute to [New\|Get\|Set\|Update]-CsTeamsShiftsConnection and [New\|Get\|Set\|Update]-CsTeamsShiftsConnectionInstance cmdlets.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsMeetingTemplatePermissionPolicy cmdlets.
  • Releases Get-CsTeamsMeetingTemplateConfiguration cmdlet.
  • Releases Get-CsTeamsFirstPartyMeetingTemplateConfiguration cmdlet.
  • Release New-CsTeamsHiddenMeetingTemplate cmdlet.
  • Adds new parameters to the Set-CsCallQueue and New-CsCallQueue Cmdlets to enable users to set No Agent Opt In/Logged In options for call handling in Call Queue. New parameters are added for No Agent disconnect/redirection options, target, shared voicemail prompts and whether to enable shared voicemail system prompt suppression and transcription.
    • -| May 2023 | [5.2.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.2.1-preview) |
  • [BREAKING CHANGE] Few cmdlets (like Set-CsUser) have an unintended issue in versions 5.3.0, 5.2.1-preview & 5.3.1-preview where errors like “Forest header can’t be null” is seen. It's suggested to use 5.4.0 to mitigate this issue.
  • [BREAKING CHANGE] Adds State parameter & output attribute to [New\|Get\|Set\|Update]-CsTeamsShiftsConnection and [New\|Get\|Set\|Update]-CsTeamsShiftsConnectionInstance cmdlets.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsMeetingTemplatePermissionPolicy cmdlets.
  • Releases Get-CsTeamsMeetingTemplateConfiguration cmdlet.
  • Releases Get-CsTeamsFirstPartyMeetingTemplateConfiguration cmdlet.
  • Release New-CsTeamsHiddenMeetingTemplate cmdlet.
    • +| July 2023 | [5.3.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.3.1-preview) |
  • [BREAKING CHANGE] Few cmdlets (like Set-CsUser) have an unintended issue in versions 5.3.0, 5.2.1-preview & 5.3.1-preview where errors like "Forest header can’t be null" is seen. Use 5.4.0 or later to mitigate this issue.
  • Adds State output attribute to Get-CsTeamsShiftsConnectionTeamMap cmdlet.
  • Releases Remove-CsTeamsShiftsConnection cmdlet.
  • Updates [Set\|Get]-CsPhoneNumberAssignment to support AssignmentCategory.
  • Updates Set-CsPhoneNumberAssignment to support location update of unassigned numbers.
    • +| June 2023 | [5.3.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.3.0) |
  • [BREAKING CHANGE] Few cmdlets (like Set-CsUser) have an unintended issue in versions 5.3.0, 5.2.1-preview & 5.3.1-preview where errors like "Forest header can’t be null" is seen. Use 5.4.0 or later to mitigate this issue.
  • [BREAKING CHANGE] Adds State parameter & output attribute to [New\|Get\|Set\|Update]-CsTeamsShiftsConnection and [New\|Get\|Set\|Update]-CsTeamsShiftsConnectionInstance cmdlets.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsMeetingTemplatePermissionPolicy cmdlets.
  • Releases Get-CsTeamsMeetingTemplateConfiguration cmdlet.
  • Releases Get-CsTeamsFirstPartyMeetingTemplateConfiguration cmdlet.
  • Release New-CsTeamsHiddenMeetingTemplate cmdlet.
  • Adds new parameters to the Set-CsCallQueue and New-CsCallQueue Cmdlets to enable users to set No Agent Opt In/Logged In options for call handling in Call Queue. New parameters are added for No Agent disconnect/redirection options, target, shared voicemail prompts and whether to enable shared voicemail system prompt suppression and transcription.
    • +| May 2023 | [5.2.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.2.1-preview) |
  • [BREAKING CHANGE] Few cmdlets (like Set-CsUser) have an unintended issue in versions 5.3.0, 5.2.1-preview & 5.3.1-preview where errors like "Forest header can’t be null" is seen. Use 5.4.0 or later to mitigate this issue.
  • [BREAKING CHANGE] Adds State parameter & output attribute to [New\|Get\|Set\|Update]-CsTeamsShiftsConnection and [New\|Get\|Set\|Update]-CsTeamsShiftsConnectionInstance cmdlets.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsMeetingTemplatePermissionPolicy cmdlets.
  • Releases Get-CsTeamsMeetingTemplateConfiguration cmdlet.
  • Releases Get-CsTeamsFirstPartyMeetingTemplateConfiguration cmdlet.
  • Release New-CsTeamsHiddenMeetingTemplate cmdlet.
    • | May 2023 | [5.2.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.2.0) |
  • Contains a new implementation of [New\|Get\|Set\|Remove\|Grant]-CsTeamsAppPermissionPolicy, [New\|Get\|Set\|Remove\|Grant]-CsTeamsAppSetupPolicy, [New\|Get\|Set\|Remove\|Grant]-CsTeamsEventsPolicy, [New\|Get\|Set\|Remove\|Grant]-CsExternalAccessPolicy, [New\|Get\|Set\|Remove\|Grant]-CsTeamsCallingPolicy. Functionality remains the same as previous implementation.
  • [BREAKING CHANGE] Updates Teams Shifts Connection cmdlets to separate connections and connection instances. The following changes apply as part of it:
    • Releases [New\|Get\|Set\|Update]-CsTeamsShiftsConnection cmdlets.
    • Updates [New\|Set\|Update]-CsTeamsShiftsConnectionInstance cmdlets. Added ConnectionId & individual sync scenario parameters. Removed EnabledConnectorScenario, EnabledWfiScenario & ConnectorId parameters. Returns updated connection instance object.
    • Updates Get-CsTeamsShiftsConnectionInstance cmdlet. Returns updated connection instance object.
    • Updates Get-CsTeamsShiftsConnectionErrorReport. Added ConnectionId parameter.
    • Updates Get-CsTeamsShiftsConnectionWfmTeam. Added ConnectionId parameter.
    • Updates Get-CsTeamsShiftsConnectionConnector cmdlet. Returns updated supported connectors object.
    • Removed New-CsTeamsShiftsConnectionTeamMap cmdlet.
  • Updates [New\|Set]-CsAutoAttendant, [New\|Set]-CsCallQueue cmdlets. Added HideAuthorizedUsers parameter.
  • Releases [Set\|Clear]-TeamsEnvironmentConfig cmdlets.
  • Releases [Get\|Set]-CsTeamsSettingsCustomApp cmdlets.
  • Fixes ComplianceRecordingPolicy and ComplianceRecordingApplication cmdlets.
    • | April 2023 | [5.1.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.1.1-preview) |
  • [BREAKING CHANGE] ComplianceRecordingPolicy and ComplianceRecordingApplication cmdlets are being migrated to a new implementation. Currently, MicrosoftTeams versions 5.0.1-preview, 5.1.0-GA, 5.1.1-preview aren't working for these cmdlets. Use versions <= 5.0.0 or versions >= 5.2.0-GA.
  • Adds Region parameter in the New-CsSdgBulkSignInRequest cmdlet in private preview.
  • Contains a new implementation of [New\|Get\|Set\|Remove\|Grant]-CsTeamsAppPermissionPolicy, [New\|Get\|Set\|Remove\|Grant]-CsTeamsAppSetupPolicy, [New\|Get\|Set\|Remove\|Grant]-CsTeamsEventsPolicy, [New\|Get\|Set\|Remove\|Grant]-CsExternalAccessPolicy, [New\|Get\|Set\|Remove\|Grant]-CsTeamsCallingPolicy. Functionality remains the same as previous implementation.
    • -| March 2023 | [5.1.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.1.0) |
  • [BREAKING CHANGE] ComplianceRecordingPolicy and ComplianceRecordingApplication cmdlets are being migrated to a new implementation. Currently, MicrosoftTeams versions 5.0.1-preview, 5.1.0-GA, 5.1.1-preview aren't working for these cmdlets. Use versions <= 5.0.0 or versions >= 5.2.0-GA.
  • [BREAKING CHANGE] Modernized versions of Get-CsOnlineUser & Get-CsOnlineVoiceUser are now being rolled out for GCC High & DoD environments as well. The following changes apply as part of it:
    • Input Parameters that aren't relevant to Teams are deprecated.
    • Output attributes:
      • A few attributes have been renamed for better relevance and consistency.
      • Attributes that aren't relevant to Teams are deprecated.
      • Format types of attributes have been improved.
    • Within the "-Filter" parameter for Get-CsOnlineUser, a few attributes and operators are no longer supported.
    • More details in [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser) & [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
  • Adds TeamsEventsPolicy to Get-CsOnlineUser output.
  • Updates ProvisionedPlan attribute in Get-CsOnlineUser output. ProvisionedPlan now includes useful information such as AssignedTimestamp, ServiceInstance, Capability, ServicePlanId, SubscribedPlanId, ProvisionedTimestamp. These values are populated currently for tenants in commercial environments only.
  • Adds Force parameter to Grant-CsTeamsUpgradePolicy.
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsVoiceApplicationsPolicy, [Get\|Set]-CsTeamsMessagingConfiguration,[New\|Get\|Set\|Remove]-CsTeamsComplianceRecordingPolicy. Functionality remains the same as previous implementation.
  • Adds RequireBackgroundEffect parameter to [New\|Get\|Set\|Remove]-CsTeamsMeetingBrandingPolicy.
  • Adds AllowTownhalls and AllowEmailEditing parameter to [New\|Get\|Set\|Remove]-CsTeamsEventPolicy.
  • Adds AllowWatermarkCustomizationForCameraVideo, WatermarkForCameraVideoOpacity, WatermarkForCameraVideoPattern, AllowWatermarkCustomizationForScreenSharing, WatermarkForScreenSharingOpacity, WatermarkForScreenSharingPattern parameters to [New\|Get\|Set\|Remove]-CsTeamsMeetingPolicy.
  • Adds EnableInOrganizationChatControl parameter to [Get\|Set]-CsTeamsMessagingConfiguration.
  • Adds InOrganizationChatControl parameter to [New\|Get\|Set\|Remove]-CsTeamsMessagingPolicy.
  • Adds InboundPstnCallRoutingTreatment and InboundFederatedCallRoutingTreatment parameters to [New\|Get\|Set\|Remove]-CsTeamsCallingPolicy.
  • Adds OrderBy (alias: Sort) parameter to Get-CsOnlineUser to enable ordering of users by property values. This parameter currently works for tenants in commercial environments only.
  • Adds new parameters to the Set-CsCallQueue and New-CsCallQueue cmdlets to enable users to set Audio file or Text to Speech Prompts when calls in Call Queue are disconnected or redirected due to overflow, timeout or when no agents are available. New parameters are added for call disconnect, redirect to user, voice app, external PSTN and personal voicemail.
    • -| March 2023 | [5.0.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.0.1-preview) |
  • [BREAKING CHANGE] ComplianceRecordingPolicy and ComplianceRecordingApplication cmdlets are being migrated to a new implementation. Currently, MicrosoftTeams versions 5.0.1-preview, 5.1.0-GA, 5.1.1-preview aren't working for these cmdlets. Use versions <= 5.0.0 or versions >= 5.2.0-GA.
  • [BREAKING CHANGE] Modernized versions of Get-CsOnlineUser & Get-CsOnlineVoiceUser are now being rolled out for GCC High & DoD environments as well. The following changes apply as part of it:
    • Input Parameters that aren't relevant to Teams are deprecated.
    • Output attributes:
      • A few attributes have been renamed for better relevance and consistency.
      • Attributes that aren't relevant to Teams are deprecated.
      • Format types of attributes have been improved.
    • Within the "-Filter" parameter for Get-CsOnlineUser, a few attributes and operators are no longer supported.
    • More details in [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser) & [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
  • Adds TeamsEventsPolicy to Get-CsOnlineUser output.
  • Updates ProvisionedPlan attribute in Get-CsOnlineUser output. ProvisionedPlan now includes useful information such as AssignedTimestamp, ServiceInstance, Capability, ServicePlanId, SubscribedPlanId, ProvisionedTimestamp. These values are populated currently for tenants in commercial environments only.
  • Adds Force parameter to Grant-CsTeamsUpgradePolicy.
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsVoiceApplicationsPolicy, [Get\|Set]-CsTeamsMessagingConfiguration. Functionality remains the same as previous implementation.
    • -| March 2023 | [5.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.0.0) |
  • Releases major updates for Get-CsOnlineUser with significant performance improvements and new filtering capabilities to scenarios without the "-Identity" parameter (currently rolled out in commercial environments):
    • Performance improvements especially with "-Filter" scenarios like using wildcard operator (\*), OnPrem\* and Timestamp attributes.
    • New attributes have now been introduced in the output to ensure parity with scenarios involving the "-Identity" parameter: CountryAbbreviation, SipProxyAddress, TeamsMediaLoggingPolicy, UserValidationErrors, WhenCreated.
    • These attributes are now enabled for filtering: Alias, City, CompanyName, CompanyName, HostingProvider, UserValidationErrors, OnPremEnterpriseVoiceEnabled, OnPremHostingProvider, OnPremLineURI, OnPremSIPEnabled, SipAddress, SoftDeletionTimestamp, State, Street, TeamsOwnersPolicy, WhenChanged, WhenCreated, FeatureTypes, PreferredDataLocation, LastName.
    • These filtering operators have been reintroduced into Get-CsOnlineUser:
      • "-like" operator now supports use of wildcard operators in 'contains' and 'ends with' scenarios. Example: Get-CsOnlineUser -Filter "DisplayName -like 'abc'"
      • "-contains" can now be used for filtering on properties that are an array of strings like FeatureTypes, ProxyAddresses and ShadowProxyAddresses. Example: Get-CsOnlineUser -Filter {FeatureTypes -contains "PhoneSystem"}
      • "-gt" (greater than), "-lt" (less than), "-le" (less than or equal to) can now be used for filtering all string properties. Example: Get-CsOnlineUser -Filter {UserPrincipalName -gt/-le/-lt "abc"}
      • "-ge" (greater than or equal to) can now also be used for filtering on policies. Example: Get-CsOnlineUser -Filter {ExternalAccessPolicy -ge "xyz_policy"}
    • Updates to type of users displayed:
      • Unlicensed Users - Unlicensed users would show up in the output for 30 days post license removal.
      • Soft deleted users - These users are displayed in the output with SoftDeletionTimestamp set to a value.
    +| March 2023 | [5.1.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.1.0) |
  • [BREAKING CHANGE] ComplianceRecordingPolicy and ComplianceRecordingApplication cmdlets are being migrated to a new implementation. Currently, MicrosoftTeams versions 5.0.1-preview, 5.1.0-GA, 5.1.1-preview aren't working for these cmdlets. Use versions <= 5.0.0 or versions >= 5.2.0-GA.
  • [BREAKING CHANGE] Modernized versions of Get-CsOnlineUser & Get-CsOnlineVoiceUser are now being rolled out for GCC High & DoD environments as well. The following changes apply as part of it:
    • Input Parameters that aren't relevant to Teams are deprecated.
    • Output attributes:
      • Few attributes are renamed for better relevance and consistency.
      • Attributes that aren't relevant to Teams are deprecated.
      • Format types of attributes are improved.
    • Within the "-Filter" parameter for Get-CsOnlineUser, a few attributes and operators are no longer supported.
    • More details in [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser) & [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
  • Adds TeamsEventsPolicy to Get-CsOnlineUser output.
  • Updates ProvisionedPlan attribute in Get-CsOnlineUser output. ProvisionedPlan now includes useful information such as AssignedTimestamp, ServiceInstance, Capability, ServicePlanId, SubscribedPlanId, ProvisionedTimestamp. These values are populated currently for tenants in commercial environments only.
  • Adds Force parameter to Grant-CsTeamsUpgradePolicy.
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsVoiceApplicationsPolicy, [Get\|Set]-CsTeamsMessagingConfiguration,[New\|Get\|Set\|Remove]-CsTeamsComplianceRecordingPolicy. Functionality remains the same as previous implementation.
  • Adds RequireBackgroundEffect parameter to [New\|Get\|Set\|Remove]-CsTeamsMeetingBrandingPolicy.
  • Adds AllowTownhalls and AllowEmailEditing parameter to [New\|Get\|Set\|Remove]-CsTeamsEventPolicy.
  • Adds AllowWatermarkCustomizationForCameraVideo, WatermarkForCameraVideoOpacity, WatermarkForCameraVideoPattern, AllowWatermarkCustomizationForScreenSharing, WatermarkForScreenSharingOpacity, WatermarkForScreenSharingPattern parameters to [New\|Get\|Set\|Remove]-CsTeamsMeetingPolicy.
  • Adds EnableInOrganizationChatControl parameter to [Get\|Set]-CsTeamsMessagingConfiguration.
  • Adds InOrganizationChatControl parameter to [New\|Get\|Set\|Remove]-CsTeamsMessagingPolicy.
  • Adds InboundPstnCallRoutingTreatment and InboundFederatedCallRoutingTreatment parameters to [New\|Get\|Set\|Remove]-CsTeamsCallingPolicy.
  • Adds OrderBy (alias: Sort) parameter to Get-CsOnlineUser to enable ordering of users by property values. This parameter currently works for tenants in commercial environments only.
  • Adds new parameters to the Set-CsCallQueue and New-CsCallQueue cmdlets to enable users to set Audio file or Text to Speech Prompts when calls in Call Queue are disconnected or redirected due to overflow, timeout or when no agents are available. New parameters are added for call disconnect, redirect to user, voice app, external PSTN, and personal voicemail.
    • +| March 2023 | [5.0.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/5.0.1-preview) |
  • [BREAKING CHANGE] ComplianceRecordingPolicy and ComplianceRecordingApplication cmdlets are being migrated to a new implementation. Currently, MicrosoftTeams versions 5.0.1-preview, 5.1.0-GA, 5.1.1-preview aren't working for these cmdlets. Use versions <= 5.0.0 or versions >= 5.2.0-GA.
  • [BREAKING CHANGE] Modernized versions of Get-CsOnlineUser & Get-CsOnlineVoiceUser are now being rolled out for GCC High & DoD environments as well. The following changes apply as part of it:
    • Input Parameters that aren't relevant to Teams are deprecated.
    • Output attributes:
      • Few attributes are renamed for better relevance and consistency.
      • Attributes that aren't relevant to Teams are deprecated.
      • Format types of attributes are improved.
    • Within the "-Filter" parameter for Get-CsOnlineUser, a few attributes and operators are no longer supported.
    • More details in [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser) & [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
  • Adds TeamsEventsPolicy to Get-CsOnlineUser output.
  • Updates ProvisionedPlan attribute in Get-CsOnlineUser output. ProvisionedPlan now includes useful information such as AssignedTimestamp, ServiceInstance, Capability, ServicePlanId, SubscribedPlanId, ProvisionedTimestamp. These values are populated currently for tenants in commercial environments only.
  • Adds Force parameter to Grant-CsTeamsUpgradePolicy.
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsVoiceApplicationsPolicy, [Get\|Set]-CsTeamsMessagingConfiguration. Functionality remains the same as previous implementation.
    • +| March 2023 | [5.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/5.0.0) |
  • Releases major updates for Get-CsOnlineUser with significant performance improvements and new filtering capabilities to scenarios without the "-Identity" parameter (currently rolled out in commercial environments):
    • Performance improvements especially with "-Filter" scenarios like using wildcard operator (\*), OnPrem\*, and Timestamp attributes.
    • New attributes are introduced in the output to ensure parity with scenarios involving the "-Identity" parameter: CountryAbbreviation, SipProxyAddress, TeamsMediaLoggingPolicy, UserValidationErrors, WhenCreated.
    • These attributes are now enabled for filtering: Alias, City, CompanyName, CompanyName, HostingProvider, UserValidationErrors, OnPremEnterpriseVoiceEnabled, OnPremHostingProvider, OnPremLineURI, OnPremSIPEnabled, SipAddress, SoftDeletionTimestamp, State, Street, TeamsOwnersPolicy, WhenChanged, WhenCreated, FeatureTypes, PreferredDataLocation, LastName.
    • These filtering operators are reintroduced into Get-CsOnlineUser:
      • "-like" operator now supports use of wildcard operators in 'contains' and 'ends with' scenarios. Example: Get-CsOnlineUser -Filter "DisplayName -like 'abc'"
      • "-contains" can now be used for filtering on properties that are an array of strings like FeatureTypes, ProxyAddresses, and ShadowProxyAddresses. Example: Get-CsOnlineUser -Filter {FeatureTypes -contains "PhoneSystem"}
      • "-gt" (greater than), "-lt" (less than), "-le" (less than or equal to) can now be used for filtering all string properties. Example: Get-CsOnlineUser -Filter {UserPrincipalName -gt/-le/-lt "abc"}
      • "-ge" (greater than or equal to) can now also be used for filtering on policies. Example: Get-CsOnlineUser -Filter {ExternalAccessPolicy -ge "xyz_policy"}
    • Updates to type of users displayed:
      • Unlicensed Users - Unlicensed users would show up in the output for 30 days post license removal.
      • Soft deleted users - These users are displayed in the output with SoftDeletionTimestamp set to a value.
    | February 2023 | [4.9.4-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.9.4-preview) |
  • Releases Get-CsSDGBulkSignInRequestsSummary cmdlet in private preview.
  • Adds Region attribute to Get-CsSdgBulkSignInRequestStatus output.
    • | January 2023 | [4.9.3](https://www.powershellgallery.com/packages/MicrosoftTeams/4.9.3) |
  • Adds Certificate parameter to Connect-MicrosoftTeams.
  • Adds WelcomeTextToSpeechPrompt parameter to [New\|Set]-CsCallQueue.
  • Fixes issues with pipeline input for Test-CsEffectiveTenantDialPlan & Test-CsVoiceNormalizationRule cmdlets.
  • Releases [Get\|Set\|Grant\|Remove\|New]-CsTeamsMeetingBrandingPolicy cmdlets.
  • In CsTeamsMeetingBrandingPolicy cmdlets, there's a known issue that prevents using the 'Remove' list modifier when trying to delete a TeamsMeetingBrandingTheme or a NdiAssuranceSlate. To remove all elements from MeetingBrandingThemes, the workaround is setting the values to null, example: Set-CsTeamsMeetingBrandingPolicy -Identity \ -MeetingBrandingThemes $null -DefaultTheme "".
    • To update the MeetingBrandingThemes, use the [Set]-CsTeamsMeetingBrandingPolicy cmdlet and pass the list of desired MeetingBrandingThemes created with the [New]-CsTeamsMeetingBrandingTheme cmdlet. Example: $exampleMeetingBrandingTheme = New-CsTeamsMeetingBrandingTheme -DisplayName "exampleTheme" -LogoImageLightUri "https://contoso.com/light.jpg" -LogoImageDarkUri "https://contoso.com/dark.jpg" -BackgroundImageLightUri "https://contoso.com/backgroundlight.jpg" -BackgroundImageDarkUri "https://contoso.com/backgrounddark.jpg" -BrandAccentColor "#000000" -Enabled $true -Identity "exampleTheme"
    • And then set the themes using the Set cmdlet: Set-CsTeamsMeetingBrandingPolicy -Identity \ -MeetingBrandingThemes @($exampleMeetingBrandingTheme) -DefaultTheme "exampleTheme"
    • Use the same approach for removing elements from NdiAssuranceSlate, using the [New]-CsTeamsNdiAssuranceSlate cmdlet and then using Set-CsTeamsMeetingBrandingPolicy to properly set the values.
    • This issue will be fixed in the next version.
  • Releases [New]-CsTeamsMeetingBackgroundImage cmdlet.
  • Releases [New]-CsTeamsMeetingBrandingTheme cmdlet.
  • Releases [New]-CsTeamsNdiAssuranceSlate cmdlet.
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsCallHoldPolicy, [New\|Get\|Set\|Remove]-CsTeamsEmergencyCallingPolicy, [New]-CsTeamsEmergencyCallingExtendedNotification. Functionality remains the same as previous implementation.
    • | January 2023 | [4.9.2-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.9.2-preview) |
  • Releases Get-CsSdgBulkSignInRequestStatus & New-CsSdgBulkSignInRequest cmdlets in private preview.
  • Adds Certificate parameter to Connect-MicrosoftTeams.
  • Adds WelcomeTextToSpeechPrompt parameter to [New\|Set]-CsCallQueue.
  • Fixes issues with pipeline input for Test-CsEffectiveTenantDialPlan & Test-CsVoiceNormalizationRule cmdlets.
    • -| November 2022 | [4.9.1](https://www.powershellgallery.com/packages/MicrosoftTeams/4.9.1) |
  • Releases Application-based authentication support in Connect-MicrosoftTeams in GA. More details in [Application-based authentication in Teams PowerShell Module](teams-powershell-application-authentication.md).
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsChannelsPolicy and [New\|Get\|Set\|Remove]-CsTeamsUpdateManagementPolicy. Functionality remains the same as previous implementation.
  • Adds UseNewTeamsClient parameter to TeamsUpdateManagementPolicy.
  • Adds EnablePrivateTeamDiscovery parameter to TeamsChannelsPolicy.
  • Fixes issues with authentication token not refreshing for some policy cmdlets.
  • Fixes issues where display format was broken for some cmdlets.
  • Adds SipProxyAddress, TeamsMediaLoggingPolicy, CountryAbbreviation, UserValidationErrors and WhenCreated attributes in Get-CsOnlineUser output when run without -Identity parameter. Out of these attributes, CountryAbbreviation, UserValidationErros and WhenCreated don't show any values yet. These updates are gradually rolled out, more details in [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser).
  • Fixes Add-TeamChannelUser & Remove-TeamChannelUser to take UPN for -User parameter to manage external members in a shared channel.
    • +| November 2022 | [4.9.1](https://www.powershellgallery.com/packages/MicrosoftTeams/4.9.1) |
  • Releases Application-based authentication support in Connect-MicrosoftTeams in GA. More details in [Application-based authentication in Teams PowerShell Module](teams-powershell-application-authentication.md).
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsChannelsPolicy and [New\|Get\|Set\|Remove]-CsTeamsUpdateManagementPolicy. Functionality remains the same as previous implementation.
  • Adds UseNewTeamsClient parameter to TeamsUpdateManagementPolicy.
  • Adds EnablePrivateTeamDiscovery parameter to TeamsChannelsPolicy.
  • Fixes issues with authentication token not refreshing for some policy cmdlets.
  • Fixes issues where display format was broken for some cmdlets.
  • Adds SipProxyAddress, TeamsMediaLoggingPolicy, CountryAbbreviation, UserValidationErrors, and WhenCreated attributes in Get-CsOnlineUser output when run without -Identity parameter. Out of these attributes, CountryAbbreviation, UserValidationErrors, and WhenCreated don't show any values yet. These updates are gradually rolled out, more details in [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser).
  • Fixes Add-TeamChannelUser & Remove-TeamChannelUser to take UPN for -User parameter to manage external members in a shared channel.
    • | October 2022 | [4.9.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.9.0) |
  • Releases [Get\|Set]-CsTeamsEducationConfiguration cmdlets in GA.
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsFeedbackPolicy, [New\|Get\|Set\|Remove]-CsTeamsMessagingPolicy, [New\|Get\|Set\|Remove]-CsTeamsMeetingPolicy, and [New\|Get\|Set\|Remove]-CsOnlineVoicemailPolicy. Functionality remains the same as previous implementation.
  • Adds ExplicitRecordingConsent, ForceStreamingAttendeeMode parameters to TeamsMeetingPolicy.
  • Adds Description, PreambleAudioFile, PostambleAudioFile, PreamblePostambleMandatory parameters to OnlineVoicemailPolicy.
  • Adds AllowChatWithGroup parameter to TeamsMessagingPolicy.
  • Adds EnableFeatureSuggestions parameter to TeamsFeedbackPolicy.
  • Releases Update-CsTeamsShiftsConnectionInstance cmdlet.
    • | October 2022 | [4.8.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.8.1-preview) |
  • Contains a new implementation of [New\|Get\|Set\|Remove]-CsTeamsMessagingPolicy, [New\|Get\|Set\|Remove]-CsTeamsMeetingPolicy, and [New\|Get\|Set\|Remove]-CsOnlineVoicemailPolicy. NOTE: These Cmdlets currently only work with powershell.exe. They don't work for pwsh.exe. This issue will be fixed in the next GA release.
  • Adds ExplicitRecordingConsent, ForceStreamingAttendeeMode parameters to TeamsMeetingPolicy.
  • Adds Description, PreambleAudioFile, PostambleAudioFile, PreamblePostambleMandatory parameters to OnlineVoicemailPolicy.
  • Adds AllowChatWithGroup and EnableFeatureSuggestions parameters to TeamsMessagingPolicy.
  • Releases Update-CsTeamsShiftsConnectionInstance cmdlet.
    • -| October 2022 | [4.8.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.8.0) |
  • [Get\|New]-CsTeamsShiftsConnectionTeamMap cmdlets - TimeZone attribute added.
  • Removes SendEmailFromAddress and SendEmailFromDisplayName input parameters from Set-CsOnlineDialinConferencingUser.
  • Removes AllowAllAcsResources and BlockedAcsResources parameters from Set-TeamsAcsFederationConfiguration.
  • Adds ForceListenMenuEnabled parameter to call flow settings in New-CsAutoAttendantCallFlow, New-CsAutoAttendant and Set-CsAutoAutoAttendant. This setting enables the tenant to ignore DTMF/speech inputs while greetings/menu options are played.
    • +| October 2022 | [4.8.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.8.0) |
  • [Get\|New]-CsTeamsShiftsConnectionTeamMap cmdlets - TimeZone attribute added.
  • Removes SendEmailFromAddress and SendEmailFromDisplayName input parameters from Set-CsOnlineDialinConferencingUser.
  • Removes AllowAllAcsResources and BlockedAcsResources parameters from Set-TeamsAcsFederationConfiguration.
  • Adds ForceListenMenuEnabled parameter to call flow settings in New-CsAutoAttendantCallFlow, New-CsAutoAttendant, and Set-CsAutoAutoAttendant. This setting enables the tenant to ignore DTMF/speech inputs while greetings/menu options are played.
    • | September 2022 | [4.7.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.7.1-preview) |
  • Releases Application-based authentication support in Connect-MicrosoftTeams in preview. The supported cmdlets are being gradually rolled out, more details in [Application-based authentication in Teams PowerShell Module](teams-powershell-application-authentication.md).
  • Releases [Get\|Set]-CsTeamsEducationConfiguration cmdlets in private preview.
  • [Get\|New]-CsTeamsShiftsConnectionTeamMap cmdlets - TimeZone attribute added.
  • Removes SendEmailFromAddress and SendEmailFromDisplayName input parameters from Set-CsOnlineDialinConferencingUser.
  • Removes AllowAllAcsResources and BlockedAcsResources parameters from Set-TeamsAcsFederationConfiguration.
    • | September 2022 | [4.7.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.7.0) |
  • Fixes issues with process clean-up when using module on PS ISE and dotnet applications.
  • Releases [Get\|New]-CsBatchTeamsDeployment cmdlets in GA.
  • Releases [New\|Set]-CSTeamsShiftsConnectionInstance, Test-CsTeamsShiftsConnectionValidate support for UKG Dimensions.
  • Fixes issues with incorrect token fetch while choosing between multiple accounts using AccountId parameter in Connect-MicrosoftTeams.
  • Default values of Conference mode & Presence mode attributes are changed from false to true for New-CsCallQueue cmdlet.
    • | August 2022 | [4.6.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.6.1-preview) |
  • Fixes issues with process clean-up when using module on PS ISE and dotnet applications.
    • | July 2022 | [4.6.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.6.0) |
  • Releases AccountType parameter for the Get-CsOnlineUser cmdlet, which allows querying for specific type of users.
  • AccountType attribute is added in the Get-CsOnlineUser output indicating the user type. Possible values for AccountType are: 'User' (user accounts), 'ResourceAccount' (app endpoints or resource accounts), 'Guest' (guest accounts) & 'Unknown' (user type not known).
  • Fixes issues with Rank & Group parameters in Grant-Cs\ cmdlets.
  • Releases [Get\|Set\|New\|Remove\|Grant]-CsTeamsEventsPolicy Cmdlets.
  • Removes all the deprecated & nonsupported cmdlets. Details in [Teams PowerShell supported versions](teams-powershell-supported-versions.md#deprecated-cmdlets).
  • Releases modernized versions of [New\|Get]-CsCloudCallDataConnection cmdlets.
  • Releases [Get\|Remove]-SharedWithTeam cmdlets.
  • Releases Get-TeamAllChannel cmdlet.
  • Releases Get-TeamIncomingChannel cmdlet.
  • Releases Get-AssociatedTeam cmdlet.
  • Releases Get-SharedWithTeamUser cmdlet.
  • Supports TenantId optional parameter for the Add-TeamChannelUser cmdlet.
  • Releases Get-TeamTargetingHierarchyStatus & [Remove\|Set]-TeamTargetingHierarchy cmdlets.
    • | July 2022 | [4.5.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.5.1-preview) |
  • Releases AccountType parameter for the Get-CsOnlineUser cmdlet, which allows querying for specific type of users.
  • AccountType attribute is added in the Get-CsOnlineUser output indicating the user type. Possible values for AccountType are: 'User' (user accounts), 'ResourceAccount' (app endpoints or resource accounts), 'Guest' (guest accounts) & 'Unknown' (user type not known).
  • Fixes issues with Rank & Group parameters in Grant-Cs\ cmdlets.
    • -| June 2022 | [4.5.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.5.0) |
  • Supports IncludeResources parameter for the Get-CsAutoAttendantStatus cmdlet.
  • Supports SoftDeletedUsers parameter for the Get-CsOnlineUser cmdlet.
  • Releases [Get\|Grant]-CsTeamsMediaLoggingPolicy cmdlets.
  • Supports AuthorizedUsers optional parameter for the [New\|Set]-CsAutoAttendant & [New\|Set]-CsCallQueue cmdlets.
  • Fixes shared voicemail prompt parameters where prompt type couldn't be switched after they have been set for Set-CsCallQueue cmdlet.
  • Fixes [New\|Set]-CsOnlineSchedule cmdlets to work in the European date-time format.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsVoiceApplicationsPolicy cmdlets.
  • Releases Get-CsHybridTelephoneNumber cmdlet.
  • Releases modernized versions of [New\|Remove]-CsHybridTelephoneNumber cmdlets.
  • Supports ToneStar and TonePound as value for DtmfResponse parameter in the New-CsAutoAttendantMenuOption cmdlet.
  • Fixes issues with PSListModifier in the AllowedDomainsAsAList parameter in the modernized Set-CsTenantFederationConfiguration cmdlet.
  • Supports Group and Rank parameters for all Grant-Cs\ cmdlets.
  • Releases Test-CsTeamsTranslationRule cmdlet.
    • -| June 2022 | [4.4.3-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.4.3-preview) |
  • Supports IncludeResources parameter for the Get-CsAutoAttendantStatus cmdlet.
  • Supports SoftDeletedUsers parameter for the Get-CsOnlineUser cmdlet.
  • Releases [Get\|Grant]-CsTeamsMediaLoggingPolicy cmdlets.
  • Supports AuthorizedUsers optional parameter for the [New\|Set]-CsAutoAttendant & [New\|Set]-CsCallQueue cmdlets.
  • Fixes shared voicemail prompt parameters where prompt type couldn't be switched after they have been set for Set-CsCallQueue cmdlet.
  • Fixes [New\|Set]-CsOnlineSchedule cmdlets to work in the European date-time format.
    • +| June 2022 | [4.5.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.5.0) |
  • Supports IncludeResources parameter for the Get-CsAutoAttendantStatus cmdlet.
  • Supports SoftDeletedUsers parameter for the Get-CsOnlineUser cmdlet.
  • Releases [Get\|Grant]-CsTeamsMediaLoggingPolicy cmdlets.
  • Supports AuthorizedUsers optional parameter for the [New\|Set]-CsAutoAttendant & [New\|Set]-CsCallQueue cmdlets.
  • Fixes shared voicemail prompt parameters where prompt type couldn't be switched after they're set for Set-CsCallQueue cmdlet.
  • Fixes [New\|Set]-CsOnlineSchedule cmdlets to work in the European date-time format.
  • Releases [New\|Get\|Set\|Remove\|Grant]-CsTeamsVoiceApplicationsPolicy cmdlets.
  • Releases Get-CsHybridTelephoneNumber cmdlet.
  • Releases modernized versions of [New\|Remove]-CsHybridTelephoneNumber cmdlets.
  • Supports ToneStar and TonePound as value for DtmfResponse parameter in the New-CsAutoAttendantMenuOption cmdlet.
  • Fixes issues with PSListModifier in the AllowedDomainsAsAList parameter in the modernized Set-CsTenantFederationConfiguration cmdlet.
  • Supports Group and Rank parameters for all Grant-Cs\ cmdlets.
  • Releases Test-CsTeamsTranslationRule cmdlet.
    • +| June 2022 | [4.4.3-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.4.3-preview) |
  • Supports IncludeResources parameter for the Get-CsAutoAttendantStatus cmdlet.
  • Supports SoftDeletedUsers parameter for the Get-CsOnlineUser cmdlet.
  • Releases [Get\|Grant]-CsTeamsMediaLoggingPolicy cmdlets.
  • Supports AuthorizedUsers optional parameter for the [New\|Set]-CsAutoAttendant & [New\|Set]-CsCallQueue cmdlets.
  • Fixes shared voicemail prompt parameters where prompt type couldn't be switched after they're set for Set-CsCallQueue cmdlet.
  • Fixes [New\|Set]-CsOnlineSchedule cmdlets to work in the European date-time format.
    • | May 2022 | [4.4.1](https://www.powershellgallery.com/packages/MicrosoftTeams/4.4.1) |
  • Improvements in the size of the module.
  • Parameters not supported in the modernized version of all the cmdlets result in error.
  • Fixes error handling for [Get\|Set]-CsOnlineDialInConferencingUser, Get-CsOnlineDialInConferencingBridge, [Get\|Set\|Register\|Unregister]-CsOnlineDialInConferencingServiceNumber & Get-CsOnlineDialInConferencingLanguagesSupported cmdlets.
  • Deprecates Test-CsOnlineLisCivicAddress cmdlet.
  • User Principal Name (UPN) & GUID can be used now as identity in modernized [Get\|Remove]-CsOnlineApplicationInstanceAssociation cmdlets.
  • [BREAKING CHANGE] Get-CsOnlineUser - Policy attributes in the output are now null if a user doesn’t have that policy assigned. These attributes used to be empty UserPolicyDefinition objects in earlier versions (3.0.0 to 4.3.1).
  • Fixes Set-CsCallQueue to allow null or empty array values in the input parameters.
  • Get-CsPhoneNumberAssignment - City & IsoSubdivision attributes are added to the output.
    • | May 2022 | [4.3.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.3.1-preview) |
  • Improvements in the size of the module.
  • Parameters not supported in the modernized version of all the cmdlets result in error.
  • Fixes error handling for [Get\|Set]-CsOnlineDialInConferencingUser, Get-CsOnlineDialInConferencingBridge, [Get\|Set\|Register\|Unregister]-CsOnlineDialInConferencingServiceNumber & Get-CsOnlineDialInConferencingLanguagesSupported cmdlets.
  • Releases Deployment at Scale cmdlets in preview - New-CsBatchTeamsDeployment & Get-CsBatchTeamsDeploymentStatus.
  • User Principal Name (UPN) & GUID can be used now as identity in modernized [Get\|Remove]-CsOnlineApplicationInstanceAssociation cmdlets.
    • | May 2022 | [4.3.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.3.0) |
  • Fixes error handlings for [Set\|Remove]-CsPhoneNumberAssignment cmdlets.
  • [Get\|Set\|Remove]-CsOnlineLisSubnet – fixes for Subnet parameter in the modernized cmdlets.
  • [Get\|Set]-CsOnlineLisLocation & [Get\|Set]-CsOnlineLisCivicAddress – fixes around the supported parameters in the modernized cmdlets (more details in the respective public documentations).
    • @@ -70,22 +71,22 @@ This page provides the latest Teams PowerShell change log for both General Avail | March 2022 | [4.0.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/4.0.1-preview) |
  • Fixes issues with ErrorAction common parameter.
    • | March 2022 | [4.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/4.0.0) |
  • This GA release completes the modernization of all the cmdlets relevant for Teams only organizations. The modern versions are gradually rolled out, so some organizations continue to see the older remoting versions.
  • Releases [New\|Set\|Remove]-CsUserCallingDelegate and [Get\|Set]-CsUserCallingSettings cmdlets in GA.
  • [BREAKING CHANGE] Except New-CsVoiceNormalizationRule; the InMemory switch is no longer supported for other cmdlets.
  • Deprecates the following cmdlets: ConvertTo-JsonForPSWS, Set-CsUserServicesPolicy, [Get\|Set]-CsNetworkConfiguration, [Set\|Remove]-CsTenantNetworkConfiguration, New-CsNetworkMediaBypassConfiguration, [Get\|Grant\|New\|Remove\|Set]-CsTeamsVerticalPackagePolicy,[Get\|Remove\|Set]-CsVoiceNormalizationRule.
  • [BREAKING CHANGE] Get-CsOnlineVoicemailPolicy returns data for MaximumRecordingLength in string format instead of TimeSpan.
    • | February 2022 | [3.2.0-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/3.2.0-preview) |
  • This release completes the modernization of all the cmdlets relevant for Teams only organizations. The modern versions are gradually rolled out, so some organizations continue to see the older remoting versions.
  • [BREAKING CHANGE] Except New-CsVoiceNormalizationRule; the InMemory switch is no longer supported for other cmdlets.
  • Connect-MicrosoftTeams performance improvements.
  • Fixes for Import-Module with Prefix.
  • Fixes handling ports with slash character "/" in [Get\|Set\|Remove]-CsOnlineLisPort.
  • Releases Test-CsTeamsUnassignedNumberTreatment cmdlet.
  • Deprecates the following cmdlets: ConvertTo-JsonForPSWS, Set-CsUserServicesPolicy, [Get\|Set]-CsNetworkConfiguration, [Set\|Remove]-CsTenantNetworkConfiguration, New-CsNetworkMediaBypassConfiguration, [Get\|Grant\|New\|Remove\|Set]-CsTeamsVerticalPackagePolicy, [Get\|Remove\|Set]-CsVoiceNormalizationRule.
    • -| February 2022 | [3.1.1](https://www.powershellgallery.com/packages/MicrosoftTeams/3.1.1) |
  • Performance improvements for Import-Module.
  • PSListModifier deserialization issue has been fixed.
    • +| February 2022 | [3.1.1](https://www.powershellgallery.com/packages/MicrosoftTeams/3.1.1) |
  • Performance improvements for Import-Module.
  • PSListModifier deserialization issue is fixed.
    • | January 2022 | [3.1.0](https://www.powershellgallery.com/packages/MicrosoftTeams/3.1.0) |
  • Renamed Cmdlet from Get-CsTeamsShiftsConnectionUser to Get-CsTeamsShiftsConnectionWfmUser.
  • Releases new parameters ResultSize, SkipUserPolicies for Get-CsOnlineUser.
  • Releases new parameters ResultSize for Get-CsOnlineDialInConferencingUser.
  • Releases new parameters First, NumberAssigned, NumberNotAssigned, PSTNConnectivity, EnterpriseVoiceStatus, CivicAddressId, LocationId for Get-CsOnlineVoiceUser.
    • | December 2021 | [3.0.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/3.0.1-preview) |
  • Releases modernized versions of Grant-CsTeamsFilesPolicy and Remove-CsTeamsFilesPolicy. These cmdlets are expected to work similar to their remoting counterparts. The modern versions are gradually rolled out. So some tenants see the older remoting version (until the rollout completes).
  • Releases [New\|Set\|Remove]-CsUserCallingDelegate cmdlets in preview.
  • Releases [Get\|Remove]-CsTeamsShiftsConnectionErrorReport cmdlets in preview.
  • Releases Get-CsTeamsShiftsConnectionOperation cmdlet in preview.
  • Releases New-CsTeamsShiftsConnectionBatchTeamMap cmdlet in preview.
  • Releases Remove-CsTeamsShiftsScheduleRecord cmdlet in preview.
    • -| November 2021 | [3.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/3.0.0) |
  • [BREAKING CHANGE] Get-CsOnlineUser and Get-CsOnlineVoiceUser: The following changes apply for TeamsOnly tenants:
    • These cmdlets have now been migrated from the earlier implementation to the newer APIs.
    • (Using -Identity parameter): Attributes that are no longer relevant for Teams have been deprecated for TeamsOnly Tenants. Some attributes have also been renamed/replaced—see [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser) and [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
    • Get-CsOnlineUser (with -Filter parameter): Formatting for filtering based on AssignedPlans and EnterpriseVoice has been modified. Filterable attributes have also been temporarily limited (based on usage) for TeamsOnly Users—see [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
    • These cmdlets are gradually rolled out and some tenants won't experience these changes until the rollout is complete by the end of CY21.
  • [BREAKING CHANGE] Get-CsTenant: Attributes that are no longer relevant in the Teams world have been deprecated for TeamsOnly tenants—see [Get-CsTenant](/powershell/module/teams/get-cstenant).
  • Releases modernized versions of all 75+ Grant-Cs\Policy cmdlets (all parameter sets). These cmdlets are expected to work similar to their remoting counterparts. The modern versions are gradually rolled out, so some tenants will see the earlier remoting version (until the rollout completes).
  • Releases modernized versions of all 75+ Remove-Cs\Policy cmdlets. These cmdlets are expected to work similar to their remoting counterparts. The modern versions are gradually rolled out, so some tenants will see the earlier remoting version (until the rollout completes).
  • Releases [Set\|Remove]-CsPhoneNumberAssignment cmdlets. These cmdlets are gradually rolled out, so some tenants will get an error message referencing the existing cmdlets that they can use (until the rollout completes).
  • Releases new parameter EnhancedEmergencyServiceDisclaimer for [Set\|New]-CsTeamsEmergencyCallingPolicy cmdlet.
  • Releases [Get\|Add\|Remove]-TeamChannelUser cmdlets.
  • Releases Export-CsOnlineAudioFile cmdlet.
  • Fixes error handlings for [Get\|Import\|Remove]-CsOnlineAudioFile cmdlets.
  • Fixes for Get-Team error handling. Outputs the error message if fetching teams data fails.
  • Fixes for Connect-MicrosoftTeams - AccessTokens the difference in expiration time is increased.
    • +| November 2021 | [3.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/3.0.0) |
  • [BREAKING CHANGE] Get-CsOnlineUser and Get-CsOnlineVoiceUser: The following changes apply for TeamsOnly tenants:
    • These cmdlets are migrated from the earlier implementation to the newer APIs.
    • (Using -Identity parameter): Attributes that are no longer relevant for Teams are deprecated for TeamsOnly Tenants. Some attributes are also renamed/replaced—see [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser) and [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
    • Get-CsOnlineUser (with -Filter parameter): Formatting for filtering based on AssignedPlans and EnterpriseVoice is modified. Filterable attributes are temporarily limited (based on usage) for TeamsOnly Users—see [Get-CsOnlineVoiceUser](/powershell/module/teams/get-csonlinevoiceuser).
    • These cmdlets are gradually rolled out and some tenants won't experience these changes until the rollout is complete by the end of CY21.
  • [BREAKING CHANGE] Get-CsTenant: Attributes that are no longer relevant in the Teams world are deprecated for TeamsOnly tenants—see [Get-CsTenant](/powershell/module/teams/get-cstenant).
  • Releases modernized versions of all 75+ Grant-Cs\Policy cmdlets (all parameter sets). These cmdlets are expected to work similar to their remoting counterparts. The modern versions are gradually rolled out, so some tenants will see the earlier remoting version (until the rollout completes).
  • Releases modernized versions of all 75+ Remove-Cs\Policy cmdlets. These cmdlets are expected to work similar to their remoting counterparts. The modern versions are gradually rolled out, so some tenants will see the earlier remoting version (until the rollout completes).
  • Releases [Set\|Remove]-CsPhoneNumberAssignment cmdlets. These cmdlets are gradually rolled out, so some tenants will get an error message referencing the existing cmdlets that they can use (until the rollout completes).
  • Releases new parameter EnhancedEmergencyServiceDisclaimer for [Set\|New]-CsTeamsEmergencyCallingPolicy cmdlet.
  • Releases [Get\|Add\|Remove]-TeamChannelUser cmdlets.
  • Releases Export-CsOnlineAudioFile cmdlet.
  • Fixes error handlings for [Get\|Import\|Remove]-CsOnlineAudioFile cmdlets.
  • Fixes for Get-Team error handling. Outputs the error message if fetching teams data fails.
  • Fixes for Connect-MicrosoftTeams - AccessTokens the difference in expiration time is increased.
    • | November 2021 | [2.6.2-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.6.2-preview) |
  • Releases modernized versions of all 75+ Grant-Cs\Policy cmdlets (all parameter sets). These cmdlets are expected to work similar to their remoting counterparts. The modern versions are gradually rolled out, tenants that aren't flighted will see the older remoting version.
  • Releases modernized versions of all 75+ Remove-Cs\Policy cmdlets. These cmdlets are expected to work similar to their remoting counterparts. The modern versions are gradually rolled out, tenants that aren't flighted will see the older remoting version.
  • Releases Set-CsUserCallingSettings cmdlet in preview.
  • Releases Export-CsOnlineAudioFile cmdlet.
  • Fixes error handlings for [Get\|Import\|Remove]-CsOnlineAudioFile cmdlets.
    • | October 2021 | [2.6.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.6.1-preview) |
  • Releases [Set\|Remove]-CsPhoneNumberAssignment cmdlets. These cmdlets are gradually rolled out. So some tenants will get an error message referencing the existing cmdlets they can use (until the rollout completes).
  • Releases Get-CsOnlineTelephoneNumberCountry and Get-CsOnlineTelephoneNumberType cmdlets.
  • Releases new parameter EnhancedEmergencyServiceDisclaimer for [Set\|New]-CsTeamsEmergencyCallingPolicy cmdlet.
  • Releases Get-CsUserCallingSettings cmdlet in preview.
    • | September 2021 | [2.6.0](https://www.powershellgallery.com/packages/MicrosoftTeams/2.6.0) |
  • Fixes the bug where MicrosoftTeams module lookup failed if made a nested module of another custom PowerShell module. Now, MicrosoftTeams cmdlets are available even if it's a nested module of another module.
  • Releases [Get\|New\|Complete\|Clear]-CsOnlineTelephoneNumberOrder cmdlets.
  • Releases Get-CsOnlineTelephoneNumberCountry and Get-CsOnlineTelephoneNumberType cmdlets.
  • Releases new parameters for these cmdlets: Get-CsOnlineApplicationInstance, New-CsExternalAccessPolicy, New-CsTeamsAppSetupPolicy, New-CsTeamsCallingPolicy, New-CsTeamsCallParkPolicy, New-CsTeamsMeetingPolicy, New-CsTeamsMessagingPolicy, Set-CsTeamsAppSetupPolicy, Set-CsTeamsCallParkPolicy, Set-CsTeamsGuestMessagingConfiguration, Set-CsTeamsMeetingPolicy, Set-CsTenantFederationConfiguration, Set-CsExternalAccessPolicy, Set-CsTeamsCallingPolicy.
  • Fixes the failure that occurred when retrying login with Connect-MicrosoftTeams after an incorrect sign-in attempt.
  • Updates to make the module's release notes available in PowerShell Gallery for each new version.
    • | September 2021 | [2.5.2-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.5.2-preview) |
  • Note: Starting from this version, the release notes will also be published on PowerShell Gallery along with the module itself to reduce the delay in availability of release notes.
  • Releases [Get\|Set\|Grant\|New\|Remove]-CsTeamsEnhancedEncryptionPolicy cmdlets.
  • Removes [Get\|Set\|New\|Remove]-CsTenantBlockedNumberExceptionPattern cmdlets.
  • Fixes the bug where the Microsoft Teams module lookup failed if it was made a nested module of another custom PowerShell module. Now, Microsoft Teams cmdlets are available even if it's a nested module of another module.
  • Releases [Get\|New\|Complete\|Clear]-CsOnlineTelephoneNumberOrder cmdlets.
  • Releases Get-CsOnlineTelephoneNumberCountry and Get-CsOnlineTelephoneNumberType cmdlets.
  • Fixes the failure that occurred when retrying sign-in with Connect-MicrosoftTeams after an incorrect sign-in attempt.
  • Fixes Add-TeamChannelUser and Remove-TeamChannelUser failing for a private channel.
    • -| August 2021 | [2.5.1](https://www.powershellgallery.com/packages/MicrosoftTeams/2.5.1) |
  • The Access Token login for Connect-MicrosoftTeams now uses a unified token array instead of separate parameters for each resource-specific token. More details can be found here: [Connect-MicrosoftTeams](/powershell/module/teams/connect-microsoftteams).
  • The interactive login failure of Connect-MicrosoftTeams in Cloud Shell has been fixed. It now defaults to using the logged-in identity of the user instead of prompting for reauthentication.
  • TeamsUnassignedNumberTreatment cmdlets are now available.
  • Get-CsOnlineDialInConferencingBridge and Set-CsOnlineDialInConferencingBridge cmdlets have now been migrated from the older implementation to the newer APIs.
  • Modernized versions of Get-CsTenant and Get-CsOnlineUser (with -identity parameter only) have been released. They no longer emit deprecated properties and have some formatting changes compared to their remoting counterparts.
  • Note: The New-Team related updates have been reverted from 2.5.0 and the previous version has been provided so as to avoid any breaking changes.
    • | +| August 2021 | [2.5.1](https://www.powershellgallery.com/packages/MicrosoftTeams/2.5.1) |
  • The Access Token login for Connect-MicrosoftTeams now uses a unified token array instead of separate parameters for each resource-specific token. More details can be found here: [Connect-MicrosoftTeams](/powershell/module/teams/connect-microsoftteams).
  • The interactive login failure of Connect-MicrosoftTeams in Cloud Shell is fixed. It now defaults to using the logged-in identity of the user instead of prompting for reauthentication.
  • TeamsUnassignedNumberTreatment cmdlets are now available.
  • Get-CsOnlineDialInConferencingBridge and Set-CsOnlineDialInConferencingBridge cmdlets are migrated from the older implementation to the newer APIs.
  • Modernized versions of Get-CsTenant and Get-CsOnlineUser (with -identity parameter only) are released. They no longer emit deprecated properties and have some formatting changes compared to their remoting counterparts.
  • Note: The New-Team related updates are reverted from 2.5.0 and the previous version is provided so as to avoid any breaking changes.
    • | | July 2021 | [2.4.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.4.1-preview) |
  • Grant cmdlets changes now available.
  • New Voice related cmdlets are released.
  • Removal of certificate thumbprint authentication for -Cs* cmdlets.
  • Logging fix for logging files of all cmdlets.
  • Fixes issues with *TeamChannelUser cmdlets.
    • | | June 2021 | [2.4.0-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.4.0-preview) |
  • Preview only release of modernized versions of Get-CsTenant, Get-CsOnlineUser (with -identity parameter only), Get-CsOnlineDialInConferencingLanguagesSupported, and Import-CsOnlineAudioFile.
  • Modernized versions of Get-CsOnlineDialInConferencingLanguagesSupported and Import-CsOnlineAudioFile are expected to work similar/same to their remoting counterparts.
  • Modernized versions of Get-CsTenant and Get-CsOnlineUser (when run with -identity parameter) don't emit deprecated properties.
  • Modernized versions of Get-CsTenant and Get-CsOnlineUser (when run with -identity parameter) have some formatting changes when compared to their remoting counter parts.
  • Releases [Get\|Set\|Grant\|New\|Remove]-CsTeamsAudioConferencingPolicy cmdlets.
  • Releases Get-CsOnlineAudioFile and Remove-CsOnlineAudioFile cmdlets.
  • Set-TeamTargetingHierarchy, Remove-TeamTargetingHierarchy, Get-TeamTargetingHierarchyStatus are now available for GCC customers.
  • Fixes the endpoint called by the Get-TeamTargetingHierarchyStatus command.
    • | | May 2021 | [2.3.2-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.3.2-preview) |
  • Support for AccessToken login with Connect-MicrosoftTeams. Added -AccessTokens parameter that accepts the array of token. MSGraph and Teams resource token are required when using the AccessTokens parameter.
  • Removed AadAccessToken and MsAccessToken parameters.
    • | | May 2021 | [2.3.1](https://www.powershellgallery.com/packages/MicrosoftTeams/2.3.1) |
  • Update from .NETCore 2.1 to 3.1
  • Added cmdlet to get multi-geo region for users and groups
  • Fixes for integrated windows authentication to use -AccountId with Connect-MicrosoftTeams
  • TeamsCallHoldPolicy cmdlets are now available
  • Updates to input parameters and output formats of many commands
  • Fixes large latency issue while remoting commands
  • GA custom package features
    • | -| April 2021 | [2.2.0-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.2.0-preview) |
  • Fixes for integrated Windows authentication to use -AccountId with Connect-MicrosoftTeams.
  • Added cmdlet to get details of total change notification events that can be sent to users.
  • Added cmdlet to get multi-geo region for users and groups.
  • Handling of values passed to TeamsEnvironment name was case sensitive. This issue has been fixed.
  • Major refactor of remote session management within the module to facilitate unit tests. There should be no functional change for tenant admins.
    • | +| April 2021 | [2.2.0-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.2.0-preview) |
  • Fixes for integrated Windows authentication to use -AccountId with Connect-MicrosoftTeams.
  • Added cmdlet to get details of total change notification events that can be sent to users.
  • Added cmdlet to get multi-geo region for users and groups.
  • Handling of values passed to TeamsEnvironment name was case sensitive. This issue is fixed.
  • Major refactor of remote session management within the module to facilitate unit tests. There should be no functional change for tenant admins.
    • | | April 2021 | [2.1.0-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/2.1.0-preview) |
  • Fixed output formatting of some remoting cmdlets (for example, Get-CsTeamsNetworkRoamingPolicy, Get-CsTeamsMeetingPolicy, Get-CsTeamsMessagingPolicy, and more).
  • Updated parameter list of policy management cmdlets.
    • | -| March 2021 | [2.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/2.0.0) |
  • Uses MSAL for authentication & authorization
  • Connect-MicrosoftTeams is the entry point for all cmdlets.
  • New-csOnlineSession is no longer available. It has been replaced with Connect-MicrosoftTeams.
  • Enable-csonlinesessionforreconnection is no longer required. The feature has been natively implemented in Teams PowerShell Module.
  • Refactored Policy Package cmdlets and adds group package assignment
  • Significant performance enhancements for Get-Team cmdlet
  • Improved logging and debugging option for existing cmdlets
  • Added template management cmdlets
  • Deprecation of New-CsOnlineSession
    • | +| March 2021 | [2.0.0](https://www.powershellgallery.com/packages/MicrosoftTeams/2.0.0) |
  • Uses MSAL for authentication & authorization
  • Connect-MicrosoftTeams is the entry point for all cmdlets.
  • New-csOnlineSession is no longer available. It's replaced with Connect-MicrosoftTeams.
  • Enable-csonlinesessionforreconnection is no longer required. This feature is natively implemented in Teams PowerShell Module.
  • Refactored Policy Package cmdlets and adds group package assignment
  • Significant performance enhancements for Get-Team cmdlet
  • Improved logging and debugging option for existing cmdlets
  • Added template management cmdlets
  • Deprecation of New-CsOnlineSession
    • | | February 2021 | [1.1.11-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/1.1.11-preview) |
  • Added template management cmdlets
  • Mezzo and batching enhancements for Get-Team cmdlet
  • Improved logging and debugging option for existing cmdlets
  • Refactored Policy Package cmdlets
    • | | December 2020 | [1.1.10-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/1.1.10-preview) |
  • Updates to New-team cmdlet with increased retries and sleep duration
    • | | December 2020 | [1.1.9-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/1.1.9-preview) |
  • Updates for Skype for Business Online Integration
  • Fix for the duplicate prompt with Connect-Microsoft Teams
    • | diff --git a/Teams/toc.yml b/Teams/toc.yml index 64edaeea55..aae1647b3e 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -105,6 +105,8 @@ items: href: new-teams-known-issues.md - name: Classic Teams client end of availability href: teams-classic-client-end-of-availability.md + - name: Manually uninstall classic Teams client + href: teams-classic-client-uninstall.md - name: Usage report for new Teams client href: new-teams-usage-report.md - name: Classic Teams clients @@ -327,8 +329,6 @@ items: href: /microsoft-365/compliance/teams-workflow-in-advanced-ediscovery - name: Privacy items: - - name: Privacy and Microsoft Teams - href: privacy/teams-privacy.md - name: Location of data in Teams href: privacy/location-of-data-in-teams.md - name: Microsoft Teams feedback privacy @@ -688,6 +688,8 @@ items: href: view-only-meeting-experience.md - name: Meeting invitations href: customize-meeting-invitations.md + - name: Privacy statement in meeting join experience + href: meeting-privacy-statement.md - name: Manage feedback surveys for anonymous participants href: meeting-surveys-anonymous-participants.md - name: Standardized meetings @@ -1630,6 +1632,8 @@ items: href: scripts/powershell-script-security-groups-edu.md - name: Set up features for educators items: + - name: Set up AI content recommendations + href: institution-settings.md - name: Set up Supervised chats in Teams href: supervise-chats-edu.md - name: Set up Assignments in Teams @@ -1717,12 +1721,6 @@ items: href: teams-exploratory.md - name: Upgrade users from Teams Exploratory href: upgrade-from-teams-exploratory.md - - name: Manage Microsoft Teams Free (classic) - href: manage-freemium.md - - name: Upgrade Microsoft Teams Free (classic) to subscription version - href: upgrade-freemium.md - - name: Retire Microsoft Teams Free (classic) - href: teams-add-on-licensing/remove-assign-free-licenses.md - name: Microsoft Teams Shared Devices licensing href: teams-add-on-licensing/teams-shared-device-license.md - name: Microsoft Teams Phone Resource Account license diff --git a/Teams/upgrade-freemium.md b/Teams/upgrade-freemium.md deleted file mode 100644 index a22678c021..0000000000 --- a/Teams/upgrade-freemium.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: Upgrade Microsoft Teams Free (classic) to subscription -author: DaniEASmith -ms.author: danismith -manager: pamgreen -ms.topic: article -ms.service: msteams -ms.reviewer: -ms.date: 08/28/2023 -audience: admin -search.appverid: MET150 -description: Learn how to easily upgrade from Microsoft Teams Free (classic) to the full version by purchasing a Microsoft 365 or Office 365 subscription plan for your users. -ms.localizationpriority: medium -f1.keywords: -- CSH -ms.custom: - - NewAdminCenter_Update - - seo-marvel-apr2020 -ms.collection: - - M365-collaboration - - m365initiative-deployteams - - tier1 - - ContentEnagagementFY24 -appliesto: - - Microsoft Teams ---- - -# Upgrade Microsoft Teams Free (classic) to subscription version - -This article is for IT admins without a Microsoft 365 subscription but who need to upgrade their users from the **Teams Free (classic)** license to a paid Teams license. - -> [!IMPORTANT] -> You must upgrade from **Teams Free (classic)** to a subscription version of Teams because the **Teams Free (classic)** license was deprecated on April 12, 2023. Upgrading from **Teams Free (classic)** requires upgrading to a business subscription. -> -> Microsoft provides a free Teams experience for personal and small business use through a Microsoft Account rather than Microsoft Entra ID. Only new customers can sign up for the new **Teams (Free)** license. - -If your organization is using **Teams Free (classic)**, you can upgrade to the full version by purchasing a Microsoft 365 or Office 365 subscription plan for your users. The full version provides other Teams features — audio conferencing, enhanced administration, and security capabilities — that the free version doesn't provide. Microsoft 365 and Office 365 combine the familiar Microsoft Office desktop suite with cloud-based versions of Microsoft's next-generation communications and collaboration services — including Exchange Online, SharePoint Online, and Office — to help users be productive from anywhere through the internet. When you upgrade Teams, your existing Teams data won't be lost; all your teams, channels, chats, files, and permissions come with you. - -> [!NOTE] -> If you already have a Microsoft 365 or Office 365 subscription, you're eligible for the trial version of Teams (with your corporate identity), not the free version. The Teams trial provides the full version of Teams for a limited time. For more information, see [Manage the Microsoft Teams Commercial Cloud Trial offer](./teams-exploratory.md). - -## Upgrade requirements - -You can upgrade to the full version of Teams if you meet the following requirements: - -- You're the person who signed up for the existing **Teams Free (classic)** subscription. -- If you're bringing your own domain, it isn't already associated with Microsoft Entra ID (via trial or purchased Microsoft 365 or Office 365 subscription). - -> [!NOTE] -> Learn about your upgrade options on the page [Microsoft Teams Free (classic) is retiring](https://www.microsoft.com/microsoft-teams/free-classic-retirement). -> -> We recommend you use one of Microsoft's upgrade methods. If you begin buying licenses outside of one of Microsoft's upgrade methods, your existing Teams data won't automatically transfer because you'll be setting up a new tenant. - -## Limitations - -Keep the following limitations in mind: - -- You can't switch back to **Teams Free (classic)** after you upgrade. -- You can't merge multiple **Teams Free (classic)** tenants into a single paid tenant. -- All users must be in the same domain. (All users will get a sign-in in the format *username*@*domain.com*.) -- All users must be upgraded: a mix of **Teams Free (classic)** and paid subscription users in the same tenant isn't supported. - -## How do I upgrade my organization? - -To upgrade to the full version of Teams, select **Upgrade** in Teams. - -![screenshot showing Upgrade button.](media/teams-freemium-upgrade-image1.png) - -Enter the email address that you use to sign in to Teams, and then purchase a **Microsoft 365 Business Standard** plan. If you would like to purchase Microsoft 365 Business Basic or an Enterprise edition of Office 365, [contact Microsoft 365 sales and support](https://www.microsoft.com/microsoft-365/business/sales-support?rtc=1). - -## What's next? - -After your upgrade is complete, see [Get started with Microsoft Teams](get-started-with-teams-quick-start.md) for first steps and [Adopt Microsoft Teams](adopt-microsoft-teams-landing-page.md) for a phased approach to Teams adoption across your organization. - -## More information - -- To find out more about Teams versions and their capabilities, see [Compare Teams plans](https://products.office.com/microsoft-teams/free). -- For more information about upgrading to the full version of Teams, see [Upgrade from Teams Free (classic) to Teams](https://support.office.com/article/Upgrade-from-Teams-free-to-Teams-29475bbd-a34f-4175-9b33-d44430f8ad39). -- For information about other admin tasks associated with upgrading users, including adding user licenses, changing user names, and assigning temporary passwords, see [For admins upgrading from Teams Free (classic) to a paid subscription](https://support.office.com/article/for-admins-upgrading-from-teams-free-to-a-paid-subscription-75a95e7f-001e-42d0-a787-ae8b992d5a52). diff --git a/Teams/user-access.md b/Teams/user-access.md index 4d5db7d948..b81b3360a9 100644 --- a/Teams/user-access.md +++ b/Teams/user-access.md @@ -10,7 +10,7 @@ ms.collection: - M365-collaboration - tier1 ms.reviewer: ritikag -ms.date: 01/28/2024 +ms.date: 03/26/2024 search.appverid: MET150 description: Learn how to manage user access to Teams by assigning or removing a Teams license to users in your organization. f1.keywords: @@ -31,8 +31,6 @@ appliesto: You manage access to Teams at the user level by assigning or removing a Microsoft Teams product license. Except for joining Teams meetings anonymously, each user in your organization must have a Teams license before they can use Teams. You can assign a Teams license for new users when new user accounts are created or to users with existing accounts. -By default, when a licensing plan (for example, Microsoft 365 Enterprise E3 or Microsoft 365 Business Premium) is assigned to a user, a Teams license is automatically assigned, and the user is enabled for Teams. You can disable or enable Teams for a user by removing or assigning a license at any time. - Use messaging policies, managed from the [Teams admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339), to control what chat and channel messaging features are available to users in Teams. You can use the default policy or create one or more custom messaging policies for people in your organization. To learn more, read [Manage messaging policies in Teams](messaging-policies-in-teams.md). You manage Teams licenses in the Microsoft 365 admin center or by using PowerShell. You must be a Global admin or User management admin to manage licenses.