It looks like MS has updated the Content Security Policies for app.powerbi.com. The underlined scripts were missing yesterday, causing the included domains to be sent to Umbrella and potentially blocked.
We have resolved the issue as well by adding the URL to the Cisco Umbrella. I'm disappointed that Microsoft has not added this to the list of known issues. It would have saved a lot of investigation time and frustration for our end users. It's not acceptable for this kind of issue to arise without it being dealt with in a proper and timely manner.
@AdrianPalumbo_H Here's a couple other things to try from earlier in this thread.
some have gotten it to work again with the simpler app.powerbi.com url
some have cleared their cache and it works after that (do browsing history and cookies if not all)
At one point v-yetao1-msft (Community Support) admitted there was a problem and said MS was looking into it. Then she/he abandoned the thread. Never to be heard from again on this topic that I have seen.
This happened after updating the gateway 11/27. Some got disable cdn and signon# added to URL. Most of ours seemed to work after clearing the cache but would come back for some folks. That's all I know but if you read up you may see somthing I missed.
The redirection is triggered by the Cisco proxy, not Microsoft. Because it is Cisco's logic. Only Cisco can provide an answer to this. Please advise your customer to request an RCA from Cisco. It is hard for Microsoft to give an RCA for an issue owned Cisco.
The redirect was in our case indeed triggered by Cisco Umbrella, but the casuse of the redirect was that parts of the content security policy were missing, for at least a week. Cisco Umbrella worked as designed, this was due to a botched update of the PBI service.
The RCA should done at Microsoft to determine how you could make a release with an incomplete CSP. It would be really embarrasing for Microsoft if you should botch a second release in this manner.
Once again, Cicsco Umbrella worked as advertised. It reacted, as it should, on an incomplete URL header that was missing necessary CSP content.
Hi all ,
Issue has been solved by whitelisting https://content.powerapps.com
Best Regards,
Community Support Team _ Ailsa Tao