Merge pull request #15455 from MicrosoftDocs/main

Publish main to live, Thursday 10:30AM PDT, 08/22

Teams/teams-analytics-and-reports/teams-town-hall-usage-report.md

@@ -25,7 +25,7 @@ The Teams town hall usage report in the Microsoft Teams admin center shows you t
 ## View the town hall usage report
 
 1. In the left navigation of the Microsoft Teams admin center, select **Analytics & reports** > **Usage reports**. On the **View reports** tab, under **Report**, select **Town hall usage reports**.
-2. Under **Date range**, select a predefined range or set a custom range. You can set a range to show data up to a year, six months before and after the current date.
+2. Under **Date range**, select a predefined range or set a custom range. You can set a range to show data up to 90 days, 45 days before and after the current date.
 3. Under **Organizer**, you can choose to show only town halls organized by a specific user.
 4. Select **Run report**.  
 

Teams/teams-recording-policy.md

@@ -41,6 +41,9 @@ Teams is enhanced to support the integration of partner recording solutions. The
 
 Compliance recording can be enabled on Microsoft 365 A3/A5/E3/E5/Business Premium, Office 365 A3/A5/E3/E5 users, Teams Rooms license, or Microsoft Teams Shared Devices license.
 
+> [!IMPORTANT]
+> Users with an assigned compliance policy experience a 4-second audio delay when making PSTN calls.
+
 > [!NOTE]
 > Compliance recording isn't currently supported for E911 emergency calling services.
 
@@ -242,6 +245,14 @@ policies](./assign-policies-users-and-groups.md#assign-a-policy-to-a-group).
 
 ## User experiences
 
+### PSTN calls
+
+Inbound call queue (CQ) calls are recorded for users who have an assigned compliance recording (CR) policy. Some routing methods might involve usability concerns with multiple announcements. We recommend appropriately configuring your call queues to align with your organization's intended user experience.
+
+Compliance recording doesn't work if users have an Internet outage, and make or receive PSTN calls using an SBA.
+
+### Notifications
+
 Support for notifications is enabled using the Teams client experiences. The experiences can be either visual or audio.
 
 **Teams clients - visual notice**
@@ -258,10 +269,6 @@ Support for notifications is enabled using the Teams client experiences. The exp
 - Audio conferencing (audio notice in dial-in number's default or user-selected language)
 - PSTN callers (audio notice in Teams user's default language)
 
-> [!NOTE]
-> 1. Inbound call queue (CQ) calls are recorded for users who have an assigned compliance recording (CR) policy. Some routing methods might involve usability concerns with multiple announcements. We recommend appropriately configuring your call queues to align with your organization's intended user experience.
-> 2. Compliance recording doesn't work if users have an Internet outage, and make or receive PSTN calls using an SBA.
-
 ## Compliance recording for Teams certification programs
 
 In addition to publishing publicly available APIs allowing partners to develop and integrate CCaaS solutions with Teams, we developed the compliance recording for Microsoft Teams certification program. This program provides customers with the assurance that each participating partner's solution is tested and verified. Customers can be assured that partners provide the quality, compatibility, and reliability they expect from Microsoft solutions.

Teams/tmr-meeting-recording-change.md

@@ -29,55 +29,77 @@ To learn about your recording policies, see [Teams meeting recording](meeting-re
 
 ## Recording storage
 
-> [!NOTE]
-> As an admin, you can't change where the recording is stored.
+### Meetings and events
 
-By default, for scheduled meetings, all recording files go to the OneDrive account of organizer. For 1-1 call and group call, recording files go to the OneDrive account of the user who selected **Record**. For channel meetings, the recording always goes to the SharePoint site of the channel.
+For **meetings, webinars, and town halls**, by default, all recording files are saved to the organizer's OneDrive **Recordings** folder. The **`-MeetingRecordingOwnership`** parameter within the PowerShell [**CsTeamsRecordingRolloutPolicy**](/powershell/module/teams/set-csteamsrecordingrolloutpolicy) cmdlet controls whether the recording is saved to the organizer's or recording initiator's OneDrive, overriding the default storage settings. This policy applies to the following meeting and event types:
 
-### Meetings and events
+- Automatically recorded meetings
+- Delegate-created meetings
+- Manually recorded meetings
+- Meet now meetings
+- Meetings scheduled in Outlook
+- Meetings scheduled in the Teams client
+- Recurring meetings
+- Town halls
+- Webinars
 
-For **meetings, webinars, and town halls**, all recording files are automatically saved to the organizer's OneDrive **Recordings** folder, even if the organizer didn't attend the meeting or event. This process applies to recurring, meet now, and delegate-created meetings. Co-organizers have the same editing permissions as organizers for recording files.
+If **`-MeetingRecordingOwnership`** is set to `RecordingInitiator`, when organizers with this policy create meetings and events, the recording saves to the OneDrive of the user who starts the recording. If the recording initiator doesn't have a OneDrive, the recording is temporarily saved to async media storage.
 
-### Delegate-created meetings
+If **`-MeetingRecordingOwnership`** is set to `MeetingOrganizer`, when organizers with this policy create meetings and events, the recording saves to organizer's OneDrive, even if the organizer didn't attend the meeting or event. Co-organizers have the same editing permissions as organizers for recording files. To understand what happens if an organizer doesn't have a OneDrive account, see the **Recording storage for organizers without OneDrive accounts** section in this article.
 
-For meetings in which an organizer appoints a **delegate** who has permission to act on the organizer's behalf, all recording files are automatically saved to the organizer's **Recordings** folder in OneDrive. When delegates are added as co-organizers, they have the same editing permissions as organizers for recording files.
+#### Delegate-created meetings
 
-### Channel meetings
+For meetings in which an organizer appoints a **delegate** who has permission to act on the organizer's behalf, all recording files are automatically saved to the organizer's **Recordings** folder in OneDrive. When delegates are added as co-organizers, they have the same editing permissions as organizers for recording files.
 
-For **Channel meetings**, the recording is stored in the Teams site documentation library in a folder named **Recordings**. For example: *Teams name - Channel name*/**Documents**/**Recordings**.
+### 1:1 and group calls
 
-### Shared accounts and Microsoft Teams Rooms meetings
+For 1-1 call and group calls, recording files go to the OneDrive account of the user who selected **Record**.
 
-For **shared accounts** and **Microsoft Teams Rooms meetings**, if the organizer has a OneDrive account, the recording gets uploaded to the organizer’s OneDrive. If the recording upload fails because the organizer’s OneDrive space is full, or the organizer, co-organizers, and recording initiator don’t have OneDrive accounts, the recording is temporarily stored to async media storage.
+### Channel meetings
 
-To understand what happens if an organizer doesn't have a OneDrive account, see the **Recording storage for organizers without OneDrive accounts** section in this article.
+For **Channel meetings**, the recording is stored in the SharePoint Teams site documentation library in a folder named **Recordings**. For example: *Teams name - Channel name*/**Documents**/**Recordings**.
 
-To learn more about Microsoft Teams Rooms meetings, see [Microsoft Teams Rooms (Windows)](https://support.microsoft.com/office/microsoft-teams-rooms-windows-e667f40e-5aab-40c1-bd68-611fe0002ba2). For details on shared accounts, see [About shared mailboxes - Microsoft 365 admin](/microsoft-365/admin/email/about-shared-mailboxes).
+### Shared accounts
 
-### Automatically recorded meetings
+For **shared accounts**, if the shared account has OneDrive, the recording is uploaded there. However, since shared accounts typically don’t have OneDrive, the recordings are uploaded to the organizer’s OneDrive in those cases. To understand what happens if an organizer doesn't have a OneDrive account, see the **Recording storage for organizers without OneDrive accounts** section in this article.
 
-For meetings that are automatically recorded, the recording is temporarily saved to async media storage.
+For details on shared accounts, see [About shared mailboxes - Microsoft 365 admin](/microsoft-365/admin/email/about-shared-mailboxes).
 
-### Videos
+### Microsoft Teams Rooms meetings
 
-Videos are just like any other file in OneDrive and SharePoint. Handling ownership and retention after an employee leaves follows the standard [OneDrive and SharePoint process](/onedrive/retention-and-deletion).
+For **Microsoft Teams Rooms meetings(MTR)**, when an organizer creates a meeting using the meet-now button in MTR, the room itself becomes the meeting organizer, and the recording is stored in the MTR’s OneDrive account. As a result, none of the meeting participants have full permissions to the file. If you want meeting participants to have full permissions to the recording file, avoid assigning OneDrive storage to an MTR.
 
-### Retention labels
+When the MTR doesn't have a OneDrive account, the recording gets saved to the organizer's OneDrive. For details on what happens if an organizer doesn't have a OneDrive account, see the **Recording storage for organizers without OneDrive accounts** section in this article.
 
-To learn how to apply retention labels to Teams meeting recordings, see [How to autoapply a retention label](/microsoft-365/compliance/apply-retention-labels-automatically).
+To learn more about Microsoft Teams Rooms meetings, see [Microsoft Teams Rooms (Windows)](https://support.microsoft.com/office/microsoft-teams-rooms-windows-e667f40e-5aab-40c1-bd68-611fe0002ba2).
 
 ### Recording storage for organizers without OneDrive accounts
 
-If the organizer doesn’t have a OneDrive account, here's what happens, in order, to the meeting recording:
+When the organizer doesn’t have a OneDrive account, here's what happens, in order, to the meeting recording:
 
-1. The recording is saved to the co-organizer's OneDrive. When there are multiple co-organizers, the recording saves to the co-organizers' OneDrive, ordered by the first number in each co-organizer's Entra object ID. The meeting or event organizer has permissions to edit and share the recording. To find the object IDs for users in your org, see [Locate important IDs for a user](/partner-center/account-settings/find-ids-and-domain-names#find-the-user-object-id).
-2. If none of the co-organizers have OneDrive accounts, the recording is saved to the OneDrive account of the user who initiated the recording.
-3. If the user who initiated the recording doesn’t have a OneDrive, the recording gets temporarily stored to async media storage.
+1. The recording is saved to the co-organizer's OneDrive, while the meeting or event organizer retains permissions to edit and share the recording. When there are multiple co-organizers, the recording saves to the co-organizers' OneDrive, ordered by the first number of each co-organizer's Entra object ID. To find the object IDs for users in your org, see [Locate important IDs for a user](/partner-center/account-settings/find-ids-and-domain-names#find-the-user-object-id).
+
+   Let's take a look at the following example with three co-organizers:
+
+   :::image type="content" source="media/objectid-co-organizer-recording-small.png" alt-text="Screenshot of the object IDs for three organizers. The first organizer's object ID starts with the letter one, the second character in the second organizer's object ID is the number 5, and the second character in the third organizer's object ID is the number 3." lightbox="media/objectid-co-organizer-recording-expand.png":::
+
+   In this example, the recording is saved to co-organizer 1’s OneDrive account. If co-organizer 1 doesn’t have a OneDrive account, the recording is saved to co-organizer 3’s OneDrive. If co-organizer 3 also doesn’t have a OneDrive account, the recording is then saved to co-organizer 2’s OneDrive.
+
+1. If none of the co-organizers have OneDrive accounts, the recording is saved to the OneDrive account of the user who initiated the recording.
+1. If the user who initiated the recording doesn’t have a OneDrive, the recording gets temporarily stored to async media storage.
 
 ### Async media storage
 
 If a Teams meeting recording fails to successfully upload to OneDrive because the organizer, co-organizers and recording initiator don’t have OneDrive accounts, or the storage quota is full, an error message appears. The recording is instead temporarily saved to async media storage. Once the recording is in async media storage, no retry attempts are made to automatically upload the recording to OneDrive or SharePoint. During that time, the organizer must download the recording. The organizer can try to upload the recording again if they get a OneDrive or SharePoint license, or clear some space in their storage quota. If not downloaded within 21 days, the recording is deleted.
 
+### Videos
+
+Videos are just like any other file in OneDrive and SharePoint. Handling ownership and retention after an employee leaves follows the standard [OneDrive and SharePoint process](/onedrive/retention-and-deletion).
+
+### Retention labels
+
+To learn how to apply retention labels to Teams meeting recordings, see [How to autoapply a retention label](/microsoft-365/compliance/apply-retention-labels-automatically).
+
 ### Planning for storage
 
 The size of a one-hour recording is 400 MB. Make sure you understand the capacity required for recorded files and have sufficient storage available in OneDrive and SharePoint. Read [Set the default storage space for OneDrive](/sharepoint/set-default-storage-space) and [Manage SharePoint site storage limits](/sharepoint/manage-site-collection-storage-limits) to understand the base storage included in the subscription and how to purchase more storage.
@@ -124,4 +146,4 @@ Closed captions are supported for Teams meeting recordings for 60 days from when
 - [Which policy takes precedence?](./policy-assignment-overview.md#which-policy-takes-precedence)
 - [Teams meeting recording](meeting-recording.md)
 - [Block the download of Teams meeting recording files from SharePoint or OneDrive](block-download-meeting-recording.md)
-- [Policy recommendations for securing SharePoint sites and files](/security/zero-trust/zero-trust-identity-device-access-policies-sharepoint)
+- [Policy recommendations for securing SharePoint sites and files](/security/zero-trust/zero-trust-identity-device-access-policies-sharepoint)

Teams/trusted-organizations-external-meetings-chat.md

@@ -125,9 +125,17 @@ Set-CsTenantFederationConfiguration -BlockAllSubdomains $True
 
 #### Block federation with Teams trial-only tenants
 
-A new admin control is being introduced to block federation with Teams trial-only tenants. Currently, trial tenants have access to the full feature set of Teams for about 30 days before being billed. However, this control can be exploited by malicious actors to launch phishing or abuse attacks against Teams users. To embrace the secure-by-default mindset for our customers, we'll disable trial tenant federation by default for all tenants and require explicit tenant action if a tenant wants or needs to federate with any trial tenants.
+You can control your organization's external access with Teams trial-only tenants (that don't have any purchased seats), by using the `-ExternalAccessWithTrialTenants` setting in PowerShell (at least version 6.4.0 is required).
 
-This change will be rolled out globally starting June 17, 2024, and is expected to complete by June 30, 2024. There will be a 30-day period for tenants to review and update the default setting before it's enforced. If no action is taken, the default value **Blocked** will be applied after this time.
+The default value for this setting is **Blocked**, but you can override it to **Allowed**, using:
+`Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants "Allowed"`
+
+To block external communication with trial-only tenants:
+`Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants "Blocked"`
+
+When set to **Blocked**, users from these trial-only tenants aren't able to search and contact your users via chats, Teams calls, and meetings (using the users' authenticated identities) and your users aren't able to reach users in these trial-only tenants. Users from the trial-only tenant are also removed from existing chats.
+
+Users from trial-only tenants are blocked by default (with no option to override) from external communication with users in other Microsoft 365 cloud environments and with Microsoft Skype for Business server users. Two tenants with only trial subscriptions can federate with each other if the -ExternalAccessWithTrialTenants is Allowed by both tenants.
 
 ##### How block federation will affect your organization