alert_policy & notification_policy return 403 error in terraform pipeline

[Sandra Herlufsen]

Terraform Provider version: atlassian/atlassian-operations 2.0.3

Affected resources:

• atlassian-operations_alert_policy
• atlassian-operations_notification_policy

Description:

When running terraform plan, the provider returns a 403 error when trying to read alert policies and notification policies:

Error: Client Error
Unable to read alert policy, status code: 403. Got response: {“errors”:[{“title”:“You are not authorized to see team details.”}]}

Error: Client Error
Unable to read notification policy, status code: 403. Got response:
{“errors”:[{“title”:“You are not authorized to see team details.”}]}

What is suspicious: The error message says “not authorized to see team details” — but we are trying to read a policy, not a team. This suggests the provider is making an internal team API call as part of reading the policy,
and that call is failing.

Account permissions:

• The account used for the API token (email_address) has Team Admin role in JSM Operations
• The same account can see and access all policies in the browser UI without any issues

What works fine with the same account:

• atlassian-operations_team 
• atlassian-operations_schedule 
• atlassian-operations_escalation 
• atlassian-operations_routing_rule 
• atlassian-operations_api_integration 
• atlassian-operations_integration_action 

What fails:

• atlassian-operations_alert_policy  403
• atlassian-operations_notification_policy  403

All of the above use the same team_id. The fact that escalations and routing rules work while policies do not — despite identical team permissions — strongly suggests this is a provider-side issue where the policy read
implementation triggers an additional team API call that is not necessary (or uses a different endpoint) compared to other resources.

Expected behavior: A Team Admin account that can view policies in the UI should be able to read them via the API/provider.

[Tuncay Senturk _Snapbytes_]

Hi @Sandra Herlufsen 

Sorry for the late response, I am unsure if you already found the solution for this.

This 403 error message usually indicates that the request being executed by the provider is hitting a Teams API endpoint internally. As you suspected, some endpoints resolve additional team metadata during the read operation.

Even if the user is a Team Admin in the UI, the API token may still lack the required scope for certain team-related endpoints. It’s worth confirming that the token is created by a user who has access to the team in JSM Operations (not just UI visibility).

I'd also suggest calling the API endpoints directly with the same token via curl or Postman). It's easier to spot the problem there.

I hope this sheds light. 

[Sandra Herlufsen]

Thanks for your response.

Our admin also created a support ticket and the Atlassian Team is currently working on the problem. It seems not to be a configuration problem but rather a problem introduced by the Terraform provider.