You’re offline. This is a read only version of the page.
Hi,
I have quite a strange scenario: I need to move a solution from one environment to another (not in the same tenant!) as managed. All good, no issues exporting and importing the solution. The problem is that the user importing the solution in the new environment doesn't have (and will not receive!) an Outlook licence, so they want another user to send the emails. It needs to be only for sending emails as all the other actions are being done by the importing user. Obviously, because they are different tenants they don't have the same user base, so can't setup this in the source environment. How can we change the connection reference only for Outlook before/during/after importing the managed solution, is there a way, please?
TIA
Yeah I get the scenario, but you don't give the person the license, so why do any of them need to be that person. It's not common at all to have multiple accounts, tied to a single flow. It's a bad architecture.
1. Open the solution up
2. Open the Flow
3. Change the Flow, which of course has to be done by the person who's email is going to be used because the installer doesn't have privileges to add a connection
**You could have the Email person create a Connection (assuming THEY have a license to create them), then use that, but if the connection goes bad... and it will...the original person has to fix it.
So yeah its not a good way to do it at all and is going to cause you lots of headaches.
4. It will create another layer on top of that managed
Done
If the installer had a license, you could
1. Create an environment Variable to store the From email address for the Action
2. Set it to whomever
3. Give the Installer Send as Privs for that Email address
done
But since you cannot give them a license, then use a service account, or do what I said.
You don't have real options here because of the limitation you guys have.
If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others
Cheers
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey
Hi Mike,
Thanks for the quick reply.
All users are normal users. Also, the suggestion would not work because, as mentioned, all actions except the Outlook one need to be under the importing user.
I'll try to paint a picture using fictional names:
So User A creates the solution in Tenant A. User A has an user, User X, in Tenant B, that will be used to import the solution. User X does not have an Outlook licence, but User Y, in Tenant B, has. User Y doesn't have any other privileges and should not be used to run any actions in the flows in the solution except the Outlook one. Tenant A and Tenant B are in totally separate locations and business, so they do not have the same user base (so it cannot be implemented in Tenant A using User Y because it doesn't exist).
Hope it makes more sense now.
Does the person that it will go out as, can it be a Shared Account, like a Service account. That way, the installer, could open a Browser instance as that user, who does have a license, and setup the connection/refs that way.
Then the installer won't need a license.
If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others
Cheers
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey
#1
Michael E. Gernaey
6
Super User 2025 Season 1
#2
KT-07051015-0
4
#3
GI-06050833-0
2
Share
Report
All responses (
Answers (