Microsoft Entra ID (formerly Azure AD) - Assign mobile app action to Groups

Microsoft Entra ID (formerly Azure AD) - Assign Mobile App Action to Groups assigns mobile application actions to Entra ID groups for:

• Assets returned by the selected query or assets selected on the relevant asset page.

📘

Note

• The mobile app ID must correspond to an existing mobile application in Microsoft Intune (device management).
• All target groups must be valid security groups in Microsoft Entra ID.

Required Fields

These fields must be configured to run the Enforcement Action.

• Use stored credentials from the Microsoft Entra ID (Azure AD) and Microsoft Intune adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

  • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

    📘

    Note

    To use this option, you must successfully configure a Microsoft Entra ID (Azure AD) and Microsoft Intune adapter connection.

• Mobile App ID - The unique identifier of the mobile application in Microsoft Entra ID.

• Mobile App Intent - The assignment intent for the mobile app. Options: AVAILABLE, REQUIRED, UNINSTALL, AVAILABLE_WITHOUT_ENROLLMENT

• Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

This Enforcement Action does not have additional optional fields.

⚠️

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

• Azure Tenant ID - The Microsoft Entra ID tenant ID (directory ID).
• Azure Client ID - The Application (client) ID of the Axonius application registered in Entra ID.
• Authentication Method - Select from Client Credentials, Certificate Based, Authorization Code, or Managed Identity.
• Client Credentials - Azure Client Secret (for Client Credentials authentication method).
• Certificate - Authentication certificate and private key (for Certificate Based authentication method).

• Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

• HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

• HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

• HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

• Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the Microsoft Graph API - POST /deviceAppManagement/mobileApps/{mobileAppId}/assignments

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 443 (HTTPS)

Required Permissions

The following permissions and requirements are needed:

• Microsoft Graph API Permissions - Application must have DeviceAppManagement.ReadWrite.All permission to assign mobile apps to groups.
• Entra ID Tenant Admin Role - Administrator or Global Administrator role with permissions to manage device and app management policies.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.