Parallels DaaS: Configure Azure prerequisites

this video is part of our parallels techbite Series this video covers configuring the prerequisites in Azure to prepare for a deployment of parallel stas this is the Azure portal we have already logged on to the subscription at this point no resource groups start with parallels and when switching to the app registration section of entra ID there are no app registrations that start with parallels this is our starting point now switch to a Powershell window and start the parallels Das prerequisites configuration script the script will import any required modules in case these are not imported yet Now log on with your administrative credentials make sure this account has owner permissions on the subscription and Global admin permission in Microsoft Ventra ID and make sure MFA for this account is enabled once complete close the browser again the Powershell script now shows at isure tenants you might have access to depending on your permissions there could be multiple tenants in this list select the tenant you want to use and press enter the Powershell script now shows Azure subscriptions underneath the tenant you selected and have access to depending on your permissions there could be multiple subscriptions in this list select the subscription you want to use and press enter now select the location of the Azure region you want to use and press enter parallels St requires two resource groups the script will create them for you first provide the name of the resource Group where you want to store the parallels D infrastructure components and press enter now provide the resource Group name where you want to store the parallels Das virtual machines and press enter next provide the name of the app registration and press enter the script creates the app registration if app registration does not exist yet and adds the required permissions optionally provide the name of an Azure key Vault to create we advise you to do so as this allows storing secure strings like app registration secrets that are required later in the parallels Dash setup this was the last step within a few seconds the script will finish the output of the script consists of the tenant ID subscription ID application ID and Resource Group names this information is needed in the next step if you did not select the option to create an Azure key Vault store the client Secret show them in the output in a safe place switching back to the Azure portal note that two resource groups have been created the infrastructure resource group contains the Azure keyal and the virtual machine Resource Group is currently empty furthermore an app registration now exists including a client secret if you selected the option to create an Azure key Vault the client secret is safely stored in there as a secret value later on you can copy the client secret to your clipboard from here during the parallels Das deployment wizard again store the output of the Powershell script in a safe place before continuing with that next step this concludes the video on configuring the prerequisites in Azure to prepare for a deployment of Parallels stas for more content subscribe to our Channel and browse to the tech bite series