Share
Report
242Hello,
I am using the AA4PP application in my environment, and everything is functioning smoothly. However, I require some clarification on the use of service accounts as it appears to be impossible to use a primary service account with the SPO connector, which is based on a user connection.
For context, users in our organization do not have premium licenses. They mainly use SharePoint lists as data sources, and premium connectors are allowed in the ORG environments.
We have six environments:
DEV ORG,
ACCEPT ORG,
PROD ORG,
DEV UA,
ACCEPT UA,
PROD UA.
When a user creates a flow in DEV UA, they use their identity for connectors. When they deploy their solution with AA4PP, they associate connection references for test and production environments with their account.
However, this method has a downside: if a user leaves the organization, the flow becomes orphaned. Although this is not a major issue due to alerts from the COE, it is still a concern.
To prevent this, I use a service account, let's call it svc_ppf, which has been assigned a premium license. For all solutions containing a flow, users must click on 'request a new connection from another user' and enter the svc_ppf account. I then approve the connection. However, using this account as a connection reference for all flows leads to several issues:
- Load distribution problems, risking reaching the daily API call limit.
- For an SPO connector, the svc_ppf account must have the necessary rights to access and write in the SharePoint list.
- Not to mention potential issues with other connectors like Forms, etc.
- I am at a crossroads regarding the strategy to adopt to simplify and streamline the use of AA4PP for our users.
I am considering advising the use of the svc_ppf account for flows containing premium connectors, and for other connectors, users would use their personal credentials.
What advice can you offer? How do you handle this issue in your organization?
Thanks
All responses (
Answers (
