Power Automate Approval Function

Samin, RJ Elizer 0 Reputation points
2025-08-28T16:05:20.47+00:00

Hey,

My team is currently using the approval function in power automate to accept and reject certain requests.

However, when we try to respond to the request in the email notification it will say "An error occurred. Please try again later"

As a work around we are having to go to the Power Automate Dashboard and respond there.

Does anyone know why we are not able to respond directly in the email?

Or is it possible to revert it back to the old format where it would redirect them to Power Automate.

Inkedimage (21)_LI

Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. John Burkholder 0 Reputation points
    2025-08-28T20:37:59.8233333+00:00

    You're encountering a common issue with Power Automate approval emails, where users see "An error occurred. Please try again later" when trying to respond directly from the email. Here's a breakdown of the causes and solutions:


    🔍 Why the Error Happens

    1. Outlook Version or Configuration
    • Older versions of Outlook Desktop may not support Actionable Messages, which are required for in-email approvals.
    • This issue is resolved in Outlook Desktop build 16.0.11901.20167 and higher [1].
    • If you're using Outlook Web (OWA), it usually works better for these messages.
    1. Tenant-Level Settings
    • Actionable messages must be enabled at the Microsoft 365 tenant level:
    Get-OrganizationConfig | ft ConnectorsActionableMessagesEnabled,SmtpActionableMessagesEnabled
    

    Both values should be $true [1].

    1. Email Layout Variability
    • Some users receive emails with blue buttons that redirect to make.powerautomate.com, while others get the older layout with direct approval buttons.
    • This inconsistency can be caused by:
      • Licensing issues (e.g., users without Power Automate licenses).
        • Account mismatches (e.g., logged into a different Microsoft account).
          • Email redirection to external platforms [2].
    1. HTTP Errors (403, 401)
    • These errors often relate to:
      • Permission issues in Power Automate or SharePoint.
        • Guest accounts or users outside the environment.
          • Expired or misconfigured connections [3].

    Workarounds and Fixes

    1. Use Outlook Web (OWA) or Teams for approvals.
    2. Update Outlook Desktop to the latest version.
    3. Enable Actionable Messages at the tenant level.
    4. Use the Actionable Messages Debugger to diagnose issues in Outlook.
    5. Recreate or reconfigure the flow using “Start and wait for an approval” to ensure consistent behavior.
    6. Reconnect shared connections if you're a co-owner of the flow [3].

    🔄 Reverting to Old Format

    Unfortunately, you can't manually revert to the old approval email format. Microsoft controls the rendering based on:

    • Outlook version
    • Tenant settings
    • User licensing
    • Flow configuration

    However, you can force redirection by using HTML emails with links to Power Automate or Teams, or guide users to respond via those platforms.


    Would you like help checking your tenant settings or crafting a fallback approval email template that redirects users to Power Automate or Teams?

    References

    [1] Issues with flow approval emails in Outlook - Power Automate

    [2] Approval email (with different layout) redirects to make.powerautomate ...

    [3] Standard Approval Errors

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.