Suspend Jira-Only Users by Email Domain (Fast Bulk Action + Safe Filters) | Atlassian Cloud

In this video, I’ll show you how to suspend a very specific subset of users in minutes: - Only users who have Jira access - No Confluence access - Email domain = “azureadlab.resolution.de” (example) - No spreadsheets - No clicking through hundreds of profiles Just clean filters + one bulk action. Hey, I’m Vin, Technical Support Engineer (DevOps) at re:solution GmbH—I spend my days preventing small admin clicks from turning into big admin weekends. When you’d use this You get a request like: • “Suspend everyone from this contractor domain who still has Jira… but not Confluence.” • Security event response • Contractor offboarding cleanup • Access governance enforcement Doing it manually is painful: 1. It takes forever 2. It’s easy to miss someone 3. It’s easy to hit the wrong people (especially with stale data) Key admin clarifications (don’t get burned) Remove app access ≠ Suspend user • Remove app access: removes Jira/Confluence access, but user stays active • Suspend user: blocks access across Atlassian services, ends sessions, and stops access immediately In this tutorial we are doing Suspend user (hard stop). Also: stale data is the real enemy. If access changed recently, your view may lag—so we start with a manual sync before running bulk actions. The solution flow (5 minutes) 1. Run sync (fresh data first) 2. Open User Browser 3. Set 3 filters: • Included apps: Jira • Excluded apps: Confluence • Email domain: azureadlab.resolution.de 4. Review the list (catch surprises) 5. Bulk select filtered users 6. Run Bulk operations → Suspend user 7. Verify results (status = suspended + bulk results log) What “Suspend” actually does (important) Suspending users: • disables access across Atlassian services • ends active sessions • invalidates API / OAuth tokens • stops automations/integrations owned by those users immediately Reactivation restores prior access state (product access & groups preserved). Verification checklist - Users show Suspended in User Browser - Bulk results log confirms who was affected - Spot-check: user can’t log in anymore Next steps (make it repeatable) • Save the filter (great for recurring contractor cleanup) • Turn it into an automated task (run without manual effort) • Add a short runbook in your wiki + do a tabletop test with 2 test accounts (including reactivation behavior) Thanks for watching, go enjoy your reclaimed clicks. #Atlassian #AtlassianCloud #JiraAdmin #ConfluenceAdmin #UserManagement #Security #Governance #Automation #ITAdmin #BulkActions