# Azure MySQL MySQL is a reliable and secure open-source relational database system. It serves as the main data store for various applications, websites, and products. This includes mission-critical applications and dynamic websites. Microsoft enables developers to create cloud-hosted MySQL databases. Through this integration, Apono helps you securely manage access to your Azure MySQL databases. *** ### Prerequisites Before starting this integration, create the items listed in the following table.

Item	Description
Apono Connector	On-prem connection serving as a bridge between an Azure MySQL database instance and Apono Minimum Required Version: 1.3.0
MySQL Info	Information for the database instance to be integrated: Hostname Port Number

Item

Description

Apono Connector

On-prem connection serving as a bridge between an Azure MySQL database instance and Apono

Minimum Required Version: 1.3.0

MySQL Info

Information for the database instance to be integrated:

Hostname
Port Number

*** ### Create a MySQL user You must create a user in your MySQL instance for the Apono connector and grant that user permissions to your databases. Use the following steps to create a user and grant it permissions: 1. In your preferred client tool, create a new user. Be sure to set a strong password for the user. ```sql CREATE USER 'apono_connector'@'%' IDENTIFIED BY 'password'; ``` 2. Expose databases to the user. This allows Apono to view database names without accessing the contents of each database. ```sql GRANT SHOW DATABASES ON *.* TO 'apono_connector'@'%'; ``` 3. Grant the user database permissions.\ \ The following commands grant Apono the following permissions: * Creating users * Updating user information and privileges * Monitoring and troubleshooting processes running on the database\\ ```sql GRANT CREATE USER ON *.* TO 'apono_connector'@'%'; GRANT UPDATE ON mysql.* TO 'apono_connector'@'%'; GRANT PROCESS ON *.* TO 'apono_connector'@'%'; ``` 4. Grant the user **only one** of the following sets of permissions. The chosen set defines the highest level of permissions to provision with Apono.\ \ Expand each of the following options to reveal the SQL commands: {% tabs %} {% tab title="READ\_ONLY" %} ```sql GRANT SELECT ON *.* TO 'apono_connector'@'%'; GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%'; ``` {% endtab %} {% tab title="READ\_WRITE" %} {% code overflow="wrap" %} ```sql GRANT SELECT,ALTER,ALTER ROUTINE,CREATE,CREATE ROUTINE,CREATE TEMPORARY TABLES,CREATE VIEW,DELETE,INDEX,INSERT,TRIGGER,UPDATE ON *.* TO 'apono_connector'@'%'; GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%'; ``` {% endcode %} {% endtab %} {% tab title="ADMIN" %} {% code overflow="wrap" %} ```sql GRANT EXECUTE,DROP,SELECT,ALTER,ALTER ROUTINE,CREATE,CREATE ROUTINE,CREATE TEMPORARY TABLES,CREATE VIEW,DELETE,INDEX,INSERT,TRIGGER,UPDATE ON *.* TO 'apono_connector'@'%'; GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%'; ``` {% endcode %} {% endtab %} {% endtabs %} 5. (MySQL 8.0+) Grant the service account the authority to manage other roles. This enables Apono to create, alter, and drop roles. However, this role does not inherently grant specific database access permissions. ```sql GRANT ROLE_ADMIN on *.* to 'apono_connector'; ``` 6. Using the credentials from step **1**, [create a secret](https://docs.apono.io/docs/connectors-and-secrets/apono-integration-secret#azure) for the database instance and associate it to the Azure connector. You can now [integrate Azure MySQL](#integrate-azure-mysql). *** ### Integrate Azure MySQL

{% hint style="success" %} You can also use the steps below to integrate with Apono using Terraform. In step **11**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance. {% endhint %} Follow these steps to complete the integration: 1. On the [**Catalog**](https://app.apono.io/catalog?search=azure+mysql) tab, click **Azure MySQL**. The **Connect Integration** page appears. 2. Under **Discovery**, click one or more resource types and cloud services to sync with Apono. {% hint style="info" %} Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage **Access Flows** to these resources. {% endhint %} 3. Click **Next**. The **Apono connector** section appears. 4. From the dropdown menu, select a connector. {% hint style="info" %} If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating an [Azure connector](https://docs.apono.io/docs/azure-environment/apono-connector-for-azure) and [associate the secret](https://docs.apono.io/docs/connectors-and-secrets/apono-integration-secret#azure) with the connector. {% endhint %} 5. Click **Next**. The **Integration Config** section expands. 6. Define the **Integration Config** settings.

Setting	Description
Integration Name	Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
Hostname	Hostname of the MySQL instance to connect
Port	Port value for the database By default, Apono sets this value to 3306.

7. Click **Next**. The **Secret Store** section expands. 8. [Associate the secret or credentials](https://docs.apono.io/docs/connectors-and-secrets/apono-integration-secret). 9. Click **Next**. The **Custom Access Details** section expands. 10. Define the **Get more with Apono** settings.

Setting	Description
Credential Rotation	(Optional) Number of days after which the database credentials must be rotated Learn more about the Credentials Rotation Policy.
User cleanup after access is revoked (in days)	(Optional) Defines the number of days after access has been revoked that the user should be deleted Learn more about Periodic User Cleanup & Deletion.
Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.

11. Click **Confirm**.

💡Are you integrating with Apono using Terraform?

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**: 1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code. 2. Click to copy the code. 3. Make any additional edits. 4. Deploy the code in your Terraform. Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/azure-mysql) for more details about the schema definition.

Now that you have completed this integration, you can [create access flows](https://docs.apono.io/docs/access-flows/access-flows) that grant permission to your Azure MySQL database instance. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apono.io/docs/azure-environment/azure-integrations/azure-mysql.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.