'List My Environments' Gives "Authentication failed" Error Message

[eliotcole]

Pretty simple, I create a button flow, with a single action, the Power Automate Management 'List My Environments' action.

I provide the login, and I test it.

Failure.

Authentication failed.

Body JSON of response:

{
  "error": {
    "code": "AuthenticationFailed",
    "message": "Authentication failed. "
  }
}

Header JSON of response:

{
  "Pragma": "no-cache",
  "x-ms-request-id": "SERVER:aaaaaaaa-aaaaaa-aaaa-aaaa-aaaaaaaaaaaa",
  "x-ms-correlation-request-id": "bbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbbbbb",
  "x-ms-flow-mobile-ios-version": "1.3.0",
  "x-ms-flow-routing-request-id": "SERVER:ccccccccccccccc:cccccccc-cccc-cccc-cccc-cccccccccccc",
  "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
  "X-Content-Type-Options": "nosniff",
  "Timing-Allow-Origin": "*",
  "x-ms-apihub-cached-response": "false",
  "Cache-Control": "no-cache",
  "Date": "Fri, 17 Jul 2020 18:09:52 GMT",
  "WWW-Authenticate": "Bearer authorization_uri=\"https://login.windows.net/\", error=\"invalid_token\", error_description=\"Could not find identity for access token.\"",
  "Content-Length": "102",
  "Content-Type": "application/json",
  "Expires": "-1"
}

It took my login from power automate, I have a full, paid for environment, with CDS, and all the trimmings.

What's the reason for this?

Also, purely asking out of curiousity ... why are these actions not marked as Premium, because it would appear that they're unusable for standard users (unless someone can tell me how to use the more useful ones on a default environment).

If you can help I'll be your best friend ever ever 😜

----------

imagery, if needed:

[abm]

Hi @eliotcole 

Sometimes these errors are temporary and it should resolve within few minutes. I have tried this and it is working as expected.

Try the following options:

1. Try using a different browser

2. Try Private window

3. Try to create another flow

4. Try to create another new connection

If none of the above works please raise a ticket with Microsoft support.

Yes this is not a premium feature. The action itself is called List My environments. This action returns only the environments where users have permission.

Thanks

[eliotcole]

Still the same issue.

Reminder, I am the global admin, and have also tried this with the specific role for this account made to Power Platform Admin (or whatever it is). The Authentication Type is "First party" because it says that "Third party" is depreciated. This is running in Microsoft's Edge DEV browser, but that shouldn't make a blind bit of difference for a web based app and how that app is communicating with its own service.

Trying It Later

I've given it a week since your response, I attempted this with a brand new flow, which gave the following in the headers of the error run:

{
  "Pragma": "no-cache",
  "x-ms-request-id": "[obfuscated]",
  "x-ms-correlation-request-id": "[obfuscated]",
  "x-ms-flow-mobile-ios-version": "1.3.0",
  "x-ms-flow-routing-request-id": "[obfuscated]",
  "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
  "X-Content-Type-Options": "nosniff",
  "Timing-Allow-Origin": "*",
  "x-ms-apihub-cached-response": "false",
  "Cache-Control": "no-cache",
  "Date": "Mon, 27 Jul 2020 15:34:40 GMT",
  "WWW-Authenticate": "Bearer authorization_uri=\"https://login.windows.net/\", error=\"invalid_token\", error_description=\"Could not find identity for access token.\"",
  "Content-Length": "102",
  "Content-Type": "application/json",
  "Expires": "-1"
}

Then I tried my original one, which gave these header errors:

{
  "Pragma": "no-cache",
  "x-ms-request-id": "[obfuscate]",
  "x-ms-correlation-request-id": "[obfuscate]",
  "x-ms-flow-mobile-ios-version": "1.3.0",
  "x-ms-flow-routing-request-id": "[obfuscate]",
  "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
  "X-Content-Type-Options": "nosniff",
  "Timing-Allow-Origin": "*",
  "x-ms-apihub-cached-response": "false",
  "Cache-Control": "no-cache",
  "Date": "Mon, 27 Jul 2020 15:34:57 GMT",
  "WWW-Authenticate": "Bearer authorization_uri=\"https://login.windows.net/\", error=\"invalid_token\", error_description=\"Could not find identity for access token.\"",
  "Content-Length": "102",
  "Content-Type": "application/json",
  "Expires": "-1"
}

Both of those runs had this in the body:

{
  "error": {
    "code": "AuthenticationFailed",
    "message": "Authentication failed. "
  }
}

Trying Another Account

When I try this with another account, not connected to this company, in another browser, on a US instance, I only get:

{
  "error": {
    "code": "AuthenticationFailed",
    "message": "Authentication failed. "
  }
}

No header response.

Trying a Final Account

This time I tried a normal hotmail flow account and since it isn't attached to a tenant, it doesn't have access to the functionality. So it was a non-starter.

Conclusion

It doesn't work.

---

@abm wrote:

Hi @eliotcole 

Sometimes these errors are temporary and it should resolve within few minutes. I have tried this and it is working as expected.

Try the following options:

1. Try using a different browser

2. Try Private window

3. Try to create another flow

4. Try to create another new connection

If none of the above works please raise a ticket with Microsoft support.

Yes this is not a premium feature. The action itself is called List My environments. This action returns only the environments where users have permission.

Thanks

---

[abm]

Hi @eliotcole 

Thanks for your response. Looks like you need to raise this with Microsoft Power Automate Support.

Thanks

[eliotcole]

I will persevere here, thanks.

If I do find a solution (here or anywhere else), I will post it in this thread as the solution. This is not resolved. Do not set this topic to solved.

[WimKrings]

@eliotcole Did you find a solution for this issue? I'm also trying to use the Power Automate Management actions and get the same authorisation failure...

[eliotcole]

Hi, @WimKrings , no, not as yet. But I've not tried since, I don't think.

@WimKrings wrote:

@eliotcole Did you find a solution for this issue? I'm also trying to use the Power Automate Management actions and get the same authorisation failure...

---

I might come back to this soon, though, as I'm getting in deeper with stuff.

I think a key part of this is the usability on a 'default' environment, because it flat out refuses there, if I remember correctly from nearly a year ago. 😅

[WimKrings]

@eliotcole hmm  I'm not sure what you mean by 'usability on a 'default' environment'. I tried this with 2 different users, both sysadmin, on non-default environments.  Allways same authentication error. Also spoke about a half year ago to someone who tried this with a global admin account. She got the same error.

This could provide very powerfull functionallity.... but first someone has to get them to work 🙂

[eliotcole]

Hiya, @WimKrings  , sorry, sometimes I use the wrong terminology, it is a curse!

So, what I mean is that if I am a free user, with a free account, I only get one environment I can use, which is classified as 'default' ... I can't create more (as far as I know). Because if you are set at 'default', this functionality essentially sees that you don't have an environment at all, and errors based upon that.

I think that's the correct read on this, but I don't mind being put right.

[WimKrings]

Ok @eliotcole that sounds plausible but still doesn't explain the errors I'm getting on a none default environment. Or do I miss something?

[eliotcole]

No, you're right, it doesn't, 🙂

I wasn't actually mentioning it because of your errors, more because I wanted it to be clear that non-enterprise/paid users will not even be able to *get* the errors that you're getting. 😅