cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ChrisGarty
Employee
Employee

Transition to List Flows as Admin V2 action from deprecated List Flows as Admin action on the Power Automate Management connector, along with associated APIs

Hi community! 

 

What's changing?

The List flows as Admin action on the Power Automate Management connector has been deprecated in favor of the List Flows as Admin (V2) action. The List Flows as Admin (V2) action can list all flows in an environment. The V2 action and its backing API has higher performance, since it returns only the identifying information about the flow. To accomplish this performance increase, the flow definition and some other metadata isn't returned. If the flow definition or additional metadata is needed, then a subsequent call can be made to the Get Flow as Admin action.

The Get-AdminFlow PowerShell cmdlet is also being updated to call the V2 List Flows API instead of the V1 List Flows API. This change will remove support for the CreatedBy filter.

The underlying V1 List Flows API is also being deprecated. The Center of Excellence (CoE) Starter Kit was updated to call the V2 List Flows API instead of the V1 List Flows API and that change was in the May 2023 release.

 

Why is this change happening?

The V2 API has higher performance, since it returns only the identifying information about the flow. The transition away from the V1 API is being made to minimize future disruptions to customer services.

 

How do I adjust to the change?

If you don't use the Center of Excellence (CoE) Starter Kit, the List flows as Admin action on the Power Automate Management connector, or the Get-AdminFlow PowerShell cmdlet, then you won't need to make any changes.

Connector actions: To take advantage of the increased performance of the V2 action and move off the V1 action, simply transition to using the List Flows as Admin (V2) action instead.

PowerShell: The Get-AdminFlow PowerShell cmdlet has been updated in version 2.0.165. You can update your copy of the Power Platform PowerShell cmdlets using Update-Module -Name "Microsoft.PowerApps.Administration.PowerShell". You can check your version using Get-Module -Name "Microsoft.PowerApps.Administration.PowerShell".

CoE Starter Kit: Update to the latest release of the CoE Starter Kit.

 

How do I find connector actions?

If you aren’t sure which flows might be calling the List flows as Admin action, then you can create a flow to list those flows. The List flows as Admin action has an operation ID of “ListFlowsInEnvironment”, so call the List Flows as Admin (V2) action, iterate over those flows calling the Get Flows as Admin action for each, parse JSON on the “actions” result, and then look for a “swaggerOperationId” of “ListFlowsInEnvironment”.

 

What's the timeline?

Connector design-time: Enforcement of the connector action deprecation at design-time is currently happening, so new flows will need to use the List Flows as Admin (V2) action. The design-time change finished rolling out to production environments 6/15.

Runtime: In August, we'll evaluate migration progress and start enforcing the deprecation at runtime, so that calls to the backing API may begin to fail at runtime. In time this will affect the old PowerShell cmdlet versions, old CoE Starter Kit versions, and calls to the deprecated List flows as Admin action.

 

What if I miss something?

We'll be watching usage levels of the deprecated List flows as Admin action, and its backing API, and we will reach out to customers that continue to have significant usage by the end of July.

 

Where can I read more?

You can read the latest guidance in the Administer environments and Power Automate resources documentation.

 

Who can I contact for more information?

Please ask any questions that you may have here and we'll get you answers. Thanks!

 

*** Update October 19, 2023 *** 

Thanks to community feedback, List Flows as Admin V2 + Get Flow as Admin APIs should now be functionally equivalent to List Flows as Admin V1 API.

List Flows as Admin V2 API is now:

- Working correctly in GCC

- Returning createdBy, createdTime, and lastModifiedTime

Get Flow as Admin API is now:

- Returning flow definition

Module Microsoft.PowerApps.Administration.PowerShell updated

 

We are going to start failing a small number of calls to the V1 List Flows as Admin API to encourage migration to the V2 API, the V2 action, and the latest PowerShell cmdlets module. For now, the failures will randomly occur on less than 1% of calls to the V1 API. 

This is the error that would be returned to calls to the API directly or via the connector:
The List Flows as Admin API is no longer supported. Please use the List Flows as Admin (V2) action
And this is the error message that will be returned from the PowerShell cmdlet:
The List Flows as Admin API used by this PowerShell cmdlet version is no longer supported. Please update to the latest PowerShell cmdlet using Update-Module

This change will roll out as RP/2310.3: Preview ~Oct 17, Canada ~Oct 24, Early regions ~Oct 25, Asia ~Oct 27, Europe ~Oct 31, North America ~Nov 2, GCC ~Nov 6.

If you encounter these error messages, then please take the remediation actions described.

 

*** Update February 1, 2024 *** 

The transition to the V2 API is progressing well and we continue to advance the process of randomly failing calls to the V1 List Flows as Admin API as a reminder to move to the V2 API. 

An update to fail 20% of calls is releasing now as RP/2401.4: Preview ~Jan 23, Canada ~Jan 30, Early regions ~Jan 31, Asia ~Feb 2, Europe ~Feb 6, North America ~Feb 8, GCC ~Feb 12.

An update to fail 40% of calls will release out as RP/2402.1: Preview ~Feb 6, Canada ~Feb 13, Early regions ~Feb 14, Asia ~Feb 16, Europe ~Feb 20, North America ~Feb 22, GCC ~Feb 26.

Updates to move the failure rates up are planned for the near future:

- 60%: Canada ~Feb 27, North America ~March 7

- 80%: Canada ~March 12, North America ~March 21

- 100%: Canada ~March 26, North America ~April 4

These dates are subject to change, but can be used as a guide. If you encounter the error messages detailed above, then please take the remediation actions described.

 

*** Update April 22, 2024 ***

Calls to the List flows as Admin API are now fully deprecated via the Power Automate Management connector or PowerShell. There is some direct use of the API from other clients, so we will begin failing those calls as well to complete full deprecation of the API by July 15th.

67 REPLIES 67

Got it. Thanks.

@ChrisGarty  Thank you for the clarification.

Nazul
Advocate I
Advocate I

@ChrisGarty good and bad news.

 

Good news, looks like Get-AdminFlow is returning values for CreatedBy property.

 

Bad news, it does not return correct data for all flows. Example.

Nazul_0-1692207241499.png

What's even weirder is that it is not the case for all flows, just some.

Nazul_1-1692207365268.png

 

Can you help us here? Or should I try via Microsoft Support?

max81
Impactful Individual
Impactful Individual

@ChrisGarty Help!

My first flows are failing and the new action is not ready yet! 

max81_0-1692258003799.png

 

max81
Impactful Individual
Impactful Individual

UPDATE: All my flows using that action are failing now. So our governance processes doesn't work anymore. 😞
Ticket was created yesterday, waiting for feedback.

I was - unluckily - able to reproduce missing creaqter information for some flows, mentioned by @Nazul 

KollyJ
Frequent Visitor

Hi! We have same issue here... We use a template flow to send us mail with new Flow and Connector. but this tempalte flow doesn't work anymore with the V2 API.

And same behavior for our Flows Inventory. We need the CreatedBy and CreatedTime back in the V2 API for PowerShell... 

I already create a support ticket. but nothing new until today.

 

 

KollyJ
Frequent Visitor

Good News, I installed the latest version of the module Microsoft.PowerApps.Administration.PowerShell (2.0.173) published 6 days ago. And now I have back the CreatedBy and CreatedTime attributes.


KollyJ_0-1692629954011.png

 

I will check if the List Admin Flows V2 (Power Automate flow) still have issue or not.

max81
Impactful Individual
Impactful Individual

@KollyJ : Please insure that you get the created information back for all flows!

In my case: only for a small percentage of our flows that information was missing

KollyJ
Frequent Visitor

Yes information ok for all my flows (~900).

with the PowerShell module version 2.0.112 only a fews flows bring up without this information. but now with the version 2.0.173 all my flow (in PowerShell) come with good attributes.

@KollyJ , great to hear that! 

@max81 , thanks for your feedback and patience on this issue! 

ChrisGarty
Employee
Employee

Problem: The CreatedBy data is not appearing for customers on sovereign clouds like GCC. This is due to problems in those sovereign regions with the mechanism we use to store that the flow detail data from the List call. 

Status: In the next couple of days, we are expecting information from a partner team that affects our plan to remedy this for sovereign clouds and the timeline, so we haven't sent out a message center follow-up to MC624197 yet. We plan to send a follow-up communication shortly.

Thanks!

max81
Impactful Individual
Impactful Individual

@ChrisGarty : I'm using the flows in europe. So no sovereign cloud like GCC and I still miss for some flows the creator information.

max81
Impactful Individual
Impactful Individual

[UPDATE] My case is still open because I'm still missing some creator information. 😞

max81
Impactful Individual
Impactful Individual

[UPDATE] Info from Microsoft: Issue found and should be fixed with the next rollout. latest on 9/25. 

 

ziv_dh
Regular Visitor

@ChrisGarty, following our migration to the new v2 connector, we've run into an issue related to fetching flow definitions using the "get flow as admin" action.

Regrettably, the flow definition isn't consistently included in the response as per the guidance that suggests making a subsequent call to retrieve it.
What approaches or techniques should we employ to guarantee that we can consistently obtain the flow definition for all of our flows?

DeeTronSEAM
Kudo Collector
Kudo Collector

We've been using the "List flows as Admin (V2)" action in a flow created back in Jan. 2022.  But starting on Oct 7, the output of that flow action changed so that some of the flow entries in the AdminFlowWithoutDefinition array are missing properties/attributes (in their AdminFlowWithoutDefinitionProperties attribute).

E.g.: state, createdTime, lastModifiedTime

 

Note that:

  1. both the attributes and the value are missing. It isn't just the value is null or blank/empty
  2. only some of the flows' entries are afflicted with this problem. Most are fine.
  3. we are not in a GCC tenancy, just plain-old boring USA business customer

Also, it appears that the problem is expanding as the number of flows missing this information has expanded each day the admin flow has run. As of today about 30% are missing the state, createdTime, and lastModifiedTime...up from 15% two days ago.  All flows that were missing the attributes on the 6th are included in the larger group that has missing attributes in today's run....so it might be an expanding problem, but could be random.  For now I'm not going to compare all five past runs to determine that because....

 

We've opened up a support ticket with Microsoft.  Since this seems to have happened before and was identified as a bug, our hope is MSFT will confirm and release a new fix for the latest apparition.

 

But in the meantime, posting here in case others are seeing the same problem...again.

 

++++

References: 

https://learn.microsoft.com/en-us/connectors/flowmanagement/#list-flows-as-admin-(v2)

 

https://learn.microsoft.com/en-us/connectors/flowmanagement/#resourcearray[adminflowwithoutdefinitio...

 

ChrisGarty
Employee
Employee

@ziv_dh , we had some discussions with partners and customers recently who highlighted that the List Flows as Admin V1 API was returning flow definitions. We were intentionally not returning flow definitions from the Get Flow as Admin API in the past, but we have a change rolling out now that will update the Get Flow as Admin API to include flow definitions, so that the combination of List Flows as Admin V2 + Get Flow as Admin is functionally equivalent to List Flows as Admin V1. With this change, an admin user doesn't have to add themselves as an owner on a flow so they can call the Get Flow API to get the definition, since instead they can simply call Get Flow as Admin to get the definition.

 

This change will roll out as RP/2310.3: Preview ~Oct 17, Canada ~Oct 24, Early regions ~Oct 25, Asia ~Oct 27, Europe ~Oct 31, North America ~Nov 2, GCC ~Nov 6.

ChrisGarty
Employee
Employee

We are going to start failing a small number of calls to the V1 List Flows as Admin API to encourage migration to the V2 API, the V2 action, and the latest PowerShell cmdlets module. For now, the failures will randomly occur on less than 1% of calls to the V1 API. 

This is the error that would be returned to calls to the API directly or via the connector:
The List Flows as Admin API is no longer supported. Please use the List Flows as Admin (V2) action
And this is the error message that will be returned from the PowerShell cmdlet:
The List Flows as Admin API used by this PowerShell cmdlet version is no longer supported. Please update to the latest PowerShell cmdlet using Update-Module

 

This change will roll out as RP/2310.3: Preview ~Oct 17, Canada ~Oct 24, Early regions ~Oct 25, Asia ~Oct 27, Europe ~Oct 31, North America ~Nov 2, GCC ~Nov 6.

 

If you encounter these error messages then please take the remediation actions described. If you do not have migration in place then a second call to the List Flows as Admin V1 API will likely succeed since only a small percentage of calls are failing as a warning.

max81
Impactful Individual
Impactful Individual

[Update] Today, I finally get all creator information back. So I can close my service ticket and start migrating to the new List Flows as Admin (V2) action.

 

My request to Microsoft for the next time:

• please make sure that new actions don't have any missing information

• a longer transition period is needed for such changes

• information transfer was really poor. The delayed message center news was bad. And questions in this thread were not answered quickly either

@ChrisGarty thank you, this is great news. Can you please share the timeline for the new changes to take place? Is it in October or November? Also can you please don't deprecate the old functionality until the new one is generally available? 

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Top Kudoed Authors
Users online (3,492)