ITSM 23. September 2026

Enable direct Jira ticket submission in Microsoft Teams

Header image What changes when the JSM portal comes to Teams

A broken laptop, a missing software license, or an access request often begins with a quick Microsoft Teams message. That may be convenient for the employee, but it leaves the service team with an unstructured request that can be difficult to assign, prioritize, and track.

The Jira Service Management portal in Microsoft Teams turns these informal requests into a consistent service process. With structured Jira ticket submission in Microsoft Teams, employees can select the correct request type, complete the required fields and forms, and follow their ticket without leaving their daily workspace. Meanwhile, service agents retain the workflows, ownership, priorities, and service-level agreements they need in Jira Service Management.

Why bring the JSM portal into Microsoft Teams?

Employees ask for help in Teams because it’s where they are already working. The service team needs those requests in Jira Service Management, where each one can be categorized, assigned an owner and priority, and tracked through resolution.

Embedding the JSM customer portal in Teams connects these two requirements. Employees receive an accessible service entry point, while agents continue working with structured requests in Jira.

Jira Service Management does not natively place a service portal in Microsoft Teams. With Microsoft 365 for Jira, employees can open the portal from Teams, choose a service desk and request type, complete the configured form, and submit a request. Putting that process where employees already ask for help makes it easier for them to use the right form, while giving the service team the details it needs to route and track the request from the start.

After submission, the request appears in Jira Service Management, where the service team can route it to the right queue, assign an agent, apply an SLA, and move it through the established workflow. Agents can also collaborate in Microsoft Teams through a chat connected to the ticket, so their discussion stays tied to the request as they work toward a resolution.

The JSM portal keeps ticket intake in Microsoft Teams structured

A chat message is suitable for asking a quick question. It is less suitable for collecting all the information needed to process an access request, investigate a device problem, or onboard a new employee.

The JSM portal solves this by preserving the request structure already configured in Jira Service Management. Different request types can collect different information. An account request may ask which system and access level are required, while a hardware request may ask for the device, location, business impact, and preferred replacement date.

Required fields help prevent incomplete requests. Jira forms can collect additional or conditional information, and suggested Confluence knowledge base articles may help employees resolve common issues before submitting a ticket.

This gives the service team better information from the beginning. It also reduces follow-up questions such as “Which device is affected?” or “When do you need access?”

Employees can follow requests without opening Jira

Ticket submission is only one part of the employee experience. People also want to know whether their request has been received, who is working on it, and whether further information is required.

The Teams portal app includes areas for new requests, existing requests, and activity. Employees can use “My Requests” to review their tickets and follow their progress. Configured notifications can inform them about public comments, approvals, and status changes.

The service agent remains in Jira Service Management. The employee remains in Microsoft Teams. Both sides work with the same request and status instead of maintaining separate conversations.

The Teams portal app documentation explains the available portal settings, request notifications, deployment responsibilities, and supported forms. The rollout can follow how your organization is structured, whether by department, location, or function. Jira administrators choose which JSM portal the app displays, while Teams administrators deploy it to the users who need that portal. This puts the relevant service entry point in front of the right team.

Give guidance but keep other ticket creation options available

The JSM portal should guide employees through repeatable requests that need structured information. But people will still report problems in the conversation they are already having, email someone they know, or mention an issue on a call. If those reports stay outside Jira, they also stay outside the team’s queues, ownership, and tracking.

Keep a path from each of those interactions into the service workflow. A Teams chat or channel message can become a Jira request linked to the conversation. From Outlook, an agent can create a Jira or JSM request from an email, include relevant content and attachments, and submit it on behalf of the sender. Agents can also create tickets directly in Jira for phone calls, monitoring alerts, or meetings.

The portal remains the standard entry point. These other routes ensure that an unexpected way of reporting a problem does not prevent it from becoming managed service work.

How to implement the JSM portal in Teams

Start by reviewing the request types and forms employees already use. Remove unnecessary fields, make essential information mandatory, and confirm that portal permissions are appropriate for the intended audience.

Next, install Microsoft 365 for Jira from the Atlassian Marketplace and activate the required Teams features. The Jira administrator prepares and configures the portal app, while the Microsoft Teams administrator deploys it to the relevant users. Microsoft 365 permissions and notifications may also require administrative approval.

Before a wider rollout, test the complete employee journey:

  1. Open the portal in Teams.
  2. Submit each important request type.
  3. Verify fields, forms, attachments, and knowledge suggestions.
  4. Confirm that the request reaches the correct JSM project and queue.
  5. Test comments, approvals, notifications, and “My Requests”.
  6. Verify access with a representative employee account.

The Microsoft 365 for Jira setup guide describes the responsibilities of Jira, Teams, and Microsoft 365 administrators.

Can employees submit JSM requests without opening Jira?

Yes. Microsoft 365 for Jira can make a configured Jira Service Management customer portal available as an app in Microsoft Teams. Employees can select request types, complete portal fields and forms, and submit requests from Teams. The support-ticket submission guide shows the available submission and tracking options.

Do customers / employees need a paid Jira license?

Employees (customers) can submit and track JSM requests as customers without a paid Jira license; licenses are for agents who work on the tickets. Customer access is a separate question. An employee using the portal in Teams must still be allowed into the relevant JSM portal. Depending on the organization’s settings, they may be invited in advance, allowed to create a customer account, or created as a customer when they first open the Teams portal. JSM then applies the portal’s access rules. Authentication may use a password or configured single sign-on; Atlassian’s portal access guidance explains those settings.

Does the Teams portal support Jira forms and custom fields?

The Teams portal can use the forms and fields configured for the JSM customer portal. This allows administrators to preserve structured intake. Current form support and configuration guidance are documented under raising support tickets from Teams and the Teams portal app.

Can employees track their requests in Microsoft Teams?

Yes. Employees can use “My Requests” to access submitted tickets and review their progress. Notifications can cover events such as status changes, public comments, CSAT and approvals. The portal app must be installed for notification recipients, and notifications must be configured in the relevant JSM project. See the Teams portal notification guidance.

Can a Teams message be converted into a Jira request?

Yes. Supported Teams chat messages and channel conversations can be used to create Jira work items or JSM requests. This is useful when an informal discussion becomes actionable. The portal remains the better option when the service team needs users to select a defined request type and provide mandatory information. Review the conversation-to-work-item documentation for supported fields, sharing behavior, and configuration requirements.

Can employees or agents create JSM requests from Outlook?

Microsoft 365 for Jira also supports Outlook-based workflows. Agents can create requests from emails, transfer relevant content and attachments, and create a request on behalf of the sender when the JSM configuration permits it. A customer portal can also be deployed in Outlook. See the documentation for creating work items from Outlook emails and the JSM customer portal in Outlook.

How does this fit with Atlassian’s Microsoft and Rovo strategy?

Rovo in Copilot and Teams is the AI layer: it helps users find information and create or update Jira work using natural language. Microsoft 365 for Jira is the integration layer: it keeps Teams conversations, Outlook emails, and meetings connected to the relevant Jira work item.

Both connect Microsoft 365 with Jira, but from different directions. Rovo helps users act on knowledge, while Microsoft 365 for Jira preserves the communication context around the work. These connections lay a foundation for AI: Rovo skills could use linked communication to understand what happened around a work item instead of relying only on its fields.

Which administrators are required for setup?

The rollout requires coordination between Jira and Microsoft administrators. Jira administrators install Microsoft 365 for Jira, select the relevant JSM portal, and prepare the Teams portal app. The Microsoft Teams administrator deploys the app and may need to authorize notifications. Microsoft 365 permissions may require additional consent. Learn more in the administrator setup guide.

How does yasoon protect data in Microsoft 365 for Jira?

Data security is a core priority for yasoon. Therefore, yasoon is ISO 27001 certified and SOC 2 compliant. In addition, data storage is minimized by retaining identifiers instead of sensitive content. Data is encrypted, and regular penetration testing helps maintain a strong level of security.

Detailed security information and reports are available in the Security Documentation and yasoon Trust Center, where customers can also request the SOC 2 report.

What changes when you bring the JSM portal to Teams?

Employees no longer have to choose between the convenience of Microsoft Teams and the structure of Jira Service Management. They can submit and track requests where they already work, while service teams retain forms, ownership, SLAs, workflows, and reporting.

The practical benefits reported by Microsoft 365 for Jira customers include approximately 60% faster response times in complex projects, 30 to 40% faster processing of service requests, and an estimated 25% productivity increase for support teams. These are customer-specific outcomes from connected Microsoft 365 and Jira workflows, not guaranteed results from the portal alone.

Microsoft 365 for Jira connects this structured portal intake with Teams conversations, Outlook email, and automation. Book a tailored demo to explore what the same approach could change in your organization.

Book a demo