An HTML report can look finished in your browser and still leave a colleague wondering what to do with the attachment. Before changing the report, check what you sent: the file itself, a document-library link, or the address of a published page.
Those routes have different permissions and different ways of displaying HTML. The aim is to get the reader to the report they can actually use.
Start with the report the team needs
This sample project update has a summary, workstream status, and filters for blocked work. The figures and people are fictional. Try the filter: a screenshot can show the summary, while the working page lets a reader narrow the list before a meeting.
Open the complete example or download its HTML.
If a dated snapshot is the deliverable, keep a PDF. If colleagues need to filter the tasks or return for corrections, keep the working page as well. Choose the format for that job rather than converting every report to a link.
What an attachment does, and what it does not promise
Microsoft’s file-sharing guide explains that channel files use the connected SharePoint site and chat attachments use OneDrive. Sharing a file does not by itself publish it as an HTML page, and a link to the stored file can still lead to a file viewer or download.
If a colleague sees a download, ask them to open the file in a browser after downloading it, or send a published page instead. If the file refers to a local images folder or a separate script, include those assets or make a self-contained file. The attachment alone cannot provide files that stayed on your computer.
Also check the sharing permission. Access to a Teams conversation and access to the linked file or website are not interchangeable. Test the actual reader’s route before assuming the report is broken.
Check your organization’s SharePoint HTML option
Microsoft documents a native HTML page workflow in Site Pages. Where available, you can upload an HTML file or folder, publish it, and share the page. The site must allow HTML files, and you need the relevant page permissions.
Existing HTML upload and direct text editing do not require a Copilot license. Copilot-assisted creation and editing have separate license requirements. Microsoft notes that parts of the feature are rolling out gradually, so ask your site owner if the controls are missing.
Use this route when the page belongs inside the organization’s approved Microsoft environment. Check the page sandbox’s limitations, particularly external scripts and data requests, before relying on a dashboard that fetches other services.
When an external page is the better fit
For a public workshop summary or a client-facing sample, you may want a page outside the organization’s document library. Publish it with a web tool your organization permits, then send its reader link in Teams.
For the sample above, the same HTML can be saved as a NOS document and opened through a share link. Check the filters there before sending it. NOS does not turn a public link into a company-only page; remove internal information first.
Open the report’s actual share link.
- Open the saved document and choose Share → Share link.
- Create the link and open it in a signed-out browser window.
- Check the title, the task list, and the filter using that reader link.
- Paste the link in the intended Teams conversation with the action you want readers to take.
For example: “Please filter to Blocked and check the two approvals before Thursday’s review.” That tells colleagues what they are opening and why.
A link preview may depend on the app and your organization’s settings. The destination should still make sense when the message shows only the URL. Do not treat a missing preview image as proof that the page itself is unavailable.
A Website tab is a separate question
Adding a site as a tab is not the same as sending its link. Microsoft documents cases where embedding restrictions or Conditional Access prevent a site from loading inside Teams. Open the site in a browser when that happens, and check your organization’s supported tab options.
If the goal is simply to let a colleague read and use the report, a normal page link avoids making the tab setup part of the task.
Correct the report people already have
Suppose a task’s owner changes after you share the report. Edit the owner in the saved page and check the same reader link again. With NOS, a wording change can be made directly on the rendered text; a change to filter behavior belongs in the HTML.
The link can continue to point to the corrected page. If you also issued a dated PDF, keep its status clear: it remains a snapshot of that date. Important corrections still need a message to the team; editing the web page does not notify everyone who read the earlier version.