Anyone want to raise a new ticket for this request as Atlassian appear to have found a great loophole to prevent the actual spirt of the request being actioned while still being able to point to a document with the words 'default non-billable policy' and claim completion?

Hi Atlassian Team, this is really very much disappointing. There is no benefit with this announcement (After waiting for so many years) and issue is closed. Please reopen this issue and allow to implement non billable policy as a default which helps for domain users. As of now zero benefit and all the customers looking for the same.

I agree with Steffen, you didn't solve the issue!

new users still going to the paid policy, you must add a way to configure what is the default policy for new users on a domain.

Similar problem for me - I need to make the "New users" from identity provider sync to be "nonbillable" by default (which is currently not possible), because anyone of a 10000 user base could just login with the domain name and would be put into the default identity provider policy. If i want to use features like SSO I can manually move them to a paid policy to enable those features. 

There is no need to even have valid users / mail-addresses: Just login / register with "abcdef@domainname" (or a typo in the user mail which happens frequently)  causes the "new user" (identity provider) policy to pick up the user and we would have to pay for it.

But at the moment i have to manually move all "new users" (~50 / month) to the nonbillable policy right before billing is due.

Can you please enable "nonbillable" policy for default identity provider policies as well? Thank you!

Good intentions, but perhaps not such a good idea. How about when you already have a non-billable policy not linked to the domain? It will resent/resends all the user password!

And why not simply make it possible for an already existing linked domain policy do be non-billable and default?

To me this really looks like an after-thought and something to make a simple thing more complicated.

Possibly it's alright if you start with an empty organization but you have to keep in mind that's not always the case.

For me, this implementation doesn't really solve my problem.

This feature is now available in Atlassian Cloud Admin. For more information about how to set up a default non billable policy see this page: https://support.atlassian.com/security-and-access-policies/docs/understand-authentication-policies/#To-make-a-default-policy-non-billable

We are in the process of rolling this out to all customers. It's live for the majority of customers, though we still have some customers to migrate. I expect this to be complete over the next few weeks.

Hi @BenMargo,
 Since we have past mid August, when can we expect this is PROD?
Is it in testing phase now? Can you please update us.

Any update on ETA?

7d5f9977c93d At this point we expect to deliver this capability to all customers in early August.