Merge branch 'public' into patch-27

.github/workflows/AutoLabelAssign.yml

@@ -1,23 +1,41 @@
-name: Auto label and assign pull requests
+name: Assign and label PR
 
 permissions:
   pull-requests: write
   contents: read
+  actions: read
 
-on: [pull_request_target]
+on: 
+    workflow_run:
+        workflows: [Background tasks]
+        types:
+            - completed
 
 jobs:
+    download-payload:
+        name: Download and extract payload artifact
+        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-prod
+        with:
+            WorkflowId: ${{ github.event.workflow_run.id }}
+            OrgRepo: ${{ github.repository }}
+        secrets:
+            AccessToken: ${{ secrets.GITHUB_TOKEN }}
 
-  auto-label-assign:
-    uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelAssign.yml@workflows-prod
-    with:
-      PayloadJson: ${{ toJSON(github) }}
-      AutoAssignUsers: 1
-      AutoLabel: 1
-      ExcludedUserList: '["user1", "user2"]'
-      ExcludedBranchList: '["branch1", "branch2"]'
-    secrets:
-      AccessToken: ${{ secrets.GITHUB_TOKEN }}
+    label-assign:
+        name: Run assign and label
+        needs: [download-payload]
+        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelAssign.yml@workflows-prod
+        with:
+            PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }}
+            AutoAssignUsers: 1
+            AutoLabel: 1
+            ExcludedUserList: '["user1", "user2"]'
+            ExcludedBranchList: '["branch1", "branch2"]'
+        secrets:
+            AccessToken: ${{ secrets.GITHUB_TOKEN }}
+
+
+
+
 
-
-
+

.github/workflows/AutoLabelMsftContributor.yml

@@ -0,0 +1,40 @@
+name: Auto label Microsoft contributors
+
+permissions:
+  pull-requests: write
+  contents: read
+  actions: read
+
+on: 
+    workflow_run:
+        workflows: [Background tasks]
+        types:
+            - completed
+
+jobs:
+    download-payload:
+        if: github.repository_visibility == 'public'
+        name: Download and extract payload artifact
+        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-prod
+        with:
+            WorkflowId: ${{ github.event.workflow_run.id }}
+            OrgRepo: ${{ github.repository }}
+        secrets:
+            AccessToken: ${{ secrets.GITHUB_TOKEN }}
+
+    label-msft:
+        name: Label Microsoft contributors
+        if: github.repository_visibility == 'public'
+        needs: [download-payload]
+        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelMsftContributor.yml@workflows-prod
+        with:
+          PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }}
+        secrets:
+          AccessToken: ${{ secrets.GITHUB_TOKEN }}
+          TeamReadAccessToken: ${{ secrets.ORG_READTEAMS_TOKEN }}
+
+
+
+
+
+

.github/workflows/BackgroundTasks.yml

@@ -0,0 +1,26 @@
+name: Background tasks
+
+permissions:
+  pull-requests: write
+  contents: read
+
+on:
+  pull_request_target:
+
+jobs:
+  upload:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Save payload data
+        env:
+          PayloadJson: ${{ toJSON(github) }}
+          AccessToken: ${{ github.token }}
+        run: |
+          mkdir -p ./pr
+          echo $PayloadJson > ./pr/PayloadJson.json
+          sed -i -e "s/$AccessToken/XYZ/g" ./pr/PayloadJson.json
+      - uses: actions/upload-artifact@v4
+        with:
+          name: PayloadJson
+          path: pr/

.github/workflows/LiveMergeCheck.yml

@@ -0,0 +1,22 @@
+name: PR can merge into branch
+
+permissions:
+  pull-requests: write
+  statuses: write
+  contents: read
+
+on: 
+  pull_request_target:
+    types: [opened, reopened, synchronize, edited]
+
+jobs:
+
+  live-merge:
+    uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-LiveMergeCheck.yml@workflows-prod
+    with:
+      PayloadJson: ${{ toJSON(github) }}
+    secrets:
+      AccessToken: ${{ secrets.GITHUB_TOKEN }}
+
+
+

.github/workflows/PrFileCount.yml

@@ -0,0 +1,22 @@
+name: PR file count less than limit
+
+permissions:
+  pull-requests: write
+  statuses: write
+  contents: read
+
+on: 
+  pull_request_target:
+    types: [opened, reopened, synchronize, labeled, unlabeled, edited]
+
+jobs:
+
+  file-count:
+    uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-PrFileCount.yml@workflows-prod
+    with:
+      PayloadJson: ${{ toJSON(github) }}
+    secrets:
+      AccessToken: ${{ secrets.GITHUB_TOKEN }}
+
+
+

.github/workflows/ProtectedFiles.yml

@@ -1,4 +1,4 @@
-name: Protected Files
+name: PR has no protected files
 
 permissions:
   pull-requests: write
@@ -9,12 +9,12 @@ on: [pull_request_target]
 
 jobs:
 
-  check-files:
-    uses: MicrosoftDocs/MAX-CPUB-Test/.github/workflows/Shared-ProtectedFiles.yml@main
+  protected-files:
+    uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ProtectedFiles.yml@workflows-prod
     with:
       PayloadJson: ${{ toJSON(github) }}
     secrets:
       AccessToken: ${{ secrets.GITHUB_TOKEN }}
 
 
-
+

Skype/SfbPartnerCertification/certification/test-spec.md

@@ -2,7 +2,7 @@
 ms.date: 06/11/2018
 title: "Skype for Business certification program — Test Specifications"
 ms.author: serdars
-author: msdmaguire
+author: slamprianou
 manager: serdars
 ms.reviewer: dougand
 ms.topic: article

Teams/CQD-data-and-reports.md

@@ -3,8 +3,8 @@ title: Data and reports in Call Quality Dashboard (CQD)
 author: mkbond007
 ms.author: mabond
 manager: pamgreen
-ms.reviewer: mikedav, siunies, gageames
-ms.date: 11/28/2017
+ms.reviewer: jamp, siunies, mikedav, gageames
+ms.date: 07/31/2024
 ms.topic: article
 ms.tgt.pltfrm: cloud
 ms.service: msteams
@@ -29,7 +29,7 @@ description: Learn about the data and reports available in Microsoft Call Qualit
 
 # Data and reports in Call Quality Dashboard (CQD)
 
-Microsoft Call Quality Dashboard (CQD) uses a near-real-time (NRT) data feed. Call records are available in CQD within 30 minutes of the end of a call and remain in CQD for 12 months, except for EUII fields which are removed after 28 days.
+Microsoft Call Quality Dashboard (CQD) uses a near-real-time (NRT) data feed. Call records are available in CQD within 30 minutes of the end of a call and remain in CQD for 12 months, except for end user identifiable information (EUII) fields which are removed after 28 days.
 
 ## Many ways to access call quality data
 
@@ -39,12 +39,12 @@ You can access call quality data by several different avenues. Pick the one that
 |---|---|
 |Teams admin center [(https://admin.teams.microsoft.com)](https://admin.teams.microsoft.com)|Call quality data is included on the **Users** page in the Teams admin center, showing the most common data you need in an easy-to-read format. You can't customize the data that you find under **Users**.|
 |CQD portal [(https://cqd.teams.microsoft.com)](https://cqd.teams.microsoft.com)|Robust summary and detailed reports that meet most needs, with drill-through filtering. You can also customize reports in the CQD portal. <br><br>Get two [CQD report templates](#import-the-cqd-report-templates) to help you analyze data in the CQD portal.|
-|Power BI|Use direct queries to view your CQD data in Power BI using [customizable Power BI templates](CQD-Power-BI-query-templates.md). [Download Power BI query templates for CQD](https://www.microsoft.com/download/details.aspx?id=102291).<br><br>You can also [use the REST API to access CQD data](/skypeforbusiness/management-tools/call-quality-dashboard/data-api) through Power BI. Use this method if you want to download your CQD data so you can work on it offline. The benefit of using this method is better performance, especially useful for large data sets that bog down in Power BI when you're online.|
+|Power BI|Use direct queries to view your CQD data in Power BI using [customizable Power BI templates](CQD-Power-BI-query-templates.md). The CQD Power BI templates are regularly updated to support new Teams features, calling scenarios, and the latest telemetry we have available in CQD.|
 |Graph API|Access raw call quality data yourself using the [Graph API](/graph/api/resources/callrecords-api-overview). This is the most complex method, but it gives you the most control and flexibility in analyzing your call quality data. For example, if you need to join it with other data for your organization, you can use the Graph API to create a data model and incorporate call quality data. Please note that CallRecords Graph API may not contain all of the fields that are available in CQD and naming conventions may differ between the two products. |
 
 ## Import the CQD report templates
 
-Download [two curated CQD report templates](https://aka.ms/qertemplates) (All Networks and Managed Networks) to help you get up to speed quickly with CQD. The All Networks template, though optimized to work with a building data file, can be used while you work toward collecting and uploading building information into CQD, as described in the next section.
+Download [two curated CQD report templates](https://aka.ms/qertemplates) (All Networks and Managed Networks) to help you get up to speed quickly with CQD on the web. The All Networks template, though optimized to work with a building data file, can be used while you work toward collecting and uploading building information into CQD, as described in the next section.
 
 **To import the templates (.CQDX) into CQD**:
 
@@ -57,25 +57,37 @@ Download [two curated CQD report templates](https://aka.ms/qertemplates) (All Ne
 4. Repeat steps 2 and 3 for the second CQD template.
 
    > [!NOTE]
-   > Each user must import the CQD templates into their CQD instance.
+   > Templates and saved reports are unique for each admin that logs into CQD. Each user must follow the steps to import the CQD templates if they wish to use them.
+   >
+   > For the best experience with using CQD, we recommend using [the latest QER experience in Power BI](cqd-power-bi-query-templates.md) instead.
 
 ## EUII data
 
-For compliance reasons, end-user identifiable information (EUII) data (also known as personally-identifiable information or PII) is only kept for 28 days. As NRT data crosses the 28-day mark, fields that contain EUII are cleared, resulting in EUII-free NRT data. Fields that contain EUII data are:
+For compliance reasons, EUII data (also known as personally-identifiable information or PII) is only kept for 28 days. As CQD's data crosses the 28-day mark, fields that contain EUII are cleared, resulting in EUII-free data. Fields that contain EUII data are:
 
-- Full IP address
-- Media Access Control (MAC) Address
-- Basic Service Set identifier (BSSID)
-- Session Initiation Protocol (SIP) URI (Skype for Business only)
-- User Principal Name (UPN)
-- Machine Endpoint Name
-- User Verbatim Feedback
-- Object ID (the Active Directory object ID of the endpoint's user)
+- IP Address
+- User ObjectId
+- MAC Address
+- Sip Uri (Skype for Business only)
 - Phone Number
+- UPN
+- Feedback Text
+- Client Endpoint Name
+- Local Address
+- Remote Address
+- Base Address
+- Local Site
+- Remote Site
 - Auto Attendant Identity
 - Call Queue Identity
-- Video Teleconferencing (VTC) Device Name
-- Video Teleconferencing (VTC) Device Detail
+- Transferred from Call Queue Identity
+- Organizer ObjectId
+- Organizer UPN
+- Organizer Sip Uri (Skype for Business only)
+- VTC Device Name
+- VTC Device Detail
+
+
 
 ### Admin roles with and without EUII access
 
@@ -140,12 +152,12 @@ If you want to use Power BI to analyze your CQD data, read [Use Power BI to anal
 
 ### Select product data to see in reports
 
-In the Summary and Location-Enhanced Reports, you can use the **Product Filter** drop-down to show all product data, only Microsoft Teams data, or only Skype for Business Online data.
+In the Summary and Location-Enhanced Reports, you can use the **Product Filter** drop-down to show all product data, only Microsoft Teams data, or only Skype for Business data.
 
 > [!div class="mx-imgBorder"]
 > ![Screenshot: shows the Product Filter control options.](media/206ad818-0f72-4c8e-b25e-3cc8fcfbef05.png)
 
-In Detailed reports, you can use the **Is Teams** dimension to filter the data to Microsoft Teams or Skype for Business Online data.
+In Detailed reports, you can use the **Is Teams** dimension to filter the data to Microsoft Teams or Skype for Business data.
 
 ## Summary Reports
 
@@ -222,7 +234,6 @@ As the names indicate, the classification criteria is based on the type of clien
 The CQD Summary Reports dashboard includes a **Tenant Data Upload** page, accessed by selecting **Tenant Data Upload** from the settings menu in the top-right corner. This page is used for admins to upload their own information, such as:
 
 - A map of IP address and geographical information.
-- A map of each wireless AP and its MAC address.
 - A map of Endpoint to Endpoint Make/Model/Type, etc.
 
 We recommend that you upload your tenant, building, and location data so CQD can include this information in your reports. If you haven't already uploaded this data, read [Upload tenant and building data](CQD-upload-tenant-building-data.md).
@@ -303,7 +314,7 @@ In order to select multiple filter values, begin by adding a new filter to the r
 
 Then, click **Search** (a magnifying glass icon next to the new filter). You'll see a text field, and a number of options, including **Select All** and **Invert**. Enter a value,  and click **Search** next to that field to search. Alternatively, leave the text field empty and click **Search** to view up to the first 100 options.
 
-```powershell
+```URL
 /filter/[AllStreams].[Second Tenant Id]\|[YOUR TENANT ID HERE]
 ```
 
@@ -317,7 +328,7 @@ Certain CQD reports have dashboard-level filters added to them, making it easy t
 
 ![Screenshot of a dashboard filter.](media/qerguide-image-dashboardfilters.png)
 
-```powershell
+```URL
 /filter/[AllStreams].[Is Teams]|[TRUE | FALSE]
 ```
 
@@ -328,7 +339,7 @@ Excluding federated data from CQD reports is useful when you're remediating mana
 
 To add a filter, append the following to the end of the URL:
 
-```console
+```URL
 /filter/[AllStreams].[Second Tenant Id]\|[YOUR TENANT ID HERE]
 ```
 
@@ -354,7 +365,7 @@ To apply URL filters with multi-select values, separate each value with a pipe (
 
 If you specify an invalid name or value, the URL filter won't be applied.
 
-You can use a URL filter to filter every report for a specific dimension. The most common URL filters are used to filter reports to exclude federated participant telemetry, or focus on only Teams or Skype for Business Online. Excluding federated data from CQD reports is useful when you're remediating managed buildings or networks where federated endpoints might influence your reports.
+You can use a URL filter to filter every report for a specific dimension. The most common URL filters are used to filter reports to exclude federated participant telemetry, or focus on only Teams or Skype for Business. Excluding federated data from CQD reports is useful when you're remediating managed buildings or networks where federated endpoints might influence your reports.
 
 |Filter|Description|CQD query filter example|
 |---|---|---|

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

@@ -131,11 +131,15 @@ Perform the following steps:
 
     - Per Day reporting retrieves one daily summary record for each Auto attendant, Call queue, and Agent. This results in fewer records being returned to the client, reducing the possibility of hitting the 90,000 default or 200,000 per query record limit. Per Day reporting is based on a UTC-00:00 day (00:00:00-23:59:59 UTC) only and any UTC offset supplied by the user is ignored.
 
-6. Sign in with an account. Select **Organizational account**, and then select **Sign in**.
+5. Sign in with your Teams account.
+   - Select **File**, then **Options and settings**, and then **Data source settings**.
+   - Select **Edit Permissions**, and then **Edit**.
+   - Select **Organizational account**, and then **Sign in**.
+   - Select **Save**, then **OK**, and then **Close**.
 
-   :::image type="content" source="media/aa-cq-historical-report-03-v300.png" alt-text="Screenshot showing sign-in for V3.x.x.":::
+     :::image type="content" source="media/aa-cq-historical-report-03-v301.png" alt-text="Screenshot showing sign-in for V3.x.x.":::
 
-7. Select **Connect**, and the data refreshes.
+6. Select **Refresh**, in the ribbon bar and the data refreshes.
 
 ## Data latency for Auto attendant and Call queue analytics
 

Teams/alerts/teams-admin-alerts.md

@@ -34,7 +34,7 @@ You can use Teams monitoring and alerting to do the following items:
 
 ## How to manage monitoring and alerting
 
-You must be a global admin in Microsoft 365 or a Teams service admin to configure alerting rules. See [Use Teams administrator roles to manage Teams](../using-admin-roles.md) to learn more about Teams admin roles and which reports each admin role can access.
+You must be a Teams service admin to configure alerting rules. See [Use Teams administrator roles to manage Teams](../using-admin-roles.md) to learn more about Teams admin roles and which reports each admin role can access.
 
 1. Sign in to the Teams admin center.
 2. From the left navigation, select **Notifications & alerts**.