For azure, you can probably limit it quite a bit (assuming this is your deployment environment) unless they'll be on call or you don't have CI/CD set up. If the latter is true, is make that your first priority. If the former is true, I'd be wary of doing this without some kind of partnership/help for the dev.
For jira or any other issue tracker, they should have the ability to read, comment on and create tickets. The first two are to help them get work items and ask questions about them. The latter are in case they run across something that is awry. Such tickets should be reviewed and prioritized appropriately.
Again this is super context dependent. A junior dev on a 5 person startup needs different permissions from a junr dev joining a 100 person engineering team.