- 18 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Microsoft Entra ID (formerly Azure AD) - Delete Assets
- Updated on 18 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Microsoft Entra ID (formerly Azure AD) - Delete Assets deletes an asset record from an Entra ID for each asset that matches the parameters of the saved query supplied as a trigger (or devices that have been selected in the asset table).
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- 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 Entra ID Adapter - Select this option to use the first connected Entra ID adapter credentials.
- To use this option, you must successfully configure an Microsoft Entra ID adapter connection.
Required Fields
These fields must be configured to run the Enforcement Set.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
Connection and Credentials
When Use stored credentials from the adapter is toggled off, these fields need to be configured:- Azure Client ID (required) - The Application ID of the Axonius application, as detailed in the Required Permissions section.
- Azure Client Secret (required) - A user created key for the Axonius application, as detailed in the Required Permissions section.
- Azure Tenant ID (required) - The ID for Microsoft Entra ID, as detailed in the Required Permissions section.
- 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.
APIs
Axonius uses the following APIs
Delete a user
Delete a device
Required Ports
Axonius must be able to communicate with the value supplied in DC Address via the following ports:
- TCP/UDP port 389.
If you choose to use the stored credentials from the adapter then refer to Required Ports for information about all additional ports required.
Required Permissions
To delete a user, the value supplied in User name must have one of the following permissions
Delegated/Application User.ReadWrite.All
The user must have one of the following Entra ID roles:
User Administrator
Privileged Authentication Administrator
Global Administrator
Intune Administrator
Windows 365 Administrator
Cloud Device Administrator.
The user name and the password used for the adapter connection must have the Add Users or Devices to Microsoft Entra ID Group to add assets.
For more details about other Enforcement Actions available, see Action Library.