Feature Request: Enable PowerShell/REST API Control for Refresh Failure Notification Recipients

Dear Power BI Product Team,

As part of our enterprise deployment automation, we rely heavily on PowerShell scripts and REST APIs to manage semantic model configurations, including refresh schedules and parameter updates. One critical gap we've encountered is the inability to programmatically set refresh failure notification recipients beyond the semantic model owner.

Currently, the refreshFailureNotificationSettings endpoint returns a 404 (Not Found) for newly published datasets, and the refreshSchedule endpoint only supports "MailOnFailure" without allowing us to specify additional contacts. This limitation forces us to manually configure notification recipients in the Power BI Service UI — a time-consuming and error-prone step that undermines the automation goals of enterprise-scale deployments.

We request the following enhancements:

1. Enable support for refreshFailureNotificationSettings via REST API and PowerShell for all dataset types, including newly published semantic models.
2. Allow specification of multiple recipients (e.g., distribution lists or service accounts) in the refresh schedule or notification settings.
3. Document the supported structure and timing for applying these settings post-deployment to avoid silent failures or refresh schedule overrides.

This feature would significantly improve deployment reliability, reduce manual overhead, and align with enterprise automation best practices.

Thank you for considering this request. We’d be happy to provide additional context or participate in feedback sessions if needed.