web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / SendEmailV2 403 error ...
Power Apps
Answered

SendEmailV2 403 error for some users but it works for most of them, why?

(0) ShareShare
ReportReport
Posted on by 179

Hello!

 

In my powerapps, I use this code to allow users to send an email :

Office365Outlook.SendEmailV2(varStringEnvoyerCourrielA; "A task for you";"Hello world!";

{From:"xxx@yyy.zzz";Cc:CurrentUser.Email;Importance:"Normal"}

 

You may notice I use from because I want the email to be sent from a generic "customer service" email. Not all users have access to this mailbox (neither do I). But I added a data connector inside the app to the mailbox that HAS access to this generic mailbox.

During my phase tests, everything looked great : I was able to send email on behalf of a mailbox I cannot access otherwise (I can't access it in Outlook). Now I deployed it and it works for some users including myself but not for many other users and they get this error :

Volt26_0-1684508066725.png


I don't understand why it works for me and it doesn't for others. Here is a screenshot of the mailbox I added in the app (the user had to enter his password to make this work) :

Volt26_1-1684508179524.png

 

I can make it work with a powerautomate that is triggered when the Sharepoint list changes BUT it takes 4 minutes for the whole process to work for reasons I didn't grasp yet while the script within Power Apps does it instantly (except the first time of the day that takes 2 minutes for unknown reasons). I get much faster results with the script when it runs within PowerApps than when it runs from Power Automate. For this reasons, I would rather make it work in PowerApps.

 

Can someone bring me light on this issue?

Categories:
I have the same question (0)
  • Verified answer
    BCBuizer Profile Picture
    22,636 Super User 2026 Season 1 on at

    Hi @Volt26,

     

    When a user uses a PowerApp, they use their own connections, with all the (lack of) permissions that come with it. This is exactly what your are experiencing. The same will happen if your use a power automate flow that is triggered from PowerApps. 

     

    The workaround you described is indeed the one to use, but delays are to be expected.

  • Verified answer
    developerAJ Profile Picture
    4,763 on at

    Hi @Volt26 

     

    as BCBuizer said it uses user connection so it should not even work for you as you do not have permission to from Mailbox. Please check again probably you have permission for it.

     

    Workaround is the way you suggested other work around using Powerapp triggered flow and child flow together. Child flow will have an option to use run by connection

    developerAJ_2-1684594692148.png

     

    Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

     

     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 493 Most Valuable Professional

#2
11manish Profile Picture

11manish 479

#3
Haque Profile Picture

Haque 328

Last 30 days Overall leaderboard