atlassian-operations Terraform provider doesn't work with service accounts — please add scoped-token

[Vani Puppireddy]

Hi Atlassian team — writing because we can't use the atlassian/atlassian-operations Terraform provider with a service account, and we'd really like to.

Issue:

Our team uses a service account to manage our JSM Operations setup as code. When we try to run Terraform, we get this error:

"Unable to read user, got an empty response. This could be due to invalid credentials or no user being found for the given email address."

Someone else reported the same error a year ago — see this unanswered thread.

reason:

The provider only accepts classic (unscoped) Atlassian API tokens. It cannot use scoped tokens or OAuth 2.0. But Atlassian only lets service accounts create scoped tokens or OAuth credentials — classic tokens can only be created from a personal Atlassian account. So service accounts are locked out by design.

• The Teams resource calls https://{domain}.atlassian.net/gateway/api/public/teams/v1/org/. This URL returns 401 for scoped tokens (related: CLOUD-12617).
• No code in the provider repo uses api.atlassian.com/ex/jira/{cloudId}/..., which is where scoped tokens do work.
• No OAuth 2.0 support. Verified against the latest release v2.0.3 (March 2026).

Our workarounds:
Fall back to the older opsgenie/opsgenie provider — works with our service account via an Opsgenie API key, but Opsgenie REST APIs shut down on April 5, 2027. Temporary fix only.

Ask:

Please add below atlassian/atlassian-operations:
Scoped-token support via the api.atlassian.com/ex/jira/{cloudId}/... URL pattern.

This would unblock service-account automation before the April 2027 Opsgenie cutoff forces everyone to re-migrate.

Thanks.