locked
Connecting Web Apps to API across Subscriptions RRS feed

  • Question

  • Hi

    Our customer has a series of Web Apps - incl. App1 - built in App Service - under Subscription SubA.

    There is an integration service API (Svc1) - running on an IaaS Windows VM (vm1), on Vnet1 - under Subscription SubB - same Region as SubA

    App1 needs to consume Svc1

    How to allow this Outbound access??

    From reading, it looks like "VNet Integration" is not a runner due to there being 2 different subscriptions

    Other possible seems to be "Hybrid connections" - but this seems more oriented towards connecting to on-premise resources, e.g. backend DB. Thats not the use case here - we need to allow App1 to consume Svc1, programmatically.

    Any ideas please?

    (PS my background is infrastructure, not apps :-)

    Tks

    Padraig

    Thursday, April 9, 2020 1:50 PM

All replies

  • This forum is for C# specific questions only. Your question seems related to Azure or network configuration. For Azure please post your questions over at Microsoft Q&A. For general networking questions please post in TechNet.

    Michael Taylor http://www.michaeltaylorp3.net

    Thursday, April 9, 2020 1:52 PM
  • Hi padraigd,

    You can set up VNet peering across two different subscriptions. For more information, see https://docs.microsoft.com/en-us/azure/virtual-network/create-peering-different-subscriptions.

    Hope this helps.


    Thanks in advance, Ryan

    Thursday, April 9, 2020 4:25 PM
  • Hi Ryan

    Yes we are aware of VNet peering to connect VNets. What we need here is an outbound connection from Azure App Service, where there is no VNet as such - to a VNet in a different subscription. Is it possible to:

    a) Use VNet Integration to connect the app to a VNet in the  same SubA

    b) peer from that VNet to a VNet in the other SubB

    c) From the app, access the service on the VNet in SubB via the peered connection?

    Maybe thats what you're recommending here? Can it be done?

    Thanks

    Padraig

    Thursday, April 9, 2020 8:32 PM
  • Hi Ryan

    Yes we are aware of VNet peering to connect VNets. What we need here is an outbound connection from Azure App Service, where there is no VNet as such - to a VNet in a different subscription. Is it possible to:

    a) Use VNet Integration to connect the app to a VNet in the  same SubA

    b) peer from that VNet to a VNet in the other SubB

    c) From the app, access the service on the VNet in SubB via the peered connection?

    Maybe thats what you're recommending here? Can it be done?

    Thanks

    Padraig

    Hi Padraig, see my response over at https://docs.microsoft.com/answers/answers/22626/view.html

    Thanks in advance, Ryan

    Monday, April 13, 2020 9:03 PM