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

Community site session details

Session Id : ayPRofamJq2vbE7fpsSfvJ
Power Automate - Using Connectors
Unanswered

Connecting Flow To Multiple Tenants

Like (0) ShareShare
ReportReport
Posted on 24 Sep 2019 11:06:17 by 2

I have two Azure subscriptions, which have unique tenant IDs. One is my company's "production" environment and the other is one each of our developers received with a monthly credit from our Visual Studio MPN, I'll call that one "dev". For O365 we only have one tenant.

 

I have created an Azure Automation Runbook in dev and added to a flow that is triggered by a Sharepoint list item creation event. It works great and I was able to test the code several times without messing with our production Azure environment. Once I got the sign-off to migrate to the production side, I can't seem to access the production tenant. It doesn't appear in the drop down, I've tried submitting the subscription ID as it states in the dialog box as well the tenant ID. Neither of those worked and I reveice the below message

Could not retrieve values. The access token is from the wrong issuer 'https://sts.windows.net/58e6813e-XXXX-XXXX-XXXX-3aXXXXXXX58b/'. It must match the tenant 'https://sts.windows.net/1617d2f6-XXXX-XXXX-XXXX-44XXXXXX46a4/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/1617d2f6-XXXX-XXXX-XXXX-44XXXXXX46a4' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later.

 

Is there something that I"m missing to register the production tenant and how is it that the dev one seems to be the default without me doing anything?

I have the same question (0)
  • v-litu-msft Profile Picture
    on 25 Sep 2019 at 06:11:24
    Re: Connecting Flow To Multiple Tenants

    Hi @jmathews,

     

    Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later.

    Is it the first time to sign-in the production environment? If not, it could be caused by you just transferred your subscription.

    Now, have you still have the issue?

    Best Regards,
    Community Support Team _ Lin Tu
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • jmathews Profile Picture
    2 on 25 Sep 2019 at 10:38:22
    Re: Connecting Flow To Multiple Tenants

    We only have one O365 subscription which we've been using for years. The production Azure tenant has also been around for some time. It appears that somehow Flow got paired to the development tenant in Azure and won't see the production one.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 788 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 452 Moderator

#3
developerAJ Profile Picture

developerAJ 302

Last 30 days Overall leaderboard

Featured topics