Access management after migration

Opsgenie’s Single Sign-On (SSO) isn’t natively supported in Jira Service Management or Compass. You can use Atlassian Guard to replicate SSO and security features. 

Migration summary

Is this feature fully available in all Jira Service Management and Compass plans?

No. Opsgenie SSO is deprecated and isn’t available in Jira Service Management or Compass. To continue using SSO, customers must purchase an Atlassian Guard subscription separately.

Is this feature auto-synced after data migration?

No, SSO settings aren’t migrated. Customers must manually configure Atlassian Guard and claim user accounts to restore SSO functionality in Jira Service Management or Compass.

Are there required actions for full workflow parity?

Yes, users must:

• Work with your billing admin to see if you have an Atlassian Guard subscription or set up a new one. 

• Work with your Org admins to configure SSO in Atlassian Guard for Opsgenie users migrating to your destination product.

• Claim user accounts in Atlassian Guard to ensure continued access control.

• Review their Atlassian Guard billing after migration if they already have an AG subscription.

Understand Atlassian Guard and set up a subscription

Before configuring SSO, contact your organization admin to check whether your organization already has an Atlassian Guard subscription. If a subscription isn’t in place, review which plans are available based on the product and plan you’re migrating to.

1. Once you select a plan, review requirements and read how to subscribe to an Atlassian Guard plan.

2. After you’re subscribed, or if you already have an active subscription, proceed with provisioning users from your identity provider.

Get started with Atlassian Guard.