- 15 Dec 2022
- 2 Minutes to read
- Print
- DarkLight
- PDF
Microsoft Azure (Azure AD) - Delete Assets
- Updated on 15 Dec 2022
- 2 Minutes to read
- Print
- DarkLight
- PDF
Microsoft Azure (Azure AD) - Delete Assets deletes an asset record from an Azure AD 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 - Click to 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, Adapter 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 Azure AD Adapter - Select this option to use the first connected Azure AD adapter credentials.
- To use this option, you must successfully configure an Microsoft Azure Active Directory (Azure AD) adapter connection.
Required Fields
These fields must be configured to run the Enforcement Set.
Instance name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
- 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) - Microsoft Azure AD ID, as detailed in the Required Permissions section.
Verify SSL - 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 Azure AD roles:
User Administrator
Privileged Authentication Administrator
Global Administrator
To delete a device a user the value supplied in User name must have one of the following permissions
Delegated (work or school account) Directory.AccessAsUser.All
The user must have one of the following Azure AD roles:
Global Administrator, Intune Administrator, Windows 365 Administrator, or Cloud Device Administrator.The user name and the password used for the adapter connection must have the Add Users or Devices to Microsoft Active Directory (AD) Group to add assets.
For more details about other Enforcement Actions available, see Action Library.