Forum Discussion

NA_ARTM's avatar
NA_ARTM
Frequent Visitor
4 years ago
Solved

Power BI Refresh Failure Group

Hello,

 

The IT created for me distribution list to receive the failure notification for dataset refresh and Dataflow. When I am using it as a contact in the Send failure notification box, I have the message "At least one contact user(s) or group(s) does not have required permission to receive refresh failure notification."

 

I can't find any requirement on what I can use in this box. I need a generic e-mail address / group which can forward the message to anyone in the group so I wouldn't have to maintain an e-mail list in each dataset or dataflow.

 

Regards,

  • Here is a good resource for which security groups can be used where in power bi.

    There are many different types of Azure groups, not all of them can be used for every service in power bi.

    And for your scenario, my guess is you put the distribution list in a dataset setting in a workspace. Pro license is required if you want to access a workspace. That could be the reason?

  • NA_ARTM's avatar
    NA_ARTM
    4 years ago

    Thank you for the link.

    It worked with the mailed enabled security group without using any Power bi pro licence.

11 Replies

  • otravers's avatar
    otravers
    Community Champion

    I've always found these admin notifications in the Power BI service to be pretty limited so for requirements like this I tend to capture the emails with a Power Automate flow then route them to my liking (including for instance using Teams notifications).

  • Check if the Delivery Management for that distribution list is limited to internal senders. If yes, you need to change that to internal and external, because Power BI service is considered as external sender with the email [email protected].

    • NA_ARTM's avatar
      NA_ARTM
      Frequent Visitor

      Unfortunatly, it did not solve the problem. I still have the error 😞

      • Tutu_in_YYC's avatar
        Tutu_in_YYC
        Super User

        Do you have nested security groups on the distribution list? That could also be an issue. If yes, also check the delivery management for them.