I recently did a video here –

Video link = https://www.youtube.com/watch?v=KZkhK41lynI

but I’ve now been able to produce the following steps for your to replicate this.

Automate Daily Updates in Teams with Copilot Studio & Power Automate: A Step-by-Step Guide

Ever wanted a little bot to automatically post daily updates, fun facts, or important reminders into your Microsoft Teams channel? Maybe a “This Day in History” update, a daily project status reminder, or a motivational quote?

In this guide, we’ll walk through how to build an automated agent using Microsoft Copilot Studio and Power Automate that posts information to a Teams channel on a daily schedule. We’ll use the example from the video: creating a bot that posts significant computer history events for the current day.

What You’ll Need:

1. A Microsoft 365 account.

2. Appropriate licenses to use Power Automate and Copilot Studio.

3. Access to Microsoft Teams and permission to post in a specific channel.

The Overall Process:

We’ll create a system with a few interconnected parts:

1. Power Automate Flow #1 (Trigger): Runs once a day on a schedule.

2. Copilot Studio Agent: Receives a prompt from Flow #1, uses its general knowledge (AI) to find the relevant information (e.g., historical events).

3. Copilot Studio Topic: Takes the AI-generated response and triggers another flow.

4. Power Automate Flow #2 (Action): Receives the formatted response from the Copilot Topic and posts it to a designated Teams channel.

Let’s break it down!

Step 1: Create Your Copilot in Copilot Studio

1. Navigate to Microsoft Copilot Studio.

2. Create a New Copilot. Let’s name it “History Bot” for this example (the video used “History”).

3. Configure Basic Details:

   • Name: History Bot

   • Description: An agent that posts historical events daily.

   • General Instructions: Use general knowledge to create a list of historical events that happened on this day relating to computers. (Adapt this instruction based on the type of information you want the bot to post).

4. Enable Orchestration: Ensure the “Use generative AI to determine how best to respond…” toggle under Orchestration is Enabled. This allows the Copilot to understand the instructions and use AI.

5. Configure Knowledge:

   • Go to the Knowledge section (you might need to scroll down or find it in the left navigation).

   • Ensure “Allow the AI to use its own general knowledge” is Enabled. This lets the bot search the web based on your instructions. We won’t add specific documents for this example.

Step 2: Create the Daily Trigger Flow (Power Automate Flow #1)

This flow starts the process each day.

1. Go to Microsoft Power Automate.

2. Create a New Flow > Scheduled cloud flow.

3. Configure the Trigger:

   • Give your flow a name (e.g., “Daily History Trigger”).

   • Set the schedule: Repeat every 1 Day.

   • Choose a specific time for it to run (e.g., 12:45 PM as shown in the video).

4. Add Action: Send Prompt to Copilot:

   • Click “+ New step”.

   • Search for and select the “Copilot Studio” connector.

   • Choose the action “Sends a prompt to the specified copilot for processing (Preview)”.

   • Select your Copilot: Choose the “History Bot” (or whatever you named it) from the dropdown.

   • Prompt: Enter the text you want to send to the Copilot each day. Based on the video and our Copilot instructions, this would be something like: Please tell me about today in history with computers.

5. Save this flow.

Step 3: Create the Posting Topic in Copilot Studio

This topic handles the response from the AI and sends it to the next flow for posting.

1. Go back to your History Bot in Copilot Studio.

2. Navigate to the Topics section.

3. Optional Cleanup: The video creator removed the default/generic system topics. You might want to do this for a dedicated bot like this to keep things clean, but it’s not strictly necessary.

4. Create a New Topic > From blank.

5. Name the Topic: Call it “Post Result”.

6. Configure the Topic Trigger:

   • Click on the default “Phrase” trigger and delete it.

   • Add a new trigger. Select the trigger type: AI response generated (or similar wording like “On Generated Response”). This means the topic starts after the Copilot AI has formulated its answer based on the prompt from Flow #1.

7. Add Action: Call Power Automate Flow:

   • Click the + below the trigger and select Call an action > Create a flow. This will open Power Automate in a new tab to create Flow #2.

Step 4: Create the Posting Flow (Power Automate Flow #2)

This flow takes the Copilot’s response and posts it to Teams.

1. Power Automate should have opened with a trigger “When an agent calls the flow (Preview)”. This trigger will have an input field ready.

2. Define Input:

   • Click on the trigger step.

   • Add an input of type Text. Name it something descriptive like CopilotResponseContent. This is where the Copilot topic will pass the AI’s generated text.

3. Add Action: Post to Teams:

   • Click “+ New step”.

   • Search for the “Microsoft Teams” connector.

   • Select the action “Post message in a chat or channel”.

   • Post as: Choose Flow bot.

   • Post in: Select Channel.

   • Team: Select the Team you want to post to.

   • Channel: Select the specific Channel within that Team.

   • Message: Click in the message box. The dynamic content panel should appear. Select the CopilotResponseContent input variable you defined in the trigger step. This inserts the text generated by the Copilot.

4. Add Action: Respond to Agent:

   • Click “+ New step”.

   • Search for “Copilot Studio” connector.

   • Select the action “Respond to the agent”. (This step simply tells the Copilot topic that the flow has finished). You usually don’t need to add outputs here for this simple scenario.

5. Save this flow. Give it a name like “Post History Bot Result to Teams”.

Step 5: Connect the Topic to the Flow

1. Go back to the Copilot Studio tab where you were editing the “Post Result” topic.

2. The “Call an action” step should now let you select the flow you just created (“Post History Bot Result to Teams”). Select it.

3. Map Inputs: You’ll see the CopilotResponseContent input field you created in Flow #2. You need to tell the topic what to send to this input.

   • Click the input field.

   • Select the lightning bolt icon (Insert variable).

   • Go to the System variables.

   • Find and select Response.FormattedText. This variable holds the final, formatted answer from the Copilot’s AI generation process.

4. End the Topic: Add a final step to the topic: End conversation > End current topic.

5. Save the topic.

Step 6: Testing and Troubleshooting

1. Test Flow #1: In Power Automate, open the “Daily History Trigger” flow. Click Test > Manually > Run flow. This simulates the daily schedule.

2. Check Copilot Activity: In Copilot Studio, go to the Activity tab for your “History Bot”. You should see a new session started by the “History Trigger”. It will show steps like “Knowledge sources used” and eventually call the “Post Result” topic.

3. Check Teams: Look in the designated Teams channel. The message should appear shortly after the flows run successfully.

4. Troubleshooting Connection Issues (Common Problem):

   • Symptom: In the Copilot Studio Activity > Transcript view, you might see the process get stuck on “Waiting for user” and display a card saying “Additional permissions are required to run this action. To proceed, please select ‘Connect’…” This usually means the connection for Flow #2 (posting to Teams) isn’t working correctly.

   • Problem: The “Connect” button on that card might not work reliably.

   • Workaround 1 (Recommended): In Copilot Studio, go to the Test your agent pane > click the More options (…) menu > Manage connections. This opens the connection management page. Find the connection related to your “Post History Bot Result to Teams” flow (it will likely show an error or ask for reconnection) and fix it, ensuring it’s properly authenticated to Teams.

   • Workaround 2 (Advanced): As shown in the video, you can use your browser’s Developer Tools (F12). Inspect the non-working “Connect” button element in the transcript view. Find the aria-label or similar attribute containing a URL (it will look something like https://copilotstudio.microsoft.com/c2/tenants/…/user-connections). Copy this URL, paste it into a new browser tab, and follow the prompts to fix the connection.

   • After fixing the connection, you may need to re-test Flow #1.

Conclusion

That’s it! You’ve now built an automated system where Power Automate triggers a Copilot Studio agent daily, the agent uses AI to generate content, and another Power Automate flow posts that content into Teams.

You can adapt the Copilot’s instructions, the trigger schedule, and the final Teams message formatting to suit countless automation needs. Happy automating!