Microsoft 365 for Jira service management

Microsoft 365 for Jira connects Microsoft Teams and Outlook with Jira Service Management. Customers and employees can communicate through familiar Microsoft 365 tools, while JSM retains the request workflow, ownership, SLAs, and reporting.

Internal ticketing with Microsoft and Jira is relevant for IT support, HR, facilities, finance, legal, procurement, security, workplace management, and shared service teams. It can support organizations across manufacturing, trade and logistics, financial and payment services, healthcare, clinical research, construction, energy, retail, professional services, and the public sector.

It is particularly useful when service teams manage structured requests in JSM while employees and frontline workers communicate through Microsoft Teams or Outlook. Regulated organizations should define appropriate access, sharing, and retention rules for each service workflow.

Yes. Organizations can embed the JSM customer portal in Microsoft Teams. We recommend the portal as the primary way to submit structured requests. However, organizations can also turn messages from dedicated support channels or existing Teams conversations into requests and use automation for routing, updates, and follow-up actions. This provides a flexible workflow that can be adapted to different service processes and user habits.

Yes. The Outlook integration lets agents create requests from emails, including on behalf of the sender when permissions allow it. Email content, formatting, and attachments can be transferred to Jira.

The JSM customer portal is also available in Outlook. We recommend onboarding users with one clear, preferred way to raise requests based on how they normally communicate, while keeping alternative channels available for flexibility.

Yes. Teams chats can be started from JSM requests and used for ongoing communication with requesters or internal teams. Depending on the service workflow, we recommend automatically creating a dedicated Microsoft Teams chat for appropriate support cases.

Combined with agentic workflows for intake, summaries, routing, and updates, this creates a consistent, low-friction service experience while JSM retains the workflow, ownership, and SLAs. Messages can remain accessible in Teams and Jira from the initial request through resolution.

No. Customers can create and track support requests through the Teams portal app without a Jira license. They can access request details, leave comments, and monitor progress under “My Requests”.

Microsoft 365 for Jira supports more than one-way notifications. Users can submit requests and communicate in Teams, while messages, status changes, comments, and selected updates remain connected to the relevant JSM request. Adaptive Cards can present structured Jira information in Teams.

The standard Jira email channel creates requests from messages sent to a service address. Microsoft 365 for Jira extends the workflow into Outlook and Teams, allowing users to create requests from existing communication and enabling agents to keep chats, emails, meetings, and ticket context connected.

Microsoft-first organizations can make JSM workflows available where employees already communicate. This reduces the need to introduce another daily interface and can lower Jira adoption barriers without removing Jira’s structure or reporting capabilities.

Depending on the configured features, AI can assist with preparing request content, answering routine questions, or summarizing connected communication. Agents remain responsible for decisions and outcomes.

Customer estimated saving approximately 5 to 10 minutes per request by reducing manual creation and context transfer. At around 5,000 requests per year, this represents a rounded calculation of approximately 400 to 800 hours saved annually.

Microsoft 365 for Jira supports Jira Cloud and Jira Data Center, but some capabilities differ between the two deployment models. Atlassian has announced that affected Data Center products, including Jira and Jira Service Management, will reach end of life on March 28, 2029. At that point, Data Center subscriptions and associated Marketplace apps will expire and become read-only. Administrators should review the Cloud and Data Center feature comparison and include the integration in their Cloud migration planning.

Implementation normally requires both Jira and Microsoft administrators. The Jira administrator installs and configures Microsoft 365 for Jira, while Microsoft administrators approve access and help deploy the Outlook add-in or Teams apps.