Execute the PowerShell Script in Windows PowerShell ISE

Set up PowerShell

1. Download the PowerShell script file and extract the contents to a folder on your local system. You can run the script either on Windows or via Azure Cloud Shell.

   Running the Script on Windows:

   1. Press the Windows key, search for Windows PowerShell ISE, and Run as Adminstrator.

      
   2. Click on File > Open... from the top menu to open the script file.

      
   3. Navigate to the extracted folder and select the script inside the LoadFAST Windows PowerShell Script folder.

      
   4. Press F5 key or click the green Play button in the toolbar to execute the script.

      
   5. The script will begin execution and prompt you for input. Provide the required information as requested.

      

   {% hint style="warning" %} The Windows PowerShell ISE must be opened in the same location as the downloaded PowerShell zip. {% endhint %}

   For running script in Azure cloud shell

   1. Open Azure portal and launch Azure cloud shell.

   

   1. Click Switch to PowerShell.

   

   1. Click Manage files to upload your script.

   

   1. Upload both files from LoadFAST Azure PowerShell Script inside the extracted folder.

   

   1. Run the script using & './Azure Cloud PowerShell Script.ps1' command.

   2. The script will prompt you for required input. Fill in the information as needed.

      

      If you see an error message after entering inputs

      

      Click on New session and re-run the script.

      
   3. You’ll be prompted to log in. Copy the code shown and click the provided link.

      
   4. Paste the code into the login screen and sign in with your account.

      
   5. After logging in, enter your client secret when prompted. The script will now run successfully.

      

Provide inputs for the prompts

Enter your tenant ID

Follow the steps below to find your tenant ID:

1. Type “App registrations" in the Azure portal search bar and select said option as it appears.

   
2. Find and select the application registration previously created for the LoadFAST API on the list.

   
3. This takes you to its summary page where you can find the directory (tenant) ID and copy it directly to your clipboard.

   
4. In the PowerShell terminal, paste/enter the subscription ID from the previous step.

Enter your subscription ID

Follow the steps below to find your subscription ID:

1. Type “Resource groups" in the Azure portal search bar and select said option as it appears.

   
2. Once on the page, you will see a list of resource groups displayed. Select the resource group where you want to deploy the tool resources to. This can be resource group

   
3. Copy the subscription ID as shown below.

   
4. In the PowerShell terminal, paste/enter the subscription ID from the previous step.

Enter your resource group name

1. Type “Resource groups" in the Azure portal search bar and select said option as it appears.\

   
2. Once on the page, you will see a list of resource groups displayed. Select the resource group that you have used earlier to create the managed application.

   
3. Find and select the managed application as shown in the image below:\

   
4. Copy the name of the managed resource group.

1. Paste/enter the managed resource group name in the PowerShell terminal like the previous steps.

Log into Azure through the PowerShell pop-up window

If already logged into Azure, it will ask you to pick an account. If not, then you need to sign in with your Azure account.

Other details

• See the output and any actions performed by the script in the console pane at the bottom of the PowerShell window.

  
• To verify the backend deployment, follow these steps:

  1. Type “Kubernetes services" in the Azure portal search bar and select said option as it appears.

     
  2. Once on the page, you will see a list of Kubernetes clusters displayed. Select the Kubernetes cluster created for your web app (more information regarding cluster name detailed in the note).

     {% hint style="info" %}Note: Kubernetes clusters are automatically created and named as follows: "WebAppName_AksCluster".

     In our case, our web app was named "powerbiloadanalyzer" (as seen in step 4 of this process). Thus, our Kuberenetes cluster name is "powerbiloadanalyzer_AksCluster". {% endhint %}

     

     3. Select **Workloads** (under Kubernetes resources) from the left pane.

     
  3. Under the Deployments tab, you can see all the deployments. Ensure that they all have a green tick in the Ready column.