Power Automate Workflow Setup Guide: From Zero to Your First 5 Automations (2026)

What You Need Before Starting

Before you open the Power Automate designer, confirm that your organization’s Microsoft 365 plan includes Power Automate with standard connectors. Most Microsoft 365 Business and Enterprise plans — including Office 365 E3, E5, and Microsoft 365 Business Premium — provide access to standard connectors at no extra cost. If you can log into make.powerautomate.com with your work or school account, you are already set.

Use this checklist to verify your setup:

• You have a Microsoft 365 work or school account with a Business or Enterprise license.
• You can access make.powerautomate.com and see the Power Automate home page.
• You have permission to create flows in your default environment (most users do by default).
• You can access the services you want to connect — SharePoint, Teams, OneDrive, Forms, and Outlook — with the same account.

If your organization has strict Data Loss Prevention (DLP) policies, some connectors may be blocked from working together. You will see an error when you try to add a blocked connector. In that case, contact your Microsoft 365 admin to request an exception for the specific connectors you need.

The Trigger-Action Mental Model (The Only Concept You Need)

Every Power Automate flow follows the same pattern: something happens (the trigger), and then something else happens as a result (the action). Think of it like a vending machine: you press a button (trigger), and the machine dispenses a drink (action). The flow sits between the two, waiting for the trigger and executing the action automatically.

Power Automate supports three main types of triggers:

• Automated triggers — An event starts the flow automatically, such as a new email arriving or a SharePoint list item being added.
• Instant triggers — You start the flow manually from a button in Power Automate, Teams, or a mobile device.
• Scheduled triggers — The flow runs at a specific time or interval, such as every morning at 8:00 AM.

After the trigger fires, the flow runs one or more actions in sequence. An action can be sending an email, creating a file, posting a message, or updating a database. You can add conditions, loops, and parallel branches, but the core structure is always trigger → action.

Flow 1: Save Email Attachments to OneDrive or SharePoint

This flow watches your inbox for emails with attachments and automatically saves those attachments to a folder you choose. It is the most common entry-level flow and can be built in under 10 minutes using a template.

Step-by-step

1. Go to make.powerautomate.com and sign in with your work or school account.
2. In the left navigation, click Create and search for the template called "Save email attachments to OneDrive for Business."
3. Select the template. Power Automate will ask you to connect your Outlook and OneDrive accounts if they are not already connected.
4. Set the folder path where attachments should be saved (e.g., /Email Attachments).
5. Optionally, add a condition to filter by sender or subject. For example, only save attachments from your manager or emails with "Invoice" in the subject line.
6. Click Save and then Test to send yourself an email with an attachment and watch the flow run.

Flow 2: Post a Teams Notification When a SharePoint List Item Changes

This flow connects SharePoint and Teams — two services your organization likely already uses. When someone adds or modifies an item in a SharePoint list, the flow posts a message to a Teams channel with the item details.

Step-by-step

1. In Power Automate, click Create and then Automated cloud flow.
2. Search for the trigger When an item is created or modified (SharePoint connector). Select it and click Create.
3. Provide the SharePoint site URL and the list name you want to monitor.
4. Click New step and search for Post a message in a chat or channel (Teams connector).
5. Select the Teams channel where the notification should appear.
6. Build the message using dynamic content from the trigger. For example: "A new item was added to [List Name]: [Item Title]." Click into the message box and select fields like Title and Modified from the dynamic content panel.
7. Save and test by adding a new item to your SharePoint list.

This flow is especially useful for project tracking, issue logs, or any shared list where team members need real-time visibility into changes.

Flow 3: Route an Approval Request from a Form Submission

Approval workflows are one of the most requested automation patterns in Microsoft 365 organizations. This flow starts when someone submits a Microsoft Form, sends an approval request to a manager, and then acts on the response — either updating a SharePoint list or sending a confirmation email.

Step-by-step

1. Create a new Automated cloud flow and select the trigger When a new response is submitted (Microsoft Forms connector).
2. Select your form from the dropdown. If you have not created one yet, go to forms.office.com and build a simple request form (e.g., "IT Access Request" with fields like Employee Name, Request Type, and Justification).
3. Click New step and search for Start and wait for an approval (Approvals connector).
4. Configure the approval: set the approval type to "Approve/Reject — First to respond," assign the approver (a manager's email), and build the request details using dynamic content from the form response.
5. Add a condition step: if the approval response equals "Approve," add an action to send a confirmation email or update a SharePoint list. If "Reject," send a different notification.
6. Save and test by submitting a response to your form. The approver will receive an email or Teams notification with Approve and Reject buttons.

Flow 4: Send a Daily Scheduled Email Digest

Scheduled flows run at a specific time without waiting for an event. This flow gathers data from a SharePoint list or Excel file and emails a summary to you or your team every morning.

Step-by-step

1. Click Create and then Scheduled cloud flow.
2. Set the schedule: choose a start date and time, then set the repeat frequency to Day and enter 1 for the interval. Pick a time that works for your team, such as 7:00 AM.
3. Click New step and add a Get items action (SharePoint connector) pointing to the list you want to summarize.
4. Add a Compose action to build the email body. Use dynamic content to insert item titles, statuses, and due dates into a formatted HTML table.
5. Add a Send an email action (Outlook connector). Set the recipient, subject (e.g., "Daily Project Summary — [Date]"), and body to the output of the Compose step.
6. Save and test manually to verify the email looks correct before the first scheduled run.

This pattern works for daily status reports, task reminders, or any recurring data summary. You can extend it by adding a filter to only include items modified in the last 24 hours.

Flow 5: Log Form Responses to Excel or SharePoint Automatically

By default, Microsoft Forms stores responses inside the form itself. This flow captures each new response and writes it to an Excel spreadsheet or SharePoint list, giving you a permanent, queryable record that other tools can access.

Step-by-step

1. Create a new Automated cloud flow with the trigger When a new response is submitted (Microsoft Forms connector). Select your form.
2. Click New step and choose either Add a row into a table (Excel Online connector) or Create item (SharePoint connector).
3. If using Excel: provide the OneDrive or SharePoint file path, select the table name, and map each form field to the corresponding column using dynamic content.
4. If using SharePoint: provide the site URL and list name, then map form fields to list columns.
5. Save and test by submitting a new form response. Check your Excel file or SharePoint list to confirm the row was added.

This flow is ideal for registration forms, feedback surveys, help desk tickets, or any data collection that needs to feed into a reporting dashboard or downstream process.

Bonus: When to Upgrade — Signs You Need Premium Connectors

The five flows above use only standard connectors included with your Microsoft 365 license. You may eventually encounter a scenario that requires a premium connector — for example, connecting to Salesforce, SAP, or a custom API, or using attended desktop flows for legacy applications. The Power Automate Premium plan costs $15 per user per month (billed annually) and unlocks those capabilities along with Dataverse storage and AI Builder credits.

Testing and Monitoring Your Flows

Before you let a flow run unattended, test it with real data. Power Automate provides a built-in test mode that lets you run the flow manually and inspect each step.

How to test a flow

• Open your flow in the designer and click Test in the top-right corner.
• Choose "Manually" to trigger the flow yourself, or "Automatically" to wait for the next real trigger event.
• Watch each step as it runs. Green checkmarks indicate success; red X marks indicate failure with an error message.
• Use Flow Checker (available in the designer toolbar) to catch common issues like missing connections or invalid expressions before testing.

Monitoring run history

After a flow is live, you can monitor its performance from the My Flows section in Power Automate. Each flow shows a 28-day run history, including start time, duration, status, and any error details. Click on any run to see the input and output of every step — this is invaluable for debugging failed runs.

Next Steps and Resources

You have now built five practical automations using only standard connectors included with your Microsoft 365 license. More importantly, you have internalized the trigger-action model that underlies every Power Automate flow — from simple email handlers to complex multi-step approvals.

Here are recommended next actions:

• Explore the template gallery in Power Automate — there are hundreds of pre-built templates for scenarios like automated email responses, calendar management, and social media monitoring.
• Join the Power Automate Community on the Microsoft Power Platform forums to ask questions and share flows.
• If your needs grow beyond standard connectors, compare Power Automate with Zapier, Make, and n8n to find the best fit for your workflow automation requirements.
• Review the official Power Automate documentation for advanced topics like error handling, parallel branches, and environment variables.

The five flows in this guide are a starting point, not a ceiling. Every flow you build from here will follow the same trigger-action pattern you have already learned.