Bridging the Impossible: Connecting Jira On-Prem to Power Automate & Copilot Studio — The Solution Nobody Built Until Now"
Connect Jira On-Premises to Power Automate & Copilot Studio
The complete enterprise solution nobody else has built — 45-action Custom Connector + On-Premises Gateway + AI Agent that talks to your Jira Data Center in natural language
In This Post
A Problem Thousands Face — Nobody Solved
Microsoft's built-in Jira connector only works with Jira Cloud. Thousands of enterprises running Jira Server or Data Center on-premises are stuck — the native connector fails with 401 errors because it expects Jira Cloud's auth format. The community forums are full of unanswered questions about this exact problem.
Existing workarounds are either raw HTTP actions (tedious, no reusable connector) or paid middleware like CData ($$$). Nobody has published a complete, free, production-ready custom connector with gateway integration, flow wrappers, and an AI agent.
Until now.
The Architecture
Copilot Studio throws "Setting 'gateway' cannot be null" when calling custom connectors with on-prem gateway. The fix: wrap each action in a Power Automate flow, then add the FLOW to the agent. This workaround isn't documented anywhere — I discovered it during development.
Authentication — What Actually Works
Basic Auth + PAT
Username + Personal Access Token as password. Works everywhere.
Basic Auth + Password
Legacy method. Works but Atlassian discourages it.
Bearer Token
Needs API Key auth — not available in all environments.
OAuth 1.0a
Jira DC uses 1.0a. Power Automate only supports 2.0.
SSO/M365 login? Doesn't affect the connector. SSO is for browser login. The REST API accepts Basic auth + PAT separately — two different doors into Jira. You enter the PAT once when creating the connection. No second login, no popups, forever.
The Jira Simulator — Test Without Risk
I built a complete Jira Data Center simulator that mimics the real REST API v2 — same endpoints, same auth, same response format. 3 projects, 12 seeded issues, real Atlassian-style dashboard with Kanban board.
npm install
npm start
# Server prints your IP address — use THAT in the connector, never localhostOn-Premises Data Gateway
Download from
aka.ms/on-premises-data-gateway-installerInstall on the machine running Jira (or one that can reach it)
Sign in with your Power Platform account
Verify Online in Power Automate → Data → Gateways
The Custom Connector — 45 Actions
Import the OpenAPI spec, set host to your IP, scheme to HTTP, check the gateway box, set Basic auth. That's it.
The connector configured with the real IP address (10.0.0.4:8080), HTTP scheme, and on-premises gateway checkbox enabled.
| Category | Actions Included |
|---|---|
| Issues | Search, Create, Get, Update, Delete, Assign, Bulk Create |
| Comments | Get, Add, Update, Delete |
| Transitions | Get Available, Transition Issue |
| Worklogs | Get, Add |
| Projects | List, Get, Components, Versions, Statuses |
| Users | Current User, Get, Search, Assignable |
| Agile | Boards, Sprints, Sprint Issues, Backlog, Epic Issues |
| Metadata | Priorities, Statuses, Issue Types, Fields, Filters, Dashboards |
It Works — Screenshots Don't Lie
Manual trigger → Get all fields → Create issue (INFRA, Bug, High priority, assigned to Kerolos). Completed in 0 seconds.
INFRA-111 created successfully — Bug, To Do, High priority, Kerolos Admin. The gateway host 10.0.0.4:8080 visible in the banner.
SharePoint List → Jira Issue — Automatic
This is the real power — a SharePoint list triggers a flow that creates Jira issues automatically. When someone adds a row to your SharePoint list, a Jira ticket appears instantly.
When a SharePoint list item is created → Get current user → Create Jira issue (SEC project, Task type, Low priority). Output: SEC-57 created at /rest/api/2/issue/SEC-57.
SEC-57 — "test from power automate spo list to on prem jira server 2026". Status: To Do, Priority: Low, Reporter: Kerolos Admin. Created 4/12/2026. Full detail view with comments and attachment sections.
A non-technical user adds a row in SharePoint. Behind the scenes, a flow fires, calls the custom connector through the gateway, and creates a real Jira ticket on the on-prem server. No code, no VPN, no middleware fees.
Flow Wrappers — The Secret Sauce for Copilot Studio
Copilot Studio can't call custom connectors with on-prem gateway directly. The solution: wrap each Jira action in a Power Automate flow, then add the FLOW to the agent.
Plus Add Comment and Transition Issue flows — 5 total. Each tested and working.
Copilot Studio Agent — Natural Language to Jira
Add the 5 flows to the agent, paste the system prompt, turn on generative orchestration. Users chat in Teams and the agent translates to JQL + API calls automatically.
INFRA-100 — Firewall firmware (In Progress, Highest)
Bug | High | Want to assign?
Switch to Real Jira — 3 Changes
| Setting | Simulator | Real Jira |
|---|---|---|
| Host | 10.0.0.4:8080 | jira.yourcompany.com |
| Scheme | HTTP | HTTPS |
| Password | test | Your real Jira PAT |
Use HTTPS and your actual Jira URL (e.g. https://jira.yourcompany.com). The connector, flows, agent, and instructions all stay exactly the same — only the host, scheme, and PAT change. The 45 API actions match the real Atlassian Jira Data Center REST API v2 specification.
Download the Complete Package
Jira simulator + OpenAPI connector spec + deployment scripts + full documentation
Download Complete Package
Comments
Post a Comment