Unanswered

How to access flow built in other environment or region

(0) Share

Report

Posted on by rameshmukka

1,115

I have built a flow for client whose Default Environment is from Europe Region. I am being from India, can access client's tenant SharePoint and Teams. But when I try to access flow.microsoft.com am redirected to india.flow.microsoft.com, But I would like to access client's Power Platform Environment which is emea.flow.microsoft.com. Now what permission should my guest account to be given to access flows in my client's environment? Or if it doesnt work that way, what license my client should possess to create a envrionment for Asia and add my guest account in that environment?

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (0)

eliotcole 4,363 Moderator on at

Like (0)

Report

I think there are some issues in general, @RameshMukka , with access to environments and access.
Power Automate running slow - Power Platform Community (microsoft.com)

Once those are sorted out, though, have you thought about creating a "worker" account on the tenant's 365 instance (without any paid licences), so that you can at least log in there. You can then have that provided with the required permissions 'on site', to just allow you to at least get a quick work around to the issue you're seeing.

I know it's not perfect, but it'll at least give you something.

That said, from what I'm aware (and I could be wrong) the different flow subdomains shouldn't make too much issue to how you access any relevant environments to your connected tenancy(ies).

Hopefully this all made sense! 🙂

Was this reply helpful? Yes No
rameshmukka 1,115 on at

Like (0)

Report

@eliotcole I too noticed today that flows were not triggered at all for my client at Romania. I thank you for that information. But my question was altogether not related to it.

What I needs to do to access flows created in his emea environment? Where my guest account needs to be added? Do client has to create a new environment for me? What license should my client possess for that?

Thanks,
Ramesh

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

If you have noticed that error, would you be able to mention it in the thread, it'd help show that there's multiple users in multiple countries seeing it.

With regard to your issue, @RameshMukka , have you tried the work around to getting the 'worker' account on the tenant's 365 tenancy?

That has always been my go to move, mate.

Was this reply helpful? Yes No
rameshmukka 1,115 on at

Like (0)

Report

@eliotcole Can you tell me guests can also have worker accounts and create flows? Do you have any quick reference on how to do it?

Also there are no errors at all. I just noticed the flows were not triggered at all. They did trigger yesterday, but was very slow in triggering.

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

If you're at admin level you should have access to their 365 administration centre, once there you can create a user that does not have an office licence, and just provide it with any relevant user levels that you need.

If you are not comfortable doing this, then have a colleague perform the act for you.

Either way, once you have the new 'local' account you can simply open up flow in a private window on your browser, log in as the newly created user, and achieve what you need to achieve 'locally'.

As I say, it's not the perfect situation, but the bonus is that you then have a local worker account, whereby you can do some very cool stuff. I set up a lot of Power Automate alerting for system level alerts that simply weren't being reported a year ago. However their alerting systems have improved a little since then. 😉

Was this reply helpful? Yes No
rameshmukka 1,115 on at

Like (0)

Report

@eliotcole So you mean if I create a account that way and when I access flow.microsoft.com from India using that account, the flows created in EMEA envrionment would be shown to me?

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

OK, @RameshMukka , what I'm suggesting is purely to enable access to a customer's environment.

So, let's say that my company, Company A, has Company B as a tenancy, they are able to access their systems through the tenancy administration options (I don't know those links, sorry).

We could create any users required for Company B, and we should be able to use our Company A access to manage most aspects of their tenancy through the tenancy administration panels.

However, sometimes we need to perform or test 'local' actions, as a 'local' user. So what I have described to you, above, is you creating another version of yourself at Company B. It won't have a company email address (just something like rameshm@companyb.onmicrosoft.com ), but it will allow you to perform testing and trialling of stuff at Company B using any facilities that will work on a free licence (or paid if they're willing to pay for it!).

Flow has free access, so you can create the account on their tenancy, then log in to Microsoft Power Automate with it, too.

-----

Separately ... and I can't stress this enough ... completely separately. I'm saying this so that you aren't conflating what I'm about to say with what I said above ... 😉

When you sign up for Microsoft Power Automate, you must pick a location. This location is likely something to do with both local privacy / data protection laws, and probably also CDN style replication (or caching) of data for Microsoft's data ... which includes your flows or those of your client/tenant.

So this could mean that India and the US is currently browsing Flow just dandy. Where-as the UK and Australian could be having issues.

I'm not 100% sure on all of this, but (given the current issues) it seems about right.

Was this reply helpful? Yes No