Integrate with Azure Management Group or Subscription
Create an integration to manage access to your Azure services
Last updated
Was this helpful?
Documentation and Guides
Create an integration to manage access to your Azure services
Last updated
Was this helpful?
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.
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
Learn how to update an existing Azure connector.
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
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:
On the Catalog tab, click Azure. The Connect Integration page appears.
Under Discovery, choose Management Group.
Select one or more resources.
Click Next. The Apono connector section expands.
From the dropdown menu, select a connector.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating an Azure connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
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.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.\
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.
Click Confirm.
Now that you have completed this integration, you can create access flows that grant permission to your Azure services.
