Guest Tenancy Account and Model Driven App Workflow Email Action

[ZiaUddin]

Hi,

Our PowerApps Model Driven Application exists in our tenancy (let's call this A), but we have a parent company where our users are being migrated to and this also has an azure tenancy of it's own (let's call this B). Recently Microsoft in May this year have enabled people from outside the tenancy who have office 365 / azure accounts in another tenancy to be added in as guest accounts. We have been adding our migrated users from Tenancy B into our PowerApps in Tenancy A. They are able to access without issues from Tenancy B.

However, one issue we have discovered is that in the PowerApps native workflow engine if we add an email action then no email is sent. Further testing has indicated that this applies to only those users from Tenancy B, because they have email addresses that from their B domain and therefore need authorization within the PowerApps Dynamics email approval action from the exchange server owned by Tenancy B. Is there anyway we can get around this issue so that emails do work for these workflows for users in Tenancy B ? At the moment the only way we can get the email action to work is if we publish the workflow as an admin with account in Tenancy A where the PowerApps application exists. We really don't want to do a full solution and data migration of the PowerApp to Tenancy B right now.

Any help appreciated.

ZiaUddin

[HSheild]

Hi @ZiaUddin 

Have you tried sending the emails from a generic email account that exists in tenant A instead of sending emails from the user's account?  For example, you may have a user in tenant A with an email address of no-reply@[company_name].com

[ZiaUddin]

Hi HShield,

Yes we are using that as a work-around for now in our workflows; but wondering about issues when we come to use an email activity - the user's from the guest tenancy - they will have issues ?

Zia