No dynamic content available/unable to connect to SharePoint through new or existing flows in environment

[TrayH]

I have a couple of environments setup for Power Automate, one of which is named Prod. For the past several months on a daily basis I've been working on several flows in this environment with no issues. Today I went to edit one of them, and on the flyout for dynamic content it doesn't show anything but a message which reads "No dynamic content available."

I found the same issue with all other flows in the environment. I tried creating a new flow as a test, selecting a trigger for SharePoint - When an item is created or modified." None of my SharePoint sites are displayed in the dropdown list - 

If I switch over to the default environment, I'm able to pull up dynamic content just fine. If I create a new flow, it is able to connect to my available SharePoint sites.

All of this is being done under the same account, so I'm at a loss as to why everything in this environment is suddenly unable to connect back to my SharePoint data.

Edit: Confirmed now it is happening in multiple environments.

[zmorek]

Just ran into this now myself, I think there might be something going on

[TrayH]

Interesting. I just tried another of my environments and ran into the same thing.

[TrayH]

I was able to work around it by going to add connection on my trigger, and adding the same credentials I'm already logged in with. After that it is able to connect to the data.

Edit - Never mind. When I went to save the changes I got an error, so I guess this didn't fix anything.

[dbeckemeyer]

I attempted this solution and it does not appear to help in my case. Dynamic Content is not showing up and the fields filled in with content already show as "Body/" as shown below:

Very odd issue

[TrayH]

It didn't really fix it for me either. It did allow me to at least connect to my SharePoint data through the trigger, but I got an error when I went to save the changes to the flow.

I did see there is an active issue in Service Health, which mentions external users being unable to access SharePoint data. I wonder if this connection back from Power Automate is considered external, and impacted by that issue.

[dbeckemeyer]

I went ahead and submitted a Service Health report to Microsoft for this issue. Hopefully they get to it soon!

[TrayH]

Good idea, I just did the same.

[TrayH]

When I try to perform a test one of my flows in the impacted environments, I noticed they are failing with this error. Anyone else getting the same?

[hgartner]

I too have the same problem since last week. I'm creating a recurring flow and getting items, but the power automate reports that it has no dynamic content. This way, I can't create the filters to get only the items I want. I hope microsoft fixes the problem.