以服务主体身份运行azure逻辑应用程序/连接器 [英] Run azure logic app / connector as service principal

问题描述

是否可以将逻辑应用程序或连接器作为服务主体运行，尤其是在使用计划下?

Is it possible to run a logic app or connector as a service principal, in particular under the consumption plan?

我猜想强迫该应用程序通过Powershell在非消费计划中运行对服务主体的更多控制.

I'd guess forcing the app to run in a non-consumption plan via powershell might give more control over the service principal.

我希望它避免在自动部署期间使用个人帐户的原因.

The reason I'd want it to avoid an individual's account to be used during an automated deployment.

我认为最接近的是将 https://github.com/logicappsio/LogicAppConnectionAuth 纠缠到使用服务主体自动地执行oauth，但是尝试对数据工厂连接进行类似的操作证明是徒劳的，而且非常耗时，因此，如果我发现错误的树，我宁愿早发现.

The closest I thought was to wrangle https://github.com/logicappsio/LogicAppConnectionAuth to do the oauth automagically using a service principal, however trying similar things for data factory connections proved unfruitful and very time consuming, so I'd rather find out sooner than later if I'm barking up the wrong tree.

推荐答案

具有OAuth身份验证的API连接(例如Office 365和Microsoft Team连接器)需要人工同意.不幸的是，此时，对这些用户的身份验证还不能完全自动化.

API Connections with OAuth authentication, like Office 365 and Microsoft Team connectors, require manual consent. Unfortunately, at this point in time, authentication for those cannot be fully automated.

正如您提到的，此脚本 https://github.com/logicappsio/LogicAppConnectionAuth 可以避免一些用户在验证连接器时单击，但是最后将是一个手动步骤.

As you mentioned, this script https://github.com/logicappsio/LogicAppConnectionAuth will avoid some user clicks when authenticating the connectors, but at the end is going to be a manual step.

HTH

这篇关于以服务主体身份运行azure逻辑应用程序/连接器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！