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; } } }

Anybody Having Problems With Rovo's Retention of Connected Data (e.g., Teams)

Eric J Trumbull

We recently found out that when Rovo indexed Microsoft Teams data, it does not then remove/delete messages when they are removed in Teams. We have an 8 day retention policy in Teams for Chat messages for industry-specific legal purposes.

Rovo started providing answers for Teams data from months ago. We checked with support and they told us Rovo won't respect the retention policy deletions.

We were also told there may be no manual way to purge our Teams data from Rovo.

Accepted answers

All comments

Arkadiusz Wroblewski

Hello @Eric J Trumbull

Still, you should keep working this through Atlassian Support or your Atlassian account team as well.

Community members can compare documentation and behavior, but only Atlassian can confirm the connector’s deletion semantics and whether your indexed Teams data can be purged. That´s beyond us.

Best,
Arkadiusz

Eric J Trumbull

Hi, @Arkadiusz Wroblewski - thanks for the reply.

We are still working with Atlassian Support on this. I'd just like to know if others are experiencing the problem, if they've found any helpful info in their own conversations with Support or found work arounds. We're currently waiting to hear if the Dev team can purge this data on our behalf.

Also hoping to bring visibility to something that I find surprising - that the connector won't reflect the retention of the source. There are huge legal implications to that.

Thanks!

Arkadiusz Wroblewski

@Eric J Trumbull

Yes, I fully understand your concern, and I'm fully on your side with that.

On the other hand, all integrations are coming out of their baby phase, so I think your matter will take on significance with time.

Rebekka Heilmann (viadee)

Hi @Eric J Trumbull

Rovo Connectors generally retain data for 30 days after disconnecting them so I'd guess that it also retains data that is deleted in the connected App for 30 days. From my understanding, permissions are updated more timely - not quite immediately but I think it's only a few minutes.

I don't have any Apps connected yet so I can't test that theory. Support should be able to shine some light on this and it would help the Community if you'd post the answer here as a comment

Eric J Trumbull

Hi, @Rebekka Heilmann _viadee_ -

Support has confirmed that the data will be purged 30 days after disconnecting the connector.

However, were told that data deleted by retention policies does not get deleted from the Connector index, only chats/messages deleted by a user will be removed.

They also confirmed they are unable to manually purge the data before the 30-day mark, which is unfortunate.

I'm hopeful these are changes that will be coming down the road!

Eric

Rebekka Heilmann (viadee)

I would have thought a delete is a delete. But with Atlassian, anything is possible.

Eric J Trumbull

Agreed, haha!

Looks like there's an open issue folks can vote on to start including this, which is much appreciated.

https://jira.atlassian.com/browse/ROVO-990

Eric

Dr Valeri Colon (Connect Centric)

@Eric J Trumbull this is an important distinction. Atlassian’s current documentation says admin-managed connectors listen for source deletions and update the Rovo index, but Support has apparently confirmed that Teams retention-policy deletion isn’t treated the same as user deletion. That’s a meaningful governance gap for organizations relying on source retention policies. Until ROVO-990 is addressed, I’d include connector-index retention in AI/data-retention reviews before enabling Teams.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

ms-teams

rovo-atlassian-intelligence

rovo