-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
As a partner, I work with a lot of different organizations. This year I've been getting more and more pushback on creating service accounts in the organization's Azure AD/365 tenant because Jira requires an active email account to be able to use the service account to log in and issue it an API token. Adding mailboxes to service accounts both consumes a 365 license and often violates organizational policies for service accounts. This issue is compounded in organizations using Azure sync for user management (SCIM) because we aren't able to create local Jira accounts.
If we could issue API tokens for service accounts without having to log in as the service account to issue it, that would bypass these organizational issues. Oftentimes it takes weeks to convince the client to create the mail-enabled service account, which has a very negative impact on our projects.
28b71527d627 the link Atlassian is providing in the admin area leads to a 404: Atlassian Support
I found some additional information in the release track: Atlassian Cloud changes Jul 28 to Aug 4, 2025