Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi all,
I'm reaching out to the community to see if anyone has any information on the new publish to web warning.
According to official MS documentation (updated May 2025), the warning used to read: "Do not publish confidential or proprietary information, or an individual's personal data".
However, today when I published, the warning had changed to: "Do not publish confidential or proprietary information, or an individual's personal data because any Internet user with access to the embed code for this report can fully access all the data in the semantic model anonymously".
The new wording really concerns me. Does this imply that anyone who has access to the public embed code will be able to connect to the granular data in the semantic model? This is completely contradictory to my understanding of publish to web, which I thought only gave users access to data aggregated at the visual level. I also cannot understand how someone would be able to connect to the semantic model with just the embed code.
Has anyone else come across this/been in contact with Microsoft to understand the impacts? Any guidance would be appreciated.
Solved! Go to Solution.
Hi @PowerUp2000 ,
Thank you for following up. I understand the confusion regarding the updated warning’s wording. The phrase “any Internet user with access to the embed code for this report can fully access all the data in the semantic model” means users can access the data shown in the report’s visuals and interactive features, but not the semantic model directly. Anonymous users cannot connect to or query the dataset using tools like DAX Studio, XMLA, or external APIs. However, if the report includes detailed tables, drillthroughs, or filters, it may still reveal sensitive or row-level data from the underlying model. Microsoft revised the warning to emphasize that report authors need to manage data exposure carefully, as Publish to Web removes authentication barriers. The technical behavior remains unchanged; the warning is just clearer to help users assess data exposure risks.
I hope this provides the clarification you needed. If you require any further assistance, please feel free to reach out.
Thank you.
Hi @PowerUp2000 ,
Thank you for following up. I understand the confusion regarding the updated warning’s wording. The phrase “any Internet user with access to the embed code for this report can fully access all the data in the semantic model” means users can access the data shown in the report’s visuals and interactive features, but not the semantic model directly. Anonymous users cannot connect to or query the dataset using tools like DAX Studio, XMLA, or external APIs. However, if the report includes detailed tables, drillthroughs, or filters, it may still reveal sensitive or row-level data from the underlying model. Microsoft revised the warning to emphasize that report authors need to manage data exposure carefully, as Publish to Web removes authentication barriers. The technical behavior remains unchanged; the warning is just clearer to help users assess data exposure risks.
I hope this provides the clarification you needed. If you require any further assistance, please feel free to reach out.
Thank you.
Hi @PowerUp2000 ,
Thank you for reaching out to the Microsoft fabric community forum.
The “Publish to Web” warning updated in July 2025 does not change how the feature works but uses clearer language to highlight possible data exposure risks.
The warning now makes it clear that anyone with the embed code can anonymously access the report and see all data shown in the report visuals. Although users cannot query the semantic model directly, the report may still display detailed data depending on the setup of visuals, filters, drill through, or tooltips.
This update is meant to help report authors evaluate privacy risks before publishing. If your report contains sensitive, proprietary, or personal data even if it seems aggregated it is recommended to use secure options like organizational sharing, embedding with authentication, or row-level security.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi v-tsaipranay,
Thank you very much for providing some further detail. However, I am still confused about the sentence in the new warning: "any Internet user with access to the embed code for this report can fully access all the data in the semantic model". This seems completely contradictory to your statement above "users cannot query the semantic model directly."
Are you able to explain why the new warning makes any reference to the semantic model? Your explanation makes it seem like users access the data shown in visuals, so it's the responsibility of the report creator to set up their visuals, fitlers, drillthroughs etc to meet their security requirements. Is there any risk that an annonymous user could access the underlying semantic model beyong what is visualised?
They are just telling you that anybody with the link will be able to see the data published, nothing is changin from before, they just stated that in a more maybe scaring way 🙂
If this helped, please consider giving kudos and mark as a solution
@me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 9 | |
| 8 | |
| 8 |