Louis_Frolio
Databricks Employee
Databricks Employee

‎05-12-2025 11:30 AM

To enable file events for the File Arrival Trigger on your Azure Databricks Workspace, ensure the following requirements and configurations are in place:
  1. Azure Managed Identity Roles: Confirm that the Azure Managed Identity used has the necessary roles assigned:
    • Storage Blob Data Contributor
    • EventGrid EventSubscription Contributor
    • Storage Queue Data Contributor (required only if Azure Databricks is expected to create storage queues for you).
  2. External Location Permissions: Verify that you are the owner of the external location or have the MANAGE privilege assigned on that external location in Unity Catalog.
  3. Unity Catalog Configuration: The workspace must have Unity Catalog enabled, and the external location should be properly configured using Unity Catalog with file events enabled as mentioned in the documentation.
  4. Storage Account Configuration:
    • Log into the Azure Data Lake Storage account linked to your external location and validate the IAM permissions for your managed identity using the connector ID or user-assigned managed identity ID obtained from the Catalog > External Locations section in Databricks.
    • Ensure that all required roles have been granted in Azure IAM.
  5. Enable File Events in External Location:
    • Navigate to Catalog > External data > External Locations, and select the external location of interest.
    • Click Edit under the kebab menu next to the "Test connection" button.
    • In Advanced Options, enable File events and choose the file event type:
      • Automatic: Allows Databricks to set up subscriptions and events for you.
      • Provided: Requires you to manually configure Azure storage queues and provide the queue URL in the corresponding field.
  6. Testing Connection: After enabling file events, wait a few minutes and then use the Test connection functionality to confirm that file events are active on the external location.
If the option to enable file events is still not visible after completing these steps, check for the following potential issues: - Managed identity permissions in Azure IAM might be incorrectly configured, even if they appear complete.
- There may be a limitation or requirement specific to your version of Unity Catalog or Azure Databricks Workspace that is causing the issue (this feature is in Public Preview).
 
Hope this helps. Cheers, Lou.
0 Kudos