nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rovo permissions on Microsoft Teams

Kristiyan Milanov

Hello,

I'm stuck at Review consent loop in MS Teams when trying to create request through Rovo Agent.

My Configuration in Microsoft is as follows:
Screenshot 2026-06-09 151919.png
Despite approving every time I receive following Review prompts and I'm in constant loop: Screenshot 2026-06-09 152038.png

My user has permissions to create requests and everything else, also the application is without required assignment and despite that I specifically assigned my user to it just in case. Still I cannot create requests.

From our ticket portal Rovo can create requests without any issues:
Screenshot 2026-06-09 152336.png

Could anyone advice if I'm missing something ?

Accepted answers

Kristiyan Milanov

Hi everyone,

Just sharing the fix in case someone else runs into the same Rovo issue in Microsoft Teams.

The consent/review loop was caused by missing Microsoft Graph permissions for the Rovo Teams app in Entra ID.

Initially, our Rovo Enterprise Application in Entra only had these permissions granted:

email
offline_access
openid
profile
User.Read

After working with Atlassian Support, we confirmed that the Rovo Microsoft Teams integration also requires the following permissions:

ChannelMessage.Read.All
Chat.Read

Since Rovo is a third-party multi-tenant app, we could not manually add those permissions directly from our own App Registration because we do not own the app registration. The permissions had to be requested/granted through the Rovo Microsoft Teams admin consent flow.

After granting the missing permissions, the Microsoft Teams/Rovo Review → sign-in → consent loop was resolved, and Rovo was able to proceed to the ticket creation screen.

So the fix was:

Go to Entra ID → Enterprise Applications → Rovo → Permissions.
Confirm whether ChannelMessage.Read.All and Chat.Read are present.
If they are missing, re-run the Rovo Microsoft Teams admin consent/setup flow from Atlassian.
Grant the requested permissions as a Microsoft admin.
Retry Rovo in Teams.

Thanks to Atlassian Support for pointing me to the updated Microsoft Teams permissions documentation.

All comments

Arkadiusz Wroblewski

Hello and Welcome to the Atlassian Community @Kristiyan Milanov

Does this happen in a 1:1 Teams chat with Rovo or within a channel/group chat ? Also, as a quick test, what happens if you manually type Confirm instead of clicking the Review button after Rovo shows the proposed ticket?

Best,

Arkadiusz🤠

Kristiyan Milanov

Hello, thanks for the warm welcome!

It's in 1on1 chat I will test it out in group chat but I think the behavior it will be similar.

When I type confirm, it tells me the ticket is created but I cannot find it nowhere.

Screenshot 2026-06-11 094446.png Screenshot 2026-06-11 094537.png Screenshot 2026-06-11 094254.png

Dr Valeri Colon (Connect Centric)

Welcome @Kristiyan Milanov based on your screenshots and follow-up, this may be more than a consent or permission issue. There have been several reports across the forum where Rovo reports that an action completed successfully, but the underlying action was never actually executed or persisted. While most reported cases involve Confluence page creation, the pattern is similar. Since ticket creation works from the portal but not from Microsoft Teams this could be a limitation or a defect. I would recommend opening an Atlassian Support ticket and including screenshots, timestamps, and the request details so they can review the backend logs for the Teams integration.

Kristiyan Milanov

Thank you Valeri!

I've opened a request and will give updates if we find something.

Danilo Divina Jr.

We're also experiencing similar Rovo permission issue in Teams. The "Grant Admin" consent request keeps popping up for a non-Global admin user even if the request was already approved by a Global admin and consented on behalf of our organization. It seems that there are additional missing API permissions.

Kristiyan Milanov

I was able to create request but only after giving the application administrator role to the user, otherwise it doesn't work. If anyone know what is the missing permission it would be really helpful so we can grand access to regular users to use it and open tickets from teams chat.
Screenshot 2026-07-06 162854.png

Kristiyan Milanov

Hi everyone,

Just sharing the fix in case someone else runs into the same Rovo issue in Microsoft Teams.

The consent/review loop was caused by missing Microsoft Graph permissions for the Rovo Teams app in Entra ID.

Initially, our Rovo Enterprise Application in Entra only had these permissions granted:

email
offline_access
openid
profile
User.Read

After working with Atlassian Support, we confirmed that the Rovo Microsoft Teams integration also requires the following permissions:

ChannelMessage.Read.All
Chat.Read

After granting the missing permissions, the Microsoft Teams/Rovo Review → sign-in → consent loop was resolved, and Rovo was able to proceed to the ticket creation screen.

So the fix was:

Go to Entra ID → Enterprise Applications → Rovo → Permissions.
Confirm whether ChannelMessage.Read.All and Chat.Read are present.
If they are missing, re-run the Rovo Microsoft Teams admin consent/setup flow from Atlassian.
Grant the requested permissions as a Microsoft admin.
Retry Rovo in Teams.

Thanks to Atlassian Support for pointing me to the updated Microsoft Teams permissions documentation.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management

rovo-atlassian-intelligence

rovo