What kind of restrictions are there with the ChatOps automation to create Teams Meetings?

[Alexander Gorham]

My organization is setting up the automation to create a teams meeting any time an incident is created. We are attempting to use a generic service account for this automation actor. The service account is an org admin, and a teams admin, however we are receiving an error that the actor can not create a teams meeting. 

We have also tried to use the "User who triggered the event" as the actor, and receive an error because Automation for Jira is not able to start teams meetings, even though there would be no scenario where the user creating the incident would be unable to create a meeting. 

Is there any kind of restriction on this automation/ChatOps that prevent a generic account from being the actor? 

[Marc - Devoteam]

Hi @Alexander Gorham 

Simple question, you have created tis user in Jira.

Is there a related MS Teams account, if not how can a Jira account create a teams meeting?

Have you gone over this documentation to complete all the necessary steps?

https://support.atlassian.com/jira-service-management-cloud/docs/connect-microsoft-teams-to-your-service-project/ 

[Alexander Gorham]

Hi Marc,

The account does have a teams account. I have signed into it and created meetings with it. We have followed all steps in the documentation as well. 

[Marc - Devoteam]

HI @Alexander Gorham 

The user in Atlassian, does it have a JSM license and is it granted access on the project.

You can also only doe this on an Incident not on other issue types

Create Teams chat or meeting for an incident From the navigation on the left, select Incidents.

Open the incident you’d like to create the chat or meeting for.

In the Details section, find the Microsoft Teams field and select Create chat or meeting. Select the Microsoft tenant you want to create your chat or meeting in.

Under the Type field, select Chat.

To start a video call with your team, select Meeting.
You can edit the auto-filled Chat name.
Add a Chat description.
Add people to your chat using the Participants field.
Select Create. T

he group chat you’ve created will be linked to the incident’s details section.
Select Open [chat/meeting name] from the Microsoft Teams field in the Details section of the incident.

But also I don't see any options to use automation to create a meeting.

[Alexander Gorham]

Correct. It is an administrator in the project and is licensed in JSM. It is also an org admin in our instance. 

[Marc - Devoteam]

Hi @Alexander Gorham 

What does your automation look like?

As I don't see any options to use automation to create a meeting via automation.

[Alexander Gorham]

We have blocked out the tenant, but it is present. 

[Marc - Devoteam]

Hi @Alexander Gorham 

What does the audit log then tell, on running the rule?

[Alexander Gorham]

@Marc - Devoteam 

We can't save the automation with that actor, so I can't provide an audit log history. 

We're currently using a regular user's account as the actor and the automation is running normally, but would prefer to not do it this way. 

[Alexander Gorham]

This is the error when trying to use the generic account as the actor, even though we've verified all permissions, and created meetings with this account manually. 

[Marc - Devoteam]

Hi @Alexander Gorham 

So there is a permission issue at the MS side not on Jira.

Connect with the responsible IT on your side in relation to Microsoft.