Before the Meter Starts: How a Small IT Team Keeps Its Atlassian Licenses Healthy

Atlassian license bill shock shown as a man in round glasses staring at a sheet of paper with one hand on his head

Summary

Atlassian starts billing for automation steps beyond each organization’s monthly allowance on December 3, 2026, with Rovo credits metered from the same date, which gives small IT teams that run Jira a reason to check their licenses now. James Clark sets out five checks: confirm which user tier you pay for, remove inactive users before adding new ones, work out your automation allowance, watch platform usage and decide what happens at the limit, and time billing changes around the renewal window. The plan type decides when a clean-up saves money, since annual plans bill a whole tier and only drop at renewal, while monthly plans bill the highest user count reached in the billing cycle. He recommends turning the checks into a routine, with usage reviewed monthly, inactive users and the agent list reviewed quarterly, and tier position and extra usage limits reviewed before each renewal.

On 3 December 2026, Atlassian starts billing for automation steps beyond each organization’s monthly allowance. Rovo credits get the same treatment on the same date. Atlassian says most customers won’t exceed their allowances. This is probably true. It’s also exactly what everyone assumes until the invoice says otherwise.

If you’re the small IT team that inherited Jira, this is a good excuse for a proper license check-up. Cloud list prices also went up on 13 October, so a tidy Atlassian license estate is worth a bit more than it was.

None of the steps below are one-offs, though. They work just as well next quarter, and the quarter after that.

1. Know which tier you’re actually in

Atlassian Cloud is priced in user tiers, and how the tiers work depends on how you pay.

On an annual plan, you pay for one fixed tier. Atlassian’s own example: 480 Jira Standard users are billed at the 500-user tier. Add 85 people, and you’re at 565, which puts the whole subscription in the 600-user tier, with a prorated charge for the rest of the term. So what matters is how far you are from the next tier boundary, not how many people you have.

On a monthly plan, the price is worked out across tiered bands of users, and the bill uses the highest number of users who had access at any point in the billing cycle. Atlassian calls this maximum quantity billing.

To see your billable users, go to Settings, then Billing, then Manage subscriptions. Each product shows its own count.

If you run Jira Service Management, remember that you license agents. Customers raising requests are free and don’t need a license. So ask whether everyone with agent access actually works tickets.

2. Clean up inactive Atlassian users before you add anyone

A user counts towards your bill as soon as they’re given product access. They stop counting only when you remove that access, suspend them or remove them from the organization. Leavers whose accounts were never touched still count toward the bill.

The user list in Atlassian Administration shows when each person was last active. Atlassian’s own advice is to check with people before you deactivate them, which is sensible. The person who logs in once a quarter to approve something will notice.

A few things catch people out:

  • Access often comes through groups, not just the default group. Removing app access in a user’s profile takes them out of every group that grants that app. Removing them from one group might not.
  • If users sync from an identity provider such as Entra ID, make the change there. Otherwise, the sync may put them straight back.
  • Suspending is reversible and keeps a user’s groups and roles. Removing isn’t, and you’d have to set everything up again.

Timing matters too. On a monthly plan, removing someone mid-cycle doesn’t reduce that month’s bill, because the maximum has already been counted. Do the clean-up before you add new starters, not after. On an annual plan, fewer users only saves money at renewal, when you can ask to move down a tier.

3. Find out what your Atlassian automation allowance is

Automation is now measured in steps. Every trigger, condition, action, branch, and loop that runs counts as one step. Atlassian’s example is a rule with one trigger, one condition, and two actions, which uses four steps each time it runs. A trigger that fires and finds nothing to do still counts as a step.

Your allowance depends on your products and plans. It’s pooled across the whole organization and refreshes monthly, even on an annual plan. Unused steps don’t roll over. As a guide, Jira Standard includes 400 steps a month for each user and Jira Premium 750. Jira Service Management Standard includes 3,000 and Premium 6,500. Atlassian’s example adds 100 Jira Premium users and 100 Confluence Standard users together for a shared pool of 85,000 steps a month.

Two details are easy to miss

  1. Steps run in a sandbox count towards the same allowance
  2. Automation steps that use Rovo or an agent are charged in Rovo credits rather than steps.

To estimate a rule’s cost, multiply how often it runs by the number of components it runs through. Rules that fire on every issue update deserve a closer look. A bulk edit of a few thousand issues can trigger them a few thousand times.

4. Watch your Atlassian usage and decide what happens at the limit

Go to Atlassian Administration, then Insights, then Platform usage. You’ll see usage against your allowance, up to 90 days of history and an estimate for the month. You can also export the data as a CSV. The dashboard filters by app rather than by rule, so you’ll still need your own estimates for the busy rules.

Alerts at 80% and 100% of your allowance only go to organization admins and billing admins. Check that those roles belong to people who read their email.

Then make a decision rather than inheriting a default. Atlassian’s usage-based pricing page says extra usage is switched on by default for most customers. With it on, rules keep running and extra steps are billed at $0.50 per 1,000. With it off, automation stops when the allowance runs out, and stays stopped until the allowance resets. Events that happen in the meantime aren’t replayed. There’s a middle option: keep extra usage on but set a monthly spending limit. You can do this separately for each meter, so automation and Rovo credits can have different rules.

5. Time your Atlassian billing changes deliberately

Annual subscribers get a renewal quote automatically 90 days before expiry, and you can only renew within that 90-day window. Put the date in the diary, and do the user clean-up before the quote is generated, not after.

Don’t assume annual is cheaper. Annual charges for the whole tier whether you fill it or not, while monthly charges for the users you actually have. A team sitting low in a tier can pay less on monthly, so run both against your real user count before you switch. If annual does win, size the tier after the clean-up, or you’ll be paying a year’s worth for leavers.

A routine worth keeping

These steps are a routine worth repeating:

  • Monthly – look at Platform usage and see which way it’s trending.
  • Quarterly – review inactive users and the agent list.
  • Before each renewal – check how close you are to a tier boundary, and whether extra usage limits still make sense.

It isn’t glamorous, but neither is explaining an invoice.

Atlassian Licensing FAQs

When does Atlassian start billing for automation steps and Rovo credits?

Billing begins on 3 December 2026 for most meters, though timing can depend on the capability and your billing cadence. It applies only to usage beyond your included monthly allowance. Cloud list prices are a separate change, which took effect on 13 October.

How do Atlassian user tiers work on annual and monthly plans?

On an annual plan you pay for one fixed tier, so 480 Jira Standard users are billed at the 500-user tier, and adding 85 people (565) moves the whole subscription into the 600-user tier with a prorated charge. What counts is how close you are to the next boundary. On a monthly plan, the price is worked out across tiered bands, and the bill uses the highest number of users with access at any point in the billing cycle. In Jira Service Management you license agents only, and customers raising requests are free.

How do you stop inactive users inflating the Atlassian licensing bill?

A user counts as soon as they have product access and stops counting only when you remove that access, suspend them, or remove them from the organization. Check last-active dates in Atlassian Administration, confirm with people before deactivating, and watch for group-based access and identity provider sync, which can put users straight back. Suspending is reversible and keeps groups and roles, whereas removing isn’t. Clean up before adding new starters, because removing someone mid-cycle on a monthly plan doesn’t reduce that month’s bill.

What counts as an automation step with Atlassian, and what is my allowance?

Every trigger, condition, action, branch, and loop that runs counts as one step, and a trigger that fires and finds nothing to do still counts. A rule with one trigger, one condition, and two actions uses four steps per run. Allowances are pooled across the organization, refresh monthly even on annual plans, and don’t roll over. As a guide, Jira Standard includes 400 steps per user a month, Jira Premium 750, Jira Service Management Standard 3,000, and Premium 6,500. Steps that use Rovo or an agent are charged in Rovo credits instead.

What happens when the allowance runs out?

It depends on a setting you should choose deliberately. Extra usage is on by default for most customers, so rules keep running and extra steps are billed at $0.50 per 1,000. With it off, automation stops until the allowance resets, and events in the meantime aren’t replayed. A middle option keeps extra usage on with a monthly spending limit, set separately for automation and Rovo credits. Alerts at 80% and 100% go only to organization admins and billing admins.

Is an annual plan cheaper than monthly, and when should you act before renewal?

Not necessarily. Annual charges for the whole tier whether you fill it or not, while monthly charges for the users you have, so a team sitting low in a tier can pay less monthly. Run both against your real user count. Annual subscribers get a renewal quote automatically 90 days before expiry and can only renew within that window, so finish the user clean-up before the quote is generated.

Further Reading

James Clark
James Clark
Director at TribusIT Limited

James Clark is Director of TribusIT Limited, an Atlassian Silver Solution Partner in Huddersfield. He has worked with Atlassian tools for many years, the last seven as a full-time consultant, and helps UK IT teams that have inherited Jira Cloud. 

Want ITSM best practice and advice delivered directly to your inbox? Why not sign up for our newsletter? This way you won't miss any of the latest ITSM tips and tricks.

nl subscribe strip imgage

More Topics to Explore

Leave a Reply

Your email address will not be published. Required fields are marked *