Power BI has a full set of features that allows you to create and host reports for your organization to interact with. However, these reports are within the Power BI environment and outside users or applications won't be able to view or render them. In this course, Building Your First Application with the Power BI REST API, you will learn how to call the API endpoints and render Power BI objects within an application that lives outside of Power BI. First, you will learn how to register an app in Azure. Next, you will discover how to implement a web API that will fire off requests against Power BI. Finally, you will explore how to create a front-end application to render the objects. When you're finished with this course, you will have the skills and knowledge of the Power BI endpoints needed to render and retrieve any object externally to Power BI.
Auret is a technical trainer, mentor and tech enthusiast with 10 years experience in delivering technical courses. He has also delivered Webinars and Blogs on various different topics.
Section Introduction Transcripts
Section Introduction Transcripts
Course Overview Hi everyone. My name is Auret Swanepoel, and welcome to my course, Building Your First Application with the Power BI REST API. I am a frontend developer at Servcorp and a big advocator for Power BI. Power BI is gaining immense popularity and is growing as one of the lead competitors in the marketplace. In this course, we are going to be looking at the fundamental steps for getting Power BI objects in an external application. Some of the major topics that we will cover include creation of an Azure app registration, configuring your environment, calling Power BI API endpoints, and embedding reports using Angular. By the end of this course, you'll know what the minimal requirements are for embedding, and be able to embed any report in an external application. Before beginning the course, you should have a basic understanding of C#, Angular, and PowerShell. I hope you'll join me on this journey to learn Power BI embedding with the Building Your First Application with the Power BI REST API course, at Pluralsight.
Intro of the Power BI Rest API Hi, I am Auret Swanepoel, and welcome to an introduction to the Power BI Rest API. In this module, we will be covering how you can use the Power BI APIs as a developer, and some of the more common tasks performed by developers.
Securing Your Reports for Use Outside of Power BI Hi, I am Auret Swanepoel, and in this module, we will be talking about how to approach Securing Your Reports for Use Outside of Power BI. This is crucial to understand, as it takes a different approach depending on your requirements. In this module, we will lay out the two different approaches to embedding, that is embedding for your customers or embedding for your organization. Embedding for your customers is the ability to extend Power BI beyond your Azure tenancy. In short, it means that you can provide anybody access to Power BI reports or other items. This is possible as we can use a master account and embed tokens to validate the request for a resource. Whereas embedding for your organization is a little easier. To successfully embed a report or any item from Power BI for an organizational user, you must provide them with an access token. The access token is then used on a pre-request basis to determine if the user has access to that requested resource.
Finalizing the Back-end Logic Hey, I am Auret Swanepoel, and in the following module, we will be tying up all the loose ends that remain in the backend code. The module in front of us will be mainly driven by demonstrations and will give you a clear view on what is needed in the final part of your Web API. Now we have a few pieces that need to be finished off in the backend before we move on to the frontend logic. And in this module, that focus will be the backend. Now the backend logic will require you to get a hold of the application ID of the app you've registered. This is the app registration process we've covered earlier. The ID is then added into the web.config file to be referenced when needed. Next, we will cover what logic is needed to be able to query reports, either as a list of reports or on an individual basis if needed. This will allow the frontend user to pick from a list of reports and choose which one they want to render. Once we have the logic in place to fetch the reports on demand, we will finish off the module by creating a method that will allow the frontend application to get a hold of an object containing the embed information.