Merge branch 'main' into docs-editor/multi-tenant-people-search-1759196561

Author: dstrome

.github/workflows/AutoLabelAssign.yml

@@ -15,7 +15,7 @@ jobs:
     download-payload:
         name: Download and extract payload artifact
         if: github.repository_owner == 'MicrosoftDocs'
-        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-prod
+        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-test
         with:
             WorkflowId: ${{ github.event.workflow_run.id }}
             OrgRepo: ${{ github.repository }}
@@ -26,12 +26,15 @@ jobs:
         name: Run assign and label
         if: github.repository_owner == 'MicrosoftDocs'
         needs: [download-payload]
-        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelAssign.yml@workflows-prod
+        uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelAssign.yml@workflows-test
         with:
             PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }}
             AutoAssignUsers: 1
+            AutoAssignReviewers: 1
             AutoLabel: 1
             ExcludedUserList: '["user1", "user2"]'
             ExcludedBranchList: '["branch1", "branch2"]'
         secrets:
-            AccessToken: ${{ secrets.GITHUB_TOKEN }}
+            AccessToken: ${{ secrets.GITHUB_TOKEN }}
+            PrivateKey: ${{ secrets.M365_APP_PRIVATE_KEY }}
+            ClientId: ${{ secrets.M365_APP_CLIENT_ID }}

.github/workflows/BackgroundTasks.yml

@@ -6,6 +6,7 @@ permissions:
 
 on:
   pull_request_target:
+    types: [opened, synchronize, reopened, ready_for_review]
 
 jobs:
   upload:

.openpublishing.redirection.copilot.json

@@ -14,6 +14,11 @@
          "source_path": "copilot/pin-copilot.md",
          "redirect_url": "/copilot/microsoft-365/pin-copilot-chat-navbar",
          "redirect_document_id": false
+      },
+      {
+         "source_path": "copilot/copilot-tuning-responsible-ai-faq.md",
+         "redirect_url": "/copilot/responsible-ai/copilot-tuning-responsible-ai-faq",
+         "redirect_document_id": false
       }
    ]
 }

.openpublishing.redirection.frontline.json

@@ -69,6 +69,11 @@
          "source_path":"microsoft-365/frontline/deploy-dynamic-teams-at-scale.md",
          "redirect_url":"/microsoft-365/frontline/deploy-flexible-membership-teams-at-scale", 
          "redirect_document_id":true
+      },
+      {
+         "source_path":"microsoft-365/frontline/set-up-open-shifts-across-locations.md",
+         "redirect_url":"/microsoft-365/frontline/shifts-for-teams-landing-page", 
+         "redirect_document_id":false
       }
    ]
 }

copilot/TOC.yml

@@ -173,6 +173,8 @@ items:
     href: enterprise-data-protection.md
   - name: Transparency Note
     href: microsoft-365-copilot-transparency-note.md
+  - name: Flow Builder privacy and data subject request (DSR) FAQ
+    href: flow-builder-privacy-data-subject-request-faq.md
 - name: Extensibility and building agents
   items:
   - name: Extend Microsoft 365 Copilot
@@ -211,8 +213,6 @@ items:
         href: copilot-tuning-troubleshooting-guardrails.md
       - name: Microsoft 365 admin center
         href: copilot-tuning-troubleshooting-mac.md
-    - name: Responsible AI FAQ
-      href: copilot-tuning-responsible-ai-faq.md
 - name: Service description and training for Microsoft 365 Copilot
   items:
   - name: Service description
@@ -223,3 +223,12 @@ items:
     href: https://m365.cloud.microsoft/copilot-prompts
   - name: Submit Copilot feedback to Microsoft
     href: provide-feedback.md
+- name: Responsible AI
+  items:
+  - name: Overview
+    href: responsible-ai/responsible-ai-overview.md
+  - name: FAQ for Copilot Tuning
+    href: responsible-ai/copilot-tuning-responsible-ai-faq.md
+  - name: FAQ for Flow Builder
+    href: responsible-ai/flow-builder-responsible-ai-faq.md
+

copilot/employee-self-service/customize.md

@@ -155,20 +155,22 @@ Terms to know:
 
 **Default:** On
 
+**Topic JTBD:** Redirect User Context retrieval topics and attributes from other data sources to improve response relevancy.
+
 **Maker JTBD:** Maker needs to add redirection of the User Context retrieval topics from different ESS agent ISV packages. Or, if Makers configure other Topics to retrieve User Context attributes from other systems, then they should also be added as Topic redirections in this Topic.
 
 **Maker - What to customize:** </br>
 **Requirement to use:** None.
 
 1. After message disclaimer (blank). Add message or delete it if you don't want the disclaimer to appear.
-1. Official source badge - no configuration required. You can use this setting in its default state.
+1. Official source badge - no configuration required. Use in its default state.
 
 |Step |Action |Expected result |
 |-----|-------|----------------|
 |1    |Open the ESS agent in Copilot Studio. |ESS agent available to customize. |
 |2    |Navigate to **Topics** to see the list of Topics. |Shows Custom Topics. |
 |3    |Select **[Admin] User Context - Setup**. |Opens custom topic in the design canvas. |
-|4    |Add a redirect to another Topic where it sets the user context, such as one from an ISV. |Maker able to add a custom disclaimer message. |
+|4    |Add a redirect to another Topic where it sets the user context, such as one from an ISV. |Maker able to set user context. |
 |5    | Save the changes. |Your changes are saved. |
 
 #### [System] Response Preparation
@@ -188,7 +190,7 @@ Terms to know:
 **Requirement to use:** None.
 
 1. After message disclaimer (blank). Add message or delete it if you don't want the disclaimer to appear.
-1. Official source badge - no configuration required. You can use this setting in its default state. |
+1. Official source badge - no configuration required. Use in its default state.
 
 |Step |Action |Expected result |
 |-----|-------|----------------|

copilot/employee-self-service/prerequisites.md

@@ -34,8 +34,6 @@ The ESS Agent is built on top of Microsoft 365 Copilot. Users need the following
 |Users                         |Microsoft Teams |[Manage user access to Microsoft Teams](/microsoftteams/user-access) |
 |Environment admins and makers |Copilot Studio  |[Copilot Studio licensing and subscriptions](/microsoft-copilot-studio/requirements-licensing-subscriptions) |
 
-*Premium licenses are required for some third-party connectors.
-
 ## Set up Copilot Studio capacity
 
 The ESS agent uses agent flows. You need to set up the Copilot Studio capacity. [Learn about Copilot Studio capacity](/microsoft-copilot-studio/requirements-messages-management).

copilot/employee-self-service/usage-analytics.md

@@ -41,6 +41,8 @@ Feedback about Copilot is collected from Copilot experiences, such as when selec
 
 You can view feedback in the [Microsoft feedback portal](https://feedbackportal.microsoft.com/feedback). To view feedback submitted to Microsoft, select **My feedback** and sign in. If using Copilot at work or school, your IT admin might not allow use of the feedback portal.
 
+Administrators can view end-user feedback in the **Product feedback** page in the Microsoft admin center (MAC) under the **Health** section.
+
 ## Auditing and logging
 
 The ESS agent is built on Copilot and Power Platform. You can use auditing capabilities from these platforms to log and monitor usage.

copilot/flow-builder-privacy-data-subject-request-faq.md

@@ -0,0 +1,97 @@
+---
+title: Flow Builder privacy and data subject request (DSR) FAQ
+description: Frequently asked questions about Flow Builder's privacy and data subject request (DSR) processes.
+author: sbasi19
+ms.author: ralinga
+manager: dansimp
+ms.date: 09/19/2025
+ms.topic: concept-article
+ms.service: microsoft-365-copilot
+ms.reviewer: cyanderson
+ms.update-cycle: 180-days
+---
+
+# Flow Builder privacy and data subject request (DSR) FAQ
+
+Flow Builder is a Microsoft 365 Copilot agent that helps users create automation flows using natural language. This FAQ explains how Flow Builder works, how it handles data, and what controls are available to users and administrators.
+
+## What is Flow Builder?
+
+Flow Builder is a Copilot agent that enables users to automate tasks by describing them in natural language. It generates flows using supported Microsoft connectors and displays them directly in the Microsoft 365 Copilot experience.
+
+## How are flows stored, exported, or deleted?
+
+Flows created with Flow Builder are stored in the user's Power Platform environment. These flows are visible within the Flow Builder agent interface in Microsoft 365 Copilot but aren't surfaced in Power Automate.
+
+Users can export or delete flows using standard Power Platform tools. Flows are subject to Microsoft’s Data Subject Request (DSR) processes.
+
+Here are some resources about DSR requests:
+
+- [Responding to DSR delete requests for Microsoft Dataverse customer data](/power-platform/admin/dataverse-privacy-dsr-guide)
+- [Responding to DSR delete requests to delete Power Apps customer data](/power-platform/admin/powerapps-privacy-delete-dsr)
+- [Export process data](/power-automate/minit/export)
+
+## Is conversation history stored or exportable?
+
+No. Flow Builder doesn't retain conversation history. All interactions are processed in real time and aren't stored in Microsoft 365 Copilot conversation history or backend services.
+
+Because no chat history is stored, there's no conversational data to export or delete under DSR.
+
+To learn more about how Microsoft 365 Copilot handles data, see [Data, Privacy, and Security for Microsoft 365 Copilot](microsoft-365-copilot-privacy.md).
+
+## How is Flow Builder managed by administrators?
+
+Administrators can manage Flow Builder in the Microsoft 365 admin center under **Copilot > Agents**. Available controls include:
+
+- Enable or disable the agent
+- Assign, block, or remove access
+- Control visibility using “Allow users access to agents”
+
+Flow Builder respects tenant-level settings configured in the Microsoft 365 admin center and Power Platform Admin Center (PPAC). These settings determine:
+
+- Whether Flow Builder is enabled
+- Whether feedback collection is allowed
+- Whether analytics and telemetry are collected
+- Which Copilot features are available to users
+
+To learn more about managing Copilot agents and tenant settings, see [Manage Copilot Agents](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps?view=o365-worldwide&preserve-view=true)
+
+## What connectors are supported?
+
+Flow Builder currently supports the following connectors:
+
+- Recurrence
+- Outlook
+- Microsoft Teams
+- Approvals
+- Run a prompt
+- SharePoint
+
+Connector availability may vary depending on tenant policies and data loss prevention (DLP) configurations.
+
+## How is user feedback handled and controlled?
+
+Users can submit thumbs-up or thumbs-down ratings and optional comments.
+
+Here are some important points about feedback collection. Feedback data:
+
+- Isn't used to train foundation models
+- Isn't linked to individual identities
+- Doesn't include content samples
+- Can be enabled or disabled by administrators at the tenant level
+
+Feedback collection settings apply consistently across all Flow Builder surfaces. If Flow Builder is embedded in an iframe or accessed through other Microsoft 365 interfaces, feedback controls configured at the tenant level apply to both entry points.
+
+Here's some additional information about feedback collection:
+
+- [Providing feedback about Microsoft Copilot with Microsoft 365 apps](https://support.microsoft.com/en-us/topic/providing-feedback-about-microsoft-copilot-with-microsoft-365-apps-c481c26a-e01a-4be3-bdd0-aee0b0b2a423)
+- [Manage feedback for Microsoft 365 apps](/microsoft-365/admin/manage/manage-feedback-ms-org?view=o365-worldwide&preserve-view=true)
+
+## Can usage be audited?
+
+Yes. Organizations can use Microsoft 365 audit logs and Power Platform analytics to monitor usage of Flow Builder.
+
+## Related articles
+
+- [Learn about the new Microsoft Purview portal](/purview/purview-portal)
+- [Power Platform Admin Center](https://aka.ms/ppac)