Start runbook in Azure - Change connection not working?

[David Quiram]

When I was looking into setting up this action in an automation, I used my own account to establish the connection. Natural habit.

My account is an admin level account, so it worked fine, but looking back now, I would rather it use a service account we have setup specifically for these situations and not be tied to my account. 

I can see the "change connection" button, but when I click the "new connection" option, it just creates a new connection with the same account, mine.

How can I get this thing to forget my credentials or re-prompt for new credentials?

Is there something within my Jira account I could reset or change? Is this functioning as intended? I feel like I'm going crazy here. 

[Marc - Devoteam]

Hi @David Quiram 

The same applies in Confluence or other tools when creating a connection in an automation rule.

The work around is to logon to the system with the service account ( if exist) and then setup the automation rule. The connection user will then be service account, as your are in the system with this user.

Make sure this user has sufficient rights, to do the automation action.

https://support.atlassian.com/cloud-automation/docs/connect-your-automation-rule-to-another-tool/ 

I can't find any related open request to change this on the https://jira.atlassian.com