Axonius Documentation
Start typing to search…

Microsoft Entra ID (formerly Azure AD) - Update Entra ID Device

Microsoft Entra ID (formerly Azure AD) - Update Entra ID Device creates, replaces, or modifies extension attributes in Entra ID devices for:

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

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

📘

Note:

Required Fields

These fields must be configured to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
  • Use stored credentials from the Microsoft Entra ID (formerly Azure AD) 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 (formerly Azure AD) adapter connection.

Additional Fields

These fields are optional.

  • Extension Attribute 1-9 - Add a value for any of the Extension Attributes fields (up to 9) to be updated in Entra ID. If you leave a field blank, this won’t delete the value in Entra ID; only fields with values will be considered.
💡

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 Client ID -The Application ID of the Axonius application.

  • Azure Client Secret - Specify a non-expired key generated from the new client secret.

  • Azure Tenant ID - The ID for Microsoft Entra ID.

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

  • Enable Certificate-Based Authentication - Select to enable Axonius to send requests using the Azure certificates uploaded to allow secure Azure authentication for this adapter.

  • Click Upload File next to Private Key File to upload an Azure private key file in PEM format.

  • Click Upload File next to Certificate File to upload an Azure public key file in PEM format.

📘

Note

The following parameters are only relevant for customers who have the Axonius SaaS Applications product.

  • Account Sub Domain - The Microsoft account's sub domain (.onmicrosoft.com).

  • User Name and Password - The credentials for a user account that has the permissions needed to perform this action.

  • 2FA Secret Key - The secret generated in Microsoft Entra ID for setting up 2-factor authentication for the Microsoft user.

  • SSO Provider - If your organization uses Microsoft Entra ID for SSO, you can select this check box. For more information, see Connecting your SSO Solution Provider Adapter

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

APIs

Axonius uses the Microsoft API about adding custom data to resources using extensions.

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

  • Device.ReadWrite.All Application permission

For more details about other Enforcement Actions available, see Action Library.

Updated about 11 hours ago