As we set up our EasyMorph Hub we are trying to use your out-of-the-box solutions and industry best practices. The server where the Hub resides is managed by our devops team, while I am administrating the Hub and EasyMorphs. Devops has created a service account to use for all activities that need an account but should not be tied to a user. One of those use cases is the Teams Bot. Those messages should not be sent by a user account. The devops team is managing this service account, including the password.
The Teams Bot action is designed so that the Microsoft account doesn't sign in till the action is placed and the channel is selected. This means that every time we use this action (and we want to use it a lot) the devops team member has to sign into the computer of the ETL dev adding and configuring the Teams Bot action and type in the password. This is quite the added burden to our organization.
Is it possible to pin the Microsoft account to the connector instead of the action? I'm sure you had some rational behind doing it this way, but perhaps we could choose when the account signs in, in the connector or in the action. Thanks!
