Set up Power BI and Azure
Detailed below are the Power BI capacity and Azure CLI-related prerequisite steps to set up the LoadFAST.
Last updated
Detailed below are the Power BI capacity and Azure CLI-related prerequisite steps to set up the LoadFAST.
Last updated
Ensure you have at least one embedded or premium Power BI capacity to use LoadFAST on. If one is not available, follow the steps detailed below to create a capacity:
Log into the Azure portal.
Type “Power BI Embedded" in the search bar and select said option as it appears.
Click on Create.
Fill in the required information and then click on Review + Create.
PROJECT DETAILS
Subscription: Choose the same subscription that will be used to deploy the LoadFAST tool in Azure Marketplace.
Resource group: Choose a resource group. The resource group should be inside the same tenant/subscription that will be used to deploy the LoadFAST tool.
RESOURCE DETAILS
Resource name: Create and enter a name. This is the embed capacity name and will be used for the Assign capacity to your Power BI workspace steps (in pre-deployment) and the steps following it.
Location: Choose a location.
Size: This is the Power BI embed capacity size. Select the resource size that best meets your needs.
Power BI capacity administrator: Enter the relevant user.
You need an active Azure subscription to deploy resources.
You need to grant yourself the “Owner” (Privileged Administrator) role for the subscription to create a managed application. This gives you full ownership and extensive permissions. Follow the steps listed below to assign yourself the Owner role:
Type “Subscriptions" in the Azure portal search bar and select said option as it appears.
Click on your subscription's name to open its overview page.
Select Access Control (IAM) from the left pane.
Click on Add and select Add role assignment from the drop-down pane.
Select the Privileged administrator roles subsection and search for Owner in the search box.
Select the Owner role and click on Next at the bottom of the page.
Click on Select members.
Search for your account ID in the Select entry field and select it.
Review the details. Click on Review + assign to complete the process.
You need to have a resource group (in the Azure subscription) where all the resources related to this application will be deployed.
Having Owner access grants you full control over the subscription, allowing you to create, manage, and delete resources.
You must have Owner access within the Azure subscription to deploy resources (follow the steps detailed in point 2. to assign this access).
You must have the necessary CPU cores quota inside the subscription for the Kubernetes resource to be deployed successfully. Follow the steps below to check or assign the Kubernetes Regional Cores Quota:
Type "Subscriptions" in the Azure portal search bar and select said option as it appears.
Select Usage + quotas (under Settings) from the left pane. Use the filter next to the search bar to ensure the grid is filtered to Compute.
Search for Standard DASv4 Family vCPU.
Calculate the available cores needed (maximum concurrent load count * 2).
Note: The maximum concurrent load count value is the largest number that you will enter under Load testing count in the tool. This is the highest number of simulated users you want to test using your Power BI reports/pages.
In the Deployment section, you will be asked to select your maximum concurrent load count from a list of predetermined options. To ensure the tool runs smoothly and quotas align, the maximum concurrent load count value used in the calculation here needs to be to one of the predetermined options:
30
40
50
75
100
150
200
Example: If the maximum concurrent load count value needed is 175, we can either round up to 200 or round down to 150. We recommend rounding up for more flexibility but do what best suits your organization's resources.
Warning: The option selected for the maximum concurrent load count value later in the Deployment section CANNOT be increased after deployment. If an increase is needed, the tool will have to be re-deployed and re-set up from the beginning.
Take this into consideration as you select an option.
Example:
If 100 was selected as the maximum concurrent load count value but...
I only need 50 --> The load limit can be reduced directly within the tool.
I need 150 --> The tool will have to be re-deployed.
For the region where you want to deploy the LoadFAST tool in, check if the Current usage value meets the available cores needed value (e.g., in the image below, the Current usage value is 40 of 1,500).
Example:
Maximum concurrent load count = 200
Available cores needed = maximum concurrent load count * 2 = 200 * 2 = 400
If the Current usage value is 50 of 500, it means 450 is available. Since we only need 400, this means that there are enough cores available.
If your subscription does not have enough cores, then increase the core quota limit by clicking on the pencil icon under the Adjustable column.
Enter the new limit required (400 is used as an example value in the image). Click on Submit and wait for the request to process.
A pop-up page, as shown below, will appear once the request is successfully processed.
