Home

Power BI - Content Not Available

%3CLINGO-SUB%20id%3D%22lingo-sub-61485%22%20slang%3D%22en-US%22%3EPower%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61485%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20add%20a%20Power%20BI%20Tab%20and%20link%20it%20up%20to%20a%20report%20I'm%20the%20only%20person%20who%20is%20able%20to%20see%20it.%20%26nbsp%3BOther%20members%20of%20the%20team%20are%20not%20able%20to%20see%20it%20and%20recieve%20the%20dreaded%20%22This%20Content%20is%20not%20available%22%20message.%20%26nbsp%3B%20Everyone%20can%20post%20their%20own%20content%20but%20nobody%20can%20see%20it.%20%26nbsp%3B%20Does%20anyone%20know%20why%20this%20is%20happening%3F%20%26nbsp%3BWhen%20I%20first%20created%20the%20team%20I%20was%20able%20to%20link%20up%20reports%20and%20I%20know%20at%20least%20one%20person%20was%20able%20to%20see%20it.%20%26nbsp%3B%20But%20something%20changed%20that%20is%20preventing%20it%20now.%20%26nbsp%3B%20Any%20assistance%20would%20be%20helpful.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-61485%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnalytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308381%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308381%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue%20for%20newer%20created%20Power%20BI%20queries.%26nbsp%3B%20Power%20BI%20support%20confirmed%20that%20this%20is%20an%20iissue%20with%20Teams%20and%20they%20raised%20a%20ticket%20at%20the%20Teams%20support.%20So%20far%20I%20did%20not%20get%20any%20feedback.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285096%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285096%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20have%20the%20same%20problem%20and%20my%20workspace%20have%20a%20premium%20capacity%20assigned.%20I%20published%20it%20in%20the%20Team's%20workgroup%20and%20nobody%20can%20see%20the%20content%20except%20me.%20It%20works%20when%20they%20go%20with%20powerbi.com%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWeird....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174893%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174893%22%20slang%3D%22en-US%22%3E%3CP%3EPower%20BI%20Premium%20has%20a%20high%20cost%20and%20may%20not%20be%20suitable%20for%20smaller%20companies%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPower%20BI%20Premium%20is%20suitable%20for%20large%20organisations%20with%20thousands%20of%20Power%20BI%20users.%20Power%20BI%20Premium%20comes%20at%20a%20fixed%20monthly%20cost%2C%20regardless%20of%20how%20many%20users%20in%20the%20organisation%20will%20use%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20small%20companies%20with%20just%20a%20couple%20of%20dozen%20Power%20BI%20users%2C%20Power%20BI%20Premium%20will%20not%20be%20a%20good%20fit.%20The%20break%20even%20point%20sits%20at%20around%205000%20Power%20BI%20Pro%20licenses.%20If%20you%20don't%20have%20that%20many%20Power%20BI%20users%2C%20Power%20BI%20Premium%20will%20cost%20you%20more%20than%20individual%20Power%20BI%20Pro%20licensing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174483%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174483%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20check%20Power%20BI%20Premium%20as%20a%20possible%20solution.%20All%20the%20internal%20users%20who%20wish%20to%20consume%20reports%2Fdashboards%20will%20benefit%20from%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-bi%2Fservice-premium%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-bi%2Fservice-premium%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers.%3C%2FP%3E%0A%3CP%3EFahad.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-111446%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-111446%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20thread%20is%20a%20bit%20old%2C%20but%20we%20just%20recently%20came%20onboard%20using%20Teams%20and%20now%20also%20trying%20to%20use%20Power%20BI.%26nbsp%3B%20I%20just%20posted%20my%20frustrations%20about%20the%20licensing%20issues%20in%20the%20Power%20BI%20community%2C%20but%20would%20like%20to%20vent%20my%20frustrations%20here%20as%20well.%3C%2FP%3E%3CP%3EIt%20doesn't%20make%20sense%2C%20licensing-wise%2C%20that%20it%20is%20possible%20to%20post%20a%20global%20link%20for%20anyone%20to%20see%20a%20report%20%2C%20but%20for%20internal%20publication%20in%20Teams%20it%20is%20not%20possible%2C%20a%20Power%20BI%20license%20is%20required.%26nbsp%3B%20For%20that%20reason%20we%20have%20shelved%20Power%20BI.%3C%2FP%3E%3CP%3ETore%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61859%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61859%22%20slang%3D%22en-US%22%3E%3CP%3EOr%20another%20way%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPublish%20the%20report%20in%20My%20Workspace%2C%20create%20a%20dashboard%20and%20share%20that%20dashboard%20with%20all%20my%20team%20members%20via%20the%20dashboard%20sharing%20option.%20Then%20add%20a%20Power%20BI%20tab%20in%20Teams%20and%20point%20to%20the%20report.%20Because%20the%20dashboard%20is%20shared%2C%20everybody%20who%20it%20is%20shared%20with%20will%20also%20be%20able%20to%20see%20the%20report.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61816%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61816%22%20slang%3D%22en-US%22%3E%3CP%3EI%20took%20what%20Juan%20mentioned%20below%20and%20did%20someting%20a%20little%20differently.%26nbsp%3B%26nbsp%3B%20I%20have%20links%20to%20to%20my%20Power%20BI%20reports%20on%20our%20Team%20site.%26nbsp%3B%20I%20copied%20those%20links%20and%20pasted%20them%20into%20a%20Wiki%20tab%20in%20Teams.%26nbsp%3B%26nbsp%3B%20Now%20this%20may%20prove%20to%20be%20a%20pain%20because%20of%20having%20to%20update%20the%20hyperlinks.%26nbsp%3B%26nbsp%3B%20But%20at%20least%20staff%20has%20easy%20access%20to%20the%20reports.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61810%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61810%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20Power%20BI%20Pro%20is%20required%20for%20other%20team%20members%20to%20view%20the%20report%20then%20this%20function%20is%20completely%26nbsp%3B%20worthless.%26nbsp%3B%20As%20already%20mentioned%20above%2C%20the%20cost%20for%20the%20entire%20staff%20to%20have%20a%20Pro%20license%20is%20unreasonable%20just%20to%20be%20able%20to%20%22view%22%20reports.%26nbsp%3B%26nbsp%3B%20I%20have%20a%20Pro%20license%20because%20I'm%20one%20of%20a%20handful%20of%20Power%20BI%20%22users%22.%26nbsp%3B%20Our%20staff%20uses%20the%20reports%20I%20build%20for%20informational%20purposes%20to%20keep%20track%20of%20various%20things.%26nbsp%3B%26nbsp%3B%20They%20don't%20manipulate%20the%20data.%26nbsp%3B%20Now%20in%20teams%20they%20aren't%20able%20to%20see%20the%20same%20info%3F%26nbsp%3B%20Makes%20no%20sense.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61608%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61608%22%20slang%3D%22en-US%22%3EYeap%2C%20forget%20this%20part...indeed%20this%20is%20a%20common%20practices%20Microsoft%20is%20following%20not%20only%20with%20Teams%20but%20also%20with%20other%20staff%20that%20allows%20to%20display%20Power%20BI%20content%20such%20as%20the%20Power%20BI%20WebPart%20for%20modern%20pages...a%20possible%20workaround%20that%20is%20not%20secure%20consist%20on%20the%20following%3A%3CBR%20%2F%3E(1)%20Publish%20your%20PowerBI%20report%20using%20the%20option%20of%20publishing%20in%20the%20web%3CBR%20%2F%3E(2)%20Grab%20the%20publishing%20code%20for%20the%20report%20and%20paste%20it%20on%20a%20script%20editor%20WebPart%20you%20have%20added%20to%20a%20SPO%20page%20of%20your%20Teams%20site.%3CBR%20%2F%3E(3)%20Add%20a%20new%20Tab%20in%20the%20Team%20pointing%20to%20the%20page%20where%20you%20added%20the%20Power%20BI%20embedded%20report%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61557%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61557%22%20slang%3D%22en-US%22%3E%3CP%3EVery%20common%20feedback%20about%20the%20current%20model%20that%20PowerBI%20is%20using.%20Those%20trial%20licenses%20will%20let%20you%20keep%20renewing%20them%20forever%20in%20my%20experience%2C%20but%20agreed%20that%20this%20is%20not%20a%20viable%20long%20term%20solution.%20Microsoft%20will%20probably%20point%20you%20towards%20upgrading%20to%20an%20E5%20license%20for%20your%20scenario.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61551%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61551%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20a%20licensing%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20trial%20Power%20BI%20Pro%20license.%20Sharing%20with%20O365%20Groups%2FTeams%20is%20a%20Pro%20feature%20and%20all%20people%20who%20want%20to%20consume%20the%20report%20published%20to%20the%20team%20space%20must%20have%20a%20Pro%20license.%20The%20other%20team%20members%20don't%20have%20a%20pro%20license.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20way%20too%20expensive.%20The%20Power%20BI%20Pro%20license%20costs%20us%20more%20than%20the%20Office%20365%20subscription%20and%20my%20company%20will%20never%20buy%20Power%20BI%20Pro%20for%20every%20user%20in%20the%20organisation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20limitation%20is%20not%20conducive%20to%20promoting%20Office%20365%20adoption.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61548%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61548%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20are%20the%20steps%20to%20%22properly%20publish%22%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Power%20BI%20Desktop%2C%20I%20click%20Publish.%3C%2FP%3E%3CP%3EI%20select%20the%20Team%20space%2C%20not%20my%20workspace.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F13124i55A8D35564226E77%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%222017-04-12_10-09-52.png%22%20title%3D%222017-04-12_10-09-52.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20confirm%20all%20the%20dialogs.%3C%2FP%3E%3CP%3EI%20get%20%22Success%22.%3C%2FP%3E%3CP%3EMy%20team%20members%20can't%20see%20the%20report%20in%20the%20tab%20for%20Power%20BI%20in%20Teams.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3BI%20still%20don't%20know%20where%20the%20problem%20is.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20would%20you%20recommend%20next%3F%20What%20do%20I%20need%20to%20do%20differently%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61534%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61534%22%20slang%3D%22en-US%22%3EAs%20David%20has%20said%2C%20you%20need%20to%20properly%20publish%20the%20PowerBI%20dashboard%20so%20others%20can%20see%20it...you%20can%20test%20it%20easily%20asking%20your%20colleagues%20to%20access%20the%20dashboard%20out%20of%20teams%20so%20if%20they%20are%20not%20able%20to%20see%20it%2C%20yo%20know%20where%20the%20problem%20is%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61520%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61520%22%20slang%3D%22en-US%22%3E%3CP%3EI%20see%20exactly%20the%20same%20thing.%20I%20published%20a%20report%20to%20my%20team's%20workspace.%20I%20can%20see%20it%20in%20the%20team%20workspace%20in%20the%20Power%20BI%20Service%20in%20the%20browser%20and%20I%20can%20see%20it%20in%20the%20Power%20BI%20tab.%20But%20my%20other%20team%20members%20don't%20see%20it%20in%20the%20tab%2C%20not%20even%20listed%20as%20a%20possible%20report%20to%20add.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20670px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F13119i768634DCD5FD90BC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222017-04-12_8-28-46.png%22%20title%3D%222017-04-12_8-28-46.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61491%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61491%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20checked%20the%20permissions%20on%20your%20dashboard%2Freport%20to%20make%20sure%20those%20people%20who%20are%20getting%20those%20errors%20have%20permissions%3F%20If%20your%20content%20is%20coming%20from%20a%20different%20workspace%20than%20the%20team's%2C%20you'll%20need%20to%20share%20it%20with%20people%20appropriately.%20Adding%20a%20PowerBI%20tab%20is%20not%20actually%20granting%20that%20permission%2C%20it%20is%20only%20displaying%20to%20people%20who%20have%20access.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheck%20here%20for%20how%20to%20share%20in%20PowerBI%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fpowerbi.microsoft.com%2Fen-us%2Fdocumentation%2Fpowerbi-service-share-unshare-dashboard%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpowerbi.microsoft.com%2Fen-us%2Fdocumentation%2Fpowerbi-service-share-unshare-dashboard%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-720118%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-720118%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F114849%22%20target%3D%22_blank%22%3E%40Karlheinz%20Rettig%3C%2FA%3E%26nbsp%3BHere%20is%20a%20solution.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20publishing%20your%20report.%20Got%20to%20File%20and%20Select%20Embed%20as%20shown%20in%20the%20diagram%20below%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20313px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120603i99DA2274584F96D8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22embedd.JPG%22%20title%3D%22embedd.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20on%20the%20resultant%20Pop-up%20screen%3B%20Copy%20the%20link%20as%20shown%20below%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20580px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120605i238D9E698EFDC48A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Pop%20Up.JPG%22%20title%3D%22Pop%20Up.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThen%20Go%20Teams%2C%20Add%20a%20Tab%20and%20paste%20the%20copied%20URL%20in%20the%20URL%20section.%20Give%20your%20Tab%20a%20Proper%20name%20and%20Save!!%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20has%20worked%20for%20me.%20It's%20just%20like%20embedding%20on%20a%20Website%20for%20public%20viewing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017543%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20BI%20-%20Content%20Not%20Available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017543%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F114849%22%20target%3D%22_blank%22%3E%40Karlheinz%20Rettig%3C%2FA%3E%26nbsp%3Bdid%20Microsoft%20get%20back%20to%20you%20regarding%20this%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

When I add a Power BI Tab and link it up to a report I'm the only person who is able to see it.  Other members of the team are not able to see it and recieve the dreaded "This Content is not available" message.   Everyone can post their own content but nobody can see it.   Does anyone know why this is happening?  When I first created the team I was able to link up reports and I know at least one person was able to see it.   But something changed that is preventing it now.   Any assistance would be helpful.  

17 Replies
Highlighted

Have you checked the permissions on your dashboard/report to make sure those people who are getting those errors have permissions? If your content is coming from a different workspace than the team's, you'll need to share it with people appropriately. Adding a PowerBI tab is not actually granting that permission, it is only displaying to people who have access.

 

Check here for how to share in PowerBI: https://powerbi.microsoft.com/en-us/documentation/powerbi-service-share-unshare-dashboard/

Highlighted

I see exactly the same thing. I published a report to my team's workspace. I can see it in the team workspace in the Power BI Service in the browser and I can see it in the Power BI tab. But my other team members don't see it in the tab, not even listed as a possible report to add.

2017-04-12_8-28-46.png

 

 

Highlighted
As David has said, you need to properly publish the PowerBI dashboard so others can see it...you can test it easily asking your colleagues to access the dashboard out of teams so if they are not able to see it, yo know where the problem is
Highlighted

What are the steps to "properly publish"?

 

In Power BI Desktop, I click Publish.

I select the Team space, not my workspace.

2017-04-12_10-09-52.png

I confirm all the dialogs.

I get "Success".

My team members can't see the report in the tab for Power BI in Teams. 

 

@Juan Carlos González Martín I still don't know where the problem is. 

 

What would you recommend next? What do I need to do differently?

Highlighted

It's a licensing issue.

 

I have a trial Power BI Pro license. Sharing with O365 Groups/Teams is a Pro feature and all people who want to consume the report published to the team space must have a Pro license. The other team members don't have a pro license.

 

This is way too expensive. The Power BI Pro license costs us more than the Office 365 subscription and my company will never buy Power BI Pro for every user in the organisation.

 

This limitation is not conducive to promoting Office 365 adoption. 

Highlighted

Very common feedback about the current model that PowerBI is using. Those trial licenses will let you keep renewing them forever in my experience, but agreed that this is not a viable long term solution. Microsoft will probably point you towards upgrading to an E5 license for your scenario.

Highlighted
Yeap, forget this part...indeed this is a common practices Microsoft is following not only with Teams but also with other staff that allows to display Power BI content such as the Power BI WebPart for modern pages...a possible workaround that is not secure consist on the following:
(1) Publish your PowerBI report using the option of publishing in the web
(2) Grab the publishing code for the report and paste it on a script editor WebPart you have added to a SPO page of your Teams site.
(3) Add a new Tab in the Team pointing to the page where you added the Power BI embedded report
Highlighted

If Power BI Pro is required for other team members to view the report then this function is completely  worthless.  As already mentioned above, the cost for the entire staff to have a Pro license is unreasonable just to be able to "view" reports.   I have a Pro license because I'm one of a handful of Power BI "users".  Our staff uses the reports I build for informational purposes to keep track of various things.   They don't manipulate the data.  Now in teams they aren't able to see the same info?  Makes no sense. 

Highlighted

I took what Juan mentioned below and did someting a little differently.   I have links to to my Power BI reports on our Team site.  I copied those links and pasted them into a Wiki tab in Teams.   Now this may prove to be a pain because of having to update the hyperlinks.   But at least staff has easy access to the reports. 

Highlighted

Or another way:

 

Publish the report in My Workspace, create a dashboard and share that dashboard with all my team members via the dashboard sharing option. Then add a Power BI tab in Teams and point to the report. Because the dashboard is shared, everybody who it is shared with will also be able to see the report. 

Highlighted

This thread is a bit old, but we just recently came onboard using Teams and now also trying to use Power BI.  I just posted my frustrations about the licensing issues in the Power BI community, but would like to vent my frustrations here as well.

It doesn't make sense, licensing-wise, that it is possible to post a global link for anyone to see a report , but for internal publication in Teams it is not possible, a Power BI license is required.  For that reason we have shelved Power BI.

Tore

Highlighted

Hi,

 

Please check Power BI Premium as a possible solution. All the internal users who wish to consume reports/dashboards will benefit from this.

 

https://docs.microsoft.com/en-us/power-bi/service-premium

 

Cheers.

Fahad.

Highlighted

Power BI Premium has a high cost and may not be suitable for smaller companies

 

Power BI Premium is suitable for large organisations with thousands of Power BI users. Power BI Premium comes at a fixed monthly cost, regardless of how many users in the organisation will use it.

 

For small companies with just a couple of dozen Power BI users, Power BI Premium will not be a good fit. The break even point sits at around 5000 Power BI Pro licenses. If you don't have that many Power BI users, Power BI Premium will cost you more than individual Power BI Pro licensing.

Highlighted

Hi, I have the same problem and my workspace have a premium capacity assigned. I published it in the Team's workgroup and nobody can see the content except me. It works when they go with powerbi.com

 

Weird....

Highlighted

I have the same issue for newer created Power BI queries.  Power BI support confirmed that this is an iissue with Teams and they raised a ticket at the Teams support. So far I did not get any feedback. 

Highlighted

@Karlheinz Rettig Here is a solution. 

 

After publishing your report. Got to File and Select Embed as shown in the diagram below;

embedd.JPG

 

Then on the resultant Pop-up screen; Copy the link as shown below;

Pop Up.JPG

Then Go Teams, Add a Tab and paste the copied URL in the URL section. Give your Tab a Proper name and Save!! :) 

 

It has worked for me. It's just like embedding on a Website for public viewing.

 

Highlighted

@Karlheinz Rettig did Microsoft get back to you regarding this issue?

Related Conversations