Static ip address for whitelists

Category: azure scheduler

Question

Christian Trolle Mikkelse on Thu, 21 Dec 2017 11:09:41


Hi

Ive just setup 7 jobs on the Azure Scheduler service, one collection on Free and one on paid.

We are in a transition and want to use the Scheduler to call our remote on premise endpoints.

For this we normally take the static ip address from our Azure VM's and whitelist them, but i cant find an ip address or assign an ip address to the Scheduler service as far as i can tell.

Can you help me?

**Update**

I can find posts which claim that this is not possible. So im looking into setting up a proxy or creating a hybrid network instead. This seems quite over the top, and expensive, when all we need is an ip :/. Now we have to do a rather complex setup just to post to an endpoint on a schedule.... 

Kind regards

Christian Trolle Mikkelsen




Replies

Kevin Lam _ Microsoft on Fri, 22 Dec 2017 03:50:48


As an alternative you can use Azure Logic Apps which has the same scheduling capabilities as Azure Scheduler plus gives you access to over 200 connectors including some that connect to on-premises resources.  Azure Logic Apps has static IPs which are listed here https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-limits-and-config#configuration-ip-addresses.

Christian Trolle Mikkelse on Fri, 22 Dec 2017 07:32:08


Hi Kevin

Thank you for the response.

Using a shared IP in our whitelist is not an option though it is better to limit it to EU north for ex. But it would have a hard time standing a security check, since any logic app from Azure would have those ips. However i must dig into that.

Our own ip would be better to so that we cloud limit access as much as possible.

Do you know of any other options?


Christian Trolle Mikkelse on Fri, 22 Dec 2017 09:07:23


Hi Kevin

Is it possible to force the scheduler's ip address to originate from our own Azure network if we setup an ipsec vpn to our on premise servers?

Kind regards

Christian

Femisulu on Fri, 16 Feb 2018 02:53:43


Hi Christian - apologies for the delayed response. Based on the implementation complexity you called out and given the fact that this may not be a supported implementation, I would strongly recommend that we engage Azure support via the Azure portal (ref: "Help + Support" blade) to see if we can get an expert to review your scenario and provide some guidance. I am able to set you up with a one-time free Azure support entitlement for this specific issue. If you would like a one-time free support, please send mail to AzCommunity@Microsoft.com with your subscription ID and I can enable free support for you on the back end. Also include the link to this MSDN post for context.