Resolve Atlassian Guard payment issue

We want to make sure you can easily restore your settings after you resolve an Atlassian Guard payment issue. When you have a payment issue, we let you know in a series of emails. If you’re unable to resolve the payment issue for your subscription within a certain time frame, then your subscription becomes inactive.

What data is retained after a subscription becomes inactive?

When your subscription is inactive, you have a grace period of 14 days to reactivate it. If you’re unable to reactivate your subscription during the grace period, you permanently lose all Atlassian Guard settings and configuration.

Data retained during the 14 day grace period:

• SAML and SCIM configurations

• Authentication policy memberships

• Guard Detect configuration and existing alerts

• Audit log webhook configuration

Data retained indefinitely:

• Data security policy configuration

• Data classification configuration (content also retains its classification)

What features are limited once a subscription is inactive?

For more information on the changes your users or administrators might notice, see:

• Unsubscribe from Atlassian Guard Standard

• Unsubscribe from Atlassian Guard Premium

Reactivate Atlassian subscription

You must contact our support team to reactivate your Atlassian subscription. Support will reactivate your Atlassian Guard Standard or Atlassian Guard Premium subscription for a 30-day free trial.

You can then enter payment information for a monthly or annual subscription plan.

How to reactivate a subscription

Restore authentication policy settings

Once your Atlassian Guard Standard subscription is active, you can restore the security settings in authentication policies.

To restore settings in authentication policies:

1. Go to admin.atlassian.com. Select your organization if you have more than one.

2. Select Security > Authentication policies.

3. Select Edit for the policy you want to restore.

4. Select the setting you want to restore:

   • single sign-on

   • mandatory two-step

   • block user API token access