From e3f8c0d3c25cdf65b44b22943b2728f1f2c66af4 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 1 Jul 2026 00:54:31 +0000
Subject: [PATCH 1/3] Initial plan


From bde9749445ec787f8d27f157f6e6c65cdd70a803 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 1 Jul 2026 01:03:23 +0000
Subject: [PATCH 2/3] fix: sync rendered lab docs with recent README updates

---
 _labs/agent-builder-m365.md                   | 12 ++---
 _labs/agent-builder-sharepoint.md             | 14 ++---
 _labs/ask-me-anything.md                      | 52 +++++++++---------
 _labs/autonomous-account-news.md              | 10 ++--
 _labs/autonomous-cua.md                       | 20 +++----
 _labs/autonomous-support-agent.md             | 30 +++++------
 _labs/core-concepts-agent-knowledge-tools.md  | 42 +++++++--------
 ...core-concepts-variables-agents-channels.md | 22 ++++----
 _labs/mcs-orchestration.md                    | 34 ++++++------
 _labs/mcs-tools.md                            | 54 +++++++++----------
 _labs/setup-for-success.md                    | 22 ++++----
 11 files changed, 156 insertions(+), 156 deletions(-)

diff --git a/_labs/agent-builder-m365.md b/_labs/agent-builder-m365.md
index eb3d95e2..87bd820d 100644
--- a/_labs/agent-builder-m365.md
+++ b/_labs/agent-builder-m365.md
@@ -183,7 +183,7 @@ Create, configure, and test a web-based Copilot agent that serves as a knowledge
 >
 >   ![alt text](images/correct-copilot-page.png)
 >
-> - Make sure the **logged in user** is the fictitious one used in the lab. If you need your normal work user account, **select** the name and toggle to the fictitious user account.
+> - Make sure the **logged in user** is the fictitious one used in the lab. If you see your normal work user account, **select** the name and toggle to the fictitious user account.
 >
 >   ![alt text](images/logged-in-user.png)
 
@@ -245,7 +245,7 @@ Create, configure, and test a web-based Copilot agent that serves as a knowledge
 
 #### Create your learning assistant agent
 
-6. On the left side navigation pane, select **Agents** to open the **Agent Store**, then select **Create agent** (or the **New agent** card)
+6. On the left side navigation pane, select **New agent**.
 
 
 7. Notice that you can explore existing available templates. For this lab, paste the following into the **Describe the agent you want to create** input area at the top of the form (the describe textbox is the primary input — there is no separate tab to select), and then select Send.
@@ -297,9 +297,9 @@ Create, configure, and test a web-based Copilot agent that serves as a knowledge
 
 13. Fix any issue like max character limit for starter prompt titles.
 
-14. You can test your agent in the test pane. When ready, select **Create** in the upper right corner to finish creating your agent.
+14. You can test your agent in the **Preview** pane. When ready, select **Create** in the upper right corner to finish creating your agent.
 
-![Agent Builder test pane](images/agent-builder.png)
+![Agent Builder Preview pane](images/agent-builder.png)
 
 #### Share and test your agent
 
@@ -408,7 +408,7 @@ Build a sophisticated Sales Admin Assistant that integrates organizational data
 
 5. Return to [Microsoft 365 Copilot](https://m365.cloud.microsoft/chat/?auth=2&home=1).
 
-6. On the left side pane, select **Agents** to open the **Agent Store**, then select **Create agent** (or the **New agent** card).
+6. On the left side pane, select **New agent**.
 
 7. In the **Describe the agent you want to create** textbox at the top of the new agent page, paste the following prompt and press Send (or Enter). The describe textbox is the primary input — there is no separate tab to select.
 
@@ -659,7 +659,7 @@ Use the Analyst agent to perform a detailed ROI analysis with NPV, IRR, and disc
 
 1. Navigate to [Microsoft 365 Copilot](https://m365.cloud.microsoft/chat/?auth=2&home=1).
 
-2. Select the **Analyst** agent. You can find it by:
+2. Select the **Analyst** agent.
    - Selecting the agent picker and choosing **Analyst**
    - Or typing `@Analyst` in the chat input area
 
diff --git a/_labs/agent-builder-sharepoint.md b/_labs/agent-builder-sharepoint.md
index cebb8e2f..36c203fd 100644
--- a/_labs/agent-builder-sharepoint.md
+++ b/_labs/agent-builder-sharepoint.md
@@ -124,15 +124,15 @@ Build a specialized agent with SharePoint integration and advanced AI capabiliti
 
 1. Navigate to [Microsoft 365 Copilot Chat](https://m365.cloud.microsoft/chat/?auth=2&home=1) and go to the **Chat** tab.
 
-2. On the side pane, expand **Agents** and select **Create agent**.
+2. On the side pane select **New agent**.
 
-3. When prompted to **describe the agent**, use this specific prompt:
+3. In the **describe the agent** chat, use this specific prompt:
 
     ```
     You are a Sales Admin Assistant. Your job is to help sales managers track revenue and identify trends across product lines. You understand product hierarchies, time periods (e.g. quarters, fiscal years), and sales metrics. Users can ask questions like 'Graph the sales for the last 2 years with a breakdown per product line and quarter'. You always respond in a friendly and professional tone, aiming to be helpful and insightful.
     ```
 
-4. **Confirm** the suggested agent name when prompted.
+4. Go to the **Configure** tab.
 
 5. Go to the **Configure** tab
 
@@ -146,12 +146,12 @@ Commented out; screenshots need update due to CPS updates.  Last minute change t
 -->
 
 6. Under **capabilities**, enable:
-   - **Code interpreter** (for data analysis and chart generation)
-   - **Image generator** (for creating visual content)
+   - **Create documents, charts, and code** (for data analysis and chart generation)
+   - **Create images** (for creating visual content)
 
 #### Finalize configuration
 
-6. Navigate to the **Configure** tab to review and refine:
+6. Review and refine the following:
    - Agent name and description
    - Instructions
    - Starter prompts
@@ -228,7 +228,7 @@ Design a professional badge for the first place winner of our 2026 sales contest
 
 8. Select **...** next to your agent name in the side bar navigation, and choose **Edit**
 
-9. Select the Sales agent you created
+9. In the **Configure** tab, explore additional **knowledge** capabilities:
 
 10. In the **Configure** tab, explore additional **knowledge** capabilities:
    - All **Websites** (or specific websites)
diff --git a/_labs/ask-me-anything.md b/_labs/ask-me-anything.md
index 292f6117..7d63b125 100644
--- a/_labs/ask-me-anything.md
+++ b/_labs/ask-me-anything.md
@@ -1,7 +1,7 @@
 ---
 module: ask-me-anything
 title: "Create an 'Ask me anything' agent for your employees"
-description: "Empower employees with answers that matter – Build an intelligent agent that connects to your knowledge and data."
+description: "Build an agent that answers employee questions using your organization's knowledge and data."
 order: 13
 duration: 40
 difficulty: 200
@@ -159,7 +159,7 @@ Create a new agent with SharePoint knowledge integration that provides grounded,
 
 ### Step-by-step instructions
 
-1. Navigate to the Copilot Studio home page at [copilotstudio.microsoft.com](https://copilotstudio.microsoft.com/)
+1. Go to the Copilot Studio home page at [copilotstudio.microsoft.com](https://copilotstudio.microsoft.com/)
 
 2. Go to the Solutions menu (located in the left-hand menu under the ellipsis …)
 
@@ -175,14 +175,14 @@ Create a new agent with SharePoint knowledge integration that provides grounded,
 
 8. Go to **Knowledge**
 
-    ![alt text](images/knowledge-sharepoint.png)
+    ![Copilot Studio "Add knowledge" dialog with SharePoint option highlighted](images/knowledge-sharepoint.png)
 
 9. Select **SharePoint**, and paste the SharePoint Knowledge URL and select **Add**.
 
     > [!IMPORTANT]
     >  * For configuration, use the provided values in the **Lab Resources** (specific per training).
 
-10. Choose **Add**  
+10. Select **Add**
 
     > [!TIP]
     > - If an error appears after adding the SharePoint URL, click "Browse items" and then "Confirm selection".
@@ -291,7 +291,7 @@ Make the agent available in Microsoft 365 Copilot for your users.
 
 8. Select **See agent in Microsoft 365** 
 
-   ![alt text](images/m365-copilot-channel.png)
+   ![Copilot Studio agent published to Teams and Microsoft 365 Copilot channel successfully](images/m365-copilot-channel.png)
 
 9. In the **Microsoft 365 Copilot** experience, the agent description will pop up. Select **Add**
 
@@ -355,17 +355,17 @@ Let's start by asking for the user country at the beginning of the conversation.
 
 <!-- replacing with instrucftions on how to do this on message received, so it works in M365 channel too
 
-2. Now, in your 'Ask Me Anything' agent, go to the **Topics** tab, and then to the **System topics** tab.
+2. In your 'Ask Me Anything' agent, go to the **Topics** tab, and then to the **System topics** tab.
 
 3. Open the **Conversation Start** topic
 
 4. At the beginning of the topic, right after the **Trigger**, add a new node **(+)** and choose **Add a tool**.
 
-5. Go the **Connector** tab, and search for `Microsoft Entra ID Get user`
+5. Go to the **Connector** tab, and search for `Microsoft Entra ID Get user`
 
 6. Select the **Get user** connector action and **Submit**.
 
-    ![alt text](images/add-tool-connector.png)
+    ![Get user Microsoft Entra ID connector tool in Copilot Studio flow editor](images/add-tool-connector.png)
 
     > [!IMPORTANT]
     > - If you don't see the **Get user** action, select another of the Microsoft Entra ID actions, such as **Create user**  and **Submit**.
@@ -378,9 +378,9 @@ Let's start by asking for the user country at the beginning of the conversation.
 
 8. Toggle the **End user authentication** to **Agent author authentication**.
 
-9. In the **Inputs** tab, for **User Id or Principal Name**, select `...`, go the the **System** tab, and select **User.Id**.
+9. In the **Inputs** tab, for **User Id or Principal Name**, select `...`, go to the **System** tab, and select **User.Id**.
 
-    ![alt text](images/select-user-id.png)
+    ![Microsoft Copilot Studio Get user action with User.Id system variable selected as input](images/select-user-id.png)
 
 10. **Save**
 
@@ -392,7 +392,7 @@ Let's start by asking for the user country at the beginning of the conversation.
 
 4. At the beginning of the topic, right after the **Trigger**, add a new node **(+)** and choose **Add a tool**.
 
-5. Go the **Connector** tab, and search for `Microsoft Entra ID Get user`
+5. Go to the **Connector** tab, and search for `Microsoft Entra ID Get user`
 
 6. Select the **Get user** connector action and **Submit**.
 
@@ -402,7 +402,7 @@ Let's start by asking for the user country at the beginning of the conversation.
 
 8. Toggle the **End user authentication** to **Maker-provided credentials**.
 
-9. In the **Inputs** tab, for **User Id or Principal Name**, select `...`, go the the **System** tab, and select **User.Id**.
+9. In the **Inputs** tab, for **User Id or Principal Name**, select `...`, go to the **System** tab, and select **User.Id**.
 
     ![alt text](images/select-user-id.png)
 
@@ -414,9 +414,9 @@ Let's start by asking for the user country at the beginning of the conversation.
     Hello!
     ```
 
-15. Navigate to the **Topics** tab, open the **Conversation Starts** topic, and to see what values are returned from the connector, enter the **Variables** pane in the topic command bar. Go the **Test** to see the variable values at runtime (i.e., as you are testing in the conversation test pane).
+15. Go to the **Topics** tab, open the **Conversation Starts** topic, and to see what values are returned from the connector, enter the **Variables** pane in the topic command bar. Go the **Test** to see the variable values at runtime (i.e., as you are testing in the conversation test pane).
   
-    ![alt text](images/variables-pane.png)
+    ![Variables panel open with Test tab selected, showing Topic variable GetUser of type record](images/variables-pane.png)
 
 16. Select **Value** under the **GetUser** record, and **expand** it to see if the expected value was returned.
 
@@ -468,7 +468,7 @@ Let's start by asking for the user country at the beginning of the conversation.
     > - Use the formula provided in the **Lab Resources** (specific per training).
     > - Notice how the formula concatenates the SharePoint URL with the office location, effectively using context to target the correct source and location for the content.
 
-    ![alt text](images/sharepoint-formulas.png)
+    ![Copilot Studio topic editor configuring SharePoint data source with a dynamic formula using office location variable](images/sharepoint-formulas.png)
 
 27. Select **Insert** once done, then **Save** your topic
 
@@ -496,7 +496,7 @@ Let's start by asking for the user country at the beginning of the conversation.
 
 32. We need to set the variable value in-between the parenthesis. **Type** `/` and select **Power Fx**.
 
-    ![alt text](images/instructions-formula.png)
+    ![Power Fx option highlighted in Instructions panel dropdown menu](images/instructions-formula.png)
 
 33. **Type** `Global.GetUser.officeLocation` and select **Insert**
 
@@ -554,7 +554,7 @@ This use case demonstrates **agent scoping** principles:
 
 2. Go to the **Agents** tab, and **+ Add an agent**
 
-    ![alt text](images/add-agent.png)
+    ![Choose how to extend your agent dialog with 'Create an agent' option selected](images/add-agent.png)
 
 3. Update 
     - Its **Name** to: `IT Support Agent`
@@ -575,7 +575,7 @@ This use case demonstrates **agent scoping** principles:
 
 5. Select **ServiceNow**
 
-6. Choose the **ServiceNow** connection under **Your connections**, and **Next**
+6. Select the **ServiceNow** connection under **Your connections**, and **Next**
    
 8. Select **Knowledge** as the knowledge source.
 
@@ -603,9 +603,9 @@ This use case demonstrates **agent scoping** principles:
     > [!IMPORTANT]
     > In production scenarios, you may want to use the user context when making the connection to ServiceNow. Here, your context (as the author) is used by end-users of your agent when searching for incidents.
 
-8. For **Record Type**, under **Fill using**, choose **Custom value** and choose `Incident`
+8. For **Record Type**, under **Fill using**, select **Custom value** and select `Incident`
 
-9. Select **+ Add input** and choose **Query**
+9. Select **+ Add input** and select **Query**
 
 10. Next to **Dynamically fill with AI**, select **Customize** and use this for **Description**:
 
@@ -619,7 +619,7 @@ This use case demonstrates **agent scoping** principles:
 
 11. Select **+ Add input** and choose **Limit**
 
-12. Under **Fill using**, choose **Custom value** and  set **1**
+12. Under **Fill using**, select **Custom value** and  set **1**
 
 13. Select **Save**
 
@@ -639,7 +639,7 @@ This use case demonstrates **agent scoping** principles:
     > - Creates user-friendly responses with proper formatting
     > - Combines ServiceNow data with other knowledge sources when needed
 
-    ![alt text](images/multi-agent-servicenow.png)
+    ![Copilot Studio activity map showing IT Support Agent handling USB troubleshooting and ServiceNow ticket query](images/multi-agent-servicenow.png)
 
 29. **Observe** how your agent now demonstrates scoped capabilities:
     - **Tool Selection**: Automatically chooses the right ServiceNow tool based on user intent
@@ -703,7 +703,7 @@ In this section, you'll configure any third-party knowledge to enrich knowledge
 
 5. Add a new node > **Advanced**, **Send HTTP request**
 
-6. For **URL**, select `...`, go the **Environment** tab, and choose the **Custom Knowledge Endpoint**  variable you had created.
+6. For **URL**, select `...`, go the **Environment** tab, and select the **Custom Knowledge Endpoint**  variable you had created.
 
 7. **Method**: `Post`
 
@@ -734,7 +734,7 @@ In this section, you'll configure any third-party knowledge to enrich knowledge
 
 13. Under **Save response as**, select **Create a new variable**, select the variable name that was created (e.g., **Var1**) and rename it `KnowledgeResults`.
 
-    ![alt text](images/http-request.png)
+    ![HTTP Request action configured with POST method, JSON body using System.Activity.Text, saving results as KnowledgeResults table](images/http-request.png)
 
 14. Add a new node, **Variable management** > **Set a variable value**
 
@@ -768,7 +768,7 @@ In this section, you'll configure any third-party knowledge to enrich knowledge
 > Notice how the knowledge step returned results that contain citations to a fictitious knowledge base.
 
 
-  ![alt text](images/custom-knowledge-source.png)
+  ![Knowledge node response showing vendor update steps with 3 referenced sources highlighted](images/custom-knowledge-source.png)
 
 ---
 
@@ -855,7 +855,7 @@ In this section, you'll learn how to upload files and run files through a prompt
 
 14. **Save** your prompt
 
-    ![alt text](images/prompt.png)
+    !Copilot Studio AI prompt node "Meeting AI Notes" with GPT-4o model returning JSON meeting data](images/prompt.png)
 
 14. **Save** the topic.
 
diff --git a/_labs/autonomous-account-news.md b/_labs/autonomous-account-news.md
index 9d8367dc..6729c964 100644
--- a/_labs/autonomous-account-news.md
+++ b/_labs/autonomous-account-news.md
@@ -161,7 +161,7 @@ Set up an autonomous agent with a recurring trigger that automatically activates
 
 1.  In the agent's **Overview** tab, scroll to the **Triggers** section.
 
-  > [!TIP]
+  > [!IMPORTANT]
   > The triggers section may not be immediately available as it depends on background processes started when the agent is created.  This should take no more than a minute to complete.
 
   1.  Select **Add trigger**, select **Recurrence**, and then select **Next**
@@ -215,7 +215,7 @@ Set up an autonomous agent with a recurring trigger that automatically activates
 
 1. Search for `List rows` and select the **List rows from selected environment** action (under **Microsoft Dataverse**, displayed as *List rows from a table in a Power Platform environment*).
 
-1. Choose an existing Dataverse connection or add a new one (select Oauth as authentication type).
+1. Select an existing Dataverse connection or add a new one (select OAuth as authentication type).
 
     > [!IMPORTANT]  
     > If you need to create the connection use OAuth and sign in with your workshop credentials. Your user requires permission to access Opportunity records, which is provided as part of the workshop.
@@ -671,7 +671,7 @@ Automate the final step: format relevant news into a clean, branded email for ac
 
 1. Select **Insert**.
 
-1. Save the **Conversation start** topic
+1. Save the **Conversation start** topic.
 
 1. Now that your agent has a preloaded HTML template, configure an Outlook email tool to deliver the report.
 
@@ -708,7 +708,7 @@ Automate the final step: format relevant news into a clean, branded email for ac
 
 1. Now that you've created the report template and configured the email tool, you'll guide the agent to use them as part of its orchestration.
 
-1. Go to your agent and go to the **Overview** tab.
+1. Go to your agent and select the **Overview** tab.
 
 1. In the **Instructions** section, add the following steps:
 
@@ -728,7 +728,7 @@ Automate the final step: format relevant news into a clean, branded email for ac
 1. **Save** your agent's instructions. The instructions should appear as follows:
     ![Instructions After Topics](images/final-instructions.png)
 
-1. Go to the **Triggers** section and Select **Test trigger** on the `Analyze Opportunities` trigger.
+1. Go to the **Triggers** section and select **Test trigger** on the `Analyze Opportunities` trigger.
 
 1. Once the agent finishes executing, verify:
    - It retrieved opportunities from the Sales App
diff --git a/_labs/autonomous-cua.md b/_labs/autonomous-cua.md
index 994c3c11..c420e839 100644
--- a/_labs/autonomous-cua.md
+++ b/_labs/autonomous-cua.md
@@ -139,11 +139,11 @@ Learn how to create and configure an autonomous agent that listens for specific
 
 #### Creating the agent and trigger setup
 
-1. Navigate to [copilotstudio.microsoft.com](https://copilotstudio.microsoft.com)
+1. Go to [copilotstudio.microsoft.com](https://copilotstudio.microsoft.com)
 
 1. Make sure you're in the correct environment by looking at the top right corner. In these labs, the environment name should start with **'DEV - '**
 
-1. Go to the **Solutions** menu (located in the left-hand menu under the ellipsis `...`)
+1. Go to the **Solutions** menu (located in the left navigation menu under the ellipsis `...`)
 
 1. Select the solution you had created previously for your labs
 
@@ -157,7 +157,7 @@ Learn how to create and configure an autonomous agent that listens for specific
 
 #### Configuring email triggers
 
-9. Scroll down to the triggers section and click **+Add trigger**
+9. Scroll down to the triggers section and select **+Add trigger**
 
 1. Search and select `When a new email arrives (V3) (Office 365 Outlook)`
 
@@ -201,7 +201,7 @@ Learn how to integrate and configure tools for desktop automation and email comm
 
 #### Configuring the Computer use tool
 
-1. Navigate to **Tools** in the top-level menu
+1. Go to **Tools** in the top-level menu
 
 1. Select **+ Add a tool**
 
@@ -247,7 +247,7 @@ Learn how to integrate and configure tools for desktop automation and email comm
     - The left panel shows your instructions and a step-by-step log of the tool’s reasoning and actions.
     - The right panel shows a preview of the actions on the machine you set up for computer use.
 
-    ![alt text](images/test_CUA.jpg)
+    ![Financial Portfolio Dashboard showing portfolio 44123BCD for Munson's Pickles, valued at $120,000,000](images/test_CUA.jpg)
 
 18. Select **Finish testing**
 
@@ -277,11 +277,11 @@ Learn how to integrate and configure tools for desktop automation and email comm
 1. Customize the **Body** input and set its **Description** to:
     `Write the email body using HTML and highlight the requested data.`
 
-1. Click **Save** to finalize the tool configuration
+1. Select **Save** to finalize the tool configuration
 
 #### Configuring agent instructions and AI settings
 
-29. Navigate to **Overview** tab and then **Edit** the **Instructions**
+29. Go to **Overview** tab and then **Edit** the **Instructions**
 
 1. Paste the following comprehensive instructions:
     ```
@@ -291,7 +291,7 @@ Learn how to integrate and configure tools for desktop automation and email comm
     > [!IMPORTANT]
     > For each of the placeholder <...> in the description, use / to insert the tools you just configured in your instructions.
 
-    ![alt text](images/agent_instructions.jpg)
+    ![Copilot instruction editor with dropdown showing "Reply to email" tool selected](images/agent_instructions.jpg)
 
 31. **Save** the instructions
 
@@ -319,7 +319,7 @@ Learn how to integrate and configure tools for desktop automation and email comm
 
 1. Select the trigger instance and then **Start testing**
 
-    ![alt text](images/test_trigger.jpg)
+    ![Test your trigger" dialog with Jul 10 instance selected and Start testing button](images/test_trigger.jpg)
 
 38. Check your emails for the agent’s reply.
 
@@ -327,7 +327,7 @@ Learn how to integrate and configure tools for desktop automation and email comm
 > - Monitor the Computer use tool's actions in the Test chat window or through the agent's **Activity** page.
 > - In the **Activity** page select the current run and switch from **Activity map** to **Transcript** to get a real-time view of all the steps of the Computer use tool along with their respective screenshots. This view is especially useful in autonomous agent runs.
 
-> [!NOTE]
+> [!TIP]
 > Send an additional email request for another portfolio ID and observe the results.
 
 ---
diff --git a/_labs/autonomous-support-agent.md b/_labs/autonomous-support-agent.md
index a8301254..ea3b926b 100644
--- a/_labs/autonomous-support-agent.md
+++ b/_labs/autonomous-support-agent.md
@@ -165,7 +165,7 @@ Create an autonomous agent that automatically triggers when new support emails a
 
 7. Select **Create**.
 
-> [!TIP]
+> [!NOTE]
 > Choose a descriptive name that clearly identifies the agent's purpose for easier management in larger environments.
 
 #### Configuring Email Triggers
@@ -235,9 +235,9 @@ In this section, you'll learn how to integrate knowledge sources, configure Serv
 
 #### Adding Knowledge Sources
 
-1. Navigate to the **Knowledge** tab in your agent and select **+ Add knowledge**
+1. Go to the **Knowledge** tab in your agent and select **+ Add knowledge**
 
-2. Choose **Public website** as your knowledge source type
+2. Select **Public website** as your knowledge source type
 
 3. **Add** this URL: `https://support.servicenow.com/` 
 
@@ -250,7 +250,7 @@ In this section, you'll learn how to integrate knowledge sources, configure Serv
 
 5. Search for `ServiceNow List records` and select **List records**
 
-6. Ensure your connection is selected from the dropdown, or select `Create New Connection` and enter the details from the Lab Resources.
+6. Make sure your connection is selected from the dropdown, or select `Create New Connection` and enter the details from the Lab Resources.
 
 7. Select **Add and configure**
 
@@ -302,31 +302,31 @@ In this section, you'll learn how to integrate knowledge sources, configure Serv
 
 22. Under **Additional details**, set **Credentials to use** to **Maker-provided credentials**
 
-23. For the **To** input, keep **Dynamically fill with AI**, click on **Customize** to set its **Description** to:
+23. For the **To** input, keep **Dynamically fill with AI**, select on **Customize** to set its **Description** to:
 
     ```
     Use the "from" email of the triggering received email.
     ```
 
-24. For the **Subject** input, keep **Dynamically fill with AI**, click on **Customize** to set its **Description** to:
+24. For the **Subject** input, keep **Dynamically fill with AI**, select on **Customize** to set its **Description** to:
 
     ```
     Use the original subject of the triggering received email.
     ```
 
-25. For the **Body** input, keep **Dynamically fill with AI**, click on **Customize** to set its **Description** to:
+25. For the **Body** input, keep **Dynamically fill with AI**, select on **Customize** to set its **Description** to:
 
     ```
     Write the email body using minimal HTML that renders well in Outlook. Use <p> for paragraphs, <br> for line breaks, <ul>/<ol> for bullet points, and <table> for simple tables if needed. All URLs must be formatted as HTML links using <a href="...">, not left as plain text. Do not use Markdown syntax like [1] or reference-style links. Do not include full HTML documents or tags like <html> or <head>. The HTML must be valid as a JSON string: escape double quotes (") and avoid unescaped special characters.
     ```
 
-26. Click **Save** to finalize the tool configuration
+26. Select **Save** to finalize the tool configuration
 
 #### Configuring Agent Instructions and AI Settings
 
-27. Navigate to **Overview** and then click the **Edit** for **Instructions**
+27. Go to **Overview** and then click the **Edit** for **Instructions**
 
-28. **Paste** the following comprehensive instructions:
+28. **Paste** the following instructions:
 
     ```
     1. Understand and isolate each question from the received email body.
@@ -341,13 +341,13 @@ In this section, you'll learn how to integrate knowledge sources, configure Serv
     > [!TIP]
     > Note: the UX may differ and you don't have that option, leave the description as-is.
 
-    ![alt text](images/instructions-and-tools.png)
+    ![Reply to email tool selected in agent instructions dropdown menu](images/instructions-and-tools.png)
 
-29. Click on **Save** to save the instructions and **Publish** your agent to activate it
+29. Select on **Save** to save the instructions and **Publish** your agent to activate it
 
 #### Testing Your Complete Agent
 
-30. **Send** a test email to your training user email by using the **Workshop Agent**. Simply ask `Send a support email`. You will then shortly receive the email in **Microsoft Outlook**.
+30. **Send** a test email to your training user email by using the **Workshop Agent**. Ask it to `Send a support email`. You will then shortly receive the email in **Microsoft Outlook**.
 
     > [!IMPORTANT]
     > - Access the workshop agent in the same location as when you created your training user account.
@@ -373,7 +373,7 @@ In this section, you'll learn how to integrate knowledge sources, configure Serv
     > [!TIP]
     > You don't need to repeat the original trigger event to make more tests. In the **Test** pane, you can select `...`, choose **Test trigger** and then select the desired trigger and from there, decide to execute a past trigger again.
     > 
-    > ![alt text](images/test-trigger.png)
+    > ![Test trigger option highlighted in the Test your agent dropdown menu"](images/test-trigger.png)
 
 32. Check the execution of your  autonomous agent by going to the **Activity** tab. Select the **Refresh** icon until you see the execution.
 
@@ -394,7 +394,7 @@ In this section, you'll learn how to integrate knowledge sources, configure Serv
 >   - Fallback
 >   - Multiple topics matched
 
-![alt text](images/autonomous-agent-plan.png)
+![Copilot Studio activity map showing "Send a Teams message" connector action marked Complete](images/autonomous-agent-plan.png)
 
 ---
 
diff --git a/_labs/core-concepts-agent-knowledge-tools.md b/_labs/core-concepts-agent-knowledge-tools.md
index ee0a9e88..497b401c 100644
--- a/_labs/core-concepts-agent-knowledge-tools.md
+++ b/_labs/core-concepts-agent-knowledge-tools.md
@@ -159,9 +159,9 @@ Create a fully configured Copilot Studio agent with clear instructions and Claud
 
 #### Create Your Agent
 
-1. Navigate to [Microsoft Copilot Studio](https://copilotstudio.microsoft.com) and sign in with your credentials.
+1. Go to [Microsoft Copilot Studio](https://copilotstudio.microsoft.com) and sign in with your credentials.
 
-   > [!NOTE]
+   > [!IMPORTANT]
    > On a first sign-in (especially for workshop / fresh-tenant accounts) you may see a one-time **Welcome to Microsoft Copilot Studio** consent dialog. Select **Get Started** to dismiss it. (If it later appears stacked *behind* the **Name your agent** dialog, select **Cancel** on that dialog, choose **Get Started**, then create the agent again.)
 
 1. In the left navigation, select **Agents**.
@@ -208,13 +208,13 @@ Create a fully configured Copilot Studio agent with clear instructions and Claud
 
 1. Select **Public websites** from the list of knowledge source options.
 
-1. Input the following URL and select **Add**
+1. Input the following URL and select **Add**.
 
    ```
    https://learn.microsoft.com
    ```
 
-1. The website should appear in the list of links, select **Add to agent** to save the change.
+1. The website should appear in the list of links. Select **Add to agent** to save the change.
 
 
 #### Test Your Agent
@@ -283,7 +283,7 @@ Add a document knowledge source to your agent and verify that it accurately answ
 
 #### Add Document Knowledge Source
 
-1. In your Copilot Studio agent, Select  **Knowledge** in the top navigation bar for the agent.
+1. In your Copilot Studio agent, select  **Knowledge** in the top navigation bar for the agent.
 
 1. Download the [Copilot Studio Licensing Guide (June 2026)](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/bade/documents/products-and-services/en-us/bizapps/Microsoft-Copilot-Studio-Licensing-Guide-June-2026-PUB.pdf). Just make sure you have the file local on your computer.
 
@@ -305,7 +305,7 @@ Add a document knowledge source to your agent and verify that it accurately answ
 
 #### Configure Knowledge Source Settings
 
-1. Once the document is indexed, Select on the knowledge source to view its details.
+1. Once the document is indexed, select on the knowledge source to view its details.
 
 1. Review the **Name** and **Description** fields. Update if needed to make the source easily identifiable.
 
@@ -313,9 +313,9 @@ Add a document knowledge source to your agent and verify that it accurately answ
 
 The Use information from the web setting is available on the Generative AI settings page or the Web Search setting in the Knowledge section of the agent's Overview page. This setting lets your agent access broad, real-time, and up-to-date information beyond what is available in predefined or enterprise-specific knowledge bases. For our scenario, we want to keep the use of knowledge focused on our provided resources and not the broader web.
 
-1. Navigate to the Overview tab, scroll down to the Knowledge section
+1. Go to the Overview tab, scroll down to the Knowledge section
 
-1. Select Disabled on the Web Search option.
+1. Select **Disabled** on the Web Search option.
 
 #### Disable Ungrounded Responses
 
@@ -330,11 +330,11 @@ The Use information from the web setting is available on the Generative AI setti
 
 #### Set Knowledge Source as Official
 
-1. Navigate back to the **Overview** tab and scroll down to the **Knowledge** section.
+1. Go back to the **Overview** tab and scroll down to the **Knowledge** section.
 
 1. Select the uploaded licensing guide file to open its details.
 
-1. Set the source to **Official** and select **Save**.
+1. Set the source to **Official** and select Got it if advised that it will Update agent instructions.
 
    > [!NOTE]
    > Marking a knowledge source as **Official** in Copilot Studio tells the agent to treat that content as authoritative and trustworthy. When multiple knowledge sources are available, the agent will prioritize official sources over non-official ones when generating responses. This is especially useful for policy documents, licensing guides, and other content where accuracy is critical.
@@ -454,11 +454,11 @@ Create and configure two tools that extend your agent's capabilities beyond simp
    > [!IMPORTANT]
    > Maker credentials mean the tool authenticates using YOUR account. This is suitable for testing and internal tools. For production scenarios with end users, use connection references. For anonymous APIs and APIs that use API keys, you should also set these to maker-provided credentials so the connection is configured by the maker rather than requiring end users to authenticate.
 
-1. In the **Inputs** section, find the **Units** input. Change it from **Dynamically fill with AI** to **Custom value**.
+1. In the **Inputs** section, find the **Units** input. Change it from **Fill with AI** to **Custom**.
 
 1. Click into the value field and select **Imperial** or **Metric** depending on your preference.
 
-1. Review the tool configuration and click **Save**.
+1. Review the tool configuration and select **Save**.
 
 #### Test the Weather Tool
 
@@ -476,7 +476,7 @@ Create and configure two tools that extend your agent's capabilities beyond simp
    Orlando
    ```
 
-1. Review the weather information returned by the agent. Notice how it uses the tool to fetch real-time data. Also notice that the agent automatically used the **Imperial** or **Metric** unit you selected earlier without asking the user — this is because you set that input to a custom value instead of letting the AI fill it dynamically.
+1. Review the weather information returned by the agent. Notice how it uses the tool to fetch real-time data. Also notice that the agent automatically used the **Imperial** or **Metric** unit you selected earlier without asking the user. The agent knew this is because you set that input to a custom value instead of letting the AI fill it dynamically.
 
    > [!TIP]
    > If the agent doesn't use the tool automatically, check that the tool is enabled and that you've saved your agent configuration.
@@ -495,9 +495,9 @@ Create and configure two tools that extend your agent's capabilities beyond simp
    > [!NOTE]
    > The first time you open the Prompt builder, a **Define your intent** product tour (1 of 3) appears as a coachmark overlay. Click **X** to dismiss it (or step through with **Next**) before continuing.
 
-1. Select the current name e.g., **Custom prompt...** at the top left and change the name to **Prompt Analyzer**.
+1. Select the current name for example, **Custom prompt...** at the top left and change the name to **Prompt Analyzer**.
 
-1. In the **Instructions** section, add the following :
+1. In the **Instructions** section, add the following:
 
    ```
    Analyze this prompt (replace with text) based upon the CARE Prompt Guidance to determine what are recommendations on how to improve writing the prompt and if it is very good. Respond using markdown language bolding and using bullets to make the answer more visually appealing to the user.
@@ -509,9 +509,9 @@ Create and configure two tools that extend your agent's capabilities beyond simp
 
 1. Select **Text** from the list of content types.
 
-1. Input **PromptToAnalyze** for the name.
+1. Enter **PromptToAnalyze** for the name.
 
-1. Input **Summarize this text: "Text"** for the sample data.  This will be used to test the prompt.
+1. Enter **Summarize this text: "Text"** for the sample data.  This will be used to test the prompt.
 
 1. Select **Close**.
 
@@ -621,15 +621,15 @@ Create a custom topic that handles a specific user intent (mailing list signup)
 
 #### Create a Topic with Description
 
-1. In your Copilot Studio agent, click **Topics** in the top navigation bar.
+1. In your Copilot Studio agent, select **Topics** in the top navigation bar.
 
 1. Select **+ Add a topic**.
 
 1. Select **Add from description with Copilot**.
 
-1. Input **Join Copilot Studio Mailing List** for the name of your topic.
+1. Enter **Join Copilot Studio Mailing List** for the name of your topic.
 
-1. Input the following description in the **Create a topic to...**:
+1. Enter the following description in the **Create a topic to...**:
 
    ```
    Join Copilot Studio Mailing List. Let the user provide their email address, first and last name to be added to the email mailing list for copilot studio announcements.
@@ -677,7 +677,7 @@ Create a custom topic that handles a specific user intent (mailing list signup)
 
 1. Check your nodes and if you don't already have a node that thanks the user then select + after the last node and select a **Message** node.
 
-1. Input the following as the message:
+1. Enter the following as the message:
 
    ```
    Thank you! Your information has been recorded. (In production, this would submit to the mailing list system.)
diff --git a/_labs/core-concepts-variables-agents-channels.md b/_labs/core-concepts-variables-agents-channels.md
index ef281e98..205a1efd 100644
--- a/_labs/core-concepts-variables-agents-channels.md
+++ b/_labs/core-concepts-variables-agents-channels.md
@@ -68,11 +68,11 @@ Think of variables, child agents, and channels like organizing a company:
 
 ## Introduction
 
-Variables, child agents, and channels are the keys to building enterprise-grade agent solutions. Variables act as your agent's memory - storing user information and conversation context. Child agents enable modular architecture where specialized sub-agents handle specific domains. Channels determine where and how users interact with your agent - whether through Teams, web widgets, or custom applications.
+Variables, child agents, and channels are the keys to building enterprise-grade agent solutions. Variables act as your agent's memory - storing user information and conversation context. Child agents enable modular architecture where specialized sub-agents handle specific domains. The agents configured channels (such as Teams, web widgets, or custom applications) determine where and how users interact with your agent.
 
 **Real-world example:** An IT support agent collects a user's employee ID and department at the start of the conversation, storing them in variables for personalized responses throughout the interaction. When the user asks about password policies, the parent agent delegates to a specialized "Security Policies" child agent with deep authentication knowledge. The entire experience is available in Microsoft Teams (where employees chat daily), on the company intranet (for quick access), and through a mobile app (for field workers). Variables maintain context, child agents provide expertise, and channels ensure accessibility.
 
-This lab teaches you how to architect sophisticated agent solutions that scale with your organization's complexity - combining conversation memory, specialized intelligence, and strategic deployment.
+This lab teaches you how to architect sophisticated agent solutions that scale with your organization's complexity by combining conversation memory, specialized intelligence, and strategic deployment.
 
 ---
 
@@ -164,7 +164,7 @@ Understand variable types, properties, scope, and behavior by exploring the exis
 
 #### Open the Mailing List Topic
 
-1. Navigate to [Copilot Studio](https://copilotstudio.microsoft.com).
+1. Go to [Copilot Studio](https://copilotstudio.microsoft.com).
 
    > [!NOTE]
    > **You can do this lab in the new experience.** You created the **Copilot Studio Assistant** in the previous lab using the *previous* experience, then switched the **New experience** toggle back on. That's the right place to be for this lab — your classic agent reopens with its full **Overview / Knowledge / Tools / Agents / Topics / Channels** canvas under the new experience, so Variables, child agents, and channel deployment all work here. If for any reason the agent doesn't show those tabs, confirm you opened the **Copilot Studio Assistant** classic agent from the previous lab (not a new-type agent).
@@ -196,7 +196,7 @@ Understand variable types, properties, scope, and behavior by exploring the exis
 
 1. Select the variable name to open the variable properties panel.
 
-1. Review the variable configuration — do not change any values:
+1. Review the variable configuration, but do not change any values:
    - **Variable Name**: The variable identifier used in the topic
    - **Type**: Data type (Text, Number, Boolean, etc.)
    - **Usage**: Topic-level or Global
@@ -317,15 +317,15 @@ Create a specialized child agent and configure the parent agent to orchestrate c
 
 #### Create a Child Agent
 
-1. In your Copilot Studio Assistant agent, Select  **Agents**  in the agent top navigation bar.
+1. In your Copilot Studio Assistant agent, select  **Agents**  in the agent top navigation bar.
 
-1. Select  **Add an agent**.
+1. Select  **+ Add** to Add an agent.
 
-1. In the **Create a child agent** section, Select **New child agent**.
+1. In the **Create a child agent** section, select **New child agent**.
 
 1. Enter  **CARE Prompt Guidance** in the **Name** field.
 
-1. Input the following for the **Description**
+1. Enter the following for the **Description**
 
     ```
     This agent provides information on the CARE Prompt guidance.
@@ -491,7 +491,7 @@ Deploy your agent to Teams and Microsoft 365 Copilot channels with proper config
 
 #### Navigate to Channels
 
-1. In your Copilot Studio agent, select **Channels** in the top navigation bar.
+1. In your Copilot Studio Assistant agent, select **Channels** in the top navigation bar.
 
 1. Review the Channels overview page to see available channel options:
    - **Microsoft 365 and Microsoft Teams**: Native Teams + Microsoft 365 Copilot integration (this is the tile you'll deploy to later in this use case)
@@ -537,7 +537,7 @@ Deploy your agent to Teams and Microsoft 365 Copilot channels with proper config
     > [!NOTE]
     > This step pre-authenticates Teams in your browser. Without it, the later **See agent in Teams** step may fail or redirect you into a login flow that interrupts the lab.
 
-1. Before you can deploy to a channel, you must first publish your agent.  Select **Publish** from the top right corner of the screen.  Follow the prompts.
+1. Before you can deploy to a channel, you must first publish your agent. Select **Publish** from the top right corner of the screen.  Follow the prompts.
 1. Return to the Channels page and select **Microsoft 365 and Microsoft Teams**.
 
 1. Review the **Agent preview** section that shows how users will see your agent.
@@ -562,7 +562,7 @@ Deploy your agent to Teams and Microsoft 365 Copilot channels with proper config
 
 1. Select **Availability options** and review what is available:
 
-1. After reviewing the options select the back arrow to return to the prior panel.
+1. After reviewing the options, select the back arrow to return to the prior panel.
 
 1. Select **See agent in Teams**, this will load a new browser tab with the Teams web application.
 
diff --git a/_labs/mcs-orchestration.md b/_labs/mcs-orchestration.md
index 78ffa754..5538d5ee 100644
--- a/_labs/mcs-orchestration.md
+++ b/_labs/mcs-orchestration.md
@@ -158,7 +158,7 @@ Confirm the environment is ready and the sample connected agent is published.
 
 #### Make sure that Dataverse Search is set to on
 
-1. In the upper right corner of Copilot Studio, Select the **Gear** icon
+1. In the upper right corner of Copilot Studio, select the **Gear** icon
 
 1. Select **Go to Power Platform admin center**
 
@@ -166,7 +166,7 @@ Confirm the environment is ready and the sample connected agent is published.
 
 1. Select your environment from the list to open its details page
 
-1. Select **Settings** on the **top navigation bar** of that page (the **Settings** command across the top of the environment — *not* the gear/global settings). Navigate to it through the admin center rather than pasting a direct URL.
+1. Select **Settings** on the **top navigation bar** of that page (the **Settings** command across the top of the environment — *not* the gear/global settings). Go to it through the admin center rather than pasting a direct URL.
 
 1. Expand the **Product** group and select **Features**
 
@@ -180,22 +180,22 @@ Confirm the environment is ready and the sample connected agent is published.
 
 #### Ensure that indexes are in place for our connected agent
 
-> [!IMPORTANT]
+> [!NOTE]
 > This is not required for a connected agent to work, but to make sure that the one we have pre-loaded for you will return results we must index a few tables in your environment.
 
 1. Go to the Power Apps maker portal [https://make.powerapps.com](https://make.powerapps.com)
 
-    ![Open Power Apps](images/image-19.png)
+    ![Microsoft 365 app launcher in Copilot Studio showing various apps including Power Apps highlighted](images/image-19.png)
 
-1. In the left menu select **Tables**
+1. In the left menu, select **Tables**
 
 1. Select the **Account** table from the list
 
 1. Select **Views** from the Data experiences section
 
-1. Select **Quick Find Active Accounts** option from the list of Views
+1. Select **Quick Find Active Accounts**  from the list of Views
 
-1. Select **View Column** to verify the following list of columns are in the view, you may have to scroll to see all of the included columns:
+1. Select **View Column** to verify the following list of columns are in the view. You may have to scroll to see all of the included columns:
    - Address 1: State/Province
    - Address 1: ZIP/Postal Code
    - Address 1: City
@@ -206,7 +206,7 @@ Confirm the environment is ready and the sample connected agent is published.
 
     ![Account View](images/image-20.png)
 
-1. Add the ability to search on certain fields by making sure that the following items are in the **Find by** on the bottom right. Select the **Edit find table columns** option to check:
+1. Add the ability to search on certain fields by making sure the following items are in the **Find by** on the bottom right. Select the **Edit find table columns** option to check:
    - Address 1: State/Province
    - Address 1: ZIP/Postal Code
    - Address 1: City
@@ -251,7 +251,7 @@ Confirm the environment is ready and the sample connected agent is published.
 
 1. In the Copilot Studio tab in your browser, go to the **Account Data Lookup Agent**
 
-1. Open the Test chat by Selecting **Test** in the upper right-hand corner
+1. Open the Test chat by selecting **Test** in the upper right-hand corner
 
 1. Enter `What are the accounts in Texas?`
 
@@ -266,7 +266,7 @@ Confirm the environment is ready and the sample connected agent is published.
     > [!NOTE]
     > Use the **Connected agents** *section on the Generative AI page* — **not** the separate **Connected Agents** item in the Settings left navigation. That left-nav item opens an input/output management page ("Manage input and output for the agent") and does **not** contain this toggle.
 
-1. Close the Settings menu by Selecting the **X** in the upper right-hand corner
+1. Close the Settings menu by selecting the **X** in the upper right-hand corner
 
 1. Select **Publish**. In the **Publish this agent** dialog, make sure **Force newest version** is checked, then select **Publish** to confirm.
 
@@ -602,7 +602,7 @@ Stand up a new-type agent and validate how the New Orchestrator's Agentic Reason
 > [!NOTE]
 > These environment features are required for the **Dataverse MCP** tool you'll add below — they are not specific to the New Orchestrator.
 
-1. Navigate to the **Power Platform admin center** the same way you did in [Use Case #1](#use-case-1-get-the-sample-connected-agent-working) — in Copilot Studio, select the **Gear** icon in the upper right, then **Go to Power Platform admin center**.
+1. Go to the **Power Platform admin center** the same way you did in [Use Case #1](#use-case-1-get-the-sample-connected-agent-working) — in Copilot Studio, select the **Gear** icon in the upper right, then **Go to Power Platform admin center**.
 
 1. Select the **Manage** tab, then **Environments**, choose your environment, then select **Settings** on the **top navigation bar** of the environment page (the same top-nav **Settings** command you used in Use Case #1).
 
@@ -654,7 +654,7 @@ You'll add two tools. In the new designer, adding a tool is **Add tool → pick
 
     ![Add tool – MSN Weather Get current weather](images/new-orch-02.png)
 
-1. In the **Tools** list in the right rail, **select the `Get current weather` tool** to open its **Tool details**. (Clicking a tool in this menu is how you configure it — there's no separate settings button; the tool's name opens its Details, Inputs, and Outputs panels.)
+1. In the **Tools** list in the right rail, **select the `Get current weather` tool** to open its **Tool details**. (Select a tool in this menu is how you configure it — there's no separate settings button; the tool's name opens its Details, Inputs, and Outputs panels.)
 
 1. Under **Authentication mode**, select **Maker**. A **Connection** field appears — select **Not connected → Create new connection → Create**. Once it shows your connection, select **Save**.
 
@@ -663,7 +663,7 @@ You'll add two tools. In the new designer, adding a tool is **Add tool → pick
     > [!IMPORTANT]
     > **Use Maker for anonymous or API‑key / service‑account tools.** The MSN Weather connector authenticates anonymously, so it should run as the **maker** — your connection is reused for every end user and no one is prompted to connect at runtime. The same rule applies to any connector that authenticates with a **shared API key or service account** rather than the end user's identity: set those to **Maker** too. If you leave such a tool on **User**, the agent returns a **"Connection Required"** card the first time it tries to call it. (Tools that act *as the signed-in user* — e.g. a mailbox or files connector — would instead keep **User** authentication.)
 
-1. Still in **Tool details**, select **Inputs** from the left panel. Leave **Location** set to **AI** (the agent infers the location from the conversation). For **Units**, change **How is this filled?** from **AI** to **Value** so you control the unit system, then bind it to a variable: open the **Value** picker, select **+ Add variable**, and in the variable's **Value** field **click the chevron on the right** — *that chevron is where the unit options appear*. Choose **I** (Imperial) for this lab, then **Save**.
+1. Still in **Tool details**, select **Inputs** from the left panel. Leave **Location** set to **AI** (the agent infers the location from the conversation). For **Units**, change **How is this filled?** from **AI** to **Value** so you control the unit system, then bind it to a variable: open the **Value** picker, select **+ Add variable**, and in the variable's **Value** field **select the chevron on the right** — *that chevron is where the unit options appear*. Choose **I** (Imperial) for this lab, then **Save**.
 
     > [!NOTE]
     > **Units** accepts **`I`** for Imperial (°F) or **`C`** for Celsius (°C). This lab uses **`I`**, but set whichever matches your preference — the agent reports temperatures in the unit you pick here.
@@ -811,11 +811,11 @@ In Use Case #3 you added the internal `company_policies_sample.pdf` from the **H
 
 #### Add the MCP server tools to the Sales Account Assistant
 
-Attach the two servers to the **new-type** agent, creating each connection inline as you add it.
+1. In the **Sales Account Assistant** (Build tab). In the right rail, select **Add tool** (the **+** on the Tools section).
 
-1. Return to the **Sales Account Assistant** (Build tab). In the right rail, select **Add tool** (the **+** on the Tools section).
+1. On **Review capabilities**, the server's actions now load. Select **Confirm** to attach it.
 
-1. Filter to **Model Context Protocol (MCP)**, search **Order Management**, and select **Order Management MCP Server**. On the connection step, choose **Create new connection → Create**, then **Add**.
+    ![MCP capabilities load for the new-type agent](images/uc4-tool-capabilities.png)
 
 1. Repeat for **Warehouse MCP Server**. Your **Tools** list should now show four tools: **Get current weather**, **Microsoft Dataverse MCP Server**, **Order Management MCP Server**, and **Warehouse MCP Server**.
 
@@ -1015,7 +1015,7 @@ You extended a new-type agent with a **Skill**, two **custom MCP servers**, a se
 
 ## Summary of learnings
 
-True learning comes from doing, questioning, and reflecting. Across this lab, you've seen Copilot Studio's orchestration engine from two distinct angles:
+Learning comes from doing, questioning, and reflecting. Across this lab, you've seen Copilot Studio's orchestration engine from two distinct angles:
 
 * **Standard generative orchestration** (Use Case #2) — a single-pass planner that picks one tool / child / knowledge source per turn based on the user's intent. Highly inspectable: every decision shows up in the activity tracker, and *Get rationale* lets you read the planner's reasoning back to you. Tunable through agent Instructions, child-agent and tool Names + Descriptions, and input-parameter Descriptions.
 * **New Orchestrator – Agentic Reasoning Loop** (Use Case #3) — the default orchestrator in new-type agents (previewed on classic agents as Enhanced Task Completion). Plans, acts, observes, iterates within a single turn until the task is complete. Better when users want finished outcomes; worse when authors and users need step-by-step transparency.
diff --git a/_labs/mcs-tools.md b/_labs/mcs-tools.md
index c3767f2d..a6f41915 100644
--- a/_labs/mcs-tools.md
+++ b/_labs/mcs-tools.md
@@ -1,4 +1,4 @@
----
+    ---
 layout: lab
 module: tools-overview
 title: "Copilot Studio Tools"
@@ -9,7 +9,7 @@ lab_type: local
 section: intermediate_labs
 journeys: ["business-user", "developer"]
 bootcamp_order: "7"
-description: "Learn how to extend your agents with powerful tools including connectors, agent flows, MCP servers, and custom prompts in Microsoft Copilot Studio."
+description: "Learn how to extend your agents with tools including connectors, agent flows, MCP servers, and custom prompts in Microsoft Copilot Studio."
 
 ---
 
@@ -114,7 +114,7 @@ This lab teaches you how to use each tool type through hands-on scenarios.
 In this lab, you'll extend agents with multiple tool types to address different integration scenarios. By the end of the lab, you will:
 
 - Use connectors to integrate external services with your agent
-- Build an agent flow with deterministic business logic for commission calculations
+- Configure a workflow for an agent with deterministic business logic for commission calculations
 - Connect a Dataverse MCP server for real-time natural language data access
 - Create custom prompts that structure agent responses with specific data fields
 - (Extra Credit) Configure a Computer Using Agent to automate a legacy system without API access
@@ -161,7 +161,7 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
 
 #### Create the Dictionary Agent
 
-1. Go to [Microsoft Copilot Studio](https://copilotstudio.microsoft.com) and make sure you are in your development environment.
+1. Go to [Microsoft Copilot Studio](https://copilotstudio.microsoft.com) and confirm you are in your development environment.
 
 1. Select **Agents** on the left navigation.
 
@@ -171,7 +171,7 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
 
 1. Select **Agents** in the left navigation, then select **Create blank agent**. In the **Name your agent** dialog, enter `Dictionary Agent` and select **Continue**.
 
-1. Once the agent is provisioned, confirm its name is `Dictionary Agent`. If you need to change it, select **Edit** in the **Details** section on **Overview**.
+1. After the agent is provisioned, confirm its name is `Dictionary Agent`. If you need to change it, select **Edit** in the **Details** section on **Overview**.
 
 1. Enter the following as the **Description:**
 
@@ -179,19 +179,19 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
     This agent allows a user to lookup the definition of a word
     ```
 
-1. Select **Save**.
+1. Select **Save**..
 
 #### Create the Custom Connector
 
 1. Select **Tools** in the top navigation.
 
-1. Select **Add Tool**.
+1. Select **Add a tool**.
 
-1. Under **Create new**, Select **See all**.
+1. On the right top corner of the  **Create new** section, select **See all**.
 
 1. Select **Custom connector**.
 
-1. In the top navigation, Select **New custom connector**.
+1. In the top navigation, select **New custom connector**.
 
 1. Select **Create from blank**.
 
@@ -208,7 +208,7 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
     > [!NOTE]
     > This API doesn't require authentication, but this is where you would select the authentication type for APIs that do.
 
-1. Make sure the authentication type is set to **No authentication** and Select **Definition**.
+1. Confirm the authentication type is set to **No authentication** and select **Definition**.
 
 #### Define the API Action
 
@@ -221,12 +221,12 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
     Lookup a word in the dictionary
     ```
 
-    > [!TIP]
+    > [!NOTE]
     > The description will later be used as the tool description, which allows the orchestrator to know when to use this tool. Make sure you are descriptive here to allow the best conversation routing.
 
 1. In the **Operation ID** field, enter **WordLookup**
 
-1. Under **Request**, Select **Import from sample**.
+1. Under **Request**, select **Import from sample**.
 
 1. Select **Get** as the **Verb**.
 
@@ -238,7 +238,7 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
 
 1. Select **Import**.
 
-1. Select the down arrow next to **word** and Select **Edit**.
+1. Select the down arrow next to **word** and select **Edit**.
 
 1. In the **Description** field, enter:
 
@@ -312,7 +312,7 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
 
 1. Select **Import**.
 
-1. Update the following body items by selecting the down arrow on each and selecting **Edit**, change the data and then select **back**:
+1. Update the following body items by selecting the down arrow on each and selecting **Edit**, change the data and then select **Back**:
 
     - **origin**
     - **Title:** `origin`
@@ -331,7 +331,7 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
 
 #### Add the Custom Connector as a Tool
 
-1. Go back to the browser tab with Copilot Studio.
+1. Return to the browser tab with Copilot Studio.
 
 1. Refresh the page.
 
@@ -352,12 +352,12 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
 
 1. You should see the connection with a green check mark. Select **Add and configure**.
 
-1. Select **Additional details** and set **Credentials to use** to **Maker-provided credentials**.
+1. In the **Details** section, select **Additional details** and set **Credentials to use** to **Maker-provided credentials**.
 
     > [!TIP]
     > For unauthenticated APIs, it is best to use Maker-provided credentials so you don't require users to create a connection for anonymous connectors.
 
-1. In the **Inputs** section, Select **Customize** next to **word**.
+1. In the **Inputs** section, select **Additional details** below **word**.
 
 1. Notice that all your inputs have been populated from your connector definition - this is why it is important to provide detailed descriptions when building your connector.
 
@@ -422,11 +422,11 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
 
 ## Use Case #2: Build Deterministic Logic with Agent Flows
 
-Build a Sales Commission Calculator using agent flows to implement deterministic business logic that always produces consistent, predictable results.
+Build a Sales Commission Calculator using workflows to implement deterministic business logic that always produces consistent, predictable results.
 
 | Use case | Value added | Estimated effort |
 |----------|-------------|------------------|
-| Build Deterministic Logic with Agent Flows | Implement business rules that always produce consistent, predictable results | 15 minutes |
+| Build Deterministic Logic with Workflows | Implement business rules that always produce consistent, predictable results | 15 minutes |
 
 **Summary of tasks**
 
@@ -467,7 +467,7 @@ Use a pre-created agent that calculates sales commissions with deterministic bus
 
 #### Test Your Commission Calculator
 
-1. Select **Test** in the upper right-hand corner of Copilot Studio.
+1. If the **Test your agent** panel is not showing , select **Test** in the upper right-hand corner of Copilot Studio to show it.
 
 1. Type the following in the test pane:
 
@@ -501,7 +501,7 @@ Use a pre-created agent that calculates sales commissions with deterministic bus
     - Product Mix Bonus: $3,000.00 (Strategic products >= 30%)
     - **Total Commission: $84,000.00**
 
-1. Reset the conversation and test with a different scenario:
+1. Reset the conversation by selecting **New test session** at the top of the panel, and test with a different scenario:
 
     ```
     Calculate my commission
@@ -606,7 +606,7 @@ Create and configure a Copilot Agent with Dataverse MCP Server integration that
 
 1. Scroll down in the **Overview** tab to the **Suggested prompts** section and select **Add suggested prompts**.
 
-1. Add the following prompts, then Select **Save**:
+1. Add the following prompts, then select **Save**:
    - **Title:** Account Search | **Prompt:** `List all accounts in Redmond`
    - **Title:** Contact Search | **Prompt:** `List all contacts from Coho Winery`
 
@@ -781,7 +781,7 @@ Create a Chit Chat Agent with a custom prompt tool that controls response behavi
 
 1. Select the down arrow next to **GPT-4.1 mini** to see the list of available model options.
 
-1. Select a different model and Select **Test** again.
+1. Select a different model and select **Test** again.
 
 1. Notice how the response style changes depending on the model selected.
 
@@ -804,7 +804,7 @@ Create a Chit Chat Agent with a custom prompt tool that controls response behavi
 
 1. In the **Inputs** section, change the **Query** input's **Fill Using** setting to **Custom value**.
 
-1. In the **Value** field, Select the **...** button, then Select **System** and select **Activity.Text**.
+1. In the **Value** field, Select the **...** button, then select **System** and select **Activity.Text**.
 
     > [!TIP]
     > System.Activity.Text stores the last thing the user said to the agent. This automatically passes the user's message into your custom prompt.
@@ -971,7 +971,7 @@ Create an autonomous agent that uses the Computer use tool to retrieve portfolio
     If no portfolio data is found, reply that you couldn't find a portfolio with the specified ID.
     ```
 
-1. Keep **Use hosted browser** enabled to create a connection to the hosted browser.
+1. Select **Add and configure**.
 
 1. Update the **Name** of the Computer use tool to `Look up portfolio data`.
 
@@ -990,7 +990,7 @@ Create an autonomous agent that uses the Computer use tool to retrieve portfolio
 
 #### Test the Computer Use Tool
 
-1. In the **Instructions** section, select the **Test** button on the right.
+1. In the **Instructions** section, select the **Test Directly** button on the right.
 
 1. Add the sample value `44123BCD` and select **Test now**.
 
@@ -1112,6 +1112,6 @@ To maximize the impact of tools in Copilot Studio:
 * Test with realistic data and edge cases before deploying
 * Structure agent responses with custom prompts when consistency matters for business decisions
 
-By following these principles, you'll build agents that go beyond conversation - they take action, access live data, execute business logic, and integrate with the systems your organization relies on.
+By following these principles, you'll build agents that go beyond conversation and take action, access live data, execute business logic, and integrate with the systems your organization relies on.
 
 ---
diff --git a/_labs/setup-for-success.md b/_labs/setup-for-success.md
index e566b1cf..ad8127f7 100644
--- a/_labs/setup-for-success.md
+++ b/_labs/setup-for-success.md
@@ -1,7 +1,7 @@
 ---
 module: setup-for-success
 title: "Set yourself up for success & discover ALM best practices"
-description: "Build agents with confidence. Deploy with control. Master the lifecycle of your Microsoft Copilot Studio agents with best practices."
+description: "Build agents with confidence. Deploy with control. Manage the lifecycle of your Microsoft Copilot Studio agents with best practices."
 order: 11
 duration: 35
 difficulty: 200
@@ -108,7 +108,7 @@ With the ALM practices in this lab, you'll avoid these pitfalls and set yourself
 
 ## Summary of Targets
 
-In this lab, you'll configure your ALM foundation for working with Microsoft Copilot Studio like a pro. By the end of the lab, you will:
+In this lab, you'll configure your ALM foundation for working with Microsoft Copilot Studio. By the end of the lab, you will:
 
 * Create and configure a structured solution for your customizations.
 * Set up a custom publisher to track ownership and maintain ALM hygiene.
@@ -151,9 +151,9 @@ Set up your development environment by creating a solution and custom publisher
 
 #### Open the Solutions area
 
-1. Go to the [copilotstudio.microsoft.com](https://copilotstudio.microsoft.com/).
+1. Go to the [copilotstudio.microsoft.com](https://copilotstudio.microsoft.com/)
 
-2. Confirm you are in the correct environment (top-right corner).
+2. Make sure you are in the correct environment (top-right corner).
 
 #### Create a solution
 
@@ -172,7 +172,7 @@ Set up your development environment by creating a solution and custom publisher
 
 #### Create a publisher
 
-6. If this is your first solution, click **+ New publisher** to create one.
+6. If this is your first solution, select **+ New publisher** to create one.
 
 > [!TIP]
 >  * You may use your organization’s name.
@@ -184,8 +184,8 @@ Set up your development environment by creating a solution and custom publisher
 
 #### Set and create
 
-7. Check **Set as your preferred solution** (so any new component goes into it by default).
-8. Click **Create**.
+7. Select **Set as your preferred solution** (so any new component goes into it by default).
+8. Select **Create**.
 
 ---
 
@@ -231,7 +231,7 @@ In this section, you'll learn how to create environment variables and connection
 
 ### Step-by-step instructions
 
-1. Open the solution you created in Use Case #1.
+1. Open the solution you created in the previous use case.
 
 2. Select **+ New**, then go to **More** and choose **Environment variable**.
 
@@ -249,7 +249,7 @@ In this section, you'll learn how to create environment variables and connection
     > [!TIP]
     >  * Notice how, under **Advanced**, you can set whether the current value can follow through with your solution deployment, or if it should be reset each time the solution is deployed to a new environment
 
-6. Click **Save**.
+6. Select **Save**.
 
     > [!TIP]
     >  * Environment variables can also be of type **Secret** to retrieve secure values like API keys from Azure Key Vault at runtime.
@@ -263,7 +263,7 @@ In this section, you'll learn how to create environment variables and connection
 
 9. Select the connector **ServiceNow**.
 
-10. In the connection dropdown, choose **New connection** if none exists.
+10. In the connection dropdown, select **New connection** if none exists.
 
 11. Log in through Power Apps in a new tab if needed, then return to Copilot Studio.
 
@@ -271,7 +271,7 @@ In this section, you'll learn how to create environment variables and connection
     >  * For **ServiceNow** configuration values, use the provided values in the **Lab Resources** (specific per training).
     >  * For **ServiceNow**'s `Instance` configuration, be sure to scroll down in the connection screen.
 
-12. Above the **Connection** dropdown, select **Refresh** and choose the newly created connection.
+12. Above the **Connection** dropdown, select **Refresh** and select the newly created connection.
 
 > [!TIP]
 >  * If the **Create** button is grayed out, it's just because you pasted the display name. Type an extra character in the display name field and remove it to be able to create. 

From 16d4fc0276f58abc30d27efe486f36145f4a85a6 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 1 Jul 2026 01:07:13 +0000
Subject: [PATCH 3/3] fix: address review findings in synced lab docs

---
 _labs/agent-builder-m365.md                  | 2 +-
 _labs/agent-builder-sharepoint.md            | 4 ----
 _labs/ask-me-anything.md                     | 2 +-
 _labs/core-concepts-agent-knowledge-tools.md | 4 ++--
 _labs/mcs-orchestration.md                   | 8 ++++----
 _labs/mcs-tools.md                           | 2 +-
 6 files changed, 9 insertions(+), 13 deletions(-)

diff --git a/_labs/agent-builder-m365.md b/_labs/agent-builder-m365.md
index 87bd820d..f12bd37c 100644
--- a/_labs/agent-builder-m365.md
+++ b/_labs/agent-builder-m365.md
@@ -659,7 +659,7 @@ Use the Analyst agent to perform a detailed ROI analysis with NPV, IRR, and disc
 
 1. Navigate to [Microsoft 365 Copilot](https://m365.cloud.microsoft/chat/?auth=2&home=1).
 
-2. Select the **Analyst** agent.
+2. Select the **Analyst** agent. You can find it by:
    - Selecting the agent picker and choosing **Analyst**
    - Or typing `@Analyst` in the chat input area
 
diff --git a/_labs/agent-builder-sharepoint.md b/_labs/agent-builder-sharepoint.md
index 36c203fd..1b5c95d3 100644
--- a/_labs/agent-builder-sharepoint.md
+++ b/_labs/agent-builder-sharepoint.md
@@ -134,8 +134,6 @@ Build a specialized agent with SharePoint integration and advanced AI capabiliti
 
 4. Go to the **Configure** tab.
 
-5. Go to the **Configure** tab
-
 <!--
     ![alt text](images/knowledge-files.png)
 Commented out; screenshots need update due to CPS updates.  Last minute change to labs required so will do at a later date
@@ -229,8 +227,6 @@ Design a professional badge for the first place winner of our 2026 sales contest
 8. Select **...** next to your agent name in the side bar navigation, and choose **Edit**
 
 9. In the **Configure** tab, explore additional **knowledge** capabilities:
-
-10. In the **Configure** tab, explore additional **knowledge** capabilities:
    - All **Websites** (or specific websites)
    - All **SharePoint** data (or specific files or sites)
    - All **Teams** data (or data from specific group chats, meetings, or channels)
diff --git a/_labs/ask-me-anything.md b/_labs/ask-me-anything.md
index 7d63b125..fb27fd9a 100644
--- a/_labs/ask-me-anything.md
+++ b/_labs/ask-me-anything.md
@@ -855,7 +855,7 @@ In this section, you'll learn how to upload files and run files through a prompt
 
 14. **Save** your prompt
 
-    !Copilot Studio AI prompt node "Meeting AI Notes" with GPT-4o model returning JSON meeting data](images/prompt.png)
+    ![Copilot Studio AI prompt node "Meeting AI Notes" with GPT-4o model returning JSON meeting data](images/prompt.png)
 
 14. **Save** the topic.
 
diff --git a/_labs/core-concepts-agent-knowledge-tools.md b/_labs/core-concepts-agent-knowledge-tools.md
index 497b401c..6913b5d5 100644
--- a/_labs/core-concepts-agent-knowledge-tools.md
+++ b/_labs/core-concepts-agent-knowledge-tools.md
@@ -334,7 +334,7 @@ The Use information from the web setting is available on the Generative AI setti
 
 1. Select the uploaded licensing guide file to open its details.
 
-1. Set the source to **Official** and select Got it if advised that it will Update agent instructions.
+1. Set the source to **Official** and select **Got it** if prompted that this will update agent instructions.
 
    > [!NOTE]
    > Marking a knowledge source as **Official** in Copilot Studio tells the agent to treat that content as authoritative and trustworthy. When multiple knowledge sources are available, the agent will prioritize official sources over non-official ones when generating responses. This is especially useful for policy documents, licensing guides, and other content where accuracy is critical.
@@ -476,7 +476,7 @@ Create and configure two tools that extend your agent's capabilities beyond simp
    Orlando
    ```
 
-1. Review the weather information returned by the agent. Notice how it uses the tool to fetch real-time data. Also notice that the agent automatically used the **Imperial** or **Metric** unit you selected earlier without asking the user. The agent knew this is because you set that input to a custom value instead of letting the AI fill it dynamically.
+1. Review the weather information returned by the agent. Notice how it uses the tool to fetch real-time data. Also notice that the agent automatically used the **Imperial** or **Metric** unit you selected earlier without asking the user. This is because you set that input to a custom value instead of letting the AI fill it dynamically.
 
    > [!TIP]
    > If the agent doesn't use the tool automatically, check that the tool is enabled and that you've saved your agent configuration.
diff --git a/_labs/mcs-orchestration.md b/_labs/mcs-orchestration.md
index 5538d5ee..6f634a14 100644
--- a/_labs/mcs-orchestration.md
+++ b/_labs/mcs-orchestration.md
@@ -654,7 +654,7 @@ You'll add two tools. In the new designer, adding a tool is **Add tool → pick
 
     ![Add tool – MSN Weather Get current weather](images/new-orch-02.png)
 
-1. In the **Tools** list in the right rail, **select the `Get current weather` tool** to open its **Tool details**. (Select a tool in this menu is how you configure it — there's no separate settings button; the tool's name opens its Details, Inputs, and Outputs panels.)
+1. In the **Tools** list in the right rail, **select the `Get current weather` tool** to open its **Tool details**. (Selecting a tool in this menu is how you configure it — there's no separate settings button; the tool's name opens its Details, Inputs, and Outputs panels.)
 
 1. Under **Authentication mode**, select **Maker**. A **Connection** field appears — select **Not connected → Create new connection → Create**. Once it shows your connection, select **Save**.
 
@@ -811,11 +811,11 @@ In Use Case #3 you added the internal `company_policies_sample.pdf` from the **H
 
 #### Add the MCP server tools to the Sales Account Assistant
 
-1. In the **Sales Account Assistant** (Build tab). In the right rail, select **Add tool** (the **+** on the Tools section).
+Attach the two servers to the **new-type** agent, creating each connection inline as you add it.
 
-1. On **Review capabilities**, the server's actions now load. Select **Confirm** to attach it.
+1. Return to the **Sales Account Assistant** (Build tab). In the right rail, select **Add tool** (the **+** on the Tools section).
 
-    ![MCP capabilities load for the new-type agent](images/uc4-tool-capabilities.png)
+1. Filter to **Model Context Protocol (MCP)**, search **Order Management**, and select **Order Management MCP Server**. On the connection step, choose **Create new connection → Create**, then **Add**.
 
 1. Repeat for **Warehouse MCP Server**. Your **Tools** list should now show four tools: **Get current weather**, **Microsoft Dataverse MCP Server**, **Order Management MCP Server**, and **Warehouse MCP Server**.
 
diff --git a/_labs/mcs-tools.md b/_labs/mcs-tools.md
index a6f41915..eea056d4 100644
--- a/_labs/mcs-tools.md
+++ b/_labs/mcs-tools.md
@@ -179,7 +179,7 @@ Create a custom connector for the Free Dictionary API, add it as a tool in your
     This agent allows a user to lookup the definition of a word
     ```
 
-1. Select **Save**..
+1. Select **Save**.
 
 #### Create the Custom Connector