search

microsoft / coe-starter-kit

Other
751 stars 221 forks source link

Flows To Use Service Principals Not Service Accounts #465

Open NPrice99 opened 3 years ago

NPrice99 commented 3 years ago

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Make whole of CoE be capable of using Service Principals rather than Service Accounts as service accounts are insecure.

Describe the solution you'd like Whole of CoE to use Service Accounts.

Describe alternatives you've considered None

Additional context A number of institutions ban Service Accounts as they are insecure and only use Service Principals.

I have, on my own personal tenancy, have a number of flows using service Principals (but there are so many of them it is taking time to convert them and everytime there is a new release I will have to convert them again.

manuelap-msft commented 3 years ago

At the moment, only a limited number of connectors (mostly Azure ones) support using Service Principals from flow. Whilst we can have this item on our backlog, we will depend on the product to make Service Principals available for the connectors we use - such as Power Apps for Admins etc. Our hands are tied until this capability becomes available in the product.

MarinaHadzi commented 2 years ago

Hi @manuelap-msft, can we set up CoE now with Service Principal account on Teams or on Production or both?

russrimm commented 11 months ago

@MarinaHadzi I don't believe all connectors the CoE uses support SPNs, yet. When they do, I'm wondering if the 25,000 base request limit implied on service principals since they're considered non-licensed users will cause a problem in larger environments?