Atlassian Guard be included as part of Jira subscriptions, particularly for Jira Software and Jira Service Management cloud plans.

Why Atlassian Guard Should Be Included
1. Security is Not Optional
In today's digital environment, security is a necessity, not a premium feature. With increasing cyber threats, every organization-regardless of size-requires baseline identity and access management tools to protect their workspaces. Features like SSO, enforced 2FA, audit logging, and admin insight should be standard, not locked behind a separate paywall.

2. Simplifies Adoption for Small to Medium Teams
Many smaller businesses and teams rely on Jira but struggle to justify the additional cost of Atlassian Guard. By integrating Guard with existing subscriptions, you enable these teams to adopt best security practices without friction, improving overall platform security and trust.

3. Aligns with Industry Standards
Competitors such as GitHub, GitLab, and even Microsoft (with Azure DevOps) include essential security controls in their base plans. Including Guard will help Atlassian remain competitive and aligned with industry expectations for enterprise-readiness.

4. Reduces Risk for All Users
As Jira instances grow and become more widely adopted within organizations, the risk of mismanagement or unauthorized access increases. Bundling Guard will reduce Atlassian's own exposure to incidents stemming from insecure customer setups.

5. Better User and Admin Experience
Providing Guard out-of-the-box reduces fragmentation in billing, onboarding, and configuration. Admins can implement Guard's features immediately without needing separate procurement or budget approvals, leading to faster, more secure adoption across teams.

Suggested Approach
A practical step would be to include a core tier of Atlassian Guard features with all Jira plans, and offer premium security and compliance features (e.g. advanced audit logs, DLP, and SCIM provisioning) in a higher tier. This tiered approach provides value while maintaining upgrade paths for larger organizations.

We believe this change would significantly enhance the Atlassian customer experience and foster more secure, reliable use of Jira across all industries. Thank you for considering this request.