Pre-installation tasks for Azure SQL Database

If you plan to host your AVEVA PI Vision SQL database on Azure SQL Database, complete these pre-installation tasks before installing AVEVA PI Vision.

Note: Azure SQL Managed Instance is not supported.

1. Obtain a subscription to Azure SQL services on the Azure portal.

2. Determine which authentication method you will use to connect to Azure SQL Database both to run the Go.ps1 script to create the AVEVA PI Vision database and afterwards to add permissions for the AVEVA PI Vision web services.

   The available authentication methods are:

   SQL Server authentication

   Microsoft Entra authentication (supports the authentication models listed below; for more information about each model refer to Authenticate with Microsoft Entra ID in sqlcmd)

   Note: If you plan to use Microsoft Entra Authentication for AVEVA PI Vision web services to connect to Azure SQL Database during application runtime, you will need additional Microsoft Entra authentication credentials to run the commands in Add permissions to the PI Vision database for web services after running the scripts to create the Azure SQL database.

   • Default (ActiveDirectoryDefault)

   • Integrated (ActiveDirectoryIntegrated)

   • Microsoft Entra password (ActiveDirectoryPassword)

   • Interactive (ActiveDirectoryInteractive)

   • System or User Assigned Managed Identity (ActiveDirectoryManagedIdentity)

     Note: The System or User Assigned Managed Identity option can be used only if you are using an Azure-hosted VM for the machine on which you will run the Go.ps1 script to create the PI Vision Azure SQL database and then grant permissions to the AVEVA PI Vision web services (typically the machine on which you will install AVEVA PI Vision).

   • Service Principal (ActiveDirectoryServicePrincipal)

3. Determine which authentication method you will use for AVEVA PI Vision web services to connect to the Azure SQL database during application runtime.

   The available authentication methods are:

   SQL Server authentication

   Note: SQL Server authentication is not recommended due to the need to store the password in AVEVA PI Vision’s web.config in plain text. Refer to Modify the PI Vision web.config file for details.

   Microsoft Entra authentication (supports the authentication models listed below; for more information about each model refer to Authenticate with Microsoft Entra ID in sqlcmd)

   • Default (ActiveDirectoryDefault)

   • Microsoft Entra password (ActiveDirectoryPassword)

     Note: The Microsoft Entra password option is not recommended due to the need to store the password in AVEVA PI Vision’s web.config in plain text. Refer to Modify the PI Vision web.config file for details.

   • System or User Assigned Managed Identity (ActiveDirectoryManagedIdentity)

     Note: The System or User Assigned Managed Identity option can be used only if the machine on which you will install AVEVA PI Vision is an Azure-hosted VM.

   • Service Principal (ActiveDirectoryServicePrincipal)

4. If AVEVA PI Vision web services will authenticate with the Azure SQL database using an Azure Managed Identity for application runtime after installation, you must implement the following items:

   • System Assigned Managed Identity - Ensure that the System Assigned Managed Identity is enabled on the Azure VM on which AVEVA PI Vision will be installed. Refer to Configure managed identities on Azure virtual machines (VMs) for details on how to enable the identity on an Azure VM

   • User Assigned Managed Identity - Ensure that the User Assigned Managed Identity is assigned to the Azure VM on which AVEVA PI Vision will be installed. Refer to Configure managed identities on Azure virtual machines (VMs) for details on how to assign an identity to an Azure VM.

5. Ensure that the correct permissions are granted to the account that will be authenticating with Azure SQL Database to run the go.ps1 script to create the PI Vision Azure SQL database and then afterwards to assign permissions to AVEVA PI Vision web services. To review the permissions required to create the database, refer to Required SQL permissions.