Jira Service Management

On-call capabilities: Connect schedules and aliases to Microsoft Teams

This Jira Service Management change has been rolling out to Atlassian Cloud sites since 2 Sep 2026. It changes an API, so teams with scripts, apps or integrations should test them against it.

Rolling out since 2 Sep 2026
Low impact
Admin review: api change

Read Atlassian's release note See every change

Where the rollout is

Rollout starts 2 Sep 2026 Done
First published 29 Sep 2026 Done

What changed

29 Sep 2026 First published by Atlassian

Atlas Bench began tracking Atlassian Cloud on 29 Oct 2026. Changes before that date are not in this history.

Source Atlassian's release note Read it on the Atlassian Community

Related changes

Where it lands

Where this change sits on the Stack

Every change is sorted onto the layer it touches first. This one lands on Platform and Migration.

Agents and Automation

Rovo, Agents in Jira, Forge, MCP with Claude and Copilot, agent lifecycle, usage and cost governance.

Atlassian Anthropic

Governance and Change

Permission architecture, audit and compliance, ITSM and change control, change management, strategic reporting and budgets.

Atlassian Guard Jira Service Management Strategy Collection Jira Align

Platform and Migration

Migration of every kind, tool consolidation, licensing, standardization, the system of work.

Atlassian Miro AWS Azure

Identity and Access

Human and non-human identity, SSO, SCIM, least privilege, access reviews, Guard cleanup, Agent SSO readiness.

Atlassian Guard Okta

load-bearing, bottom to top

Find out what you are actually running.

Fixed scope. The assessment reads the estate as it is: instances, schemes, licensing, and the decisions a migration would force you to make anyway. You get the findings, the ownership gaps, and the order to close them in.

Book the assessment

By sending this you agree to our privacy policy.

Not ready? Talk to an architect