Hi, I've configured Data Factory SSIS IR with VNet express injection. Per my understanding this will allow me to reach private endpoint enabled resources. I can for example access a private endpoint enabled with public access disabled Azure SQL Server as seen below: However, I fail to connect to an Storage Account / Azure Files that I would like to use to store SSIS packages: first I don't understand why can't I select the SSIS IR but have only the AutoResolverIntegrationRuntime available if I hit test connection I get: However, if I enable public access on the Storage Account then it works, I can connect. But what's the point of integrating SSIS into the VNet if I can't even use it, to access Azure Files behind private endpoint. What am I misssing?

Hi @AdamBudzinskiAZA-0329 , I think there is a misunderstood of the product here. You will call the SSIS IR only via the "Run SSIS package" activity and there you would specify your SSIS package location. Please have a look at the following article : ssis-azure-lift-shift-ssis-packages-overview So regarding you points: 1 - Linked services would be associated only with Azure IR (AutoResolveIntegrationRuntime is the default Azure IR that comes with ADF deployement) or Self Hosted IR 2- Is public access denied for this file storage, because default Azure IR would use public access Hope this would help

Azure Data Factory SSIS VNet integration issue

AdamBudzinskiAZA-0329 91

Hi,

I've configured Data Factory SSIS IR with VNet express injection. Per my understanding this will allow me to reach private endpoint enabled resources.

screen1

screen2

I can for example access a private endpoint enabled with public access disabled Azure SQL Server as seen below:

screen3

However, I fail to connect to an Storage Account / Azure Files that I would like to use to store SSIS packages:

screen4

first I don't understand why can't I select the SSIS IR but have only the AutoResolverIntegrationRuntime available
if I hit test connection I get:

screen5

However, if I enable public access on the Storage Account then it works, I can connect. But what's the point of integrating SSIS into the VNet if I can't even use it, to access Azure Files behind private endpoint.

What am I misssing?

PRADEEPCHEEKATLA-MSFT 90,146 Reputation points Microsoft Employee

2022-12-15T08:42:24.353+00:00

Hello @AdamBudzinskiAZA-0329 ,

Thanks for the question and using MS Q&A platform.

I don't understand why can't I select the SSIS IR but have only the AutoResolverIntegrationRuntime available

As per the official documentation - You can ignore Connect via integration runtime, since we always use your Azure-SSIS IR to fetch the access information for package stores.

This issue looks strange. For a deeper investigation and immediate assistance on this issue, if you have a support plan you may file a support ticket.

1 answer

Maatoug wassim 76 Reputation points

2022-12-15T09:00:48.763+00:00

Hi @AdamBudzinskiAZA-0329 ,

I think there is a misunderstood of the product here. You will call the SSIS IR only via the "Run SSIS package" activity and there you would specify your SSIS package location.

Please have a look at the following article : ssis-azure-lift-shift-ssis-packages-overview

So regarding you points:
1 - Linked services would be associated only with Azure IR (AutoResolveIntegrationRuntime is the default Azure IR that comes with ADF deployement) or Self Hosted IR
2- Is public access denied for this file storage, because default Azure IR would use public access

Hope this would help
Please sign in to rate this answer.
AdamBudzinskiAZA-0329 91 Reputation points

2022-12-15T09:13:32.573+00:00

@Maatoug wassim So why do I have the option to configure the data store for SSIS packages when creating the SSIS IR in first place? So you are telling me, that I need to have not only the SSIS IR runtime, but also a self-hosted to add the storage account behing a private endpoint as a linked service, and THEN SSIS can used it ? That doesn't make sense to me sorry. Why do I have to do it that way?

Maatoug wassim 76 Reputation points

2022-12-15T09:22:25.887+00:00

Can you post you SSIS IR configuration please?
You should not have to create a linked service for a file storage anyway

AdamBudzinskiAZA-0329 91 Reputation points

2022-12-15T09:27:48.127+00:00

@Maatoug wassim what configuration ? If you create the SSIS IR there's the following step to either create SSIS catalog hosted by Azure SQL DB/Managed Instance or create packages stores that are deployed into Azure Files for example:

So isn't the SSIS IR using that storage account for SSIS packages? And if I deploy the SSIS IR into a VNet why can't it then connect to the storage account? Or why would I have to create a self-hosted IR just for connecting to that storage account ? And as I said in my questions, I CAN CONNECT to any PaaS resource behind private endpoint with public access disabled when I hit test connection from within that SSIS IR.

Also, just added the Storage Account since for testing I enabled access from everything. It got added as seen below:

Also, if you look on the left there's "test connection" after I disabled public access again on the same storage account I can still connect to it from here ! Why isn't this working when I create the SSIS IR then ??
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Data Factory SSIS VNet integration issue

1 answer

Your answer