Troubleshoot Permission Issues in Jira Cloud for Teams Integration

Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.

Summary

Users may encounter a variety of issues when integrating Jira Cloud with Microsoft Teams. These issues include permission errors, access restrictions due to organizational configurations, plugin responsiveness, notification failures, and errors stemming from Azure Active Directory (AAD)/Entra admin restrictions or configurations that prevent app integration. Identifying your internal admin and resolving organizational settings are crucial in such cases.

Common Problems

  • Non-responsive or looping 'Review Permissions' button in Microsoft Teams

  • Permission errors or access restrictions due to Azure Active Directory (AAD)/Entra configurations

  • Inability to enable notifications or use the 'Issues' tab in Teams

  • Intermittent connectivity or plugin responsiveness issues

  • Organization-based restrictions on Jira Cloud access in Teams

Solution

Resolve Integration and Permissions Issues in Microsoft Teams for Jira Cloud

Integration issues between Jira Cloud and Microsoft Teams can arise due to Azure Active Directory (AAD) restrictions, permissions misconfigurations, or Teams application cache. Common solutions include:

For Non-Responsive 'Review Permissions' Button or General Integration Issues:

  1. Sign out of the Teams application.

  2. Fully close Teams via task manager or force quit, and reopen it.

  3. Sign in to Teams again and attempt the action (e.g., enabling notifications, reviewing permissions, etc.).

  4. If the issue persists, try using the web version of Teams at https://teams.microsoft.com.

  5. Clear the Teams app or browser cache and retry.

  6. Disconnect and reconnect the Jira integration to refresh configurations.

  7. For access issues, check with your Entra/Azure administrator to ensure you are part of the approved user group for Jira Cloud.

For Permission Errors or Access Restrictions:

  • Ensure the AAD administrator has enabled the correct application ID (512b84d2-5840-45d6-8d01-5f073836d039) in your organization's Azure portal for proper integration functionality.

  • Verify app ID, user access configurations, and consent settings within AAD if integration or the 'Issues' tab doesn't work due to a login error.

  • If your organization restricts access to Jira Cloud in Teams, you may need to contact your Entra ID/Azure AD administrator to adjust permissions. To identify the appropriate administrator, reach out internally within your organization, as Atlassian does not maintain this information.

  • If you encounter access restrictions or error messages indicating that your organization has limited access, contact your IT administrator or Entra/Azure administrator to verify permissions. You can also refer to internal organizational documentation for further information.

Addressing Permission Issues Related to Azure/Entra Admin Settings

If you encounter errors indicating restricted permissions or the need for admin approval, these typically stem from Azure configurations, such as restrictions on app consent. You will need to contact your internal IT or Azure/Entra administrator for assistance. Atlassian cannot identify your internal admin, but your organization’s IT team should be able to help. Refer to Microsoft's documentation for guidance on the admin consent workflow: Grant tenant-wide admin consent to an application - Microsoft Entra ID

Additional Troubleshooting Steps

  • Try alternative platforms: If issues persist on the desktop app, use the Teams web version: https://teams.microsoft.com.

  • Refresh the Jira integration: Disconnect and reconnect the Jira Cloud integration in Teams to ensure a clean configuration.

  • Check for organization-based restrictions: Some organizations may restrict access to certain apps or integrations. Always verify with your IT or Entra/Azure admin if you suspect this is the case.

Updated on January 12, 2026

Still need help?

The Atlassian Community is here for you.