Microsoft Power Automate Guide: Enterprise Automation for Australian Businesses

Power Automate is part of Microsoft's Power Platform, alongside Power BI, Power Apps, and Power Virtual Agents. For Australian businesses already using Microsoft 365, it provides automation capabilities with minimal additional infrastructure and familiar security models.

Power Automate Licensing for Australia

Power Automate flows consist of triggers, actions, and conditions. Understanding these building blocks is essential for creating effective automations.

Flow Types

Common Trigger Types

// Automated triggers - respond to events
When an email arrives (V3)           - Outlook
When a file is created              - SharePoint, OneDrive
When an item is created or modified - SharePoint lists
When a Teams message is posted      - Microsoft Teams

// Instant triggers - user-initiated
Manually trigger a flow             - Button press
For a selected message              - Outlook context menu
For a selected item                 - SharePoint list action

// Scheduled triggers - time-based
Recurrence                          - Run on schedule
Sliding window                      - Process items in batches

Example: Automated Document Approval

A common Australian business workflow - document approval with notifications:

{
  "trigger": "When a file is created in SharePoint",
  "folder": "/Documents/Pending Approval",
  "actions": [
    {
      "type": "Start and wait for an approval",
      "approvers": ["manager@company.com.au"],
      "title": "Please review: @{triggerOutputs()?['body/DisplayName']}"
    },
    {
      "type": "Condition",
      "expression": "@equals(outputs('Approval')?['body/outcome'], 'Approve')",
      "if_yes": [
        {
          "type": "Move file",
          "destination": "/Documents/Approved"
        },
        {
          "type": "Send email",
          "to": "@{triggerOutputs()?['body/Author/Email']}",
          "subject": "Document approved"
        }
      ],
      "if_no": [
        {
          "type": "Move file",
          "destination": "/Documents/Rejected"
        }
      ]
    }
  ]
}

Power Automate excels at connecting Microsoft 365 services. These patterns address common Australian business scenarios.

Teams Automation

Automate communication and collaboration workflows in Microsoft Teams:

SharePoint Automation

SharePoint integration is Power Automate's strongest capability:

Common SharePoint Triggers:
- When an item is created
- When an item is created or modified
- When a file is created (in a folder)
- When a file is created or modified (properties only)
- For a selected item (manual trigger)

Common SharePoint Actions:
- Create item
- Update item
- Get items (with OData filtering)
- Send an HTTP request to SharePoint
- Grant access to an item or folder
- Create sharing link for a file or folder

Outlook & Email Automation

{
  "name": "Invoice Processing Automation",
  "trigger": {
    "type": "When a new email arrives",
    "filters": {
      "subject_contains": "Invoice",
      "has_attachment": true
    }
  },
  "actions": [
    {
      "type": "AI Builder - Extract information from invoices",
      "attachment": "@{triggerOutputs()?['body/attachments']}"
    },
    {
      "type": "Create item in SharePoint",
      "list": "Invoice Register",
      "fields": {
        "Vendor": "@{outputs('AI_Builder')?['vendor_name']}",
        "Amount": "@{outputs('AI_Builder')?['invoice_total']}",
        "DueDate": "@{outputs('AI_Builder')?['due_date']}",
        "ABN": "@{outputs('AI_Builder')?['vendor_abn']}"
      }
    },
    {
      "type": "Condition",
      "expression": "@greater(outputs('AI_Builder')?['invoice_total'], 10000)",
      "if_yes": "Start approval workflow",
      "if_no": "Send to accounts for processing"
    }
  ]
}

AI Builder adds pre-built and custom AI models to your Power Automate flows, enabling intelligent document processing without machine learning expertise.

Pre-built AI Models

Custom Document Processing

Train custom models for Australian-specific documents:

Custom Model Training Process:

1. Collect sample documents (minimum 5, recommended 15+)
   - Australian tax invoices
   - Industry-specific forms
   - Internal documents

2. Label documents in AI Builder
   - Mark fields to extract
   - Handle variations in layout
   - Define data types (text, number, date)

3. Train and evaluate model
   - Review confidence scores
   - Test with new documents
   - Iterate on labelling

4. Publish and use in flows
   - Process documents automatically
   - Handle low-confidence extractions
   - Route for human review when needed

Desktop flows bring robotic process automation (RPA) capabilities to Power Automate, enabling automation of legacy Windows applications and web interfaces that lack APIs.

When to Use Desktop Flows

• Legacy ERP systems - Older MYOB, SAP GUI, custom applications
• Government portals - ATO, state government systems without APIs
• Desktop applications - Excel macros, Access databases, legacy software
• Web applications - Sites without APIs that need data entry or extraction

Desktop Flow Architecture

Power Automate Desktop Components:

┌─────────────────────────────────────────────┐
│           Cloud Flow (Orchestration)         │
│  - Triggers desktop flow                     │
│  - Passes input parameters                   │
│  - Receives output data                      │
└──────────────────┬──────────────────────────┘
                   │
                   ▼
┌─────────────────────────────────────────────┐
│        On-premises Data Gateway              │
│  - Secure connection to local machines       │
│  - Handles authentication                    │
└──────────────────┬──────────────────────────┘
                   │
                   ▼
┌─────────────────────────────────────────────┐
│    Power Automate Desktop (Local Machine)    │
│  - UI automation actions                     │
│  - Browser automation                        │
│  - Excel, file system operations             │
└─────────────────────────────────────────────┘

Recording Desktop Actions

Power Automate Desktop provides recording capabilities:

Recording Types:

Desktop Recorder:
- Records mouse clicks and keyboard input
- Captures UI element selectors
- Handles window interactions
- Best for: Windows applications

Web Recorder:
- Records browser interactions
- Captures web element selectors
- Handles dynamic content
- Best for: Web applications without APIs

Tips for Reliable Recordings:
1. Use descriptive variable names
2. Add wait conditions for page loads
3. Implement error handling
4. Use UI element selectors over coordinates
5. Test on different screen resolutions

Enterprise Power Automate deployments require robust governance to maintain security, compliance, and manageability. Australian businesses must consider data residency and privacy requirements.

Data Loss Prevention (DLP) Policies

DLP policies control which connectors can be used together:

DLP Policy Groups:

Business Data Only:
- SharePoint, OneDrive
- Microsoft 365 services
- Dynamics 365
- Approved third-party services

No Business Data Allowed:
- Social media connectors
- Personal email services
- Unapproved cloud storage

Blocked:
- Connectors not permitted in your organisation
- High-risk external services

Australian Consideration:
- Classify connectors based on data residency
- Block connectors that store data outside Australia
- Require approval for premium connectors

Environment Strategy

Recommended Environment Structure:

┌─────────────────────────────────────────────┐
│              Default Environment             │
│  - Personal productivity flows               │
│  - Limited connectors via DLP                │
│  - Self-service automation                   │
└─────────────────────────────────────────────┘

┌─────────────────────────────────────────────┐
│           Development Environment            │
│  - Flow development and testing              │
│  - Non-production data only                  │
│  - Full connector access                     │
└─────────────────────────────────────────────┘

┌─────────────────────────────────────────────┐
│           Production Environment             │
│  - Approved, tested flows only               │
│  - Strict DLP policies                       │
│  - Solution-based deployment                 │
│  - Monitoring and alerting                   │
└─────────────────────────────────────────────┘

Australian Compliance Considerations

Production-grade Power Automate implementations require attention to error handling, performance, and maintainability.

Error Handling Patterns

{
  "pattern": "Try-Catch with Scope",
  "structure": {
    "scope_try": {
      "actions": ["Main business logic"],
      "run_after": "always"
    },
    "scope_catch": {
      "run_after": {
        "scope_try": ["Failed", "TimedOut"]
      },
      "actions": [
        "Log error to SharePoint",
        "Send alert email",
        "Create incident ticket"
      ]
    },
    "scope_finally": {
      "run_after": {
        "scope_try": ["Succeeded", "Failed", "Skipped", "TimedOut"],
        "scope_catch": ["Succeeded", "Failed", "Skipped", "TimedOut"]
      },
      "actions": ["Cleanup operations"]
    }
  }
}

Performance Optimisation

Performance Best Practices:

1. Minimise API Calls
   - Use batch operations where available
   - Filter data at source (OData filters)
   - Cache frequently accessed data

2. Parallel Processing
   - Use "Apply to each" with concurrency control
   - Default: Sequential (1)
   - Maximum: 50 parallel iterations
   - Set based on connector throttling limits

3. Efficient Data Operations
   - Select only needed columns
   - Use Top N for large lists
   - Implement pagination for large datasets

4. Avoid Common Pitfalls
   - Don't nest "Apply to each" unnecessarily
   - Use variables sparingly (expression preferred)
   - Avoid "Get items" without filters

Solution-Based Deployment

Enterprise deployments should use solutions for proper ALM:

Solution Deployment Pipeline:

Development:
1. Create solution in dev environment
2. Add flows, connection references, environment variables
3. Test thoroughly with non-production data

Export:
1. Export as managed solution
2. Store in source control (Azure DevOps)
3. Version appropriately

Import to Production:
1. Import managed solution
2. Configure connection references
3. Set environment variable values
4. Enable and test flows

Benefits:
- Version control and rollback
- Consistent deployments
- Separation of configuration from logic
- Audit trail of changes

Understanding when Power Automate is the right choice versus alternatives helps Australian businesses make informed decisions.

When to Choose Power Automate

• Microsoft-centric environment - Already using M365, Dynamics 365, or Azure
• Enterprise governance needs - DLP, environments, audit requirements
• Desktop automation required - Legacy apps without APIs
• IT-controlled deployment - Central management of automations
• Australian data residency - Need data to stay in Australia

When to Consider Alternatives

• Non-Microsoft ecosystem - Primary tools are Google Workspace, AWS, or other vendors
• Simple automations - Basic integrations where Zapier is more cost-effective
• Complex data transformations - Make.com or custom code may be more suitable
• Multi-cloud integrations - Cross-platform needs beyond Microsoft