If your organization uses Azure as a cloud platform, Apono can help you securely manage access to your Azure cloud-based services, subscriptions, and resource groups.
By identifying and transforming existing privileges, Apono can shift your cloud management from broad permissions to on-demand access flows. Through our integrations, Apono enables you to perform the following access tasks:
Limit Access: Discover existing privileges in Azure and convert them to just-in-time Access Flows.
Enable Self-Service Access: Allow developers to request access to Azure services, buckets, and instances via Slack.
Automate Approval Workflows: Create automatic approval processes for sensitive Azure resources.
Restrict Third-Party Access: Grant third-parties (customers or vendors) time-based access to specific services with MFA verification.
Review Access: Audit user cloud access, permissions granted, and reasons for access across Azure.
Create an integration to manage access to Azure-managed PostgreSQL databases
PostgreSQL databases are open-source relational database management systems emphasizing extensibility and SQL compliance. Microsoft enables developers to create cloud-hosted PostgreSQL databases.
Through this integration, Apono helps you securely manage access to your Azure PostgreSQL instances.
To enable Apono to manage Azure PostgreSQL user access, you must create a user and then configure the integration within the Apono UI.
| Item | Description |
|---|---|
You must create a user in your PostgreSQL instance for the Apono connector and grant that user permissions to your databases.
You must use the admin account and password to connect to your database.
Use the following steps to create a user and grant it permissions:
In your preferred client tool, create a new user. Use apono_connector for the username. Be sure to set a strong password for the user.
You must also grant the azure_pg_admin role to the user in the database instance.
Grant privileges to the azure_pg_admin role on all databases except template0 and azure_sys.
This allows Apono to perform tasks that are not restricted to a single schema or object within the database, such as creating, altering, and dropping database objects.
For each database to be managed through Apono, connect to the database and grant azure_pg_admin privileges on all objects in the schemas.
This allows Apono to perform tasks that are restricted to schemas within the database, such as modifying table structures, creating new sequences, or altering functions.\
Connect to the template1 database and grant azure_pg_admin privileges on all objects in the schemas.
For any new databases created in the future, this allows Apono to perform tasks that are restricted to schemas within the database, such as modifying table structures, creating new sequences, or altering functions.
5. Using the credentials from step 1, create a secret for the database instance and associate it to the Azure connector.
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.
Follow these steps to complete the integration:
On the Catalog tab, click Azure PostgreSQL. The Connect Integration page appears.
Under Discovery, click one or more resource types to sync with Apono.
Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage Access Flows to these resources.
Click Next. The Apono connector section appears.
From the dropdown menu, select the connector that has been granted read access to the secret for the PostgreSQL instance.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating an Azure connector and associate the secret with the connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Click Next. The Secret Store section expands.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
Click Confirm.
Now that you have completed this integration, you can create access flows that grant permission to your Azure PostgreSQL instances.
Create an integration to manage access to a Kubernetes cluster on Azure
With Azure Kubernetes Service (AKS) on Microsoft Azure, AKS simplifies the management complexities of Kubernetes.
Through this integration, Apono helps you securely manage access to your Microsoft Azure Kubernetes cluster.
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.
Follow these steps to complete the integration:
Under Discovery, click one or more resource types and cloud services to sync with Apono.
Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage Access Flows to these resources.
Click Next. The Apono connector section appears.
From the dropdown menu, select a connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Click Next. The Secret Store section expands.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
Click Confirm.
Create an integration to manage access to your Azure services
Apono offers Azure users a simple way to centralize cloud management through our platform. Through a single integration, you can manage multiple Azure services across various management groups and subscriptions.
| Item | Description |
|---|
| Item | Description |
|---|
You can also use the steps below to integrate with Apono using Terraform.
In step 10, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.
Follow these steps to complete the integration:
Under Discovery, choose Management Group.
Select one or more resources.
Click Next. The Apono connector section expands.
From the dropdown menu, select a connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
Click Confirm.
You can also use the steps below to integrate with Apono using Terraform.
In step 10, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.
Follow these steps to complete the integration:
Under Discovery, choose Subscription.
Select one or more resources.
Click Next. The Apono connector section expands.
From the dropdown menu, select a connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
Click Confirm.
Create an integration to manage access to Azure-managed MySQL databases
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.
Before starting this integration, create the items listed in the following table.
| Item | Description |
|---|
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:
In your preferred client tool, create a new user. Be sure to set a strong password for the user.
Expose databases to the user. This allows Apono to view database names without accessing the contents of each database.
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\
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:
(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.
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.
Follow these steps to complete the integration:
Under Discovery, click one or more resource types and cloud services to sync with Apono.
Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage Access Flows to these resources.
Click Next. The Apono connector section appears.
From the dropdown menu, select a connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Click Next. The Secret Store section expands.
Click Next. The Custom Access Details section expands.
Define the Get more with Apono settings.
Click Confirm.
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Item | Description |
|---|
On the tab, click Azure Kubernetes Service (AKS). The Connect Integration page appears.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating a .
| Setting | Description |
|---|
.
| Setting | Description |
|---|
Refer to for more details about the schema definition.
Now that you have completed this integration, you can that grant permission to your Azure Kubernetes Service cluster.
On the tab, click Azure. The Connect Integration page appears.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating an connector.
| Setting | Description |
|---|
| Setting | Description |
|---|
Refer to for more details about the schema definition.
On the tab, click Azure. The Connect Integration page appears.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating an connector.
| Setting | Description |
|---|
| Setting | Description |
|---|
Refer to for more details about the schema definition.
Now that you have completed this integration, you can that grant permission to your Azure services.
Using the credentials from step 1, for the database instance and associate it to the Azure connector.
You can now .
On the tab, click Azure MySQL. The Connect Integration page appears.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating an and with the connector.
| Setting | Description |
|---|
.
| Setting | Description |
|---|
Refer to for more details about the schema definition.
Now that you have completed this integration, you can that grant permission to your Azure MySQL database instance.
Apono Connector
On-prem connection serving as a bridge between an Azure MySQL database instance and Apono Minimum Required Version: 1.3.0
PostgreSQL Info
Information for the database instance to be integrated:
Hostname
Port Number
Database Name
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.
Integration Name | Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow |
Azure Management Group Id | ID of a container for enabling efficient management of access, policies, and compliance across multiple subscriptions |
Azure Primary Domain | (Optional) Initial domain assigned to your tenant |
Disable Locks | (Optional) Allows Apono to forcefully delete the Azure lock to be able to grant or revoke access to the required resource Apono will recreate the lock after it has been deleted. |
Integration Name | Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow |
Azure Subscription Id | (Optional) Unique identifier assigned to an Azure subscription |
Azure Primary Domain | (Optional) Initial domain assigned to your tenant |
Disable Locks | (Optional) Allows Apono to forcefully delete the Azure lock to be able to grant or revoke access to the required resource Apono will recreate the lock after it has been deleted. |
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. |
Integration Name
Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
Hostname
Hostname of the PostgreSQL instance to connect
Port
Port value for the database By default, Apono sets this value to 5432.
Database Name
Name of the database to integrate By default, Apono sets this value to postgre.
SSL Mode
(Optionl) Mode of Secure Sockets Layer (SSL) encryption used to secure the connection with the SQL database server
Option
Description
require
An SSL-encrypted connection must be used.
allow
An SSL-encrypted or unencrypted connection is used. If an SSL encrypted connection is unavailable, the unencrypted connection is used.
disable
An unencrypted connection is used.
prefer
An SSL encrypted connection is attempted. If the encrypted connection is unavailable, the unencrypted connection is used.
verify-ca
An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass.
verify-full
An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass. Additionally, the server hostname is checked against the certificate's names.
Apono Connector |
Apono Premium |
User Access Administrator Role |
Integration Name | Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow |
Server URL | (Optional) URL of the Kubernetes API server used to interact with the Kubernetes cluster |
Certificate Authority | (Optional) Certificate that ensures that the Kubernetes API server is trusted and authentic Leave this field empty if you want to connect the cluster where the connector is deployed. |
Resource Group |
Cluster Name |
Subscription ID | (Optional) Subscription ID where the cluster is deployed |
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 |
NOTE: When Resource Owner is defined, an Integration Owner must be defined. |
Resource Owner |
NOTE: When this setting is defined, an Integration Owner must also be defined. |
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 |
NOTE: When Resource Owner is defined, an Integration Owner must be defined. |
Resource Owner |
NOTE: When this setting is defined, an Integration Owner must also be defined. |
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 |
NOTE: When Resource Owner is defined, an Integration Owner must be defined. |
Resource Owner |
NOTE: When this setting is defined, an Integration Owner must also be defined. |
Apono Connector |
MySQL Info | Information for the database instance to be integrated:
|
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 |
NOTE: When Resource Owner is defined, an Integration Owner must be defined. |
Resource Owner |
NOTE: When this setting is defined, an Integration Owner must also be defined. |
Apono Connector | On-prem connection serving as a bridge between an Azure instance and Apono Install an Azure connector using one of these approaches: Minimum Required Version: 1.3.6 |
Azure Management Group ID |
Azure Primary Domain |
Apono Connector | On-prem connection serving as a bridge between an Azure instance and Apono Install an Azure connector using one of these approaches: Minimum Required Version: 1.3.6 |
Azure Subscription ID |
Azure Primary Domain |
| Option | Description |
|---|---|
On-prem installed on the AKS cluster that serves as a bridge between the cluster and Apono
providing all available features and dedicated account support
that enables granting users the Azure Kubernetes Service Cluster User role. Apono does not require admin permissions to the Kubernetes environment.
(Optional) Resource group where the cluster is deployed This is the .
(Optional) Cluster name as it appears in AKS This is the .
(Optional) Fallback approver if no is found Follow these steps to define one or several integration owners:
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several :
(Optional) Fallback approver if no is found Follow these steps to define one or several integration owners:
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several :
(Optional) Fallback approver if no is found Follow these steps to define one or several integration owners:
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several :
On-prem serving as a bridge between an Azure MySQL database instance and Apono Minimum Required Version: 1.3.0
(Optional) Fallback approver if no is found Follow these steps to define one or several integration owners:
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several :
Learn how to update an existing connector.
for enabling efficient management of access, policies, and compliance across multiple subscriptions
assigned to your tenant
Learn how to update an existing connector.
assigned to an Azure subscription
assigned to your tenant
require
An SSL-encrypted connection must be used.
allow
An SSL-encrypted or unencrypted connection is used. If an SSL encrypted connection is unavailable, the unencrypted connection is used.
disable
An unencrypted connection is used.
prefer
An SSL encrypted connection is attempted. If the encrypted connection is unavailable, the unencrypted connection is used.
verify-ca
An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass.
verify-full
An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass. Additionally, the server hostname is checked against the certificate's names.
