Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA external access via Azure Application Proxy

Hello All,


We plan to expose Jira externally using Azure Application Proxy so some project managers can access the internal site without the need for a VPN. Azure Application Proxy is deployed and working great for other websites with the exception of Jira. The client has provided me with the URL but externally when accessing the website I can the error 'page can’t be found'. When I try to access the website internally the website I get prompted to login. Has anyone successfully setup Jira and what setup was used to achieve it? 


I am using v8.138 Jira. 


1 answer

0 votes

Welcome to the Atlassian Community!

This suggests that the proxy is not set up to talk to the internal site properly.

I have setup an enterprise application in Azure created a group associated with access to the application (which is basically everyone in the organization) and then configure the application proxy. Single sign-on (password-based and Sign-on) and I added the following URL

I'm not familiar about exactly how AWS does the proxy in this way, but it does look a bit wrong to me.

One of the things a proxy does is locate a service in a different URL, and I think this is what you are doing here with your AWS stuff.

The setup I have at home is Jira on server-1, Apache on server-2, other things I want to use from outside my home on server-3 and 4, and so on.  My router forwarding traffic from outside my home to Apache.  So it looks like Apache is serving up my home web-site.  The proxy is carrying traffic between HTTP://server-1:8080 and HTTPS://

I suspect that's what you need to be doing - when your people land on HTTP://, your AWS proxy should be proxying back to whatever the URL is of the Jira server internally.

Suggest an answer

Log in or Sign up to answer