Microsoft Entra ID - Groups and Roles

How to manage on-demand, temporary membership to Azure Entra ID (formerly known as Azure Active Directory) groups and roles

Apono's integration with Microsoft Entra ID (formerly called Azure Active Directory) enables centralized, dynamic management of user access by managing group memberships and role assignments.

Using Microsoft Graph APIs, the integration can add or remove users from groups and manage assignments to Entra directory roles. All access changes are logged for auditability, and aligned with least-privilege and zero-trust principles. Access is managed in a just-in-time way for the duration it is needed.

---

Prerequisite

Item	Description
Apono Connector	On-prem connection serving as a bridge between an Azure AD instance and Apono NOTE: Be sure that the Groups Administrator and Privileged Role Administrator roles have been added to the connector.

---

Integrate Azure AD Groups

You can also use the steps below to integrate with Apono using Terraform.

In step 9, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.

Follow these steps to complete the integration:

1. On the Catalog tab, click Azure AD Groups. The Connect Integration page appears.

2. Under Discovery, select one or multiple resource types for Apono to discover in all instances of the environment.

3. Click Next. The Apono connector section expands.

4. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

If the desired connector is not listed, click + Add new connector and follow the instructions for creating an Azure Apono connector.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.

   Setting	Description
   Integration Name	Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow

3. Click Next. The Get more with Apono section expands.

4. 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.

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

Now that you have completed this integration, you can create access flows that grant permission to your Azure AD instance.