You’re offline. This is a read only version of the page.
Our local government is just starting developing some automated flows to ingest data from emails in a shared mailbox into SQL tables. I'm starting to have questions about how multiple developers would manage these flows.
When developing the flow there is a connection to my outlook mailbox so if I assign a team to the owner of the flow, it gives a warning about the permission of my outlook mail box and the team then has access to it. I thought if it was a shared folder it would not have the private connection to my mailbox but I guess that is how it is connecting. Does teams use a shared user account for developing? Just trying to figure out best practices for teams developing flows and need access to each others flows for maintenance and support.
I am surprised there are no seamless integration into DevOps and using repro for versioning. What are most teams doing to protect the flows and versioning. Only thing I see is to manually export the flows and add them into Devops. Does anyone have better idea for source control?
Thanks. That gives me some information to go back with. Does your service accounts have to change passwords every so often? If so how do you all manage that?
We set up service accounts with the appropriate licensing. The service account is then set up as the primary owner for the flows and all of the connections use the credentials of the service account. Then the developers who need to work on projects together all know the login information for the service account, and they can add their own account as an additional owner if needed. The developers mostly work on projects for a specific region (for example, South America) and most regions have 2-3 developers each. This has worked out well for us. The service accounts are configured so they can only be accessed when logged into our network or you are logged in through our VPN if working remotely.
And for some fun, I asked Copilot to summarize our approach:
Service Accounts: Setting up dedicated service accounts with appropriate licensing is a smart move. These accounts act as the primary owners for the flows, providing a clear point of control.
Credentials and Connections: By using the service account’s credentials for all connections, you simplify management. Developers don’t need to juggle multiple sets of credentials, which can lead to fewer errors and smoother collaboration.
Collaboration: The shared login information for the service account allows developers to access and work on projects together. Adding their own accounts as additional owners ensures flexibility and collaboration.
Regional Focus: Assigning developers to specific regions (like South America) aligns well with project responsibilities. Having 2-3 developers per region streamlines communication and coordination.
Security Measures: Restricting service account access to your network or VPN adds an extra layer of security. It ensures that only authorized personnel can work on the projects.
Overall, your approach strikes a good balance between control, collaboration, and security.
#1
Michael E. Gernaey
497
Super User 2025 Season 1
#2
David_MA
436
Super User 2025 Season 1
#3
Riyaz_riz11
244
Super User 2025 Season 1
Share
Report
All responses (
Answers (