Skip to main content

Provisioning the database server for cloud deployment

To deploy the application you must provision either of the databases discussed in the document:

Provisioning the Azure MYSQL Database​

Follow the steps outlined below to provision Azure MySQL Database:

  1. Sign in to the Azure Portal.

  2. In the left-hand menu, select Azure Database for MySQL flexible servers.

  3. Click Create.

  4. In the Basics Configuration section, provide the following details:

    1. Resource Group: Select rg-mysql-flex (create it if it doesn’t exist).
    2. Server Name: Enter mysql-flex-rancher.
    3. Region: Choose the same region as your VM.
    4. Availability Zone: Select Zone 3.
    5. MySQL Version: Choose MySQL 8.0.
    6. Admin Username: Enter a username, for example, dbadmin, using which the database server can be accessed.
    7. Password: Provide a strong password (≥16 characters), avoiding special characters that may cause escape issues.

  5. In the Compute + Storage section, provide the following details:

    1. Compute Tier: Select General Purpose.
    2. Compute Size: Choose Standard_D2ads_v5 (2 vCores, 8 GB RAM).
    3. Storage: Set to 64 GB.
    4. IOPS: Set to 492.
    5. Enable Auto-scale storage.

  6. In the Backup section, provide the following details:

    1. Backup Redundancy: Select Locally redundant.
    2. Retention Period: Set to 7 days.

  7. In the Networking section, provide the following details:

    1. Connectivity Method: Select Public access.
    2. Firewall Rules: Choose Allow only selected IP ranges and click Add client IP.
    3. Enforce SSL: Set to Enabled.
    4. Virtual Network (VNet Integration): Leave blank.

  8. Click Review + Create to validate all settings.

  9. After validation, click Create to deploy the server.

Provisioning the Azure SQL Database​

Follow the steps below to provision SQL database server on Azure.

  1. Sign in to the Azure Portal.
  2. Go to Azure SQL → SQL logical servers.
  3. Click Create to start the SQL Database Server creation wizard.

Configure the following​

Basics​

Project Details

  1. Subscription

    • Select the appropriate subscription Example:Adeptia Product Development

  2. Resource group

    • Select an existing resource group or click Create new Example:ad-int-eus-dev-rg-010

Server Details

  1. Server name

    • Enter a unique server name Example:rancher-sql
    • Azure automatically appends: .database.windows.net

  2. Location

    • Select the region closest to your application Example:West US 2

Authentication

  1. Authentication method
    1. Select Use both SQL and Microsoft Entra authentication
  2. Microsoft Entra admin
    1. Click Set admin
    2. Choose the appropriate Entra user or group
  3. Server admin login
    1. Enter SQL admin username
  4. Password / Confirm password
    1. Enter and confirm a strong password

Networking​

Firewall Rules

  1. Allow Azure services and resources to access this server

    • Select Yes

This allows Azure-hosted services (such as App Services, Azure Functions, AKS, etc.) to connect to the SQL server.

Security​

Identity

  1. Managed Identity

    • Leave as Not enabled (default)
    • Optional: Can be enabled later if required
  • Transparent Data Encryption (TDE)

  1. Transparent data encryption

    • Leave default: Service-managed key selected

This ensures encryption at rest for databases, backups, and logs.

Additional Settings​

Microsoft Defender for SQL

  1. Enable Microsoft Defender for SQL

    • Select Not now

Defender can be enabled later if advanced threat protection is required.

Tags (Optional)​

  1. Add tags if required for cost management or governance Examples:

    1. Environment : Dev
    2. Project : Rancher

  2. If not required, leave empty.

Review + create​

Review Configuration

Verify all selected settings:

  • Subscription: Adeptia Product Development
  • Resource group: ad-int-eus-dev-rg-010
  • Server name: rancher-sql
  • Authentication: SQL and Microsoft Entra authentication
  • Location: West US 2
  • Networking: Azure services allowed
  • Security: TDE enabled (service-managed key)
  • Defender: Not enabled
  • Estimated cost: No additional charges

Create the SQL Server​

  1. Click Create to complete provisioning the SQL database server.