Atlassian Certification in 2026: Jira, Confluence and Cloud Administration Credentials

Atlassian's certification landscape in 2026 is firmly cloud-oriented and role-based. The current learning catalog separates Associate credentials for people who use Atlassian products in their daily work from Professional credentials for administrators who configure products, projects, service environments and organizations. Jira, Confluence, Jira Service Management and Atlassian Cloud administration all appear in the active learning ecosystem, alongside newer certificates and Rovo-related learning.

Candidates should treat the live Atlassian Learning catalog as the authority because the program is changing. Older server-era ACP material can still appear in search results, while current cloud credentials can be updated, combined or retired. The most important 2026 example is Managing Jira Projects for Cloud: Atlassian's current exam page says the certification will retire in January 2027 and selected content will move into Jira Administration for Cloud.

Associate credentials prove productive use of the platform

Atlassian Certified Associate options include Jira Essentials, Confluence Essentials and Jira Service Management Agent Essentials. These credentials are aimed at practitioners who need to work effectively inside the products, not at administrators responsible for enterprise-wide governance. Jira Essentials, for example, emphasizes work items, spaces, boards and collaboration in scrum and kanban environments.

That makes workflow concepts more important than memorizing the user interface. A Jira user should understand why a backlog, sprint, board, workflow status and work-item field exist and how they support the team's operating model. The comparison of Agile and Waterfall delivery models can provide useful context, but preparation should return to how Jira expresses the team's chosen way of working.

Associate preparation should include everyday collaboration behavior, not only navigation. In Jira, that means understanding how work types, fields, filters, boards and workflows support visibility and team decisions. In Confluence, it means structuring spaces and pages so information remains discoverable, permissioned and maintainable. In Jira Service Management, agents need to understand queues, request context, SLAs and knowledge use. These are ordinary activities, but certification questions become easier when the candidate can explain the purpose behind each configuration rather than remembering where a button appears in the current interface.

Professional credentials separate project, product and organization administration

Atlassian Certified Professional credentials currently include Jira Administration for Cloud, Atlassian Cloud Organization Admin, Managing Jira Service Projects for Cloud and Confluence Administration for Cloud. These roles overlap, but their control surfaces differ. A project administrator configures a project to meet team needs; a Jira administrator manages reusable configuration and broader product behavior; an organization administrator manages users, product access, domains and organization-level settings.

The ACP-420 Managing Jira Service Projects for Cloud certification belongs to the service-project specialization. The ACP-620 Managing Jira Projects for Cloud certification is still relevant in late 2026, but Atlassian explicitly marks it for retirement in January 2027. Candidates choosing between ACP-620 and Jira Administration for Cloud should therefore plan around the transition instead of assuming both paths will remain unchanged.

The practical distinction is scope. A candidate can be very strong at configuring one project and still be unprepared for global permissions, shared schemes, product-wide settings, user governance or organization administration. Professional-level preparation should make those boundaries explicit.

The professional certifications differ largely by scope of authority. A project administrator can make decisions inside a defined Jira project, while an organization or product administrator has to consider shared configuration, governance, permissions, standardization and the effect of a change on many teams. Practice should therefore include impact analysis: before changing a scheme, field, permission or workflow, identify who else uses it and what could break. This is particularly important in Cloud environments where administrators can move quickly and where one convenience change can create long-term configuration debt.

Jira Service Management adds a service-operations model

Jira Service Management is not simply Jira with a different screen. Service projects introduce request types, queues, service-level targets, knowledge integration, incident and problem workflows, approvals and operational automation. Administrators need to understand how those pieces shape the experience of requesters, agents and service owners.

This is where incident and problem management becomes a useful supporting concept. An incident workflow is designed to restore service; problem management looks for causes and recurrence reduction. A candidate who understands that distinction can configure statuses, queues and automation around the service objective rather than treating every ticket as the same kind of work.

Jira Service Management scenarios become more realistic when incident, request, problem and change work are separated by objective. A service request may follow a predictable fulfillment path; an incident prioritizes restoration; a problem seeks underlying causes; a change needs risk evaluation and controlled implementation. Candidates should practice designing queues, forms, automation and SLAs around those different outcomes. Otherwise it is easy to build a single generic ticket workflow that looks tidy but provides weak operational information and creates poor handoffs between support, engineering and business stakeholders.

Cloud organization administration is governance, not just configuration

Atlassian Cloud Organization Admin reaches above any single Jira or Confluence project. Current Atlassian material frames the role around configuring and managing cloud sites and products to support the organization. In practice that includes product access, user and account administration, domain-level concerns, security settings and governance choices that affect several teams at once.

A useful preparation habit is to define the blast radius of every setting. Is it local to one project, reused by several projects, global to a product or applied at organization level? The more broadly a setting applies, the more important change control and testing become. Administrative expertise is not knowing where the switch lives; it is understanding who will be affected when the switch moves.

Organization administration also includes identity and lifecycle concerns. Domains, managed accounts, authentication policy, product access and administrative roles affect how users enter and leave the Atlassian environment. A sound governance model should answer who can create or administer products, how access is reviewed, what happens when an employee leaves and how exceptions are documented. These are less visible than board configuration, but they become critical as an Atlassian estate grows across multiple products and business units.

Hands-on configuration should include intentional failure

Atlassian recommends documentation, on-demand learning, practice resources and real-world experience. For administrator exams, a safe cloud environment is especially valuable. Build permissions, workflows, issue or work-item configurations, service queues, automations and product access. Then introduce a failure deliberately and diagnose it from the user's point of view.

This is also where cross-platform comparisons can sharpen understanding without replacing product study. Jira and Azure DevOps can both support work tracking, but their surrounding ecosystems and administration models differ. The exam will test Atlassian behavior, so the comparison is useful only if it clarifies what Jira is doing and why.

Hands-on failure exercises are valuable because Atlassian configurations are relational. Change a permission and observe who loses access; alter a workflow condition and test which transitions disappear; modify a field context and see where the field no longer behaves as expected; create a faulty automation and inspect the audit log. This builds a causal model of the platform. It also trains the candidate to use evidence rather than intuition when a configuration works for one team but not another.

Use the 2027 transition to choose a durable path

For a candidate beginning in late 2026, timing matters. Managing Jira Projects for Cloud remains available now, but Atlassian says it will retire in January 2027 as selected content is incorporated into an updated Jira Administration for Cloud exam. Someone whose role is narrowly project administration may still have a reason to complete ACP-620 before retirement; someone building a longer-term Jira administration path may prefer to prepare for the consolidated administration direction.

Whichever credential is chosen, the strongest readiness test is operational. Can you explain which configuration layer owns a behavior, predict the side effects of a change, diagnose a permission or workflow problem and choose a configuration that scales across teams? Those are the skills that remain useful even as Atlassian adjusts individual exam names and codes.

The January 2027 retirement of Managing Jira Projects for Cloud should be treated as a planning constraint, not a reason to rush into an unsuitable exam. Candidates who are already prepared and need that credential before retirement can evaluate the remaining testing window. Others may gain more durable value from the Jira Administration for Cloud path and the content Atlassian is carrying forward. In either case, current certification pages should be checked close to scheduling because the cloud portfolio is actively being reorganized.

A final readiness check should use a small Cloud environment and a written set of business requirements. Configure a team workflow, permissions, fields, automation, reporting and a service-management use case, then ask another person to change one requirement. The revision exposes whether the configuration is understandable and resilient or whether it depends on undocumented assumptions. Record which settings are shared, which are local and which require organization-level authority. This exercise is particularly useful during a certification transition because product names can change while the underlying administrative questions remain: who owns the configuration, who is affected, how is access controlled, and how can a change be tested without disrupting other teams?

100% Real & Latest Atlassian Certification Practice Test Questions and Exam Dumps will help you prepare for your next exam easily. With the complete library of Atlassian Certification VCE Exam Dumps, Study Guides, Video Training Courses, you can be sure that you get the latest Atlassian Exam Dumps which are updated quickly to make sure you see the exact same questions in your exam.