Unable to Publish Report to Web - Public

[SimpleMan]

I've created my Power BI report in Power BI Desktop then published it to Power BI Workspace which I created from the web portal. When I open it up from app.powerbi.com and select File -> Embed Report -> Publish to web (public), I get a message saying:

"You can't create an embed code because the report is not eligible for use with Publish to web."

Under Admin Portal -> Tenant Settings -> Publish to Web, the "Enabled" setting is selected and "Allow existing and new codes" is also enabled.  There also is a message that says "To enable Publish to Web, you need to disable Block Public Internet Access first."...this is also disabled.

Any suggestions would be much appreciated.

[Polomendez]

Hola

a mi tampoco me permite publicarlo, me manda el mensaje 

Soy usuario PRO, hice un dashboard con una simple tarjeta a modo de prueba y tampoco me permite hacerlo, me sigue apareciendo el error.

Que me hace falta hacer, como lo puedo solucionar?

[SimpleMan]

Greg - thanks for the response.  I'll look through this list.

[SimpleMan]

Greg - I believe there may have been a couple of items on that list that were causing my issue and I think I know what I did to cause that.  I recreated a new dataset and then copied the visuals from another project and it seemed to work.  I'm going to leave this open for the time being until I can confirm the 2nd page I'll add tomorrow works. 

[SimpleMan]

All good.  Thanks.  New to PowerBI and I have a lot to learn.

[SimpleMan]

I do have a valid license, as you can see below.

[Greg_Deckler · Accepted solution]

@SimpleMan Perhaps you are using a feature that is not supported by Publish to Web, like row-level security for example:

• Reports using row-level security.
• Reports connecting to data using DirectQuery. Connect using composite or import mode instead. Read about the differences between the modes.
• Reports using any Live Connection data source, including Analysis Services Tabular hosted on-premises, Analysis Services Multidimensional, and Azure Analysis Services.
• Reports using a shared dataset that is stored in a different workspace from the report.
• Shared and certified datasets.
• Reports shared to you directly or through an app.
• Reports in a workspace in which you aren't an edit member.
• "R" and Python visuals aren't currently supported in Publish to web reports.
• Exporting data from visuals in a report that has been published to the web.
• Q&A for Power BI visuals.
• Reports containing report-level DAX measures.
• Single sign-on data query models, including composite models on Power BI datasets or Azure Analysis Services.
• Secure confidential or proprietary information.
• The automatic authentication capability provided with the Embed option doesn't work with the Power BI JavaScript API. For the Power BI JavaScript API, use the user owns data approach to embedding.
• Admins can block public internet access, as described in Private links for accessing Power BI. In that case, the Publish to Web option is grayed out for your tenant in the Power BI admin portal.
• License enforcement for custom visuals.
• Uncertified visuals from the organizational store, when the global tenant switch of the organization for uncertified visuals is on.
• Public visuals from the organizational store, when the global tenant switch of the organization doesn't allow visuals created using the Power BI SDK.
• Paginated reports

Publish to web from Power BI - Power BI | Microsoft Learn

[foodd]

Yup, that is the long list 🙂