This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi, I've created 'Secure embed codes' for quite a while but - until today - the format of these codes never contained the query string parameters: reportId, autoAuth and ctid.
An example report for which I created a secure embed code without these query string parameters earlier today is here:
https://app.powerbi.com/view?r=eyJrIjoiYjg0OTFkYjgtYmU4YS00MzNhLThlZTctN2ViY2U0NTllMDM4IiwidCI6ImExM...
However, just in the last hour PowerBI Service generated a different type of secure embed code for exactly the same report (after I had to make some changes in Service due to some applied colour changes not coming through in Service).
https://app.powerbi.com/reportEmbed?reportId=3729aef8-b59b-4fc0-945b-b28a4776fbef&autoAuth=true&ctid...
There are some subtle differences, in particular:
I've tried to find out more about secure embed codes and from what I'm reading it appears the latter type is standard.
Can anyone explain the difference in both secure embed codes and why I've only ever been able to create the former type of embed code?
Thanks, Bastiaan
Solved! Go to Solution.
Thanks @GilbertQ , just read up on the difference, that make sense now.
I'm just at a loss because the 'Publish to Web' option wasn't available from File earlier, which is how I (unwittingly) ended up creating the Secure embed code but now it's back again. 🤔
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 14 | |
| 10 | |
| 9 | |
| 7 | |
| 6 |
| User | Count |
|---|---|
| 33 | |
| 28 | |
| 26 | |
| 19 | |
| 16 |