I did a quick check, and it is just spinning up the regular scheduling dialog for Agent. So you could do this on a local instance on your own machine and use the script button to see what it creates. You may also have to check the jobs it creates.
But then you will face the next problem: there is no Agent in Azure SQL Database. But there are Elastic jobs, which fills the same role (and may add a little more to your Azure bill.)