Configuring Azure SQL Managed Instance as the Backend Database

Azure SQL Managed Instance is a managed database service provided by Microsoft Azure, designed to offer SQL server capabilities in the cloud. It is ideal for migrating existing on-premises SQL server applications to the cloud with minimal changes, offering high compatibility and feature parity with on-premises SQL server.

Benefits of Using Azure SQL Managed Instance for PAM360

  • High Compatibility: Ensures minimal changes are required when migrating PAM360's backend from an on-premises SQL server to the cloud.
  • Managed Service: Reduces administrative overhead with automated backups, patching, and maintenance.
  • Scalability: Allows PAM360 to grow by adding more compute and storage resources as needed.

Caution: If you have installed the PAM360 application on an on-premise server instead of an Azure Virtual Machine, ensure proper connectivity between the on-premise server and the Azure server.

Note: There is no need to import the SSL certificate like we do for other SQL database configurations because the Azure root certificate is already present in our keystore (cacerts).

This document assists you in configuring Azure SQL Managed Instance as the backend database for PAM360. To configure Azure SQL Managed Instance as the backend database for PAM360, follow these high-level steps:

1. Creating an SQL Managed Instance in Microsoft Azure

  1. Log in to the Azure portal and navigate to the More services.
  2. From the Databases categories, select SQL managed instance under Azure SQL.
  3. In the SQL managed instances window that appears, click + Create.
  4. On the Create Azure SQL Managed Instance page, follow these steps:
    1. In the Basics information tab, choose an existing resource group or create a new one.

      Note: A resource group is a container that holds related resources for an Azure solution. It can include all the resources for the solution or only those resources you want to manage as a group.

    2. Provide the Managed Instance name and select the Region.
    3. Select an Authentication method.

      Note: If you select Use Microsoft Entra-only authentication, the PAM360 application should be on the Azure connected server.

    4. Click Next : Networking > to continue with the Networking information.
    5. In the Networking tab, select the Virtual network / subnet and the Connection type (VNet-local endpoint).
    6. Select the Public endpoint, Minimum TLS version and click Next : Security > to continue.
    7. Further, set the Security, Additional Settings, and Tags as per your requirements and click Next : Review + create >.
    8. Review the SQL-managed instance information and click Create. This will further proceed with the managed instance deployment process, and upon completion, you will be notified with a deployment completion message.

  5. Navigate to the newly created managed instance via Databases >> SQL managed instance >> (created instance), and from the Overview window, copy the Host detail for further PAM360 database configuration.

2. Configuring Azure SQL Managed Instance as the PAM360 Backend Database

Stop the PAM360 service if running and proceed with the following configuration process with the server administrator rights (where PAM360 is installed):

  1. Open the command prompt or the terminal and navigate to <PAM360 Installation Folder>/bin.
  2. Execute the ChangeDB.bat file.
  3. In the DB Change Configuration dialogue box that opens, enter the following information:
    1. Select the Server Type as SQL Server.
    2. Enter the copied Host details from Azure in the Host Name field.

      Note: A managed instance operates on port 1433 locally and port 3342 publicly. If using the default port, you can specify just the host value without the port number, for example: `pam360support.##########.database.windows.net`. If it is configured as a public endpoint, include the port number in the address, such as: `pam360support.##########.database.windows.net:3342`.

    3. Provide a Database Name and select the Authentication method as SQL.
    4. Enter the Managed Instance admin login name as the Username and the password entered during the Create Azure SQL Managed Instance process.
    5. Select the Instance Type as Azure SQL and the JDBC Driver as Microsoft.
  4. Click Test. Upon successful testing, click Save.

Now, you have successfully leveraged Azure SQL Managed Instance to provide a robust, scalable, and secure backend database for PAM360. This setup ensures minimal disruption during migration while offering the benefits of a managed cloud service.
Top