Disable "Check out a report frequently opened by your collegues" in Teams

[danieletiles]

Hi to all,

some of our users are receiving this message in Microsoft Teams of "Check out a report frquenty opened by your collegues"...but it's a report that they aren't allowed and should not be allowed to (and in fact they cannot open it).

Is there a way to disable this kind of notification?

Regaards

Daniele Tiles

[v-venuppu]

Hi @danieletiles ,

I hope the information provided is helpful.I wanted to check whether you were able to resolve the issue with the provided solutions.Please let us know if you need any further assistance.

Thank you.

[v-venuppu]

Hi @danieletiles ,

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-venuppu]

Hi @danieletiles ,

Thank you @tayloramy for the prompt response.

I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.

Thank you.

[v-venuppu]

Hi @danieletiles ,

Thank you for reaching out to Microsoft Fabric Community.

The “Check out a report frequently opened…” message in Teams comes from the Power BI-Teams integration. There is no way to disable it for a single report or user. To prevent it, the Power BI admin must adjust tenant settings - either disable or restrict the Teams integration/notifications in the Power BI Admin Portal.

[danieletiles]

So with Fabric / Power BI we can limit what users can see and get, but then they get these messages about report thay cannot open and maybe they shouldn't know about...it's a bit frustrating.

[tayloramy · Accepted solution]

Hi @danieletiles, 

This can be disabled at the tenant level with the following setting in the admin portal: 

This can't be turned off on a report level. 

Individual users can also mute Power BI notifications

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution