Actions129
- Calendar Permission Actions
- CIPP Administration Actions
- Execute API Client (GET)
- Execute Auto Backup
- Execute Extension Mapping (GET)
- Execute Extension Mapping (POST)
- Execute Extension Sync
- Execute Extensions Config
- Execute Password Config (POST)
- Execute Restore Backup
- Execute Run Backup
- List Custom Roles
- List Extension Sync
- List Logs
- List Scheduled Items
- Remove Scheduled Item
- Execute API Client (POST)
- Execute Extension Test
- Execute Password Config (GET)
- List Backups
- List Function Parameters
- Group Actions
- Intune Actions
- Add MSP App
- Add Office App
- Add Policy
- Add Store App
- Assign App
- Assign Autopilot Device
- Device Action
- Get Recovery Key
- List Applications
- List Application Queue
- List Autopilot Config
- List Devices
- List Intune Scripts
- List Intune Templates
- Remove Autopilot Device
- Remove Policy
- Remove Queued App
- Add Choco App
- Add WinGet App
- Assign Policy
- Get Local Admin Password
- List Autopilot Devices
- List Intune Policies
- Remove App
- Remove Intune Script
- Sync Autopilot Devices
- License Actions
- Security & Compliance Actions
- Teams & SharePoint Actions
- Tenant Actions
- Add Alert
- Clear Tenant Cache
- Execute CA Exclusion
- Execute Named Location
- Get Tenant
- List Alerts Queue
- List Azure AD Connect Status
- List Conditional Access Policies
- List Named Locations
- List Shared Mailbox Statistics
- List Standards
- List Tenants
- Remove Standard Template
- Add Named Location
- Edit Tenant
- Execute Standards Run
- List Audit Logs
- List CSP Licenses
- List Roles
- List Standard Templates
- Tool Actions
- User Actions
- Add User
- Exec Restore Deleted User
- List User
- List User Conditional Access Policies
- List User Groups
- Clear Immutable ID
- Create Temporary Access Password
- Delete User Device
- Dismiss Risky User
- List Deleted Items
- List Inactive Accounts
- List Sign-Ins
- Remove User
- Reset MFA
- Restore Deleted Item
- Revoke Sessions
- Set Email Forward
- Set Per-User MFA
- List All Users
- List User Counts
- List User Devices
- Convert Mailbox
- Disable User
- Enable Archive
- List MFA Users
- Offboard User
- Reset Password
- Send MFA Push
- Set Out of Office
Overview
This node interacts with the CIPP API to perform operations related to users, specifically the 'Dismiss Risky User' operation. It is useful in scenarios where an administrator needs to manage user security risks by dismissing flagged risky users within a tenant environment. For example, it can be used to automate the dismissal of risky user alerts in a Microsoft 365 tenant to maintain security compliance.
Use Case Examples
- Dismissing a risky user by providing their user ID or email address along with the tenant ID or domain name to ensure the correct tenant context.
- Automating security workflows by integrating this node to handle risky user dismissals as part of a larger security incident response process.
Properties
| Name | Meaning |
|---|---|
| User ID | The user ID or email address of the user to dismiss as risky. This is a required field to identify the specific user. |
| Tenant Filter | The tenant ID or domain name to specify the tenant context in which the risky user dismissal should occur. This is required to target the correct tenant. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings to control how the API requests are made. |
Output
JSON
success- Indicates whether the risky user dismissal operation was successful.message- Provides additional information or status message about the dismissal operation.
Dependencies
- Requires an API key credential for authenticating with the CIPP API.
Troubleshooting
- Ensure the User ID and Tenant Filter are correctly specified; incorrect values may cause the operation to fail or target the wrong user or tenant.
- If SSL certificate validation fails and the 'Ignore SSL Issues' option is not enabled, requests may be blocked; enable this option only if you trust the network environment.
- Batching settings should be configured carefully to avoid hitting API rate limits or causing timeouts.
- Timeout settings should be adjusted based on network conditions and API responsiveness to prevent premature request abortion.