System/service accounts in Atlassian Cloud

[Rune Rasmussen]

Hello

Preface

In our organization, like most others, we have need of system or service accounts from time to time.
Accounts that aren't tied to any specific person but rather a function or a task.

In Atlassian Cloud every account is classified as a User account and must have a valid mailbox.

We provision all accounts from EntraID and use Exchange Online for our mailing needs.
User provisioning won't happen if there is no email address for the user.
Getting an email address requires some sort of Microsoft license and that costs money.

The question

How does other companies approach this?
Does anyone of you out there have some wise words or good advice on this topic?

[Oleksii Melnyk]

@Rune Rasmussen hi! Good question.

I use two cases depending on security policies:
1. Creating local accounts inside Jira on a free domain (Payment only to Atlassian) - not as safe, but cheaper.
2. Creating an account in an identity provider (Payment to the provider + Atlassian). - safe, but more expensive.

[Calvin]

We use Microsoft Shared mailboxes owned/shared by the group/users who will be running the service account. Checking online it looks like you can add up to 50gb of data before it requires a Microsoft license. Though I think it sill still use an Atlassian Cloud license.