An Azure service for ingesting, preparing, and transforming data at scale.
@Saurabh Sharma - Thanks for the followup. I didnt try this since I decided not to use ADF.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have setup an Azure SSIS IR on my trial subscription. I am trying to setup a pipeline to execute my SSIS package on a schedule i n the data factory.
I am following the below link for the setup. https://learn.microsoft.com/en-us/azure/data-factory/how-to-schedule-azure-ssis-integration-runtime
I run into an error when i try to debug the pipeline.
{"error":{"code":"AuthorizationFailed","message":"The client 'xxx' with object id 'xxx' does not have authorization to perform action 'Microsoft.DataFactory/factories/integrationruntimes/start/action' over scope '/subscriptions/{subscription id}/resourcegroups/xxxx/providers/Microsoft.DataFactory/factories/solverdatafactory/integrationruntimes/xxxx' or the scope is invalid. If access was recently granted, please refresh your credentials."}}
I have assigned roles - contributor and data factory contributor to my user for the data factory.
additionally, the IR also takes ages to restart. I am using a 3rd party SSIS powerpack to user a REST API connector to pull data from an API.
SO first thing is I need the pipeline to work and also the IR to restart within a practical timeframe or esle the ADF is basically not helpful if it takes hours for the IR to restart . This is beacuse IR is very expensive and we cant have to running all the time.
An Azure service for ingesting, preparing, and transforming data at scale.
@Saurabh Sharma - Thanks for the followup. I didnt try this since I decided not to use ADF.
@Anuj Shrestha Thanks for using Microsoft Q&A !!
As per the error it looks like permissions issue and you need to provide managed identity of your data factory a contributor role to itself as directed in the documented ( please check step 5).
Please can you check the permissions again if you haven't done that and try to debug the pipeline.