Merge pull request #15394 from MicrosoftDocs/main

Publish main to live, Tuesday 3:30PM PDT, 08/13

Teams/aa-cq-cqd-historical-reports.md

@@ -35,7 +35,7 @@ description: Learn about how to use the updated Teams Auto Attendant & Call Queu
 
 This Power BI template provides three reports that allow organizations to report on the number of calls processed by Auto attendants and Call queues. It also provides agent performance insights.
 
-## V3.1.7 published on July 15, 2024
+## V3.1.8 published on August 12, 2024
 
 The Teams Auto Attendant & Call Queue Historical Report Power BI template provides the following three reports:
 
@@ -94,7 +94,7 @@ For more information, see:
 | [New-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#-HistoricalCallQueueMetricsPermission) | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#-HistoricalCallQueueMetricsPermission) |
 | [New-CsTeamsVoiceApplicationsPolicy/--HistoricalAgentMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#--HistoricalAgentMetricsPermission) | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#--HistoricalAgentMetricsPermission) |
 
-#### Known Issue
+#### Known issues
 
 If the voice applications policy assigned to a user only enables the historical reporting permissions, and optionally the real-time reporting permissions, then the user can't access the historical reports. Support is working to resolve this problem. In the interim, enable at least one Auto attendant and Call queue change permission in the policy. Enabling the Auto attendant **Business hours greeting** and Call queue **Welcome greeting** is suggested, but enabling any of the change permissions will work around this issue.
 
@@ -113,15 +113,15 @@ The following steps assume the Power BI Desktop client is installed on your comp
 
 Perform the following steps:
 
-1. Download and save the [Teams Auto Attendant & Call Queue Historical Reports V3.1.7.zip](https://www.microsoft.com/download/details.aspx?id=104623) file on your computer.
+1. Download and save the [Teams Auto Attendant & Call Queue Historical Reports V3.1.8.zip](https://www.microsoft.com/download/details.aspx?id=104623) file on your computer.
 
 2. Open the zip file.
 
-3. Open the `Teams Auto Attendant & Call Queue Historical Reports V3.1.7.pbit` template file. Power BI Desktop should launch.
+3. Open the `Teams Auto Attendant & Call Queue Historical Reports V3.1.8.pbit` template file. Power BI Desktop should launch.
 
 4. Select the **DataSource**, **Report Level**, and **UTC Offset**. 
 
- :::image type="content" source="media/aa-cq-historical-report-01-v317.png" alt-text="Screenshot showing the DataSource, Report Level, and UTC Offset selections.":::
+ :::image type="content" source="media/aa-cq-historical-report-01-v318.png" alt-text="Screenshot showing the DataSource, Report Level, and UTC Offset selections.":::
 
  - **DataSource**: Select the `api.interfaces.records.teams.microsoft.com` entry.
  - **Report Level**:
@@ -749,7 +749,8 @@ Refer to: Teams Auto Attendant & Call Queue Historical Reports - Change Log.docx
 
 |Version |Date Published |Supported |Filename |Description |
 |:--------|:------------------|:---------|:-----------------------------------------------------------|:-----------------------------------------------------------------------|
-|3.1.7 |July 15, 2024 |Yes |Teams Auto Attendant & Call Queue Historical Reports V3.1.7 |Improved support for authorized users, removed original reporting templates |
+|3.1.8 |August 12, 2024 |Yes |Teams Auto Attendant & Call Queue Historical Reports V3.1.7 |Bug fix for Date slicer on Call Queue tab |
+|3.1.7 |July 15, 2024 |No |Teams Auto Attendant & Call Queue Historical Reports V3.1.7 |Improved support for authorized users, removed original reporting templates |
 |3.1.6 |April 15, 2024 |No |Teams Auto Attendant & Call Queue Historical Reports V3.1.6 |Support click2call, callback, authorized users, and some visuals changed due to deprecation |
 |3.1.5 |January 29, 2024 |No |Teams Auto Attendant & Call Queue Historical Reports V3.1.5 |Corrected an error with the Per Day query logic for fAgentTimelineAnalytics and fAgentTimelineAnalyticsSummary |
 |3.1.4 |January 24, 2024 |No |Teams Auto Attendant & Call Queue Historical Reports V3.1.4 |Per day reporting for large volume customers, accessibility improvements for screen readers |

Teams/admin-settings-for-file-drag-drop-to-third-party-storage.md

@@ -54,8 +54,6 @@ Set-CsTeamsFilesPolicy -Identity Global -DefaultFileUploadAppId ""
 Remove-CsTeamsFilesPolicy -Identity Global
 ```
 
-For more information on user-level policy changes, see [Turn off Teams Native File Upload policy](/microsoftteams/turn-off-teams-native-file-upload-policy).
-
 ### User side-error conditions
 A user side error could occur due to the following reasons:
 - The app is configured but not installed
@@ -69,9 +67,6 @@ To remove the policy for the complete list of users, use the *Remove-CsTeamsFile
 Remove-CsTeamsFilesPolicy
 ```
 
-> [!NOTE]
-> To make this policy work, *NativeFileEntryPoints* should be disabled. For more information on making related changes, see [Turn off Teams Native File Upload policy](/microsoftteams/turn-off-teams-native-file-upload-policy).
-
 ### Out of scope
 Teams Mobile support for the *DefaultFileUploadAppId* policy isn't applicable. Also note that image or media copy and paste is today treated as part of the Teams message payload and not as a cloud file. This policy doesn't impact the image or media copy and paste.
 

Teams/dial-plans-routing-overview.md

@@ -3,7 +3,7 @@ title: "Microsoft Teams Dial plans and routing"
 author: CarolynRowe
 ms.author: crowe
 manager: pamgreen
-ms.reviewer: jenstr
+ms.reviewer: roykuntz
 ms.date: 10/02/2023
 ms.topic: article
 ms.assetid: aa2ec464-3481-4bbb-8c14-e13e18093df5
@@ -41,15 +41,17 @@ If you choose Calling Plan, Operator Connect, or Teams Phone Mobile, most call r
 
 For Direct Routing, you must configure call routing by specifying the voice routes and assigning voice routing policies to users. You can configure dial plans for number translation at the trunk level to ensure interoperability with Session Border Controllers (SBCs). For more information, see [Configure voice routing for Direct Routing](direct-routing-voice-routing.md), [Manage voice routing policies](manage-voice-routing-policies.md) and [Translate phone numbers](direct-routing-translate-numbers.md).
 
-Be aware that you can assign a Direct Routing online voice routing policy to Calling Plan and Operator Connect users. You might want to do this, for example, to enable users to dial in to a call center directly. You can set up a Direct Routing trunk to the call center.
+You can assign a Direct Routing online voice routing policy to Calling Plan and Operator Connect users. You might want to do this, for example, to enable users to dial in to a call center directly. You can set up a Direct Routing trunk to the call center.
 
 If a user has a Calling Plan license, for example, that user’s outgoing calls are automatically routed through the Microsoft Calling Plan PSTN infrastructure. If you configure and assign a Direct Routing online voice routing policy to the user, the user’s outgoing calls are checked to determine whether the dialed number matches a number pattern defined in the online voice routing policy. If there’s a match, the call is routed through the Direct Routing trunk. If there’s no match, the call is routed through the Calling Plan PSTN infrastructure.
 
 For more information, see [Direct Routing voice routing policy considerations](direct-routing-voice-routing.md#voice-routing-policy-considerations).
 
 ## Match dialed number to user
 
-A process called **Reverse Number Lookup (RNL)** uses strict string matching to find a user or resource account that matches the dialed phone number for an incoming PSTN call. For example, assume that a user is assigned the phone number +14255551234;ext=1234. If an incoming PSTN call has the dialed phone number +14255551234;ext=1234, RNL finds the user and the call is transferred to that user. However, if an incoming PSTN call has the dialed phone number +14255551234, RNL won't find the user and the call will fail or be routed to [unassigned number routing](routing-calls-to-unassigned-numbers.md).
+A process called **Reverse Number Lookup (RNL)** uses strict string matching to find a user or resource account that matches the dialed number for an incoming PSTN call. For example, assume that a user is assigned the phone number +14255551212. If a PSTN caller has dialed +14255551212, RNL finds the user and the call is connected to that user. However, if the +14255551212 number hasn't been assigned to a user or resource account, the call will fail to route or be routed according to [unassigned number routing](routing-calls-to-unassigned-numbers.md), if configured.
+
+If you want internal users who call a phone number that assigned to a resource account to be connected to that number on the PSTN instead of the resource account it's assigned to, you can enable the skip RNL option for the phone number by changing the phone number assignment by using the **Set-CsPhoneNumberAssignment** PowerShell cmdlet with `-ReverseNumberLookup`. For more information, see [Set-CsPhoneNumberAssignment](/powershell/module/teams/set-csphonenumberassignment) and [Get-CsPhoneNumberAssignment](/powershell/module/teams/get-csphonenumberassignment).
 
 ## Related topics