IBA - Innovative Business Practices
TR/EN
Power Apps & Power Automate TrainingTraining

Power Apps & Power Automate Training

Power Apps and Power Automate let business users with no development background build their own department’s application. In these trainings the participant builds the selected case’s application from start to finish. The Power Automate Cloud training covers cloud automations such as approval flows and scheduled tasks as a subject of its own, separate from app development.

Power Apps & Power Automate Training

Trainings in This Category

Select a training to see its agenda, project cases and technical requirements.

App in a Day

One-Day App and Automation Workshop

01Training Overview

Duration
1 Day
Training Hours
09:30 – 16:30
Maximum Participants
10 Participants
Hands-on Ratio
80% Hands-on / 20% Theory
Certificate
Participants receive an IBA Consultancy Certificate of Participation at the end of the training.
Format
Online, On-site or Hybrid — based on the organisation's preference.
Prerequisites
None. No prior experience with Power Apps or Power Automate is required.
Training Objective

This training teaches participants, in one day, to design a simple app with Power Apps and to build an approval/notification flow connected to that app with Power Automate. The programme covers screen and form design, data connection, basic automation (trigger, condition, action) and testing, all hands-on.

The training works through a simple manual process chosen by the participant from their own department; by the end of the day, participants leave with a working app and an automation flow connected to it.

Participants start from a blank page and leave having turned a simple manual process from their own department into a working app and automation.

Technical Content

App Fundamentals

  • Introduction to the Power Apps interface
  • Screen and form design
  • Connecting to a data source
  • Basic controls and navigation

Automate Fundamentals

  • Introduction to the Power Automate interface
  • Trigger and action logic
  • Setting up approval and notification flows
  • Connecting the app to the flow and testing

02Exercises and Project Scenarios

Option A

Expense Tracking (Simple Version)

A single-screen app where the employee submits an expense claim, and a simple automation flow that sends the claim to the manager for approval.

Option B

Inventory Tracking (Simple Version)

A single-screen app where product/material stock entries are recorded, and a simple automation flow that sends a notification when stock runs low.

Option C

Travel Leave Request (Simple Version)

A single-screen app where the employee requests travel leave, and a simple automation flow that sends the request to the manager for approval.

Whichever case is selected, the technical scope and outcomes of the training remain the same — the same app design and automation topics are covered. The organisation can later extend this case into a full-scope system, including Dataverse, in IBA's AB-410 training.

03Training Agenda (1 Day)

The agenda runs end to end in a single day; participants start the morning with a blank app and finish the day with a working app and automation flow.

  1. Day 1 — App Design, Automation and End-to-End Testing

    • Introduction to Power Apps and a tour of the interface
    • Exercise 1: Creating a blank app
    • Screen and form design fundamentals
    • Exercise 2: Designing the data entry form and controls
    • Connecting to a data source
    • Morning Deliverable: Connecting the app to the data source and creating the first record
    • Introduction to Power Automate: trigger and action logic
    • Exercise 4: Building an approval/notification flow triggered when a record is created
    • End-to-end testing and debugging
    • Final Deliverable: Verifying that a record entered in the app triggers the automation
    • Overall review, Q&A and certificate presentation

04Technical Requirements

Computer

1 per participant (Windows or macOS), with an internet connection

Browser

Microsoft Edge or Google Chrome (latest version)

Account

A Microsoft work/school account

Software Installation

Not required. All work is done in the browser.

Data Source

A sample SharePoint list is used in the training; if preferred, the organisation can prepare a test list in its own environment.

Licensing

No licence purchase is required for this training.

Power Apps and Power Automate are used with the standard (non-per-app) rights included in participants' existing Microsoft 365 licences, or in a free trial environment.

If the organisation moves the app into production or adopts premium connectors such as Dataverse, a separate licensing assessment may be needed — this is outside the scope of the training.

05Learning Outcomes

Build their first app

Create a Power Apps app from scratch and carry out basic screen/form design.

Connect to a data source

Connect the app to a data source and create records.

Build automation

Build a simple approval/notification flow with Power Automate.

Test end to end

Verify that the app and automation work correctly together.

Assess scope

Assess which manual process in their own department is suitable for an app.

Power Apps + Power Automate - Basic

Basic — Foundation Level App and Automation Training

01Training Overview

Duration
4 Days
Training Hours
09:30 – 16:30
Maximum Participants
10 Participants
Hands-on Ratio
80% Hands-on / 20% Theory
Certificate
Participants receive an IBA Consultancy Certificate of Participation at the end of the training.
Format
Online, On-site or Hybrid — based on the organisation's preference.
Prerequisites
No software development knowledge is required. Basic Excel/Office skills are sufficient. Designed for business users and citizen developers.
Training Objective

This training teaches business users and citizen developers with no software development background to build a functional app with Power Apps and an automation flow connected to that app with Power Automate. The programme covers, hands-on, data source fundamentals, canvas app screen/control design, Power Fx fundamentals, a working CRUD (create-read-update-delete) app, Power Automate triggers/actions/connectors, and approval and notification flows.

Compared with IBA's "AB-410: Microsoft Power Platform App Development Training", this training offers a shorter, entry-level introduction without Dataverse — the organisation can later extend the same case to AB-410 scope, including Dataverse.

Participants leave having turned a manual process from their own department into a working app and automation that their team can actually use.

Technical Content

App Fundamentals

  • Power Platform and data source fundamentals
  • Canvas app screens, controls and Power Fx fundamentals
  • Developing a functional CRUD (create-read-update-delete) app

Automate Fundamentals

  • Power Automate: trigger, action and connector fundamentals
  • Approval and notification flows
  • Combining the app and flows in a mini project

02Exercises and Project Scenarios

Option A

Expense Tracking

An app and flow where employees submit expense claims, the manager approves them and the status is communicated through an automatic notification.

Option B

Inventory Tracking

An app and flow where product/material stock entries are recorded and an automatic notification is sent when stock runs low.

Option C

Travel Leave Request

An app and flow where the employee requests travel leave, the request goes to the manager for approval and the outcome is notified.

Whichever case is selected, the technical scope and outcomes of the training remain the same — the same app design and automation topics are covered. The training is based on a single case chosen by the participant from their own department; over four days this case is built up step by step: on Day 1 the case's first screen is built on data source and canvas app screen/control fundamentals, on Day 2 a functional CRUD app is completed with Power Fx, on Day 3 the first automation flow (trigger/action) is added to the case with Power Automate fundamentals, and on Day 4 the app-to-flow connection is completed in a mini project with approval and notification flows. The cases come from the same family as those used in IBA's AB-410 training; the organisation's own process can also be used as the case — provided it is of similar scope, this does not affect the duration or price of the training. Dataverse is not included in this training; a SharePoint list is used as the data source. The organisation can later extend this case into a full-scope system, including Dataverse, in IBA's AB-410 training.

03Training Agenda (4 Days)

The agenda is worked through day by day on the selected case; each day adds a new layer to the previous one.

  1. Day 1 — Data Source Fundamentals and the First Screen

    • Introduction to the Power Platform ecosystem
    • Data source concepts and working with a SharePoint list
    • Exercise 1: Preparing a data source suited to the case
    • Introduction to the canvas app interface: screens and controls
    • Exercise 2: Designing the case's first data entry screen
    • Introduction to Power Fx: basic formulas and logic
  2. Day 2 — Functional CRUD App

    • Creating and listing records with Power Fx
    • Exercise 3: Adding record creation and listing functions
    • Updating and deleting records with Power Fx
    • End-of-Day Deliverable: Completing an end-to-end working CRUD app
    • Improving the user experience with form and gallery controls
  3. Day 3 — Power Automate Fundamentals

    • Introduction to Power Automate: trigger and action logic
    • The connector concept and commonly used connectors
    • Exercise 4: Building the first automation flow triggered when a record is created
    • The approval flow concept
    • Exercise 5: Sending the request to the manager for approval
  4. Day 4 — Notifications, Mini Project and End-to-End Testing

    • Designing a notification flow
    • Exercise 6: Automatically notifying the requester of the approval outcome
    • Connecting the app and flows
    • Exercise 7: Completing the end-to-end scenario as part of the mini project
    • Final Deliverable: Verifying that a record entered in the app triggers the automation
    • Overall review, Q&A and certificate presentation

04Technical Requirements

Computer

1 per participant (Windows or macOS), with an internet connection

Browser

Microsoft Edge or Google Chrome (latest version)

Account

A Microsoft work/school account

Software Installation

Not required. All work is done in the browser.

Data Source

A sample SharePoint list is used in the training; if preferred, the organisation can prepare a test list in its own environment.

Licensing

No licence purchase is required for this training.

Power Apps and Power Automate are used with the standard (non-per-app) rights included in participants' existing Microsoft 365 licences, or in a free trial environment.

If the organisation moves the app into production or adopts premium connectors such as Dataverse, a separate licensing assessment may be needed — this is outside the scope of the training.

05Learning Outcomes

Build a functional app

Develop a Power Apps app for their own department with data entry, listing, update and delete functions.

Build an automation flow

Build an approval and notification flow in Power Automate that is triggered when a record is created.

Integrate end to end

Bring the app and flow together in a single working mini project.

Assess scope

Assess which manual process in their own department is suitable for an app.

Plan the move to advanced level

Identify where their case requires Dataverse and more advanced skills (AB-410 scope).

AB-410 (Power Apps + Power Automate + Dataverse)

App Development Training

01Training Overview

Duration
6 Days
Training Hours
09:30 – 16:30
Maximum Participants
10 Participants
Hands-on Ratio
80% Hands-on / 20% Theory
Certificate
Participants receive an IBA Consultancy Certificate of Participation at the end of the training.
Format
Online, On-site or Hybrid — based on the organisation's preference.
Prerequisites
No software development knowledge is required. Basic Excel/Office skills are sufficient.
Training Objective

This training aims to give participants the skills to digitise business processes end to end using Microsoft Power Apps, Power Automate and Dataverse. Throughout the programme, participants learn algorithmic thinking, data modelling, low-code development with Power Fx, flow design and enterprise data security by building a project themselves.

The key difference of this training is that topics are covered not through theoretical lectures but through a single real business scenario. Before the training, a case is chosen together with the organisation, and over six days this case is built up step by step: it starts with a simple data model, the app interface is built, automation is added, the data model is extended into a relational structure, and on the final day the security and publishing layer is set up.

Dataverse is not a separate module but is built into the process as the data foundation of the selected case; participants set up the data model, build the app on top of it and feed it with flows.

By the end of the training, participants are no longer observers but makers who can build their own department's app.

Technical Content

Power Apps

  • The Power Platform ecosystem, environments and licensing principles
  • Canvas and Model-Driven app architectures
  • Formula-based development with Power Fx
  • Form design, validation and error handling
  • Gallery, filtering, search and delegation optimisation
  • Collections, CRUD operations and multi-screen navigation
  • Mobile/responsive design and publishing

Power Automate

  • Flow types: Automated, Instant and Scheduled flows
  • Trigger–action logic, connectors and connection management
  • Conditional logic (Condition, Switch, Parallel), variables and loops
  • Approval processes, multi-level approval and escalation architecture
  • Teams integration and Adaptive Cards
  • Error handling (Try–Catch pattern), monitoring and logging

Dataverse (runs throughout the training as the projects' data foundation)

  • Dataverse architecture compared with SharePoint: which one when?
  • Tables, columns, data types and relationship types (1:N, N:1, N:N)
  • Lookup, Choice, Calculated and Rollup fields
  • Building business logic without code using Business Rules
  • Power Automate integration with Dataverse triggers
  • Security model: Business Unit, Security Role, Team
  • Record-level and field-level security
  • Solution structure and moving between environments (ALM fundamentals)

02Exercises and Project Scenarios

Option A

Expense Tracking System

A system where employees submit expense claims, upload receipts and track their status. It is extended with an approval mechanism that branches by amount, department-level spending visibility and periodic reporting.

Option B

Inventory and Asset Assignment Tracking System

A system that tracks fixed assets and stock items, the people they are assigned to, and stock-in and stock-out movements. With product, location, staff and movement tables, it is naturally strong on relational modelling; it is extended with critical stock level alerts and asset assignment approval.

Option C

Travel and Leave Request System

A system where staff create travel and leave requests and the manager approves them via Teams. It is extended with a hierarchical approval structure, accrued leave balance calculation and calendar integration.

Whichever case is selected, the technical scope and outcomes of the training remain the same — the same Power Apps, Power Automate and Dataverse topics are covered. A single project case is chosen for the training and built up step by step over six days: on Day 1 the core data model is set up in Dataverse, on Day 2 the Canvas app interface is built, on Day 3 the process is automated with Power Automate, on Day 4 the data model is extended into a relational structure, on Day 5 a Model-Driven interface and a multi-level approval architecture are added, and on Day 6 the security and publishing layer is set up. The organisation can also propose a different case from its own business processes (purchasing, field service, customer request management, etc.) — provided it is of similar scope, changing the scenario does not affect the duration or price of the training.

03Training Agenda (6 Days)

The agenda is worked through on the project case selected before the training. Every step below that mentions "the selected case" is applied to the scenario chosen by the organisation (Expense Tracking / Inventory Tracking / Travel-Leave Request, or an organisation-specific process).

  1. Day 1 — Power Platform Fundamentals and Setting Up the Data Model

    • Introduction to the Power Platform ecosystem and the low-code approach
    • Licensing models and the environment concept
    • Tour of the Maker Portal and the developer interface
    • Algorithmic thinking and introduction to Power Fx
    • Canvas vs Model-Driven apps — which one when?
    • Introduction to Dataverse: architecture and comparison with SharePoint
    • Tables, columns and data types; setting up Choice fields
    • Exercise 1: Creating the Dataverse data model for the selected case
    • Exercise 2: First screen and form design, UI/UX principles
  2. Day 2 — Developing the App Interface with a Canvas App

    • Setting up a Canvas app with a Dataverse connection
    • Exercise 3: Validation rules and error handling
    • Listing data and visual layout with Gallery
    • Exercise 4: Filtering and search
    • The delegation concept and performance optimisation
    • Exercise 5: Collections and sorting
    • CRUD operations and the Patch function
    • Multi-screen navigation structure
    • Mobile and responsive optimisation
    • Testing, publishing and version management of the app
  3. Day 3 — Process Automation with Power Automate

    • Power Automate architecture and flow types (Automated / Instant / Scheduled)
    • Trigger and action concepts; Dataverse triggers
    • Using connectors and managing connections
    • Dynamic content and expressions
    • Exercise 6: Developing a request notification flow
    • Conditional logic: Condition, Switch, Parallel Branch
    • Exercise 7: Designing an approval flow that branches by condition
    • Variables and loop structures (Apply to each)
    • Exercise 8: Error handling — Try–Catch pattern and Run After configuration
    • Interim Deliverable: The app and automation are made to work together as one
  4. Day 4 — Relational Data Modelling and Extending the Data Model

    • Multi-table data architecture and relationship types: 1:N, N:1, N:N
    • Lookup fields and accessing data across tables
    • Automatic calculation with Calculated and Rollup columns
    • Building business logic without code using Business Rules
    • Data import and data quality management
    • Exercise 9: Extending the selected case's data model into a relational structure
    • Exercise 10: Defining Business Rules for business logic
    • Displaying relational data in a Canvas App (nested gallery, lookup forms)
  5. Day 5 — Model-Driven App and Multi-Level Approval Architecture

    • Model-Driven App architecture: Form, View and Sitemap design
    • Comparing Canvas and Model-Driven on the same data model
    • Approval process (Approval Flows) architecture
    • Multi-level approval and escalation logic
    • Interactive approval with Teams integration and Adaptive Cards
    • Scheduled flows and reminder patterns
    • Exercise 11: Creating the Model-Driven interface for the selected case
    • Exercise 12: Designing a multi-level manager approval flow
    • Power Apps ↔ Power Automate integration
  6. Day 6 — Security, Governance and Final Deliverable

    • Dataverse security model: Business Unit, Security Role, Team
    • Record-level and field-level security
    • Managing data access at user, department and organisation level
    • Exercise 13: Defining and testing a department-based security role
    • Solution structure and moving between environments (ALM fundamentals)
    • Exercise 14: Packaging a solution and importing it into the target environment
    • Introduction to Data Loss Prevention (DLP) policies
    • Flow monitoring, logging and analytics
    • Final Deliverable: End-to-end testing, publishing and user handover of the selected case
    • Overall review, Q&A and certificate presentation

04Technical Requirements

Computer

1 per participant (Windows or macOS), with an internet connection

Browser

Microsoft Edge or Google Chrome (latest version)

Account

A Microsoft work/school account or a developer account opened for the training

Software Installation

Not required. All work is done in the browser.

Licensing

No licence purchase is required for this training.

All hands-on work, including Dataverse, is carried out in the Power Apps Developer Plan environment that Microsoft provides free of charge. Each participant creates their own developer environment at the start of the training and works in it throughout.

There is no additional cost on top of the organisation's existing Microsoft 365 licences.

05Learning Outcomes

Develop apps

Turn a manual process in their own department into a Power Apps app that works from data entry through to approval.

Automate processes

Move approval processes that run on Excel and email to multi-level automated approval flows.

Build a data model

Model a business need as Dataverse tables and relationships, and decide when to use SharePoint and when to use Dataverse.

Design security

Define department- and role-based access rules so that data is available to the right people.

Publish the solution

Package the solution they built as a solution and move it from the test environment to the live environment.

Assess feasibility

Judge whether an internal request can be solved with Power Platform and estimate the approximate effort.

PL-400 (Power Apps + Power Automate Advanced)

Advanced App Development Training

01Training Overview

Duration
8 Days
Training Hours
09:30 – 16:30
Maximum Participants
10 Participants
Hands-on Ratio
80% Hands-on / 20% Theory
Certificate
Participants receive an IBA Consultancy Certificate of Participation at the end of the training.
Format
Online, On-site or Hybrid — based on the organisation's preference.
Prerequisites
Power Apps, Power Automate and Dataverse knowledge at AB-410 level (completion of the AB-410 training or equivalent experience is recommended).
Training Objective

This training aims to take the Power Platform knowledge established in AB-410 to the level where participants can build production-ready solutions at enterprise scale. Throughout the programme, participants learn responsive design, advanced data processing, integration with external systems and automated document generation by extending their existing solutions.

For participants who have not taken AB-410, the same case options (Expense Tracking / Inventory Tracking / Travel-Leave Request) are set up quickly on the first day of the training and built upon.

By the end of the training, participants own not a simple app but a fault-tolerant solution that talks to external systems and can be used at enterprise scale.

Technical Content

Power Apps Advanced

  • Responsive design using containers
  • Parametric design with Component and Snippet Library
  • Dynamic content design with Flexible Height Gallery
  • Advanced Patch scenarios and bulk data operations
  • External API integration with Custom Connector
  • Performance optimisation for large datasets

Power Automate Advanced and Integrations

  • Data parsing from the web
  • XML - JSON formatting and conversion
  • Automated PDF/document generation with Power Automate
  • Outlook/Teams integration with Adaptive Cards
  • Enterprise error handling architecture (Try-Scope-Catch)
  • Advanced topics in solution management and moving between environments (ALM)

02Exercises and Project Scenarios

Option A

Expense Tracking System

The expense tracking app built in AB-410 is taken to an advanced level with responsive design, bulk expense operations, exchange rate integration and an automated approval report (PDF).

Option B

Inventory and Asset Assignment Tracking System

The inventory system built in AB-410 is taken to an advanced level with responsive design, bulk stock updates, supplier API integration and an automated asset assignment report (PDF).

Option C

Travel and Leave Request System

The travel/leave system built in AB-410 is taken to an advanced level with responsive design, bulk leave balance updates, exchange rate/per diem API integration and an automated approval document (PDF).

Whichever case is selected, the technical scope and outcomes of the training remain the same — the same responsive design, Advanced Patch, Custom Connector and automated document generation topics are covered. The training is based on a single case selected in AB-410 (or set up quickly on the first day of the training) and takes it to an advanced level step by step over eight days: on Day 1 the interface is moved to responsive design, on Day 2 a component/snippet library and a dynamic gallery are added, on Day 3 bulk data operations are added with Advanced Patch, on Day 4 external API integration is set up with Custom Connector, on Day 5 parsing of external data and scheduled synchronisation are added, on Day 6 automated PDF/report generation and rich notifications are added, on Day 7 enterprise error handling and performance optimisation are added, and on Day 8 the system is integration-tested end to end and the final deliverable is completed. The organisation's own process can also be used as the case — provided it is of similar scope, this does not affect the duration or price of the training.

03Training Agenda (8 Days)

The agenda is worked through by taking the case selected in AB-410 to an advanced level. For participants who have not taken AB-410, the same case options (Expense Tracking / Inventory Tracking / Travel-Leave Request) are set up quickly on the first day of the training and built upon.

  1. Day 1 — Moving to Responsive Design

    • Scope of PL-400 and how it relates to AB-410
    • Principles of responsive design using containers
    • Layout strategies for different screen sizes
    • What is a component and when should it be used?
    • Exercise 1: Moving the selected case's main screen to a container structure
    • Exercise 2: Creating the first component
  2. Day 2 — Component and Snippet Library

    • Parametric design with component properties (Custom Properties)
    • The Snippet Library concept and establishing organisational standards
    • Exercise 3: Extending the reusable component library
    • Dynamic content design with Flexible Height Gallery
    • Exercise 4: Redesigning the list screen with Flexible Height Gallery
    • Testing responsive design on different devices
  3. Day 3 — Advanced Patch and Bulk Data Operations

    • Advanced usage scenarios for the Patch function
    • Bulk update and delete patterns
    • Exercise 5: Developing a bulk data processing scenario with Advanced Patch
    • Fault-tolerant Patch design
    • Performance: Patch optimisation for large datasets
    • Exercise 6: Running and improving a performance test
  4. Day 4 — External System Integration with Custom Connector

    • API concepts: REST, JSON, authentication methods
    • Steps for creating a Custom Connector
    • Exercise 7: Defining a custom connector for an external API (exchange rate service)
    • Connecting the connector to Power Apps and testing it
    • Exercise 8: Adding exchange rate/external data integration to the selected case
  5. Day 5 — Power Automate Advanced Scenarios: Data Parsing

    • Techniques for parsing data from the web
    • Extracting data from HTML/JSON responses
    • XML - JSON formatting and conversion
    • Exercise 9: Parsing an external API response and passing it to the app
    • Designing a scheduled synchronisation flow
    • Exercise 10: Automatic daily update of exchange rate/external data
  6. Day 6 — Automated Document Generation

    • Methods for creating PDFs with Power Automate
    • Template-based document generation
    • Exercise 11: Creating an approval/report PDF template for the selected case
    • Rich Teams/Outlook notifications with Adaptive Cards
    • Exercise 12: Adding the PDF output to a notification with an Adaptive Card
  7. Day 7 — Error Handling and Performance Optimisation

    • Enterprise-scale error handling architecture (Try-Scope-Catch)
    • Retry and notification mechanisms
    • Exercise 13: Strengthening the system with end-to-end error handling
    • Advanced delegation and performance optimisation techniques
    • Monitoring, logging and analytics
    • Exercise 14: Setting up performance testing and a monitoring dashboard
  8. Day 8 — Integration Testing and Final Deliverable

    • Advanced topics in solution management and moving between environments (ALM)
    • Portability with environment variables and connection references
    • Final Deliverable: End-to-end integration testing and publishing of the selected case
    • User handover and documentation
    • Overall review, Q&A and certificate presentation

04Technical Requirements

Computer

1 per participant (Windows or macOS), with an internet connection

Browser

Microsoft Edge or Google Chrome (latest version)

Account

A Microsoft work/school account or a developer account opened for the training

Software Installation

Not required. All work is done in the browser.

External API Access

Test access details for the API to be used in the Custom Connector scenario (an exchange rate service or the organisation's own API) should be shared before the training.

Licensing

No licence purchase is required for this training.

All advanced features, including Custom Connector, are run in the free Power Apps Developer Plan environment.

If the organisation moves the solution built in this training to a production environment, a Power Apps Premium licence may be required depending on the features used — this is outside the scope of the training and is a matter for a separate assessment.

05Learning Outcomes

Develop mobile/responsive solutions

Move an existing app to a responsive structure that works smoothly on different screen sizes.

Integrate with external systems

Connect an external API used by the organisation (bank, ERP, exchange rate service, etc.) to their app with a custom connector.

Generate documents automatically

Produce outputs such as approvals/reports automatically as PDFs with Power Automate.

Process data in bulk

Update/delete large numbers of records in a single operation with Advanced Patch.

Resolve performance issues

Diagnose and optimise performance issues in large datasets.

Scale to enterprise level

Take the solution live with a fault-tolerant, monitorable and maintainable architecture.

Power Automate Cloud

Cloud Automation Fundamentals Training

01Training Overview

Duration
2 Days
Training Hours
09:30 – 16:30
Maximum Participants
10 Participants
Hands-on Ratio
80% Hands-on / 20% Theory
Certificate
Participants receive an IBA Consultancy Certificate of Participation at the end of the training.
Format
Online, On-site or Hybrid — set according to the organisation's preference.
Prerequisites
No software development knowledge is required. Basic Excel/Office skills are sufficient.
Training Objective

This training teaches participants to build different automation patterns (approval, scheduled, notification/integration, data processing) from scratch with Power Automate cloud flows. The programme covers trigger and action logic, connector usage, conditional logic and the basics of error handling through hands-on work.

This training has a different focus from IBA's "Power Apps + Power Automate" and AB-410 trainings: there, automation is taught as a single flow tied to an app the participant builds; here, no app is built, and the training goes straight into the breadth of four different automation patterns. If the organisation later wants to combine automation with an app, it can move on to Power Apps + Power Automate or AB-410.

By the end of the training, participants can choose and build the right flow for their own department's different automation needs (approval, scheduling, notification, data processing).

Technical Content

Cloud Flow Fundamentals

  • Introduction to Power Automate: triggers, actions and connectors
  • Trigger types: instant, automated, scheduled
  • Conditions and branching logic

Automation Patterns

  • Approval processes
  • Scheduled flows
  • Notifications and system integration (email, Teams)
  • Basic error handling

02Exercises and Project Scenarios

Scenario 1

Approval Flow

Covers a multi-stage approval flow in which a request (expenses, leave, etc.) is sent to a manager for approval and the outcome is notified automatically.

Scenario 2

Scheduled Flow

Covers a flow that runs automatically at set intervals, for example sending a weekly summary report.

Scenario 3

Notification and Integration Flow

Covers a flow triggered by an email or Teams message that sends automatic notifications to the relevant people.

Scenario 4

Data Processing Flow

Covers a flow in which incoming data is filtered and processed based on conditions and the result is written to a list/table.

Together, the four scenarios show the range of automation Power Automate provides across approval, scheduling, notification and data processing. The four scenarios below are the standard exercise set for the training and are worked through in order; they are not alternatives, and all of them are covered. The strength of Power Automate comes not from mastering a single type of flow but from being able to adapt to different trigger and integration types. If the organisation would like a scenario of similar complexity taken from its own processes (purchase approval, weekly report distribution, system notifications, etc.), it can replace one of the existing scenarios. Changing a scenario does not affect the duration or price of the training.

03Training Agenda (2 Days)

The agenda works through four independent automation patterns day by day; the first day focuses on approval and scheduled flows, the second on notification/integration and data processing flows.

  1. Day 1 — Fundamentals, Approval and Scheduled Flows

    • Introduction to Power Automate: triggers, actions and connectors
    • Exercise 1: Building a first flow (a simple trigger and action)
    • Approval processes and conditional routing
    • Exercise 2: Developing a multi-stage approval flow
    • Scheduled trigger logic
    • End-of-Day Deliverable: Completing a flow that runs on a schedule
  2. Day 2 — Notification, Integration and Data Processing

    • Notifications and system integration (email and Teams connectors)
    • Exercise 3: Developing the notification/integration flow
    • Conditional data processing and filtering
    • Exercise 4: Developing the data processing flow and writing the output to a list/table
    • Basic error handling
    • Final Deliverable: Testing all four scenarios and confirming they work
    • Overall review, Q&A and certificate presentation

04Technical Requirements

Computer

1 per participant (Windows or macOS), with internet access

Browser

Microsoft Edge or Google Chrome (latest version)

Account

Microsoft work/school account

Software Installation

Not required. All work is done in the browser.

Data Source

A sample SharePoint list is used in the training; if preferred, the organisation can prepare a test list in its own environment.

Licensing

No licence purchase is required for this training.

Power Automate is used with the standard (non-per-app) rights included in participants' existing Microsoft 365 licences.

If advanced scenarios such as premium connectors, AI Builder or unattended automation are required, a separate licensing review may be needed — this is outside the scope of the training.

05Learning Outcomes

Build approval flows

Develop a multi-stage flow that sends a request to a manager for approval.

Build scheduled flows

Design a flow that runs automatically at set intervals.

Build notification flows

Develop a flow that sends automatic notifications by email or Teams.

Process data

Process incoming data with conditional filtering and write it to a list/table.

Choose the right pattern

Assess which flow pattern suits their own department's automation needs.

Frequently Asked Questions

In order to cover the topics comprehensively and to ensure that the practical work is efficient, the beginner level training is planned as 2 days and the advanced level training is planned as 4 days. Flexible time options are offered to suit the participants' schedules.

Trainings are conducted in an interactive format by expert trainers in the field. The learning process is supported by presenting theoretical explanations and practical applications together. Power Apps training also provides remote access with the online participation option. Necessary training materials and resources are delivered to participants in a digital environment.

Microsoft Power Apps training is open to anyone who wants to digitize business processes and develop applications. Software developers, IT professionals and business analysts can also increase their competencies by attending this training.

There are no prerequisites for participating in the training. Desire to learn and interest in technology are the most important factors for a successful training process.

Participants are given a certificate of achievement when the case studies in the training programs are successfully comp leted in line with the determined concept. In cases where the concept studies are not implemented, those who actively participate in the training process receive a certificate of participation documenting that they have completed the process.

The training program for the beginner level is spread over a total of 2 days. For the advanced level, it is determined as 4 days. During this period, theoretical information and practical studies are presented in a balanced way.

Our trainings can be carried out in a face-to-face classroom environment or via online platforms. Flexibility is provided according to the participants' preferences. In both formats, an interactive learning experience is offered and active participation of the participants is encouraged.

This course is open to all professionals who want to automate their business processes. It is especially useful for business analysts, software developers and process managers. You do not need a technical background, but basic computer skills are sufficient.

Anyone can join Power Automate Training. However, having basic computer and internet knowledge will make your learning process easier. Having worked with Microsoft products before may also be an advantage.

When the case studies in the training process are successfully completed, participants are presented with a certificate of achievement. If the concept studies are not implemented, a certificate of participation is given to show that they participated in the training process.