cloud flows

(3) Share

Report

Posted on by PP-25030432-0

Issue Description

In D365 Cloud Flows, under the Connections section, some flows show the connection reference name, logical name, connector type, and the account used to connect. However, for some other flows, the connected account is not shown.

Example 1: Working

- Cloud Flow Name: Account - Get Account details

- Connection Reference: Dataverse

- Connection Reference Logical Name: Dataverse_133455

- Connector Type: Microsoft Dataverse

- Account:** dddd@domain.com

Example 2: Partial / Issue

- Cloud Flow Name: Account - Get Account details1

- Connection Reference: Dataverse

- Connection Reference Logical Name: Dataverse_133422

- Connector Type: Microsoft Dataverse

- Account: dddd2@domain.com

Problem

The cloud flow is running successfully, but in the **Details** tab under the **Connections** section:

- it is marked in **red**

- the **account ID / connected account** is not shown

Questions

Q1) Is it possible to decrypt or extract the account used for the connection reference?

If we know the account, we can create a new connection using the same account.

Q2) What are the alternative solutions to identify or recover the connected account details for that connection reference?

Request

Please advise whether this is expected behaviour, a product limitation, or an issue that can be fixed. Also, please share the recommended approach to identify the account linked to the connection reference when it is not displayed in the flow details.

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
Since the connected account cannot be recovered from an encrypted connection, the recommended practice is:

Verify the Connection Reference points to a valid connection.

Use a dedicated service account for production connections rather than personal accounts.

Rebind the Connection Reference to a new connection if the account information is missing or the status is red.

If the flow continues to run but the UI remains inconsistent after rebinding and publishing, this may indicate a product issue. In that case, capture the Flow ID, Connection Reference ID, Environment ID, and screenshots, and raise a Microsoft Support ticket for further investigation.

For production environments, using service accounts and connection references managed through solutions and ALM pipelines helps avoid these issues and makes connection ownership easier to manage and recover.

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @PP-25030432-0,

A good number suggesgtions have already been provided, I am just pointing to the good practices in your case.

Use a connection reference in a solution with Microsoft Dataverse

Connecting and authenticating to data sources

Power Automate Standards: Connection References

Basically, the missing connected account in the flow details is expected behaviour when connections are broke, expired or premissions are limited - its a platform limitations desinged for security and management reason.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @PP-25030432-0,

To answer your specific questions:

Q1 - Can you decrypt or extract the account? No, you can't decrypt the connection credentials. But you CAN identify which account owns the connection using the Power Platform Admin API. A Power Platform admin can call:

GET https://api.powerapps.com/providers/Microsoft.PowerApps/environments/{env}/connections/{connectionId}?api-version=2016-11-01
The response includes the createdBy field which shows the account that created the connection. The connectionId is visible in PPAC > Data > Connections when you open the connection.

Q2 - Alternative to identify the account:

1. PPAC > your environment > Data > Connections. Find connections of type Microsoft Dataverse, check the Created By column. Match the logical name from your flow to the connection.

2. If the connection owner has left the tenant or the account is deleted, that's the most likely reason the account doesn't show and it shows red. The connection still works because the token is cached, but eventually it will break.

The red status showing while the flow still runs is confirmed expected behavior when the connection owner account is no longer resolvable in the directory (deleted user, guest account removed, etc.). Microsoft docs confirm: connections tied to deleted accounts show as broken in the UI but may continue to run until the token expires.

Fix: rebind the connection reference to a new connection using a service account. Don't wait for it to fail in production.

Best regards,

Valantis ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/ 💼 LinkedIn ▶️ YouTube

Was this reply helpful? Yes No