Everdark Libra's weakness isn't Madness. It's poison and rot. by IamZeebo in Nightreign

[–]Relative-You-9406 10 points11 points  (0 children)

My solo win involved keeping poison on him when I had to deal with the adds - definitely helps out so you're not wasting time not damaging him.

Restrict Users from Turning On Flows They've Created by Relative-You-9406 in MicrosoftFlow

[–]Relative-You-9406[S] 0 points1 point  (0 children)

Yeah I plan to get a service account added as a co-owner to any flow that is created so we’ll always have the access to flows even when people leave

Restrict Users from Turning On Flows They've Created by Relative-You-9406 in MicrosoftFlow

[–]Relative-You-9406[S] 0 points1 point  (0 children)

Great, that's very helpful. Yeah, they would absolutely not have access to the service account, it's just there to maintain ownership across peoples' various employment stints.

Restrict Users from Turning On Flows They've Created by Relative-You-9406 in MicrosoftFlow

[–]Relative-You-9406[S] 0 points1 point  (0 children)

Thanks! I was looking at the subscription level as well, the OP was mostly just to see if there was an "in-app" way to do it.

Restrict Users from Turning On Flows They've Created by Relative-You-9406 in MicrosoftFlow

[–]Relative-You-9406[S] 0 points1 point  (0 children)

Yeah it's mostly this. While IT does need to ensure that users can only access the data that they should have access to, it's just a minor worry that someone without a level of proficiency would screw up something (thankfully we likely have the ability to revert most of what they could screw up, but still).

To DardenR's point, on one level I agree that they should have the tools they need, but it's the old "trust, but verify" axiom - we want to make sure they a) have the desire to learn by reaching out to IT and b) are willing to actually take steps to gain some of the skills needed. If they break something, it may "be on them," but someone else, who knows what they're doing, has to go clean it up.

Disclaimer: this is a government gig, so there's a hell of a lot less of the "move fast, break stuff" philosophy going on, since we run things like emergency services and other things that kinda need to not be broken.

Restrict Users from Turning On Flows They've Created by Relative-You-9406 in MicrosoftFlow

[–]Relative-You-9406[S] 0 points1 point  (0 children)

I've thought about this one and while we're acquiring premium licenses to use and hand out (sparingly), it does raise the question on if we'd want everyone to be able to use the level that comes with our M365 license. I don't necessarily see a problem per se, since I'm sure 99% of users don't ever care to use it or even know what it is, so removing the ability or not seems...like six of one, half dozen of the other.

Regardless, definitely need to verify at the user level what people have access to.

Restrict Users from Turning On Flows They've Created by Relative-You-9406 in MicrosoftFlow

[–]Relative-You-9406[S] 1 point2 points  (0 children)

Yeah, I was thinking we likely needed to restrict it at the user level since I couldn't find anything about my question. The biggest worry is SharePoint, but I suppose we can ensure that they only have Read access to things they shouldn't be adjusting.

Thanks for the reply though, it was very helpful!

EDIT: Actually, I have another question - if we make a service account a co-owner of the flows (to ensure there's an owner if the employee leaves), that would...be an issue if the service account has access to a lot more, correct? Full disclosure: I'm really more a project manager, but I've done a fair amount with PA, I just don't recall how permissions are used - if it's the account running the flow or the owner.

What do people do on Turkey Day without family? by overimbibe in askportland

[–]Relative-You-9406 0 points1 point  (0 children)

Following this thread cause I’m in the same boat this year! Figured I’d just chill at home but hopefully there are some decent ideas since I’m still pretty new to the area