Merge pull request #31130 from MicrosoftDocs/main

[AutoPublish] main to live - 03/17 15:40 PDT | 03/18 04:10 IST

Author: m365-skilling-repo-management[bot]

copilot/agent-essentials/m365-agents-faq.md

@@ -4,7 +4,7 @@ f1.keywords:
 ms.author: erikre
 author: ErikRe
 manager: dansimp
-ms.date: 11/13/2025
+ms.date: 03/17/2026
 ms.update-cycle: 180-days
 audience: Admin
 ms.topic: concept-article
@@ -20,16 +20,16 @@ description: Get answers to frequently asked questions about agents governance f
 
 ## Do I need an agent or a connector? How do I get started?
 
-Whether you need an agent or a connector depends on your business needs. Copilot agents support specialized workflows and experiences, whereas connectors help add knowledge to Microsoft 365 intelligence experiences, including Copilot.
+Whether you need an agent or a connector depends on your business needs. Agents in Microsoft 365 support specialized workflows and experiences, whereas connectors help add knowledge to Microsoft 365 intelligence experiences, including Copilot.
 
-- **Copilot agents** extend the functionality of Copilot by acting as specialized AI assistants tailored to specific domains or use cases. You can use agents to extend Copilot's knowledge, automate workflows, and deliver tailored user experiences in Microsoft Teams, Outlook, SharePoint, or custom apps. You can create a declarative agent using Copilot's AI infrastructure, model, and orchestrator. Or, for complex workflows or specific language models, you can create a custom agent. For more information, see [Agents for Microsoft 365 Copilot](/microsoft-365-copilot/extensibility/agents-overview).
+- **Agents in Microsoft 365** extend the functionality of Copilot by acting as specialized AI assistants tailored to specific domains or use cases. You can use agents to extend Copilot's knowledge, automate workflows, and deliver tailored user experiences in Microsoft Teams, Outlook, SharePoint, or custom apps. You can create a declarative agent using Copilot's AI infrastructure, model, and orchestrator. Or, for complex workflows or specific language models, you can create a custom agent. For more information, see [Agents for Microsoft 365 Copilot](/microsoft-365-copilot/extensibility/agents-overview).
 - **Copilot connectors** enable you to ingest data, such as unstructured, line-of-business data, into the Microsoft Graph so that Copilot can reason over that data alongside other data. There are more than 100 prebuilt Copilot connectors available, and the Connectors API can be used to create custom connectors. For more information, see [Microsoft 365 Copilot Connectors](/microsoft-365-copilot/extensibility/overview-copilot-connector).
 
 To get started, [review our planning guide](/microsoft-365-copilot/extensibility/planning-guide), which can help you define your business need, and determine whether you need an agent or a connector. Also see [Understand available agent options](m365-agents-admin-guide.md#understand-available-agent-options).
 
-## What kinds of Copilot agents are available?
+## What kinds of agents are available for Microsoft 365?
 
-There are two main types of Copilot agents you can create: 
+There are two main types of agents you can create for Microsoft 365: 
 
 - **[Declarative agents](/microsoft-365-copilot/extensibility/agents-overview#declarative-agents)**, which use Copilot's AI infrastructure, model, and orchestrator. These agents are built using low-code tools like Agent Builder or pro-code tools like Visual Studio, Visual Studio Code, and the Microsoft 365 Agents Toolkit. Declarative agents run in Microsoft 365 Copilot and Microsoft 365 apps like Teams, Outlook, and SharePoint.
 - **[Custom engine agents](/microsoft-365-copilot/extensibility/agents-overview#custom-engine-agents)**, which are fully customized AI assistants. These agents require hosting outside of Microsoft 365, and are typically built using low-code Copilot Studio or pro-code tools like Visual Studio, Visual Studio Code, and Agents Toolkit, using languages such as .NET, Python, and JavaScript, and frameworks like Semantic Kernel or LangChain.
@@ -39,21 +39,21 @@ For more information, see the following articles:
 - [Choose what type of agent to build](/microsoft-365-copilot/extensibility/agents-overview#choose-what-type-of-agent-to-build)
 - [Understand available agent options](m365-agents-admin-guide.md#understand-available-agent-options)
 
-## Who can create, build, and share Copilot agents?
+## Who can create, build, and share agents?
 
 - **Users** can create declarative agents in Agent Builder or SharePoint if enabled by tenant settings (requires Copilot license or subscription)
 - **Makers** can use Copilot Studio (lite or full) for low-code agents
 - **Developers** can use Copilot Studio SDK or Agents Toolkit for pro-code agents. Developers can also [submit agents to the marketplace](/copilot/microsoft-365/agent-essentials/agent-policies/agent-submit-marketplace)
 - Both **Makers** and **Developers** can add actions, connectors, and advanced logic in Copilot Studio or via the Microsoft 365 Agents Toolkit
 
-People in your organization can also [sideload agents](/copilot/microsoft-365/agent-essentials/agent-policies/agent-sideload), [share agents](/microsoft-365/admin/manage/manage-shared-agents), and [publish agents](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps#publish-agents), according to tenant policies and admin controls that are configured in the Microsoft 365 admin center. 
+People in your organization can also [sideload agents](/copilot/microsoft-365/agent-essentials/agent-policies/agent-sideload), [share agents](/microsoft-365/admin/manage/manage-shared-agents), and [publish agents](/microsoft-365/admin/manage/agent-registry#publish-agents), according to tenant policies and admin controls that are configured in the Microsoft 365 admin center. 
 
 For more information, see the following articles:
 
 - [Agents admin guide for Microsoft 365](m365-agents-admin-guide.md)
-- [Manage access to Copilot agents](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps#manage-access-to-copilot-agents)
+- [Manage access to agents in Microsoft 365](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps#manage-access-to-copilot-agents)
 
-## What tools do I need to create, build, implement, and use Copilot agents?
+## What tools do I need to create, build, implement, and use agents in Microsoft 365?
 
 Depending on what you want to do, Copilot agent tools are available, as summarized in the following table:
 
@@ -71,7 +71,7 @@ Make sure to review the following resources:
 
 ## What governance or controls are available for agents?
 
-The following governance options are available for Copilot agents:
+The following governance options are available for agents in Microsoft 365:
 
 - **[Copilot Control System](/copilot/microsoft-365/copilot-control-system/overview)**: Unified dashboard for managing Copilot and agents
 - **[Microsoft Purview](/purview/ai-microsoft-purview)**: Compliance, audit, and eDiscovery across all extensibility options
@@ -83,7 +83,7 @@ See [Understand agent security, privacy, and compliance](m365-agents-admin-guide
 
 Yes. Reports are available to help administrators monitor licenses, agents, and deployments. Custom reports can also be created. See [Copilot Control System measurement and reporting](/copilot/microsoft-365/copilot-control-system/security-governance).
 
-## Can administrators control data sources used by Copilot agents and connectors?
+## Can administrators control data sources used by agents and connectors?
 
 Yes, administrators can control data sources that are used. Administrators can also configure Copilot features, specify sharing permissions, block or unblock agents, and more.
 
@@ -93,7 +93,7 @@ Yes, administrators can control data sources that are used. Administrators can a
 
 For more information, see the following resources:
 
-- [Manage agents and integrated apps in Microsoft 365](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps)
+- [Manage agents in Microsoft 365](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps)
 - [Connectors overview in Microsoft 365](/microsoft-365-copilot/extensibility/overview-copilot-connector)
 
 ## How does an agent access data?  
@@ -107,13 +107,13 @@ For more information, see the following articles:
 - [Copilot Control System security and governance](/copilot/microsoft-365/copilot-control-system/security-governance)
 - [Understand agent security, privacy, and compliance](m365-agents-admin-guide.md#understand-agent-security-privacy-and-compliance)
 
-## What controls should administrators implement for Copilot agents?
+## How should administrators control agents?
 
 In general, administrators should take the following actions:
 
 - Use the [Copilot Control System](/copilot/microsoft-365/copilot-control-system/overview) for centralized governance, security, and measurement
 - Use [Purview DSPM for AI](/purview/dspm-for-ai?tabs=m365) to identify and mitigate oversharing and insider risks
-- Configure [integrated apps settings](/copilot/microsoft-365/microsoft-365-copilot-app-admin-settings) for extensibility enablement and granular controls
+- Configure [agent settings](/copilot/microsoft-365/microsoft-365-copilot-app-admin-settings) for extensibility enablement and granular controls
 
 For more information, see [Agents admin guide for Microsoft 365](/copilot/microsoft-365/agent-essentials/m365-agents-admin-guide).
 

copilot/people-skills-sharing-inferencing-controls.md

@@ -109,7 +109,7 @@ __Example:__
 
 - User C isn't licensed for People Skills and has User Profile Application (UPA) Skills instead
 
-If the Admin turns off People Skills user experiences for User B, and keeps People Skills user experiences turned on for A, then User B may still be able to see user A's People Skills in Copilot or on the M365 Profile Card, provided User A has Skills visibility enabled and Skills sharing turned on. User B’s Microsoft 365 Profile Card shows no Skills experience when others view User B’s card. User C sees UPA Skills on their own M365 Profile Card, and for User A and User B. While User A and User B may not see their own UPA Skills on their M365 Profile Cards, they can still view, edit, or delete them in SharePoint – [learn more about UPA Skills and People Skills here](/copilot/microsoft-365/people-skills-overview).
+If the Admin turns off People Skills user experiences for User B, and keeps People Skills user experiences turned on for A, then User B and User C may still be able to see user A's People Skills in Copilot or on the M365 Profile Card, provided User A has Skills visibility enabled and Skills sharing turned on. User B’s and User C's Microsoft 365 Profile Card will show no Skills experience when others view User B’s and User C's card. User B and User C also see no Skills experience on their own M365 Profile Card, but they can see skills for User A when viewing User A's card. User A, User B and User C cannot see User C's UPA Skills on User C's profile card. While User C may not see their own UPA Skills on their M365 Profile Cards, they can still view, edit, or delete them in SharePoint – [learn more about UPA Skills and People Skills here](/copilot/microsoft-365/people-skills-overview).
 
 
 ## Overview of the Skills AI inferencing control 

copilot/workforce-insights-agent.md

@@ -67,11 +67,11 @@ For information on responsible AI principles and usage, see the following articl
     1. [Use admin controls to manage access to Workforce Insights](#use-admin-controls-to-manage-access-to-the-workforce-insights-agent-in-your-organization)
     2. Manage delegation policies  
 1. Download the Workforce Insights agent from the Agent Store in Microsoft 365 Copilot.
-1. Set up People Skills.
+1. Set up [People Skills](/copilot/microsoft-365/people-skills-setup).
 
 ## Use admin controls to manage access to the Workforce Insights agent in your organization
 
-You have several controls to deploy the Workforce Insights agent in their organization. You should review the controls to manage Workforce Insights agent deployment and access in their tenant.
+You have several controls to deploy the Workforce Insights agent in your organization. You should review the controls to manage Workforce Insights agent deployment and access in your tenant.
 
 The following controls are available:
 
@@ -87,13 +87,13 @@ For more information on how to manage agents, see [Manage agents for Microsoft 3
 
 As a manager or leader using the Workforce Insights agent, you can assign a delegate, or multiple delegates, to access the organizational data that's available to you about your team.  
 
-For example, if you're a manager, you might have access to confidential attributes about your team. This custom attribute could be called `salary`. If you assign a delegate to access this attribute, the delegate can query data within this column. When you enable delegates, it helps managers and leaders conduct analysis with the support of their team.
+For example, if you're a manager, you might have access to confidential attributes about your team. This custom attribute could be called `salary`. If you assign a delegate to access this attribute, the delegate can query data within this column. When you use delegates, it helps managers and leaders conduct analysis with the support of their team.
 
 ### Delegation admin controls
 
 | Control | Description |
 | --- | --- |
-| Disable the ability for a user to assign delegates | As the admin, you can restrict users from assigning a delegate to view their organizational insights. Use the Microsoft 365 control access to features with PowerShell under the module name WorkforceInsights. |
+| Disable the ability for a user to assign delegates | As the admin, you can restrict users from assigning a delegate to view organizational insights. Use the Microsoft 365 control access to features with PowerShell under the module name WorkforceInsights. |
 | Assign delegates or revoke delegates on behalf of a user | Starting in January 2026, as the admin, you can use PowerShell commandlets to assign or revoke delegates access on behalf of a user. |
 
 ### Assign delegates
@@ -126,7 +126,7 @@ Delegates can request access through a similar workflow.
 
 The following explains:  
 
-- How the Workforce Insights agent uses different types of data that can be supported when made available in your organization
+- How the Workforce Insights agent uses different types of data that is supported when made available in your organization
 - How you can configure data for the Workforce Insights agent to use
 
 | Data type | Description |

microsoft-365/admin/TOC.yml

@@ -272,7 +272,7 @@ items:
            href: /copilot/microsoft-365/copilot-for-microsoft-365-admin
          - name: Microsoft 365 Copilot extensibility
            items:
-            - name: Manage Copilot agents in the Microsoft 365 admin center
+            - name: Manage agents in the Microsoft 365 admin center
               href: manage/manage-copilot-agents-integrated-apps.md
             - name: Agent 365 Overview page
               href: manage/agent-365-overview.md

microsoft-365/enterprise/microsoft-365-multi-geo.md

@@ -44,11 +44,12 @@ In a _Multi-Geo_ environment, a Microsoft 365 _Tenant_ consists of a _Primary Pr
 
 _Microsoft 365 Multi-Geo_ is available as an add-on to the following Microsoft 365 subscription plans:
 
-- Microsoft 365 F1, F3, E3, or E5
-- Office 365 F3, E1, E3, or E5
-- Standalone Exchange Online Plan 1 or Plan 2
-- Standalone OneDrive Plan 1 or Plan 2
-- Standalone SharePoint Plan 1 or Plan 2
+- Microsoft 365 F1, F3, E3, or E5 (including SKUs without Microsoft Teams)
+- Office 365 F3, E1, E3, or E5 (including SKUs without Microsoft Teams)
+- Exchange Online Plan 1 or Plan 2
+- OneDrive Plan 1 or Plan 2
+- SharePoint Plan 1 or Plan 2
+- Microsoft Teams Enterprise, EEA, or Essentials
 
 ### Minimum Licensing