@JB
Thanks for the update on the troubleshooting progress. I'll help clarify some of the points you've checked and provide guidance on the remaining ones.
IR credential sync: Good to hear that you've verified the SHIRs as synced under Credential status. This should not be the cause of the issue.
Daily auto-update schedule: You've confirmed that the schedule is set correctly, so this is unlikely to be the cause.
Azure Data Factory version: The version you found in the JSON code, "2018-06-01", refers to the API version of your Azure Data Factory instance. This is not the same as the version of the Azure Data Factory service itself. The API version is used to specify the version of the Azure Data Factory REST API that your instance is compatible with.
The Azure Data Factory service is automatically updated by Microsoft, and you don't need to worry about updating it manually. However, it's possible that your instance is not using the latest features or fixes if the API version is outdated.
To check the actual version of the Azure Data Factory service, you can follow these steps:
- Go to the Azure portal and navigate to your Azure Data Factory resource.
- Click on "Author & Monitor".
- Click on the three dots (ellipsis) next to the "Author & Monitor" button.
- Click on "About".
- Look for the "Version" information.
- Firewall or network restrictions: It's great that you're working with your internal IT to verify the firewall and network settings. Please ensure that the necessary ports and URLs are allowed, as mentioned earlier.
- Azure Data Factory logs: You don't need to remote into your SHIRs to find logs. Instead, you can check the Azure Monitor logs for your Azure Data Factory resource. To do this:
- Go to the Azure portal and navigate to your Azure Data Factory resource.
- Click on "Monitor".
- Click on "Logs".
- Select the log category and time range you're interested in.
- Look for any errors or warnings related to the auto-update process.
Additionally, you may want to consider checking the Azure Data Factory resource's activity log, as I mentioned earlier, to see if there are any errors or warnings related to the integration runtime