An SSRS email subscription can attach the rendered report to each message as PDF, Excel, Word, CSV or another export format. You set it up in the report portal: configure SMTP on the report server, store credentials for the report's data source, create a subscription, choose E-mail delivery and pick an attachment format. That covers a handful of reports and recipients. Once you have hundreds of recipients, event-driven timing or several destinations, the native subscription becomes the part of your reporting you maintain every week, and that is where we automate it with PBRS.
This guide gives you the full native procedure, the data-driven variant for personalized attachments, the failure points that cause most missing-attachment tickets, and the point at which a dedicated automation tool pays for itself.
TL;DR
- An SSRS email subscription sends the report as an attachment (a rendered file) or as a link, depending on the options you choose in the subscription.
- Prerequisites come first: working SMTP settings on the report server, a data source with stored credentials, and permission to create subscriptions.
- A standard subscription sends the same report to a fixed recipient list. A data-driven subscription reads recipients, formats and parameters from a query.
- SSRS does not check attachment size, so the mail server decides whether a large Excel or PDF gets through.
- When you manage many recipients, formats and destinations, PBRS handles scheduling, personalization, export and delivery for SSRS and Power BI reports in one place.
Table of Contents
- Attachment versus link: what the subscription actually sends
- Before you start: SMTP, credentials and permissions
- Create a standard email subscription with an attachment
- Attachment size: the mail server decides
- Personalized attachments with a data-driven subscription
- Troubleshooting: no email, no attachment, or late delivery
- Where native subscriptions stop
- Doing the same job with PBRS
- Perspective: why attachment delivery deserves its own layer
- See it on your own reports
- Checklist before you put a subscription into production
- FAQ
- Sources
Attachment versus link: what the subscription actually sends
When SSRS runs an email subscription, it renders the report in the format you pick and either embeds it, attaches it or links to it. For each subscription you decide:
- Attachment: the recipient gets a file (PDF, Excel and so on). It works offline and can be forwarded or archived, but it is a snapshot of the data at run time.
- Link: the recipient gets a URL to the report on the server. The data is live, but the recipient needs network access and permission on the report server.
- Embedded report: the report body appears inside the email, which suits short reports in HTML-capable mail clients.
For finance packs, executive KPIs and anything going outside the firewall, attachments are the usual choice because the recipient does not need a login to the report server. The cost is size and security: the file leaves your environment the moment the email is sent. Decide per audience, and keep recipients who need live data on links.
The data-driven subscription walkthrough on MSSQLTips lists the delivery properties that control this: IncludeReport (attach or not), IncludeLink, RenderFormat, Subject and Comment. Those same properties appear as fields in a standard subscription, so you can reason about both with one mental model.
Before you start: SMTP, credentials and permissions
Most failed subscriptions are not subscription problems. They are prerequisites that were never finished. Check these three things first.
1. Email settings on the report server
The report server needs an SMTP server address and a sender address. According to the SQL Shack subscription tutorial, you configure the report server's email settings and subscription settings and then restart SSRS for the change to apply. If you relay through Microsoft 365, your SMTP host, port, authentication and sender permissions have to match what your tenant allows; our Office 365 SMTP settings guide walks through the values for sending reports.
2. Stored credentials on the data source
A subscription runs unattended, so SSRS cannot prompt anyone for a password. The same tutorial has you open Manage on the report, then configure the data source with stored credentials. If the data source uses Windows integrated security or prompts for credentials, the subscription option will be unavailable or the run will fail. Use a dedicated service account with read-only access to the data the report needs, and rotate its password on your normal schedule. When the password changes, update it here, or every subscription on that data source fails at its next run.

3. Permissions
The person creating the subscription needs rights to the report in the portal. If subscriptions are missing from the menu for a user, check their role on the report or folder before changing anything on the server.
Create a standard email subscription with an attachment
The sequence below follows the SQL Shack walkthrough for the SSRS web portal. Our notes at each step point to where it goes wrong.
- Open the report's Manage page and confirm the data source uses stored credentials. If you skip this, you will get an error when saving the subscription or at first run.
- Select Subscription, then Standard subscription (the label may vary slightly by SSRS version). Give it a clear name, because a server with 300 subscriptions named "Subscription1" is impossible to audit.
- Set the schedule. The native options are hourly, daily, weekly, monthly or once. Anything more specific, such as the third business day of the month or after a data load finishes, is not a native option. People work around that with duplicate subscriptions or custom scripts, and that is how schedule sprawl starts.
- Choose E-mail as the delivery method and enter recipients. Type addresses carefully: a typo does not produce a loud error, it produces a quiet bounce to the sender mailbox.
- Write the subject and comment. The subject can use the built-in report name and execution time values, which keeps your recipients' inbox rules working.
- Pick the attachment option and format. Select the render format, such as PDF or Excel, and choose whether to include the report, a link or both.
- Set parameter values. A subscription freezes one set of parameters. If the report has a Region parameter, this subscription sends one region.
- Create the subscription and test it. Use a schedule a few minutes ahead to confirm delivery before you set the real cadence.
Which format to attach
Choose by what the recipient will do with the file:
| Recipient need | Typical format |
|---|---|
| Read, print or archive a fixed layout | |
| Analyze or re-pivot the numbers | Excel |
| Load into another system | CSV |
| Edit narrative or commentary | Word |
PDF keeps layout stable and files small. Excel is the format that causes the most size trouble, which leads to the next point.
Attachment size: the mail server decides
SSRS does not stop you from sending something too big. A widely quoted passage of the Microsoft documentation, reproduced in an Experts Exchange thread on subscription size limits, says Reporting Services does not check the attachment or message size before sending, and if it exceeds the mail server's limit the report will not be delivered. The practical consequences:
- A subscription that worked for months can start failing when the dataset grows past your relay's cap.
- The failure shows up on the mail side, so the subscription may look healthy in the portal while recipients receive nothing.
- Ask your Exchange or relay administrator what the message size limit is, and compare it with your largest scheduled Excel file.
If a file is routinely near the limit, change what you send rather than raising the limit everywhere: filter the report to each recipient's slice, switch the format to PDF, or deliver a link or a file-share copy for the largest outputs.
Personalized attachments with a data-driven subscription
A standard subscription sends one report to one list. If each regional manager, customer or cost center should receive only their own data, you need a data-driven subscription. Per the MSSQLTips tutorial, you select a data-driven subscription and E-mail delivery, define a subscriber dataset and query, and then map the returned columns to delivery properties (To, CC, BCC, IncludeReport, RenderFormat, Subject, Comment, IncludeLink) and to the report's parameters.
A minimal recipient table might hold:
| Region | Format | IncludeReport | |
|---|---|---|---|
| east.lead@example.com | East | True | |
| west.lead@example.com | West | Excel | True |
| cfo@example.com | All | True |
The subscription query returns those rows, and each row produces one email with its own attachment, format and parameter. The benefits are real: add a recipient by inserting a row instead of editing a subscription. The risks are real too:
- The recipient table becomes a governance object. Someone must own it, and wrong rows send confidential data to the wrong person.
- One bad row, such as an empty address or an unsupported format value, can cause failures that are hard to trace.
- Data-driven subscriptions are tied to the capabilities of your SSRS edition, so confirm your edition supports them before you design around them.
Our guide to SSRS subscriptions covers the standard and data-driven types side by side if you need the decision framework.
Troubleshooting: no email, no attachment, or late delivery
Work from the outside in. Most cases fall into four buckets.
The email never arrives
Check the subscription's last-run status in the portal first. If it shows an error, the message usually names the cause. If it says the mail was sent but nothing arrived, move to the mail side: check the relay's logs, the sender address's permission to send, spam filtering, and whether the recipient domain rejects the sender. A bad SMTP configuration is the first thing to rule out, so revisit the email settings and confirm the service was restarted after changes.

The email arrives without the attachment
The attachment option on the subscription is the cause more often than any server fault. Open the subscription and confirm that include report is selected and a render format is chosen. In a data-driven subscription, check that the column mapped to IncludeReport actually returns a true value for that row, and that the RenderFormat column holds a valid format name.
The subscription fails at run time
Stored credentials are the first suspect: an expired or changed password on the service account breaks every subscription that depends on it. Next, check parameters. A report whose parameter default depends on a date or a value that no longer exists will fail unattended even though it runs fine for you interactively.
The email is late
Subscriptions that all fire at 7:00 a.m. compete for the same report server resources, and the heaviest reports finish last. Stagger schedules by a few minutes, move heavy reports earlier, and keep an eye on report execution time as data grows. If the report completes on time but the email arrives late, the delay is in mail queueing, so check the relay.
Where native subscriptions stop
Native SSRS subscriptions are good at one thing: a scheduled email with a fixed set of options. Teams outgrow them for predictable reasons:
- Scheduling limits. The schedule types are fixed, and there is no native way to start a delivery when a data load, file drop or database change occurs.
- Personalization at scale. Data-driven subscriptions need a recipient table and edition support, and they put the burden of governance on whoever wrote the query.
- One destination. Email and file share cover the basics. Delivering to cloud storage, a database, or a collaboration tool means custom delivery extensions or scripts. A custom SSRS delivery extension means writing and maintaining code against the report server.
- Visibility. Subscriptions are spread across reports, and answering "who receives what, and did it go out?" takes queries against the report server database.
If you recognize two or more of those, the question is no longer how to configure one subscription correctly, it is whether subscriptions should be your delivery layer at all. Our overview of SSRS report scheduling for the enterprise lays out how that decision usually plays out.
Doing the same job with PBRS
PBRS for Power BI and SSRS is our on-premises automation software for scheduling, personalizing, exporting, packaging and delivering SSRS and Power BI reports. Each step of the native procedure above has a counterpart there:
| Native SSRS step | With PBRS |
|---|---|
| One of five schedule types | Flexible schedules, plus event triggers for event-driven delivery |
| Subscriber query and column mapping | Data-driven bursting to personalize reports per recipient |
| Email or file share | Multiple formats and destinations, including email, cloud, database and collaboration tools |
| Scripts or custom extensions for anything else | Replaced by built-in delivery options, with automated error handling |
The result we design for is the same outcome the native subscription promises, the right report in the right format to the right person at the right time, without a per-subscription build for each variation. Our walkthrough on scheduling SSRS reports to email shows the setup in practice.
Perspective: why attachment delivery deserves its own layer
Report delivery looks like a small feature of a reporting platform, so it usually gets the smallest share of attention. We see it differently. Delivery is the moment the report becomes a business decision, and the person receiving it does not care whether the schedule was clever or the SMTP relay was tidy. They care that the PDF arrived, was the right one, and was on time.
Native subscriptions are a sound starting point, and for a few reports they are enough. But our experience over more than two decades of focusing on report automation across Power BI, SSRS, Tableau and Crystal Reports is that the work grows in the gaps: a new format for finance, a personalized version for each region, a trigger tied to a data load. Each gap is a custom script or a duplicated subscription, and each one is something a person must remember to maintain.
That is why we built PBRS to treat scheduling, personalization, export and delivery as one managed process, with error handling built in and a SOC 2 Type II certified company behind it. If your attachments are going out reliably today, keep going. If you are spending hours a week exporting, re-sending or debugging, that time is the case for automating end to end.
Christian Ofori-Boateng
See it on your own reports
If your SSRS subscriptions have outgrown the portal, PBRS for Power BI and SSRS is the place to start. It runs on-premises, is available as a subscription or perpetual license, and is built to take over the scheduling, formatting and delivery you configure by hand today.

Explore PBRS and the rest of the ChristianSteven product line to see which product fits your reporting environment.
Checklist before you put a subscription into production
- SMTP host, port, authentication and sender address confirmed with your mail administrator, and SSRS restarted after changes.
- Data source set to stored credentials with a dedicated, read-only service account and a documented password rotation.
- Largest expected attachment compared with the mail server's size limit.
- Format chosen by what the recipient does with the file: PDF to read, Excel to analyze.
- Subscription names that say what is sent, to whom and how often.
- For data-driven subscriptions: a named owner for the recipient table and a check for blank or invalid values.
- Schedules staggered so heavy reports do not all start at the same minute.
- A test delivery to yourself before the first real run.
FAQ
Can an SSRS email subscription attach a report as PDF or Excel?
Yes. When you create the subscription and choose E-mail as the delivery method, you select the render format and whether to include the report as an attachment, a link or both. PDF suits fixed layouts and Excel suits recipients who will work with the numbers.
Why does my SSRS subscription send an email with no attachment?
The most common cause is the include-report option being off, or in a data-driven subscription, the column mapped to it not returning a true value for that row. Also check that the render format is valid and that the report ran without errors for that recipient's parameters.
Is there a size limit for SSRS email attachments?
SSRS does not check size before sending, so the limit is whatever your mail server enforces. If the message is larger, it is not delivered, even though the subscription may appear to have run. Compare your largest files with your relay's limit and filter or reformat the biggest reports.
What is the difference between a standard and a data-driven subscription?
A standard subscription sends one report with one set of parameters to a fixed list. A data-driven subscription runs a query and creates one delivery per row, mapping columns to recipients, format, subject and report parameters, so each person can receive a different attachment.
Sources
- Enhancing Customer Experiences with Subscriptions in SSRS, SQL Shack
- SSRS Data Driven Subscription, MSSQLTips
- Size limit for an Excel file in a subscription, Experts Exchange
- SSRS custom delivery extension, Julien Theys
