Lists and Automate

%3CLINGO-SUB%20id%3D%22lingo-sub-2684816%22%20slang%3D%22en-US%22%3ELists%20and%20Automate%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2684816%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20recently%20able%20to%20share%20the%20new%20list%20experience%20with%20a%20few%20users%20in%20our%20organization%20who%20upon%20seeing%2C%20%3CSTRONG%3Eknew%3C%2FSTRONG%3E%20it%20would%20change%20the%20way%20they%20work%20forever%20more.%26nbsp%3B%20It%20is%20why%20I%20love%20championing%20good%20products.%20People%20see%20something%20and%20light%20up!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20team%20is%20going%20to%20build%20a%20few%20lists%20for%20work%20they%20share%20across%20their%20team%20and%20immediately%20latched%20on%20to%20the%20Power%20Automate%20functions%20they%20saw.%20%3CSTRONG%3EWIN!!!%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20else%20seeing%20widespread%20adoption%20of%20lists%20and%20automate%3F%26nbsp%3B%20Is%20it%20going%20well%20or%20are%20they%20running%20into%20issues%20in%20automate%3F%20How%20are%20you%20managing%20the%20adoption%3F%20Have%20they%20broke%20anything%20you%20regret%20letting%20them%20access%3F%20Any%20advice%20is%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2684816%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Adoption%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2687710%22%20slang%3D%22en-US%22%3ERe%3A%20Lists%20and%20Automate%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2687710%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F428181%22%20target%3D%22_blank%22%3E%40Tabitha%3C%2FA%3E%26nbsp%3BOne%20thing%20I%20have%20found%20that%20when%20end%20users%20start%20to%20adopt%20M365%20technology%2C%20you%20will%20have%20to%20become%20an%20expert%20quickly.%20They%26nbsp%3B%3CSTRONG%3Ewill%3C%2FSTRONG%3E%20ask%20you%20questions%20and%20you%20need%20to%20know%20the%20answer.%20Adoption%20of%20lists%20and%20automate%20has%20been%20a%20good%20sign%20at%20my%20previous%20employer.%20Once%20they%20realized%20that%20they%20could%20automate%20workflows%2C%20it%20gave%20end%20users%20inspiration%20on%20what%20they%20could%20do.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20get%20governance%20wrapped%20around%20everything%20quickly.%20It%20will%20be%20hard%20to%20control%20the%20sprawl%20if%20you%20don't%20do%20that%20step%20very%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2687999%22%20slang%3D%22en-US%22%3ERe%3A%20Lists%20and%20Automate%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2687999%22%20slang%3D%22en-US%22%3E%3CUL%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F428181%22%20target%3D%22_blank%22%3E%40Tabitha%3C%2FA%3E%26nbsp%3BPower%20Automate%20has%20a%20few%20major%20risks...%3C%2FLI%3E%3C%2FUL%3E%3COL%3E%3CLI%3EA%20user%20is%20limited%20to%202%2C000%20API%20calls%20per%2024%20hour%20period.%20Simplistically%20an%20API%20call%20is%20any%20step%20the%20flow%20performs%20(although%20a%20step%20may%20perform%20more%20than%20one%20API%20call)%2C%20so%20if%20a%20user%20has%205%20flows%2C%20and%20each%20does%2020%20steps%20per%20flow%20run%2C%20and%20you%20run%20them%20more%20than%2010%20times%20a%20day%2C%20then%20%3CEM%3Eall%3C%2FEM%3E%20the%20flows%20for%20that%20user%20%3CSTRONG%3Ejust%20stop%3C%2FSTRONG%3E...%20so%20you%20have%20to%20ensure%20that%20no%20users%20exceed%20these%20limits%20or%20you%20will%20need%20to%20buy%20additional%20licensing%20or%20recreate%20the%20flows%20using%20service%20accounts.%3C%2FLI%3E%3CLI%3EFlows%20stop%20when%20the%20user%20who%20created%20the%20flow%20leaves%20the%20organization...%20again%20you%20can%20mitigate%20this%20with%20the%20use%20of%20service%20accounts%3C%2FLI%3E%3CLI%3EPower%20Automate%20is%20meant%20for%20%3CEM%3Epersonal%3C%2FEM%3E%20productivity.%20It%20can%20be%20used%20for%20team%2C%20or%20even%20enterprise%20apps%2C%20but%20you%20have%20to%20make%20sure%20you%20have%20governance%20in%20place.%20Installing%20the%26nbsp%3B%3CA%20title%3D%22Microsoft%20Power%20Platform%20Center%20of%20Excellence%20Kit%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-platform%2Fguidance%2Fcoe%2Fstarter-kit%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Power%20Platform%20Center%20of%20Excellence%20Kit%3C%2FA%3E%26nbsp%3Bis%20a%20good%20place%20to%20start.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I was recently able to share the new list experience with a few users in our organization who upon seeing, knew it would change the way they work forever more.  It is why I love championing good products. People see something and light up!

 

This team is going to build a few lists for work they share across their team and immediately latched on to the Power Automate functions they saw. WIN!!!

 

Is anyone else seeing widespread adoption of lists and automate?  Is it going well or are they running into issues in automate? How are you managing the adoption? Have they broke anything you regret letting them access? Any advice is appreciated.

2 Replies

@Tabitha One thing I have found that when end users start to adopt M365 technology, you will have to become an expert quickly. They will ask you questions and you need to know the answer. Adoption of lists and automate has been a good sign at my previous employer. Once they realized that they could automate workflows, it gave end users inspiration on what they could do.

 

Just get governance wrapped around everything quickly. It will be hard to control the sprawl if you don't do that step very soon.

  • @Tabitha Power Automate has a few major risks...
  1. A user is limited to 2,000 API calls per 24 hour period. Simplistically an API call is any step the flow performs (although a step may perform more than one API call), so if a user has 5 flows, and each does 20 steps per flow run, and you run them more than 10 times a day, then all the flows for that user just stop... so you have to ensure that no users exceed these limits or you will need to buy additional licensing or recreate the flows using service accounts.
  2. Flows stop when the user who created the flow leaves the organization... again you can mitigate this with the use of service accounts
  3. Power Automate is meant for personal productivity. It can be used for team, or even enterprise apps, but you have to make sure you have governance in place. Installing the Microsoft Power Platform Center of Excellence Kit is a good place to start.