Title: Dynamic subscription sends extra report emails when a link-only subscription is added.

Hi VishalSharma-71 

The behavior you’re observing with dynamic per-recipient subscriptions in Power BI Service — where running a link-only subscription triggers unexpected emails from other reports sharing the same recipient dataset — is not officially documented but appears to stem from the way Power BI currently handles shared recipient dataset evaluations across multiple dynamic subscriptions. When multiple subscriptions (like your Reports A, B, and C) reference the same recipient dataset, Power BI treats that dataset as a shared evaluation context at runtime. In practice, when one subscription runs — especially a link-only one without a dynamic filter or attachment — the service can re-evaluate the full dataset for all linked subscriptions rather than isolating only the rows related to the scheduled report. This behavior effectively causes cross-triggering, where other subscriptions using the same dataset are included in the evaluation pipeline, leading to additional unintended emails.

This is not clearly stated in Microsoft’s current documentation, and as of now, there’s no public roadmap feature addressing this overlap. However, your findings — that isolating each report with its own dedicated recipient dataset prevents the issue — align with what appears to be the current best practice: avoid sharing the same recipient dataset across mixed subscription types (especially between PDF and link-only formats). Each subscription should ideally have its own recipient source to maintain isolation and prevent shared evaluations.

This cross-triggering seems to be a by-design limitation of how Power BI batches dynamic subscription evaluations when a shared dataset is used. Until Microsoft introduces finer control or isolation logic in the dynamic subscription engine, the recommended workaround is to separate recipient datasets per report or ensure that all subscriptions referencing a shared dataset use the same delivery type (e.g., all PDFs or all link-only). This prevents Power BI from reprocessing the dataset globally and sending unintended notifications during mixed-type schedule runs.