Merge branch 'main' into cmcatee-update-copilot-usage-table

Author: cmcatee-MSFT

copilot/agent-essentials/agent-lifecycle/agent-deploy.md

@@ -4,7 +4,7 @@ f1.keywords:
 ms.author: erikre
 author: ErikRe
 manager: dansimp
-ms.date: 11/12/2025
+ms.date: 02/23/2026
 ms.update-cycle: 180-days
 audience: Admin
 ms.topic: concept-article
@@ -25,22 +25,23 @@ By deploying an agent, you effectively install the agent on behalf of a user by
 Use the following steps to deploy an individual agent:
 
 1. Open the Copilot Control System within Microsoft 365 admin center in your browser.
-2. Select **Copilot** > **Agents**.
-    You'll see the **Agent inventory** tab is selected.
+2. Select **Agents** > **All agents**.
+    You'll see as list of the agents that you can manage for your tenant.
 3. Select an agent from the list.
 4. Select **Deploy**.
-5. Review the agent **Host products**, then select **Next**.
-6. Assign users
-7. Select to assign the agent based on one of the options:
+5. Review the agent **Host products** to understand where the agent will be available.
+6. Select to assign the agent based on one of the options:
     a. Just me
     b. Entire organization
     c. Specific users/groups
     Then, select **Next**.
-8. Review the agent permissions and capabilities, then select **Next**.
-9. Review the deployment, then select **Finish deployment**.
-10. When the deployment is complete, select **Done**.
 
-   :::image type="content" source="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deployment-complete.png" alt-text="Screenshot of a completed agent deployment within Microsoft 365 admin center."  lightbox="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deployment-complete.png":::
+   :::image type="content" source="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deploy-select-users.png" alt-text="Screenshot of the step to deploy agent to selected users from within Microsoft 365 admin center."  lightbox="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deploy-select-users.png":::
 
+7. Review and confirm the agent permissions and details, then select **Next**.
+8. Review the deployment, then select **Finish deployment**.
 
+   :::image type="content" source="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deploy-review-finish.png" alt-text="Screenshot of the step to review and and finish the process when deploying an agent from within Microsoft 365 admin center."  lightbox="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deploy-review-finish.png":::
+
+9. When the deployment is complete, select **Close**.
 

copilot/agent-essentials/agent-lifecycle/agent-upload-agents.md

@@ -4,7 +4,7 @@ f1.keywords:
 ms.author: erikre
 author: ErikRe
 manager: dansimp
-ms.date: 11/12/2025
+ms.date: 02/23/2026
 ms.update-cycle: 180-days
 audience: Admin
 ms.topic: concept-article
@@ -18,9 +18,9 @@ description: Learn how to upload Microsoft 365 Copilot custom agents.
 
 # Upload Microsoft 365 Copilot custom agents
 
-The Copilot Control System in Microsoft 365 admin center provides a method to upload a custom agent, so that you can manage those agents for your organization from your agent inventory. 
+The Copilot Control System in Microsoft 365 admin center provides a method to upload a custom agent, so that you can manage those agents for your organization from your agent inventory.
 
-To upload an agent, the agent must be contained in a ZIP packet file. The ZIP file contains resources, such as manifest files, configuration files, icons, branding, and embedded knowledge files. 
+To upload an agent, the agent must be contained in a ZIP packet file. The ZIP file contains resources, such as manifest files, configuration files, icons, branding, and embedded knowledge files.
 
 Your Copilot agent ZIP file can be downloaded from Copilot Studio by selecting **Agents** > *the name of your agent* > **Channels**. Select the channel you use to publish, such as **Teams and Microsoft 365 Copilot**. Select **Availability options** > **Download .zip**.
 
@@ -30,7 +30,7 @@ Your Copilot agent ZIP file can be downloaded from Copilot Studio by selecting *
 To upload an agent as a ZIP packet file to the Microsoft 365 admin center:
 
 1. Open Copilot Control System in [Microsoft 365 admin center](https://admin.microsoft.com/) in your browser.
-2. Select **Copilot** > **Agents** > **Upload custom agent**.
+2. Select **Agents** > **Upload custom agent**.
 3. Select **Choose File** to find and select the agent ZIP file.
     The ZIP file is validated.
 4. Verify the agent’s name, icon, and host products. Then, select **Next**.
@@ -40,7 +40,7 @@ To upload an agent as a ZIP packet file to the Microsoft 365 admin center:
     > You can select a small audience for testing purposes. For instance, select **Just me**, or a single test group to narrow the availability of the agent.
 
 6. Review the agent’s permissions and capabilities. Then, select **Next**.
-7. Select Finish deployment to review and finish the agent’s deployment.
+7. Select **Finish deployment** to review and finish the agent’s deployment.
 
 :::image type="content"  source="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deploy-new.png" alt-text="Screenshot of deploying a new agent within M365 the Copilot Control System."  lightbox="/copilot/microsoft-365/agent-essentials/media/m365-agents-admin-guide/agent-deploy-new.png":::
 

copilot/agent-essentials/media/m365-agents-admin-guide/agent-appsource.png

@@ -23,12 +23,12 @@ Monitoring the usage analytics of the Employee Self-Service agent should be part
 
 There are two approaches in consuming analytics:
 
-1. Systematically monitoring agent usage, effectiveness, quality, and satisfaction, which fall within the responsibilities of the service owner and/or creator. [Learn more](/microsoft-copilot-studio/analytics-overview) about Copilot Studio analytics documentation.
-1. Review agent usage, satisfaction scores, and other metrics to assess the agent's return on investment. [Learn more](/viva/insights/org-team-insights/copilot-dashboard) about Copilot.
+1. Service owners or makers systematically monitoring agent usage, effectiveness, quality, and satisfaction. [Learn more](/microsoft-copilot-studio/analytics-overview) about Copilot Studio analytics documentation.
+1. Organization leaders review agent usage, satisfaction scores, and other metrics to assess the agent's return on investment. [Learn more](/viva/insights/org-team-insights/copilot-dashboard) about Copilot.
 
 ## Measure what matters
 
-Employee Self-Service atelemetry is designed to help organizations move beyond basic usage reporting and toward **operational clarity, trust, and continuous improvement**. While Employee Self-Service collects a single, consistent telemetry stream, **different stakeholders interpret that telemetry through different lenses**, depending on the decisions they're responsible for making.
+Employee Self-Service telemetry is designed to help organizations move beyond basic usage reporting and toward **operational clarity, trust, and continuous improvement**. While Employee Self-Service collects a single, consistent telemetry stream, **different stakeholders interpret that telemetry through different lenses**, depending on the decisions they're responsible for making.
 
 This article explains how to interpret Employee Self-Service telemetry for each stakeholder in your organization, using the same storytelling model that Microsoft's product and engineering teams use internally. This information allows customers and product teams to align on what "good" looks like and what actions to take next.
 
@@ -45,7 +45,7 @@ This model ensures telemetry is decision-oriented as well as descriptive. The sa
 |**Intent**    |What employees are trying to do.             |
 |**Behavior**  |How the Employee Self-Service agent is used. |
 |**Outcome**   |Business and experience impact.              |
-|**Action**    |What should change as a result.              |
+|**Action**    |What should change as a result?              |
 
 ## Stakeholder-based interpretation guide
 
@@ -79,11 +79,11 @@ Executives should focus on **outcome-level telemetry**, not raw interaction coun
 - Sustained adoption beyond pilot phases (trust and repeat usage)	
 - Predictable scale without increasing support or incident load
 
-**What to use When**
+**What to use when**
 
 [Copilot Analytics introduction](/viva/insights/copilot-analytics-introduction#which-tool-should-i-use-when)
 
-### 1. Product / Service Owners
+### 2. Product/Service Owners
 
 **Primary question**
 
@@ -114,6 +114,12 @@ Product/service stakeholders focused on each business domain/verticals such as H
 - Prevent regressions such as prompts, knowledge, or integrations change
 - Focus investment on highest-impact scenarios, not vanity metrics
 
+**What to use When**
+
+[Copilot Analytics introduction](/viva/insights/copilot-analytics-introduction#which-tool-should-i-use-when)
+
+[Copilot Studio - Analytics](/microsoft-copilot-studio/analytics-overview)
+
 #### Interpreting Telemetry by verticals
 This section is designed to help you operationalize the Employee Self-Service telemetry across your organization by anchoring analytics to real scenarios, clear stakeholder questions, and concrete actions.
 
@@ -125,7 +131,7 @@ This section is designed to help you operationalize the Employee Self-Service te
 - "How do I apply for parental leave?"
 - "Can I add a dependent to my benefits?"
 
-**HR stakeholders & questions**
+**HR stakeholders and questions**
 
 |Stakeholder                |Key question                                                   |
 |---------------------------|---------------------------------------------------------------|
@@ -166,7 +172,7 @@ This section is designed to help you operationalize the Employee Self-Service te
 |---------------------|--------------------------------------------------------------------------------|
 |**IT Service Owner** |Is the Employee Self-Service agent reducing ticket volume for common IT issues? |
 |**IT Operations**    |Are failures due to configuration or platform issues?                           |
-|**Security / IAM**   |Are requests handled securely and consistently?                                 |
+|**Security**         |Are requests handled securely and consistently?                                 |
 
 **Telemetry signals to review for IT**
 - Ticket deflection indicators
@@ -178,13 +184,13 @@ This section is designed to help you operationalize the Employee Self-Service te
 - **Low assisted support + high completion** = Effective IT self-service
 - **Errors clustered by scenarios** = Configuration or connector issues
 - **Latency spikes** = Throttling, dependency, or orchestration bottlenecks
-- **Security-related fallbacks** = IAM or policy misalignment
+- **Security-related fallbacks** = policy misalignment
 
 **Recommended actions for IT**
 - Focus telemetry reviews on top ticket-deflecting scenarios
 - Use diagnostics to distinguish config issues vs. product gaps
 - Validate performance telemetry before scaling rollout
-- Pair telemetry with readiness and ALM checks for production moves
+- Pair telemetry with readiness and Application Lifecycle Management (ALM) checks for production moves
 
 ***Facilities & Workplace services***
 **Typical Workplace scenarios**
@@ -220,7 +226,7 @@ This section is designed to help you operationalize the Employee Self-Service te
 - Use telemetry to justify integration investments
 - Track sentiment trends as a proxy for workplace trust
 
-### IT Administrators & Makers ###
+### 3. IT Administrators & Makers ###
 **Primary question**
 
 *Is the Employee Self-Service agent configured correctly, stable, and ready to scale?*
@@ -244,6 +250,12 @@ Administrators and Makers should interpret telemetry as **health and readiness i
 - Validates environments before promoting to production
 - Coordinate changes using ALM and readiness checks
 
+**What to use When**
+
+[Copilot Studio - Analytics](/microsoft-copilot-studio/analytics-overview)
+
+[Capture telemetry with Application Insights](/microsoft-copilot-studio/advanced-bot-framework-composer-capture-telemetry)
+
 ## Employee Self-Service analytics and evaluations: A unified playbook to accelerate time-to-value (TTV)
 
 ### Why combine telemetry and evaluations?
@@ -263,3 +275,5 @@ The shared operating model:
 **'Intent ➡️ Behavior ➡️ Outcome ➡️ Action'**
 
 Evals plug into the same model by providing repeatable evidence about whether the agent can reliably deliver the intended outcomes before you expose the change to broad employee usage.
+
+[Learn more](/microsoft-copilot-studio/analytics-overview)

copilot/agent-essentials/media/m365-agents-admin-guide/agent-deploy-new.png

@@ -68,9 +68,9 @@ For both tenants, perform the following steps:
 
 
 ```powershell
-Expand-Archive ` -Path ".\CrossTenantMigration.nupkg" ` -DestinationPath ".\CTModule" ` -Force
+Expand-Archive -Path ".\CrossTenantMigration.nupkg" -DestinationPath ".\CTModule" -Force
 
-Import-Module ` 
+Import-Module -Name ".\CTModule\CrossTenantMigration" -Force
 ```
 
 3. Set up the Cross-Tenant Migration Service Application on the **target tenant only**. Run `Grant-CTMSAppPermissions`

copilot/agent-essentials/media/m365-agents-admin-guide/agent-deploy-review-finish.png

@@ -131,9 +131,10 @@ If you need to edit Identity Mapping while any migration batches are running, do
 5. Migrated threads that are still accessible on the source tenant. They aren't locked, but any new messages sent after migration don't migrate to the target tenant.
 6. Apps aren't migrated, including Polls.
 7. Forwarded/Scheduled messages aren't migrated. If a scheduled message was sent, it migrates. If a scheduled message was scheduled, but not sent, it doesn't migrate.
-8. Messages that include unsupported emojis or decommissioned emojis don't migrate.
-9. Users with unrecognized GUID formats, users without Microsoft accounts, and users without display names or user IDs don't have their messages migrated and aren't added to target threads.
-10. Threads without any identifiable members aren't migrated.
+8. Users with unrecognized GUID formats, users without Microsoft accounts, and users without display names or user IDs don't have their messages migrated and aren't added to target threads.
+9. Threads without any identifiable members aren't migrated.
+10. Users who removed from chats before migration don't see the chat history on the target after migration.
+11. Messages with unsupported/decommissioned emojis, missing body content, legacy Skype metadata, code snippets, invalid source images, attachments without extensions, or attachments with missing markers aren't migrated.
 
 ## Meetings issues