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

Enabling Flow

Good Day

 

We are fairly new when it comes to Microsoft Flow and so far we activated the license to just a small number of users. We have Office 365 Licensing for Flow covering all associates. There are no Plan 1 or Plan 2 licenses so we are subject to the default environment and any DLP controls Global Administrators to the Tenant can apply.  Generally speaking if we were to activate the Microsoft licensing to anyone in the company what would be the main risks or concerns (we have training material covered already).  Thanks

2 ACCEPTED SOLUTIONS

Accepted Solutions
jake
Advocate II
Advocate II

A couple thoughts...

 

Support

Enabling licensing for all users will enable all users to create Flows. That's good. Eventually, some flows will grow and evolve to the point that they are shared, becoming mission-critical pieces of automation for the teams using them. What does the support structure look like if something goes wrong w/ one of those Flows? Does IT pick that up? Does it fall back on the Flow creator?

 

Architecture & Governance

When everyone in the company can create Flows, you'll have a wide assortment of individual skill-sets with the ability to design and build automation solutions. For personal productivity, that's a good thing. For bigger projects, how do you ensure that things are built in the right way? (ie. not constructed in a way that burns unnecessary Flow runs, taxes the resources of connected systems w/ poorly-designed requests, overall poor architecture, etc.)

 

Bottom line: you can't. Governance moves from the tradional up-front model to a more reactionary stance... You'll need active Admin(s) keeping tabs on what's being built, where resources are being consumed, etc. and performing outreach and adjusting environment settings accordingly.

 

Consider creating a Flow COE (Community of Excellence) or whatever internal buzzword you want to use - an internal community for employees (IT + Business) who are interested in Flow automation, sharing projects and ideas, and establishing guidelines.

 

Security

You protect your organizational data with carefully-crafted DLP policies, thereby limiting the available connectors. After that, users can get as messy as they want, and IT and Compliance can rest assured your company's trade secrets won't get ported over to Facebook, Google Drive, etc.

 

View solution in original post

v-yamao-msft
Community Support
Community Support

Hi @Manolin010 ,

 

Flow is a public cloud service to help individuals and teams to set up automated workflows between their favorite apps and services to sync information, get notification, and more.

 

When it comes to connecting to any other services, sometimes we are afraid of security info posted on other social account, such as Twitter, Facebook, etc.

 

However, you could consider using DLP policies to restrict what connectors can be used within the same Flow, which means that you could restrict the use of organization-only data inside of Microsoft Flow.

https://flow.microsoft.com/en-us/blog/introducing-http-and-custom-connector-support-for-data-loss-pr...

 

Further, as long as you are an admin, you could restrict user’s ability to access organization’s business data, manage the assignment of the paid licenses inside of your organization though of Office 365 admin portal, etc.

Please get more details from the following doc:

https://docs.microsoft.com/en-us/flow/organization-q-and-a

 

By the way, when working with Microsoft Flow, you would reach to us for any issues related to Microsoft Flow, we are always ready to help.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

3 REPLIES 3
jake
Advocate II
Advocate II

A couple thoughts...

 

Support

Enabling licensing for all users will enable all users to create Flows. That's good. Eventually, some flows will grow and evolve to the point that they are shared, becoming mission-critical pieces of automation for the teams using them. What does the support structure look like if something goes wrong w/ one of those Flows? Does IT pick that up? Does it fall back on the Flow creator?

 

Architecture & Governance

When everyone in the company can create Flows, you'll have a wide assortment of individual skill-sets with the ability to design and build automation solutions. For personal productivity, that's a good thing. For bigger projects, how do you ensure that things are built in the right way? (ie. not constructed in a way that burns unnecessary Flow runs, taxes the resources of connected systems w/ poorly-designed requests, overall poor architecture, etc.)

 

Bottom line: you can't. Governance moves from the tradional up-front model to a more reactionary stance... You'll need active Admin(s) keeping tabs on what's being built, where resources are being consumed, etc. and performing outreach and adjusting environment settings accordingly.

 

Consider creating a Flow COE (Community of Excellence) or whatever internal buzzword you want to use - an internal community for employees (IT + Business) who are interested in Flow automation, sharing projects and ideas, and establishing guidelines.

 

Security

You protect your organizational data with carefully-crafted DLP policies, thereby limiting the available connectors. After that, users can get as messy as they want, and IT and Compliance can rest assured your company's trade secrets won't get ported over to Facebook, Google Drive, etc.

 

v-yamao-msft
Community Support
Community Support

Hi @Manolin010 ,

 

Flow is a public cloud service to help individuals and teams to set up automated workflows between their favorite apps and services to sync information, get notification, and more.

 

When it comes to connecting to any other services, sometimes we are afraid of security info posted on other social account, such as Twitter, Facebook, etc.

 

However, you could consider using DLP policies to restrict what connectors can be used within the same Flow, which means that you could restrict the use of organization-only data inside of Microsoft Flow.

https://flow.microsoft.com/en-us/blog/introducing-http-and-custom-connector-support-for-data-loss-pr...

 

Further, as long as you are an admin, you could restrict user’s ability to access organization’s business data, manage the assignment of the paid licenses inside of your organization though of Office 365 admin portal, etc.

Please get more details from the following doc:

https://docs.microsoft.com/en-us/flow/organization-q-and-a

 

By the way, when working with Microsoft Flow, you would reach to us for any issues related to Microsoft Flow, we are always ready to help.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Good Day

 

Thank you all for the feedback, really appreciate it.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (5,015)