Hi everyone! 👋
What if your Jira users stop using Jira, but their licenses keep getting consumed?
If your organization syncs users and groups from Microsoft Entra ID to Jira Cloud, you might have run into this challenge.
Imagine this: an employee hasn’t logged into Jira for 90 days. They no longer need Jira access, and you want to reclaim that unused license. Seems simple, right?
But there’s a catch. 👇
🔍 Why inactive users can become a licensing headache
When your jira-software-users group is synced from Entra ID, its membership is managed by your identity provider. The synced group is read-only in Atlassian Cloud, so you can’t directly remove users from it in Jira.
That can leave Jira admins dealing with:
- 💸 Unused licenses: Inactive users may continue consuming paid Jira seats.
- 🔄 Manual follow-ups: Jira admins need to coordinate with the identity team to clean up group membership.
- ⏳ Delayed license reclamation: Cleanup depends on someone identifying inactive users and updating Entra ID.
- 📈 Potentially higher costs: Unused seats can contribute to unnecessary licensing expenses, especially at renewal.
Sound familiar?
⚙️ How can you save those licenses?
The key is to manage the licensed group membership at its source - Microsoft Entra ID.
Here’s what a streamlined workflow can look like:
1️⃣ Identify inactive users
Define an inactivity threshold, such as 90 days, based on your organization's access policy.
2️⃣ Check their Jira access
Identify users whose product access comes from an Entra ID-synced licensed group.
3️⃣ Review and update Entra ID group membership
Remove eligible users from the relevant group, following your organization's approval and exclusion rules.
4️⃣ Let provisioning sync the changes
Once the updated membership is reflected in Atlassian Cloud, those users can lose Jira product access and their Jira licenses can be reclaimed, provided they have no other source of Jira product access.
💡 One important distinction: Removing Jira product access is not the same as suspending a user account. Removing Jira access can free up a Jira license while allowing the user to retain access to other applications they still need.
🤖 Can you automate this?
Absolutely. Instead of relying on spreadsheets and recurring manual follow-ups, organizations can automate inactive-user identification and eligible licensed-group cleanup using defined rules and safeguards.
At miniOrange, our Automated User Management solution addresses this license optimization use case for Atlassian Cloud, including scenarios involving IdP-synced users and groups.
🔗 Explore the approach: Jira Cloud License Optimization for Entra ID-Synced Users
💬 Let's hear from Jira admins!
I'm curious how other teams are tackling this:
- Do you sync your Jira licensed groups from Microsoft Entra ID?
- How do you identify inactive users who still consume Jira licenses?
- Who owns license cleanup in your organization — the Jira admin team or the identity team?
- Have you automated this process, or are spreadsheets still part of the workflow?
What's your biggest challenge with Jira Cloud license optimization? Share your experience below!
