# Integrate with Azure Management Group or Subscription 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. *** ### Prerequisites {% tabs %} {% tab title="Management Group" %}

Item	Description
Apono Connector	On-prem connection serving as a bridge between an Azure instance and Apono Install an Azure connector using one of these approaches: Azure CLI PowerShell Terraform Minimum Required Version: 1.3.6 Learn how to update an existing Azure connector.
Tag Contributor Role	Azure role applied to the Apono connector, allowing Apono to add tags to resources This role is required when Azure resource locks are applied to your resources. Refer to our Azure connector documentation in the previous row to learn how to assign this role. To understand how Apono uses this role, read about the Disable Locks feature.
Azure Management Group ID	ID of a container for enabling efficient management of access, policies, and compliance across multiple subscriptions
Azure Primary Domain	Initial domain assigned to your tenant

{% endtab %} {% tab title="Subscription" %}

Item	Description
Apono Connector	On-prem connection serving as a bridge between an Azure instance and Apono Install an Azure connector using one of these approaches: Azure CLI PowerShell Terraform Minimum Required Version: 1.3.6 Learn how to update an existing Azure connector.
Tag Contributor Role	Azure role applied to the Apono connector, allowing Apono to add tags to resources This role is required when Azure resource locks are applied to your resources. Refer to our Azure connector documentation in the previous row to learn how to assign this role. To understand how Apono uses this role, read about the Disable Locks feature.
Azure Subscription ID	Unique identifier assigned to an Azure subscription
Azure Primary Domain	Initial domain assigned to your tenant

{% endtab %} {% endtabs %} *** ### Integrate Azure

{% tabs %} {% tab title="Management Group" %} {% hint style="success" %} 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. {% endhint %} Follow these steps to complete the integration: 1. On the [**Catalog**](https://app.apono.io/catalog?search=sql+-+mysql) tab, click **Azure**. The **Connect Integration** page appears. 2. Under **Discovery**, choose **Management Group**. 3. Select one or more resources. 4. Click **Next**. The **Apono connector** section expands. 5. From the dropdown menu, select a connector. {% hint style="success" %} If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating an [Azure](/docs/azure-environment/apono-connector-for-azure.md) connector. {% endhint %} 6. Click **Next**. The **Integration Config** section expands. 7. Define the **Integration Config** settings.

Setting	Description
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 temporarily remove locks from Azure resources in order to grant or revoke access, then automatically restore the locks after the operation Learn more about Disable Locks.

8. Click **Next**. The **Get more with Apono** section expands. 9. 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.

10. 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) for more details about the schema definition.

{% endtab %} {% tab title="Subscription" %} {% hint style="success" %} 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. {% endhint %} Follow these steps to complete the integration: 1. On the [**Catalog**](https://app.apono.io/catalog?search=sql+-+mysql) tab, click **Azure**. The **Connect Integration** page appears. 2. Under **Discovery**, choose **Subscription**. 3. Select one or more resources. 4. Click **Next**. The **Apono connector** section expands. 5. From the dropdown menu, select a connector. {% hint style="success" %} If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating an [Azure](/docs/azure-environment/apono-connector-for-azure.md) connector. {% endhint %} 6. Click **Next**. The **Integration Config** section expands. 7. Define the **Integration Config** settings.

Setting	Description
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 temporarily remove locks from Azure resources in order to grant or revoke access, then automatically restore the locks after the operation Learn more about Disable Locks.

8. Click **Next**. The **Get more with Apono** section expands. 9. Define the **Get more with Apono** settings.

Setting	Description
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.

Setting

Description

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.

10. Click **Confirm**.

💡Are you integrating with Apono using Terraform?

{% endtab %} {% endtabs %} Now that you have completed this integration, you can [create access flows](/docs/access-flows/creating-access-flows-in-apono.md) that grant permission to your Azure services. --- # 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/integrate-with-azure-management-groups-or-subscriptions.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.