> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-a-pentaho-administrator/define-data-connections/enter-database-connection-information/connect-to-an-azure-sql-database/connect-to-azure-azure-sql-database.md). # Connect to an Azure database Perform the following steps to connect to your database: 1. Start the PDI client and create a new transformation or job. See the **Pentaho Data Integration** document for instructions on creating a PDI transformation. **Note:** You can also use the Pentaho User Console to make this connection. See [Define data connections](/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-a-pentaho-administrator/define-data-connections.md) 2. In the **View** tab of the **Explorer** pane, double-click on the **Database connections** folder. The **Database Connection** dialog box appears, as shown below: ![Database connection dialog for Azure SQL](https://3897443520-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7HOrU4JuCmIFVNup2Gxd%2Fuploads%2Fgit-blob-f60eccc56d0067c7af5f89ba749a243be3bcdd0c%2FDatabase%20connection%20dialog%20for%20Azure%20SQL.png?alt=media) 3. Enter your database connection information. | Field | Description | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Host Name** | The name of the Azure SQL server instance. | | **Database Name** | The name of the Azure SQL database to which you are connecting. | | **Port Number** | The TCP/IP port number. The Azure SQL Database service is only available through TCP port 1433. You must set your firewall to allow outgoing TCP communication on port 1433. | | **Authentication method** | The authentication method used to connect to the Azure SQL DB instance. The default is SQL Authentication. | | **Username** | The username used to connect to the database. | | **Password** | The password used to connect to the database. | | **Always Encryption Enabled** | Select to use encryption. See [Use the Always Encryption Enabled option](/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-a-pentaho-administrator/define-data-connections/enter-database-connection-information/connect-to-an-azure-sql-database/use-the-always-encryption-option.md) for instructions on using this option. | | **Client id** | The unique client identifier, used to identify and set up a durable connection path to the server. | | **Client Secret Key** | The unique name of the key value in the Azure Key Vault. | 4. Click **Test**to verify your connection. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.pentaho.com/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-a-pentaho-administrator/define-data-connections/enter-database-connection-information/connect-to-an-azure-sql-database/connect-to-azure-azure-sql-database.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.