Getting started for administrators

Use this page as the quickest path to a successful rollout of Microsoft 365 for Jira. The setup is shared between your Jira administrator and your Microsoft administrator. Start with the app installation, decide which features you want to roll out first, then complete the Microsoft-side login and deployment steps for the products you plan to use.

Recommended approach: Decide early whether you want to start with Microsoft Teams, Outlook, or both. The technical login and the end-user rollout are handled separately for each track.

Step	Owner	What happens	Outcome
1	Jira admin	Install Microsoft 365 for Jira	App is available in Jira
2	Jira admin	Choose the initial feature set	Clear rollout scope for Teams and/or Outlook
3.1	Jira admin + Microsoft admin	Enable technical login for Teams	Users can sign in to Teams-related features
3.2	Jira admin + Microsoft admin	Coordinate the rollout of the Teams app	Teams features become usable in Microsoft Teams
4.1	Jira admin + Microsoft admin	Enable technical login for Outlook applications	Users can sign in to Outlook-related features
4.2	Jira admin + Microsoft admin	Coordinate the rollout of the Outlook add-in	Outlook features become usable in Outlook
5	Jira admin	Review use cases for inspiration	Better understanding of practical rollout options
6	Jira admin + champions	Prepare rollout presentation for key users	Smoother adoption and better feature awareness

Step-by-step setup

1. Install Microsoft 365 for Jira

This is the only step the Jira administrator can complete fully on their own. Install the app from the Atlassian Marketplace.

Make sure the app is installed successfully in your Jira site.
Open the app administration area in Jira and verify that the configuration pages are available.

If you are planning a pilot, it helps to define a small test group now so both the Jira admin and Microsoft admin can validate the setup before a broader rollout.

2. Decide on the initial feature set

Before coordinating with your Microsoft administrator, decide which features you want to introduce first. This keeps the approval and rollout effort focused.

Teams track: Microsoft Teams integration
Outlook track: Email, Calendar, Meetings, Bookings, and To Do

A phased rollout usually works best. Many teams start with one of these options:

Teams first if collaboration in chats and channels is the main priority.
Outlook first if working with emails, meetings, and calendars is the main priority.
Both in parallel if your admins are aligned and you want a broader launch.

The Microsoft login is not one single switch for everything. Teams and Outlook-related features use separate enterprise app/client setups, so plan approvals according to the features you want to launch.

Want to now more about the Microsoft terms and technical requirements? Look here

3. Teams rollout

Work together with your Microsoft administrator to allow Microsoft sign-in for the Teams feature set. Without this step, users cannot authenticate with their Microsoft work account for Teams-related functionality.

Ask your Microsoft admin to approve the required Microsoft 365 access for the Teams feature set.
Use the detailed guidance on Approve Microsoft Access.
If your organization want to restricts sign-in to selected users or groups, continuously align these groups with the rollout

Result: users can sign in to the Teams-related parts within Jira.

3.2 Coordinate the rollout of the Teams app

After sign-in is enabled, coordinate the actual Microsoft Teams app deployment with your Microsoft administrator or Teams administrator.

Enable and deploy the Microsoft Teams app in the tenant. Deployment Microsoft Teams app
We recommend to install the app for all Jira users so they can get personal notifications.
Additionally, Channel-related features require the app to be installed in the corresponding Teams.

Important: enabling Microsoft login (step 3.1) alone is not enough for the full Teams experience. The Teams app rollout is what makes the in-Teams experience available to users outside of Jira.

4. Outlook rollout

Work together with your Microsoft administrator to approve the Outlook-related Microsoft 365 access needed for Outlook applications such as Email, Calendar, Meetings, Bookings, and To Do.

Deployment Microsoft Teams app

Ask your Microsoft admin to approve the required Microsoft 365 access for the Outlook feature set.
Use the detailed guidance on Approve Microsoft Access
If your organization want to restricts sign-in to selected users or groups, continuously align these groups with the rollout

Result: users can sign in to the Outlook-related parts within Jira.

4.2 Coordinate the rollout of the Outlook add-in

Once the login is approved, coordinate deployment of the Outlook add-in with your Microsoft administrator.

Roll out the add-in to the target users or groups Deployment Outlook add-in | [inlineExtension]Office add in

If your first rollout focuses on email-based work, combine the Outlook add-in launch with a few concrete user examples such as creating Jira issues from emails or linking email conversations to work items.

5. Explore use cases for inspiration

Once the technical foundation is in place, review the available use cases to decide how you want to introduce the app in day-to-day work.

Getting started: Use cases

Use cases help you move from “the app is installed” to “this is how our teams will actually use it”.
They are especially useful for deciding which features to activate first and how to present the value to end users.
They also help identify whether your first scenario is more Teams-centric, Outlook-centric, or a combination of both.

6. Prepare a rollout presentation for key users

Before broad rollout, prepare a short enablement session for key users, team leads, or champions. This helps create early adoption and reduces support questions.

Show the selected feature set and explain why these features were chosen first.
Demonstrate the main user flows in Teams and/or Outlook.
Clarify what users need to do the first time, especially Microsoft sign-in.
Collect early feedback from key users before expanding the rollout.

A simple pilot with a short presentation and a small champion group usually leads to faster adoption, better feedback, and a smoother company-wide rollout.

Useful reference pages