Closed balintbako closed 5 years ago
@balintbako Thanks for the feedback! We are currently investigating and will update you shortly.
@balintbako Thank you for reaching out! Self-hosted IR can be shared with data factories (v2) within same tenant. It cannot be shared across different tenants due to Service Identity limitation that we use for auth. SSIS IR cannot be shared across data factories and its scope is only within the same factory.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
@balintbako Would you please provide us the reason to share IR across tenants? Is there any specific scenario/requirement? We will be glad to pass your input to the internal team to take a deep dive.
Thank you for confirming this!
It is a Dev and Prod system which will be linked to different AADs but connecting to the same on-premise data source.
Yes, there is a valid scenario. Take for example the following. You have an infrastructure per country hosting multiple DataWarehouse databases per Country Client. So this Country A can have Client 1 and Client N databases in this Country A VM. Now you need to give access to these DBs though DataFactory to each different Client Azure Tenant by using the same Integration Runtime. Currently, you need each different VM hosting one Integration Runtime (used as gateway) and pointing via SQL to the central Country A VM. By doing this you increase costs for each Client that wants data factory access to its own tenant!
Hi,
Can we share the self-hosted SSIS IR between 2 Azure tenants?
Regards, Balint
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.